Delivery marketplace orders without a second kitchen workflow

The tablet wall is a symptom. When each delivery marketplace brings its own screen, your kitchen is sequencing three or four queues by eye, and your reporting has three or four versions of the truth. The goal of restaurant delivery POS support is not more screens — it is one pass, one ledger, one 86 list.

One inbound path, one ticket format

Marketplace orders should arrive through an adapter and become ordinary orders inside the POS: same items, same modifiers, same tax treatment, same reporting. From the kitchen's perspective a delivery ticket differs from a dine-in ticket only in its destination and its timing pressure. Everything else should look identical, because familiarity is what keeps error rates low at 8pm.

Delivery adapters are country-gated for a reason

Which marketplaces matter depends entirely on where you trade, and each has its own commercial and technical terms. Rather than pretending every integration is available everywhere, availability is gated per country profile — check your market on the areas served pages. Where an adapter is not live, we say so rather than listing a logo.

Status pushes prevent the phone from ringing

Accepted, preparing, ready for pickup, completed — every status that a rider or customer can see is a call you do not take. The important discipline is that status comes from the kitchen's real actions, not from a manager tapping buttons to keep the marketplace happy. A "ready" push that is fifteen minutes early trains riders to arrive early and stand around, which slows your pass further.

86-ing has to be one action

When an item runs out, it must disappear from every channel at once. If your team has to mark it unavailable on three tablets, one will be missed and the next order will arrive for an item you cannot make. Centralising availability in the POS is the single highest-value part of consolidating delivery.

Sequencing against dine-in

Delivery tickets have a hard clock; dine-in tickets have a table waiting. Neither should automatically outrank the other. Put both on the same kitchen display system so the pass makes one prioritisation decision with full information, and let the expo see how many riders are already waiting.

Reconciliation is where the money is

Marketplace payouts arrive net of commission, often on a different cycle from your card settlement. If delivery orders live in a separate system, matching payouts to orders becomes a monthly spreadsheet exercise. Keeping them in the same order ledger means you can reconcile by channel without exporting anything.

Guest ordering as the owned channel

Marketplaces bring volume you do not own. A QR or link-based guest ordering channel, running through the same kitchen flow, gives you orders without commission and with the customer relationship intact. Most operators end up running both — the point is that they should not require two operational habits.