Before implementing Odoo, an 8-branch F&B chain in Ho Chi Minh City and neighboring provinces still updated menu prices manually: area managers called or messaged branches on Zalo every time there was a promotion or an ingredient-cost change. At one point, 3 branches were selling the same dish at 3 different prices, and a single promotion took nearly 2 days to roll out across the whole chain.
This is a case study on how Sonix helped this chain sync its menu and pricing in real time across all 8 branches with Odoo, right as the implementation team was applying lessons learned from Q2 projects to the next round of F&B rollouts.

Table of Contents
💡 Insight: For multi-branch F&B chains, even a few hours of price or menu mismatch can mean lost revenue or a poor customer experience, especially during short-term promotions. Real-time data sync across branches is no longer a “nice-to-have” feature it’s a basic operating requirement once a chain grows past 4-5 outlets.
SITUATION BEFORE IMPLEMENTATION
The problem before Odoo: one price list per branch
The chain ran on a model where each branch kept its own Excel price list, updated by the on-site manager. Whenever marketing launched a new promotion or the central kitchen adjusted prices due to ingredient-cost swings, the information had to pass through several layers before reaching whoever was operating the POS at each branch.
Three main bottlenecks made this increasingly hard to control as the chain grew from 4 to 8 branches: there was no single “source of truth” for pricing, no one could track which branches had updated and which hadn’t, and dishes discontinued at the central warehouse still showed as available on some branches’ POS for hours.
8
Branches that needed to sync menu and pricing at once
~2 days
Time for a promotion to roll out across the whole system (pre-Odoo)
3
Different prices once recorded for the same dish at the same time
IMPLEMENTATION SOLUTION
The solution: one central menu, synced to 8 branches
Sonix implemented Odoo Point of Sale together with Inventory and Sales on a multi-branch model, built around a single product catalog and price list managed centrally:
Centrally managed menu and pricing
Every dish, combo, and price list is set up once at headquarters. Each branch is registered in the POS system as its own outlet, but all of them pull data from the same source.
Real-time sync whenever devices are online
When headquarters updates a price or toggles a menu item, the change pushes out to every outlet as soon as the device is online, instead of waiting for branch staff to update it manually.
Ingredient stock linked to menu-item status
A dish that’s out of stock at the central or branch warehouse is automatically hidden from the corresponding POS, cutting down on staff taking orders for items that are no longer available.
RESULTS AFTER GO-LIVE
Results after go-live
After the initial stabilization period, the chain saw the clearest change in how fast promotions could roll out and how accurate pricing stayed across branches.
| Metric | Before Odoo | After Odoo |
|---|---|---|
| Time to roll out a promotion system-wide | ~2 days | Near-instant once devices are online |
| Price mismatches between branches | Regularly recorded with every price change | No longer occurring since all branches share one source price list |
| Orders taken for out-of-stock items | Recurred periodically at branches farther from the central warehouse | Noticeably reduced thanks to items auto-hiding when linked stock runs out |
LESSONS LEARNED
Lessons for F&B chains considering Odoo
For multi-branch F&B chains, the hardest part isn’t configuring Odoo it’s standardizing the menu catalog and item codes before feeding them into the central system, since each branch having its own names and codes for the same items is extremely common. Spending enough time on this data review and consolidation step before go-live avoids having to restructure data after the system is already running across every branch. You can also check out Sonix’s Odoo implementation services for the F&B industry.
Training POS staff at each branch should also happen in small rounds alongside the configuration process, rather than being crammed into the final week before go-live so the team has enough time to get comfortable before the new system officially replaces the old way of working.
KEY TAKEAWAYS
| Key point | What it means for your business |
|---|---|
| One central menu and price list for all 8 branches | Eliminates the situation where each branch charges a different price for the same item. |
| Real-time sync whenever devices are online | Promotions and price changes take effect almost instantly instead of taking days. |
| Menu directly linked to ingredient stock | Out-of-stock items auto-hide from the POS, reducing bad orders and poor customer experience. |
| Standardizing the product catalog before go-live is the decisive step | Helps avoid having to restructure data after the system is already live. |
Is your F&B chain facing a similar problem?
Book a 30-minute discovery call so Sonix can assess the current state of your multi-branch menu, pricing, and inventory, and propose a real-time sync roadmap that fits your current scale.
Hundreds of businesses using Odoo in Vietnam have started their journey this way.
Sonix – Our customers’ success is our joy.

Leave us your comment