Aggregator Control.
Bidirectional. By design.
Menu, prices, timings, preparation time, store status, orders, receipts, and customer identity — in lockstep across every aggregator you sell on. One system, one source of truth, one place to operate from.
Aggregator Control · Deep dive
Run every aggregator from one system.
HornbillOS is the operating system for your whole food business — kitchen, P&L, HR, supply chain. Aggregator Control is one module of many— and for multi-aggregator operators, it’s often the one that pays for the rest within a week.
Source of truth
HornbillOS
Menu · Prices · Timings · Status
Keeta
Qatar
Talabat
Qatar · GCC
Snoonu
Qatar
Rafeeq
Qatar
Foodpanda
Pakistan · SEA
Pillar 01
Unified Menu Control
One catalogue. Every aggregator. Update a price, description, modifier, photo, or category — HornbillOS pushes it to every storefront you sell on. No portal-hopping, no drift.
- Menu category sync — structure mirrors your master catalogue
- Product detail sync — name, price, description, modifiers, images
- Product availability sync — 86 an item, hidden everywhere in seconds
“We raised prices on Monday. Talabat was still selling at the old price on Friday.”
— The problem this pillar removes
Pillar 02
Storefront Operations
Open and close your storefronts, set business hours, and publish live prep time — across every platform from one switch. The kitchen finally drives the aggregators, not the other way around.
- Store timing sync — business hours, holidays, branch closures
- Preparation time sync — live pacing, not yesterday’s average
- Store status sync — open, busy, paused, closed — all platforms aligned
“Branch closed at 11. Foodpanda still took orders until 11:40. Customers called the store.”
— The problem this pillar removes
Pillar 03
Live Order Lifecycle
Every order — received, accepted, preparing, ready, picked up — flows both ways in real time. A single receipt format prints every aggregator's order on any thermal printer. No lost tickets, no manual status toggling.
- Full-lifecycle order sync — bidirectional status callbacks
- Universal receipt printing — one format, every aggregator, any printer
- Automatic retry + HMAC-signed webhooks for reliability
“The driver arrived and the kitchen ticket had never printed.”
— The problem this pillar removes
Pillar 04
Customer Intelligence
Aggregators hoard the customer. HornbillOS surfaces them. Name, phone, address, and order history flow into your CRM — so you can resolve disputes, remarket directly, and build loyalty the platform can’t switch off.
- Customer information sync — identity flows into your CRM
- Repeat-order attribution across aggregator, direct, and walk-in
- Per-region privacy posture — disclosed, operator-controlled
“Three complaints this week. We had no way to call the customer back.”
— The problem this pillar removes
Coverage matrix
10 sync surfaces · 5 aggregators
| Sync surface | Keeta | Talabat | Snoonu | Rafeeq | Foodpanda |
|---|---|---|---|---|---|
| Menu category sync | |||||
| Product detail sync | |||||
| Product availability sync | |||||
| Store timing sync | |||||
| Preparation time sync | |||||
| Store status sync | |||||
| Live order lifecycle | |||||
| Customer information sync | |||||
| Universal receipt printing |
This is one module of twelve
Aggregator Control is the door. The operating system is what’s inside.
Most operators adopt HornbillOS for aggregator sync. What keeps them is the rest of the platform — production queue, inventory, P&L, payroll, the storefront, vendor ledgers, kitchen display, and the CRM that finally makes repeat behaviour visible.
Operator scenarios
The same shift. Before HornbillOS and after.
Every one of these scenarios is drawn from the same restaurant groups that built HornbillOS — Jouzu, Chicken Express, Uncle Tetsu, ProGreen, ProPasta.
11:47 PM — close of service
Before
A manager closes the kitchen on the POS. Talabat is still taking orders for another 40 minutes. Drivers arrive to locked doors; customers file complaints.
After
One toggle in HornbillOS. Keeta, Talabat, Snoonu, Rafeeq, and Foodpanda all switch to closed within seconds. No phone calls, no missed tickets, no 1-star reviews for something you never saw.
Monday — menu repricing
Before
Finance approves new pricing. Ops opens five aggregator portals and reprices 140 items by hand. By Thursday, three platforms still show old prices and one SKU is missing a modifier group.
After
Update the master catalogue once in HornbillOS. Prices, descriptions, modifier groups, and photos push to every aggregator automatically — with a visible sync status per row.
Friday dinner rush — driver arrives for order #4821
Before
The ticket never printed. The order exists on Foodpanda's dashboard but got stuck on an old tablet. Customer complains, chargeback fee lands Tuesday.
After
Every aggregator order prints on the kitchen's existing thermal printer in one unified format. Status callbacks flow back to the aggregator automatically — accepted, preparing, ready, picked up.
Next quarter — loyalty launch
Before
You want to re-engage aggregator customers with a WhatsApp campaign. But the customer data lives inside each aggregator's app. You own the orders; you don't own the relationships.
After
HornbillOS surfaces the customer behind every aggregator order into your CRM — name, phone, address, repeat behaviour. Dispute resolution, loyalty enrolment, and direct remarketing become possible for the first time.
Reliability, not vibes
Built for 11 PM — when aggregator APIs misbehave.
Aggregator integrations aren’t a feature checkbox — they’re infrastructure. HornbillOS is engineered to behave correctly when things fail.
HMAC-signed webhooks
Every inbound and outbound call is cryptographically verified. Keys scoped per aggregator, per tenant.
Durable queues + retries
Sync actions survive API outages and automatically retry with exponential backoff. Nothing disappears silently.
Live status per row
Every menu item, timing rule, and store status row shows last-attempted and last-successful timestamps.
Also integrated
Last-mile delivery is a separate problem. We cover that too.
Aggregators bring you the order. For the drop, our direct channel orders can dispatch through regional logistics partners — rider assignment, status tracking, and proof-of-delivery logging, all inside the OPS Panel.
PandaGo
Pakistan
Bykea
Pakistan
inDrive
Pakistan
Rafeeq Delivery
Qatar
Snoonu Delivery
Qatar
FAQ
Operator questions, honest answers.
What happens when an aggregator's API goes down?+
Our webhook ingress is HMAC-signed and backed by durable queues. Outbound sync calls retry with exponential backoff and surface a visible "sync pending" state per record in the admin panel. Orders already received continue to flow to the kitchen even if an outbound API call is degraded — nothing silently disappears.
How quickly do changes propagate?+
Typical propagation is seconds to a few seconds for status and availability, and a few minutes for bulk menu updates (bounded by each aggregator's own API rate limits). Every sync row shows the last-attempted and last-successful timestamps, so operators can see at a glance whether a change has landed.
Do we have to replace our existing POS hardware?+
No. HornbillOS runs in the browser and drives whatever thermal printer you already use (any ESC/POS-compatible model). Receipt format is normalised across every aggregator, so kitchen staff don't need to read five layouts.
Is customer data sync permitted in our region?+
Aggregator APIs vary by platform and by country. We surface customer information only where the aggregator's terms explicitly allow, and we expose per-region toggles so operators can align with local data-protection expectations. The coverage matrix on this page reflects current production support.
Can we migrate without losing order history?+
Yes. Historical orders from each aggregator can be backfilled during onboarding. Post-migration, every future order — aggregator, direct, or walk-in — lives in the same order table and contributes to the same P&L.
Is HornbillOS only for operators who use all five aggregators?+
Not at all. Aggregator Control is one module of HornbillOS; it's valuable whether you sell on one aggregator or five. What operators typically adopt HornbillOS for — and what keeps them — is the breadth of the operating system around the aggregator layer.
Aggregator Control is just the start.
Request a walkthrough of the whole operating system — Admin, OPS, Kitchen Display, Storefront, Employee Portal, and the rest.