Skip to content

Delivery and takeaway12 min read

Order Status vs Payment Status: Why Restaurants Must Keep Them Apart

The operational status tells you what is happening in the kitchen and at handover. The payment status tells you what is happening with the money. Each changes with different events.

For restaurants with delivery, collection and online payments: status combinations, rules, a model example and a checklist.

Illustration: one food order split into two timelines, the kitchen from acceptance to handover above and the payment from pending through paid to a partial refund below
One order, two timelines: operations and money each move at their own pace.

The order status answers the question of what is happening to the food: whether the order has been accepted, is being prepared, is ready, is on its way or has been handed over. The payment status answers a different question: whether the guest has paid, whether payment is still pending, has failed, or money has been refunded. The two change with different events, and different people and systems change them, so they can't be merged into one ‘status’ column: ‘ready’ doesn't mean ‘paid’, and ‘paid’ doesn't mean ‘confirmed’. This guide is for owners and operations managers of restaurants that take delivery or collection orders through their website, an online shop or a delivery platform. It covers the status combinations that really occur, the rules each restaurant has to set itself, a model evening and a checklist for the shift and the end-of-day close.

Two questions for every order

The cook asks what to prepare and by when. The person at the pass or the driver asks who gets the order and where. At the end-of-day close the manager asks whether the restaurant got paid for it and, if not, why. The first two questions concern the operational status of the order, the third its payment status. That different people ask them is no accident: each status has a different owner and a different source of events.

The operational status is moved on by people in the restaurant (someone confirms the order, the kitchen starts preparing it, the pass hands it over) or by the channel the order came from. The payment status is changed by the payment gateway, the card terminal, the till, the online shop or the platform, and also by the person who takes cash at handover. The events don't arrive in the same order either. An online payment can come in before anyone confirms the order. A payment on delivery is recorded only after handover. And a refund after a complaint may come the next day, long after the order was closed.

Status names differ between systems. This article uses these:

  • Operational status: new, confirmed, in preparation, ready, out for delivery, completed, cancelled.
  • Payment status: unpaid, awaiting payment, paid, payment failed, partially refunded, refunded.

Combinations you will meet on the floor

With the statuses kept apart, every combination can be read and each one has a clear response. Some combinations are routine; others are warning signs to check during the shift.

Combinations of order status and payment status

Model situations; status names differ between systems.
Order statusPayment statusWhat it meansWhat to do
NewPaidThe guest paid online in advance; the kitchen hasn't startedConfirm and schedule preparation for the requested time
NewAwaiting paymentThe online payment hasn't gone through or hasn't been confirmedFollow the restaurant's rule: wait, or call the guest
ReadyUnpaidNormal for collection with payment on the spotTake the payment at handover and record it straight away
CompletedUnpaidThe food has gone, the money isn't recordedCheck whether only the record is missing or the payment really is
CancelledPaidThe guest paid, the order won't happenRefund; change the payment status only once the money is actually returned
CompletedPartially refundedA complaint about one item after handoverThe order stays completed; only the payment changes and the reason is recorded
CancelledPayment failedThe order fell through because the payment failedPrepare nothing; contact the guest according to the rule

Look at the second-to-last row. A refund doesn't move the order from ‘completed’ to ‘cancelled’: the food was cooked and handed over, and only the amount the restaurant ends up keeping has changed. If one field carried both, someone would have to decide which of the two truths to overwrite, and the overview would tell only half the story.

Why one ‘status’ column isn't enough

Many businesses start with a single status in a spreadsheet or an online shop: new, paid, done. That works until the first exception. Then the same mistakes appear in venue after venue:

  • Paid is read as confirmed. The online shop marks the order as paid and the kitchen treats it as accepted although nobody confirmed it, perhaps at a time when the kitchen has already closed.
  • Done overwrites unpaid. Whoever moves the order to ‘done’ erases the fact that a payment on delivery was never recorded. The gap shows up at the close, and nobody knows which order caused it.
  • Cancellation without a refund. A paid order is cancelled but nobody starts the refund, because ‘cancelled’ looks like a closed matter.
  • A complaint without a trace. After a complaint the order is switched to ‘cancelled’, so the overview no longer shows that the food was prepared and handed over.
  • Two payments for one order. The online payment isn't confirmed in time and the guest pays again by card at handover. Without payment records linked to the order, this has to be traced by hand.

Separate statuses won't remove these mistakes by themselves, but they make them visible: every mismatched combination is a signal you can search for and check before it turns into a gap at the close. Duplicate orders, where the same order is created twice in different channels, are a different problem and a topic of their own.

One order, two timelines

Separate statuses only make sense with a history. For every change you want to know which status the order moved from and to, when, and why. The operational history answers questions like ‘when did the food leave the kitchen?’ or ‘how long did it wait at the pass?’. The payment history answers ‘when did the money arrive?’ and ‘who refunded part of the amount, and why?’. In a complaint or a dispute with a guest, you need both.

The example gives a simple rule: the operational status follows what happened to the food, the payment status follows what happened to the money, and every change comes with a time and a reason.

Rules the restaurant has to set

Software can keep the statuses apart, but what to do with a given combination is an operational decision. Have the answers written down before the first disputed case, and the same for every shift.

When to start cooking

For online payments, decide whether the kitchen starts after the order is confirmed or only once the payment is confirmed. For orders for a specific time, preparation follows the requested time, not the moment the order arrived. And set how long an order may stay ‘awaiting payment’ before someone cancels it or calls the guest.

Who may cancel and refund

Cancelling a paid order must always be followed by a refund with a named person responsible. Money is usually returned where the payment was made (through the gateway, the terminal or the platform), and the payment status changes only after the money has actually been returned, not after it has been promised. Record a partial refund for a missing item together with the reason.

Payment on delivery

The driver or the person at the pass records the payment at the moment of handover, not in one go at the end of the shift. Otherwise, at the close you can't tell which order really is unpaid and which is just missing a record.

Orders from delivery platforms

With platforms, the guest usually pays the platform and the restaurant receives the order with the payment information. When and how much the platform pays out to the restaurant is set by your contract with it. That is a third, separate question; don't mix it up with the payment status of an individual order.

Bookings and the bill at the table

The same principle applies beyond delivery. A deposit or a package paid in advance with a booking says nothing about whether the guest turned up. And when a guest at the table asks for the bill through the QR menu and chooses card or cash, that is a request to staff, not a payment.

This article describes operating practice. How to handle cancellations, refunds and payments on delivery with your payment provider and in your accounts is something to check with your payment gateway provider and your accountant; rules and practice differ by country.

How RestoCraft Orders separates the statuses

RestoCraft Orders is built on a single order record. It holds the channel, the fulfilment method, the customer, a structured address, the requested time, the items and the totals, and, separately, the operational status of the order and its payment status. Each changes on its own and with different events. Order statuses follow a fixed sequence and the system rejects an invalid transition, so an order can't jump from ‘new’ straight to ‘completed’. The history stores which status the order moved from and to, when and for what reason.

An order can also have its own payment records: the provider, a reference, the amount, the currency, the status and the time of payment or refund. Where the payment information comes from, however, depends on the channel and on how far its connection has got:

  • WooCommerce: a paid order is marked as paid in RestoCraft; today this applies to paid bookings and deposits, while food orders from the online shop are in development.
  • Wolt, in pilot mode: payment details arrive with the order, and further status changes from Wolt move the same order on. Nothing is sent back to Wolt yet.
  • Your own website: the website records the payment for an order through the orders API; connecting a specific website is done as a project.
  • RestoCraft payment gateway: linking gateway payments to orders is in development.

The operations screen where an order is moved between statuses with buttons is in development, and an order status page for guests is only planned so far. What makes sense for your venue depends on the channels your orders come through, so it is worth going through them one by one.

Checklist for the shift and the close

Before you start accepting online payments or launch a new ordering channel, go through these points with the team:

  • Everyone knows which status they change: the kitchen and the pass the operational status, the till and the pass the payment status.
  • There is a written rule for ‘awaiting payment’: when to start cooking and when to cancel.
  • Payments on delivery are recorded at handover, not at the end of the shift.
  • Cancelling a paid order is always followed by a refund with a named person responsible.
  • A refund changes the payment status, not the operational status of a completed order, and always has a recorded reason.
  • At the close, search for mismatched combinations: completed and unpaid, cancelled and paid, two payments on one order.
  • For platform orders, the payment status of the order isn't mixed up with the platform's payout.
  • Once a week, go through the status history of complaints and find the step where the problem arose.

Frequently asked questions

Yes, and it needn't be a mistake. With payment on delivery, for a while the order has been handed over and the payment not yet recorded. If the combination lasts until the close, though, it is a signal to check: either the payment record is missing or the payment really is.

That depends on the restaurant's rule and the payment method. With online payment in advance it is safer to start after the payment is confirmed; with payment on delivery you can't wait. What matters is that the rule is written down and the same for every shift.

If the food was prepared and handed over, the order stays completed. The payment status changes to partially refunded or refunded, and the reason goes into the history. An order is cancelled only when it really didn't happen.

Not yet. The statuses and the rules for moving between them sit in the order core of RestoCraft Orders, but an order status page for guests is only planned. Until then, keep guests informed through the channel they ordered from.

Key takeaways

  1. Order status describes operations, payment status the money; different events and people change them.

  2. A refund changes the payment, not the fact that the food was prepared and handed over.

  3. Mismatched status combinations make the best checklist for the end-of-day close.

  4. Rules for pending payments, cancellations and payment on delivery are for the restaurant to set.

  5. In RestoCraft Orders readiness differs by channel: Wolt in pilot, your own website via API, the payment gateway in development.

Conclusion

Separating order status from payment status doesn't add bureaucracy to the floor. It means everyone is responsible for their part (the kitchen for the food, the pass and the till for the money) and that a mismatch between them shows up before it becomes a gap at the close or an unhappy guest. Start by naming the statuses and writing down the rules; only then decide which channels and tools will record them.

RestoCraft Orders

Order and payment in one record, each with its own status

See how RestoCraft Orders stores the order status, the payment status and the change history, and which channels are connected today, in pilot or in development.

Continue reading

Next articlePrepaid Restaurant Reservations: Selling Packages and Add-ons with the Booking11 min read