The tablet wall
A multi-brand delivery kitchen typically runs one tablet per marketplace per brand. Three brands across three platforms is nine devices, nine menus to keep in sync, nine places to 86 an item, and a person whose job during the rush is to watch all of them and retype orders into whatever the kitchen actually cooks from.
Every one of those retyping steps is an error the guest experiences and you refund. And every menu copy is a price change you will eventually forget to make in one place.
What ThaliPOS replaces it with
- One kitchen display for everything. Every channel and every brand arrives on the same screen, with the brand and channel marked on the ticket and each item routed to the station that cooks it.
- Per-brand menus from one system. Each brand has its own menu, pricing and identity, authored in one back office rather than in each platform's portal.
- Per-channel pricing. Marketplace prices can carry an uplift so commission is priced in rather than absorbed — set as a deliberate number, not a spreadsheet exercise.
- Per-channel pause. Buried on one brand or one platform? Pause that channel without touching the others.
- Automatic pause when the store is offline, so platforms stop sending orders nobody in the kitchen can see.
- Cancellations both ways. When an order is cancelled upstream, the ticket is flagged on the kitchen screen rather than silently vanishing — nothing gets cooked for nobody.
How the kitchen display works →
Own the reorder
Marketplaces are worth having for reach. They are an expensive way to serve someone who already knows your brand and orders the same thing every Thursday — and in a delivery-only business, that repeat customer is the whole economics.
A web storefront of your own carries no marketplace commission, and a QR code printed on the delivery bag is the cheapest reorder channel available to a cloud kitchen. Both run on the same menu as the marketplaces, and both land on the same kitchen screen.
Where the delivery integrations stand
One kitchen display, per-brand menus, your own storefront and QR
✓ available in pilotThe multi-brand menu structure, the shared kitchen display and the commission-free direct channels.
DoorDash · Uber Eats · Grubhub
◷ in partner certificationThe integration layer, order pipeline, menu push, per-channel pricing, fast 86 path and auto-pause are built and tested end to end against a simulated partner. Each marketplace still needs certification against live partner credentials before it can be enabled for a restaurant.
For a delivery-only operation this is the gating item, and we are not going to pretend otherwise. Ask us where certification stands before you plan around it.
Central kitchen and commissary
Operations that produce centrally and distribute to satellite sites need commissary transfers, production runs and stock moving between locations. That depends on inventory work that is in development — see the current inventory status before assuming it.