Order handling is the operating system behind every ordering channel. A website, app or marketplace can capture a basket, but the takeaway still has to accept it, translate it into kitchen work, meet a realistic promise and complete collection or delivery. This page is a hub for the controls that keep that flow reliable.
Define the order lifecycle
| Stage | Operational question | Minimum control |
|---|---|---|
| Received | Has the order reached the business? | Visible alert and a fallback if the device or integration fails |
| Accepted | Can the kitchen fulfil it at the promised time? | Capacity check, availability check and named acceptance role |
| Prepared | Is the kitchen making the correct basket? | Clear ticket, modifiers, sequence and station ownership |
| Checked | Is the order complete and correctly packed? | Pass or packing check against the original order |
| Ready | Can it be handed over without confusion? | Order reference, collection shelf or driver handover rule |
| Completed | Was it collected or delivered? | Status update and exception process for failed handover |
| Reconciled | Do order, payment and refund records agree? | Daily comparison and issue log |
Assign ownership at every stage
Problems often occur between roles rather than within them. Decide who:
- monitors incoming channels;
- accepts or rejects orders;
- changes preparation times;
- updates sold-out items;
- handles customer amendments;
- checks packing;
- hands orders to customers or drivers;
- authorises refunds and records the reason.
The same person may perform several tasks in a small takeaway, but the responsibility should still be explicit for each shift.
Use a single queue or a controlled queue rule
All demand must be visible to the kitchen, including telephone, walk-in, marketplace, direct and advance orders. If a single KDS or POS queue is not possible, use a clearly documented merge point and one person responsible for the combined sequence.
Prioritise according to:
- promised time;
- preparation lead time;
- food quality and holding limits;
- collection arrival or driver timing;
- large advance orders already planned into capacity.
Handle busy periods through capacity controls
During a peak, staff should not improvise a new rule for each channel. Agree in advance which controls are available:
- extend preparation times;
- limit collection slots;
- close distant delivery zones;
- pause complex or unavailable items;
- cap advance orders;
- pause selected channels;
- reduce promotion or sponsored placement.
Use workload, not order count alone. Ten simple collection orders may be easier than three large mixed baskets requiring several stations and drivers.
Protect order accuracy
Accuracy should be checked at several points:
- Menu setup: valid choices, clear modifiers and current availability.
- Checkout: complete basket review and clear collection or delivery details.
- Kitchen ticket: all items, notes and modifiers displayed in an actionable form.
- Pass: food checked against the ticket.
- Packing: sauces, drinks, sides and multiple bags confirmed.
- Handover: order reference and destination checked.
Record repeated error types. “Wrong order” is too broad to improve. Distinguish missing item, wrong modifier, duplicate preparation, incorrect address, late handover and platform mapping failure.
Manage amendments and cancellations by status
The sensible response depends on how far the order has progressed. Staff need to know whether an order is:
- received but not accepted;
- accepted but not started;
- in preparation;
- packed or ready;
- with a driver or already collected;
- completed but disputed.
The customer-facing policy should be clear, but it should not promise that every change is possible until a fixed number of minutes has passed. The practical cut-off depends on the item, channel and current kitchen status.
Plan advance orders separately
Advance orders are future workload, not free capacity. They should appear in prep planning and reduce the number of same-time orders the kitchen can accept. Large orders may need:
- earlier confirmation;
- a restricted menu;
- stock and staffing checks;
- deposit or payment terms;
- a named contact;
- a separate packing and handover plan.
Keep customer communication linked to reality
Status messages should reflect actual operational events. Do not mark an order as preparing, ready or out for delivery merely to satisfy a platform timer. False statuses create confusion for customers, drivers and staff.
When the promise will be missed:
- update the channel where possible;
- contact the customer when the delay is material;
- give a realistic revised estimate;
- offer the available resolution without making guarantees that staff cannot honour;
- record the cause for later review.
Build a short failure playbook
Prepare a practical response for:
- internet outage;
- marketplace tablet or printer failure;
- POS or KDS failure;
- payment captured but order missing;
- duplicate order;
- sold-out item after acceptance;
- driver shortage;
- customer unable to collect;
- unsafe or unclear allergen request.
The playbook should identify the first action, the person responsible, the customer message and the reconciliation step.
Daily operating checks
Before opening
- Check devices, printers, paper, sound and internet.
- Confirm menu availability and prices.
- Review advance orders and staffing.
- Test the order route after system changes.
Before the peak
- Confirm capacity limits and pause authority.
- Review delivery zones and driver coverage.
- Assign channel monitoring and packing roles.
At close
- Reconcile accepted, cancelled and refunded orders.
- Record missing or duplicate transactions.
- Review errors, late orders and complaints.
- Assign corrective actions rather than carrying unresolved issues forward.
Related operational guides
- How to Handle Busy Periods for peak-capacity controls.
- Order Accuracy and Quality Control for detailed error prevention.
- Order Modification and Cancellation Policies for status-based customer rules.
- Pre-Ordering and Advance Orders for future demand and large baskets.
- Multi-Channel Order Management for several order sources feeding one kitchen.
Good order handling makes the promise shown on the screen achievable in the kitchen. Technology should support that promise, not create a second version of reality.
Related guides
- Online Ordering — the main guide for the wider topic.
- How to Handle Busy Periods — a detailed next step for putting this guidance into practice.
- Order Accuracy and Quality Control — a detailed next step for putting this guidance into practice.
- Online Ordering Data and Analytics — a closely related operational control to review alongside this page.
- Owned Channels vs Marketplaces — a closely related operational control to review alongside this page.
- Multi-Channel Order Management — a connected decision that can change the recommended approach.
