If you operate on more than one aggregator, there is a number you almost certainly do not know: how much margin you are leaking every week because your menus are out of sync.
We have watched this number for four restaurant groups across Qatar and Pakistan. It is rarely zero. For a mid-size group with 140 SKUs and five aggregator storefronts, we have seen monthly leakage in the low six figures of PKR — not from missed orders, but from items sold at yesterday's prices on a platform the finance team assumed had been updated on Monday.
What menu drift actually is
Menu drift is the slow divergence between the master catalogue a restaurant group believes it has, and the five versions of that catalogue actually live on aggregator storefronts. It happens in four ways, and they compound:
- A price changes in HQ. Ops pushes it to four aggregators. Forgets the fifth.
- A new modifier group is added. Aggregator A supports it; aggregator B silently drops the modifier and sells the item flat.
- A photo is updated on the website. Aggregators keep the old one for weeks.
- An item is 86'd at the store for the night. The POS knows. The aggregators keep selling it.
The cost is not theoretical
Every one of these has a financial shape. Wrong price sold — margin leaks. Missing modifier — upsell lost. Stale photo — conversion degrades. Ghost availability — a ticket fires for an item you can't produce, customer refunds, chargeback fees, one-star review.
“We raised prices on Monday. Talabat was still selling at the old price on Friday.”
— Operations head, multi-brand group — Qatar
Why most attempts to fix it fail
The first instinct is a script — a cron job that pushes your menu to each aggregator's API once a day. This fixes the laziest form of drift (the forgotten-to-push problem) and almost nothing else. Because menu drift is not really a sync problem; it is a system-of-record problem.
If the master menu itself is a spreadsheet — different files for finance, ops, and kitchen — no amount of sync will help. You end up syncing yesterday's disagreement across five platforms.
The real fix is upstream
One catalogue, one place, one team of truth. Prices, modifiers, availability rules, photos, dietary tags — all edited in one interface and propagated from there. This is what HornbillOS calls Unified Menu Control.
How HornbillOS approaches it
- The HornbillOS catalogue is the canonical source. Every aggregator storefront is an observed projection of it.
- When an operator edits an item, modifier, or availability rule, the change is queued for every aggregator it's published to — with a visible sync status per row.
- Availability changes (the 86'd item) propagate in seconds; full menu changes respect each aggregator's API rate limits and retry automatically.
- An admin can always see: last attempted, last successful, and any pending conflict — per aggregator, per SKU.
But this is not only an aggregator story
Here is the part we want to be direct about: Unified Menu Control is one module of HornbillOS. It is valuable on its own, and for many operators it is the doorway — the module they adopt first because the pain is immediate and quantifiable. But the reason they stay is everything around it.
The master catalogue that drives aggregator sync is the same catalogue that drives your branded customer ordering website, your TV menu boards, your POS punch-order screen, your recipe costing, and your inventory-linked availability rules. A price update in HornbillOS is not syncing to aggregators and ignoring everyone else — it is one edit that updates every surface of your business.
That is what makes the difference between a sync tool and an operating system. A sync tool can get Talabat and Keeta to agree on a price. An operating system makes sure Talabat, Keeta, your kitchen, your website, your accountant, and your TV screens all agree on the same price — without anyone re-entering the data.
A simple test for your group
Ask your operations manager this question: "If I change the price of our top-selling item by 5 QAR right now, how many systems have to be touched before every channel sells at the new price?"
If the answer is a number greater than one, you are operating on margin-leaking infrastructure. The fix is not another aggregator integration — it's a catalogue you can trust.