Headquarters adds a new dessert to the menu; one branch still sells at the old price, while another cannot find products in stock. While the guest expects the same brand, the experience varies from branch to branch.
In a chain restaurant, consistency carries the brand, while local flexibility keeps the branch alive. Managing both at the same time requires a clear scope and authority.
In this article, we explained the balance between central menu, branch scope, transfers, consolidated revenue, staff, campaigns, and costs.
Table of Contents
HQ-branch balance
Headquarters protects the brand standard; the branch runs daily service. If this distinction is not clear, either inconsistency or excessive bureaucracy arises.
Decision ownership must be written; it must be known where menu, price, campaign, and purchasing begin and end. Gray areas create debate.
Operational space must be left for the branch manager; carrying every small decision to headquarters kills speed. An authorization matrix provides this balance.
We also discussed a similar framework with the retail chain logic in the chain store management article.
Starting with a pilot branch when establishing balance reduces risk. Rolling out new rules to all branches at the same time makes it difficult to reverse.
Central menu
The main menu is defined at the center; recipes, portions, and visual standards are distributed from there. If a branch adds products on its own, the brand falls apart.
The menu version must be dated; which branch uses which version must be tracked. Selling at old prices is the most common deviation.
If there is a need for local products, it must be managed with a center-approved "branch add-on menu". Uncontrolled local menus disrupt reporting.
Recipe costs must be tied to a central standard; we covered the topic in the portion and recipe cost article.
Price lists can also be published centrally or regionally; branch authority should be kept limited. We explained the details in the price list management article.
Branch Scope
Not every branch has to carry the entire menu; kitchen capacity and location demand determine the scope. A narrowed menu eases operations.
Scope changes must be published from the center and reflected instantly on the branch screen. A late-reflecting menu generates wrong orders.
For branches with delivery channels open, the menu can be filtered separately. We addressed this topic in the channel management article.
Dining room layout and table capacity can also remain branch-specific. The dining room management article explains this area.
The scope matrix must be documented. Which products are active in which branch must be seen without ambiguity.
Stock Transfer
Inter-branch transfers move excess stock before it spoils. Unrecorded movement, however, disrupts the inventory count of both branches.
The transfer document must carry the product, quantity, exit and entry branches. The approval step prevents unauthorized movement.
Shipments from the central warehouse to the branch must be tracked with the same discipline. Incomplete shipments effectively reduce the menu scope.
We explained the stock control practice in the stock control article.
Waste and loss must be kept on a branch basis and should not be confused with transfers. Otherwise, losses are concealed.
Consolidated turnover
Headquarters must be able to view and compare branch turnovers on the same day. Late Excel summaries delay decision-making.
The consolidated report should include breakdowns by branch, channel, product group, and time zone. A single total hides a weak branch.
The KPI set must be defined in the same language at both the branch and chain levels. We covered this in the daily KPI set article.
Chain reports should not be locked before shift closures are completed on a branch basis. X/Z report discipline is critical here.
Anomaly alerts should be sent to the headquarters team. Sudden drops in turnover or increases in returns must be spotted early.
Staff and authority
Role definitions must be standard across the chain, and branch assignments must be local. If the same role carries different authorities in different branches, auditing becomes difficult.
We explained the setup of permissions in the user permissions article.
The branch manager should have limited authority for cancellations, discounts, and waste. Unlimited authority distorts consolidated costs.
During staff transfers, the authority profile must also be transferred or reassigned. Old branch permissions must not remain active.
Training content must be published from headquarters. Portion and menu changes must reach all branches on the same day.
Campaign management
Campaigns should be defined at headquarters and published according to branch scope. Launching a campaign when some branches lack stock creates disappointment.
Campaign costs and sales growth must be measured on a branch basis. An unsuccessful campaign should not be blindly rolled out to the entire chain.
Price and discount conflicts must be tested in advance. The overlap of two campaigns unexpectedly reduces the margin.
Channel-based campaigns must be managed separately; delivery discounts should not disrupt dine-in pricing. Channel management view the article.
Prices must automatically revert to normal at the end of the campaign. Forgotten discounts are among the most expensive operational mistakes.
Cost standards
Recipe and portion standards must be uniform across the chain. Branch deviations inflate waste and cost variances.
Waste rates should be compared by branch; outlier branches indicate training or supply issues. We covered this in the kitchen waste tracking article.
Purchasing prices can be managed via central or regional agreements. Independent branch purchasing disrupts the cost band.
The difference between theoretical consumption and branch counts is an indicator of consistency. Persistent variance points to portioning or recording issues.
Cost KPIs should be visible to the branch manager. Numbers that remain solely at the headquarters do not change behavior.
Along with your existing system
EQLEM is a solution platform and does not replace your existing ERP system. Branch operations can remain on the platform while financial consolidation stays in the current system.
Branch sales can be summarized and transferred to Mikro or Logo; double entry is eliminated. We discussed this in this article.
Connections to local servers are established via an on-prem component; the security model is evaluated separately for each branch. We explained the architecture in the on-prem agent article.
The web side is mature for restaurant chain scenarios; mobile may remain partial in certain workflows. ECFR firmware is out of scope.
The scope must be verified based on your branch count, current system version, and channel structure. Instead of a blanket commitment, your specific setup is evaluated.
Points to consider
It is not mandatory to replicate every branch identically; capacity and demand define the scope. Forcing a full menu degrades quality.
Keeping central control overly strict kills branch initiative. Set authorization limits that are clear yet practical.
Do not confuse transfers with waste; these are different documents. Confusion conceals losses.
Do not launch campaigns before completing the menu rollout; running campaigns while branch screens are outdated creates chaos. Restaurant management system read the article.
Do not roll out to the entire chain without pilot branch results. The cost of rollback is high.
Frequently asked questions
Is the same menu mandatory in every branch?
The core menu must be common; the scope can be narrowed according to capacity. Local additions are managed with central approval.
How is stock transferred between branches?
With an approved transfer document. Unrecorded transfer disrupts the count of both branches.
Do I need to abandon my current ERP?
No. EQLEM works alongside your existing system and does not touch your financial order.
How often should the consolidated report be reviewed?
A daily summary and weekly deep dive are good practice. Instant alerts should be added for anomalies.
In a chain restaurant, the brand survives on a central menu and standards, while the branch survives on daily speed. The balance is established by the authority and scope matrix.
Menu version and price list must be published from the center; branch deviation must be monitored. Selling at an old price is the most expensive inconsistency.
View transfers, waste, and revenue by branch breakdown; a single total hides weak points. The consolidated report increases decision speed.
Do not launch a campaign before stock and scope are ready; ensure the price automatically reverts upon completion. A forgotten discount exhausts the chain.
It is possible to accelerate branch operations while preserving your existing accounting order. Clarify the scope according to your chain structure.
By consulting with the EQLEM team you can clarify your chain restaurant branch management scope.