How order history controls review and KDS entry

Overview

• MiniTill does not blindly send every public online order straight into kitchen production.
• When an online order is created, MiniTill checks previous completed paid-order history for the matched Customer and normalized phone number.
• If either has qualifying history, the order is marked AUTO_CONFIRMED with reason RETURNING_CUSTOMER.
• If there is no qualifying history, the order is marked NEEDS_REVIEW.
• Once operationally confirmed, the common fulfilment workflow opens the order and ensures KDS state when the order is due for preparation.
• This reduces approval taps for returning customers while preserving a review step for unfamiliar first orders.

When to use this

• Read this when staff ask why one online order reached KDS automatically while another stopped for approval.

Step-by-step

1. Customer submits the order.
2. MiniTill matches/creates the customer.
3. Completed paid history is checked for Customer and normalized phone.
4. Returning history → AUTO_CONFIRMED.
5. No history → NEEDS_REVIEW.
6. Once confirmed and due, MiniTill ensures the order on active KDS displays.

Common mistakes

• Do not assume loyalty PIN login itself causes auto-confirmation; current auto-confirmation is based on qualifying order history.
• Do not manually recreate a NEEDS_REVIEW order in POS.
• Do not assume AUTO_CONFIRMED future scheduled orders should immediately occupy KDS.

Troubleshooting

• If a returning customer still needs review, check whether historical orders match that Customer/normalized phone and have qualifying paid status.
• If an AUTO_CONFIRMED ASAP order fails to reach KDS, inspect fulfilment/system issues rather than duplicating it.