Multi-Branch Restaurant Menu Pricing: Channels, Scheduling and Controlled Publishing
Manage multi-branch menu pricing and availability with scoped exceptions, approvals, version history, scheduled publishing and controlled rollback.
- Bahram Davoodi
Prices and availability do not need to be identical across every restaurant branch and channel. Local cost, kitchen capacity, packaging and service model can justify differences, but unmanaged exceptions create wrong prices and sales of unavailable items.
Base rule and exceptions
Define a central base price and availability rule. Add only necessary branch, channel, time or campaign exceptions, each with reason, scope, start and end time, approver and owner.
Rule priority
Document which level wins when rules overlap: base catalogue, branch, channel, time window or campaign. Clear priority prevents two active rules from producing an unexpected final price.
Separate the components
- Base price
- Branch or channel override
- Discount or campaign
- Packaging or surcharge
- Tax and final display
Keeping them separate improves reporting, customer explanation and accounting review.
Availability and scheduling
An item may be available in one branch, unavailable in another or sold only at selected hours. The same status should reach POS, website, QR menu and online ordering. Seasonal prices and weekend offers need defined start and end times.
Approval, preview and rollback
Proposal, approval and publication should be separated where possible and retained in user history. Before release, preview changed products, branches, channels, final prices and availability. Each release needs a version and effective date; rollback must restore the previous version without deleting history.
Publication test
- Check base price, overrides, discounts and surcharges separately.
- Check tax and final customer display.
- Compare POS, website, digital menu and online ordering with the approved version.
- Confirm unavailable or out-of-hours items cannot be ordered.
- Test rollback.
Practical scenario
A product has different dining-room and takeaway prices in the central branch, while a second branch uses the base price. A weekend change receives start and end times, second-person approval and a preview of all four branch-channel combinations.
Measure results
Compare sales, discounts, voids, contribution and complaints before and after the change. The goal is to measure demand, operations and guest experience, not only price.
How Lonio can help
Depending on the confirmed configuration, Lonio can support central catalogue data, scoped rules, user history and reporting. Priority logic, tax behaviour, publication targets and rollback must be validated in the live setup.
Conclusion
Central management with controlled exceptions balances brand consistency and local needs.
Frequently asked questions
Must every branch and channel use the same price?
No. Exceptions can be valid, but they need a reason, scope, effective period, owner and separate reporting.
What happens when several pricing rules are active?
The priority of base, branch, channel, time and campaign rules must be defined and tested in advance.
Why is menu versioning important?
It supports traceability, comparison of published prices and controlled rollback.
What should be tested before publishing?
Final price, tax display, timing, availability and consistency across POS, website, digital menu and online ordering.
