Public order status timeline

Customer-facing QR and website statuses are read-only evidence views over order ingest, kitchen printer jobs and confirmation outbox records. Status checks never mutate POS or kitchen state.

Read-only timelineTimelines: 2Steps: 10External mutation: false

QR timelinetrue

Website timelinetrue

Core routedtrue

Printer stagetrue

Confirmation stagetrue

Evidence linkedtrue

Read-onlytrue

No LAN blocktrue

Timelines

qr_menuSteps: 5Customer visible: 5Last status: Confirmation recorded

websiteSteps: 5Customer visible: 5Last status: Confirmation recorded

Status steps

Order acceptedorder_accepted

qr_menu / sequence 1Evidence: public_intake_qr_table_7

Public status starts from the accepted order intake record, not from an external provider callback.

Sent to restaurantrouted_to_core

qr_menu / sequence 2Evidence: ingest_qr_table_7

POS, admin, kitchen desktop and kitchen printer routes are already required by order ingest.

Kitchen receivedkitchen_ticket_created

qr_menu / sequence 3Evidence: ingest_qr_table_7

Kitchen visibility is derived from accepted order ingest and remains LAN-first.

Ticket printed or queuedprinter_job_created

qr_menu / sequence 4Evidence: kpj_req_qr_7001_station_main

Printer status is read from local kitchen printer jobs and cannot trigger duplicate prints.

Confirmation recordedconfirmation_outboxed

qr_menu / sequence 5Evidence: public_confirm_qr_lan_pos_table_001

Notification status is evidence-only; WhatsApp, Telegram or email provider failures cannot block the order.

Order acceptedorder_accepted

website / sequence 1Evidence: public_intake_website_delivery

Public status starts from the accepted order intake record, not from an external provider callback.

Sent to restaurantrouted_to_core

website / sequence 2Evidence: ingest_website_delivery