← back to reference index

← back to counter

Parked orders

§13 · orders held mid-checkout, e.g. a customer stepped away or a tab is running.

STATUS: visual-only mock — behavior/empty/error/loading states not specified
Order Table Items Parked Subtotal Actions
#1041 Table 4 · Garden 3 items 8 min ago ₱765 Recall
#1038 Bar tab · walk-in 5 items 32 min ago ₱1,410 Recall

A parked order isn't a hold on inventory or a table's status — both stay exactly as they were before parking (§13).

Implementation notes for Cursor

Entities: Order with status=parked (same entity as an in-progress or completed order, not a separate table).

Key states: parked → recalled (back to in-progress on the counter) or voided. In the real app, Recall should reopen the exact cart on pos-counter.html, not navigate to a blank screen — this mock links back to pos-counter.html only because it can't restore cart state across a static page load (D16 constraint, not a product decision).

Forbidden inventions: parking/voiding does not touch Inventory or table/resource status — only checkout (Charge) does (§13). Recall/Void are mocked here (see link/button titles).

Governs: §13 (Order lifecycle), §13 (POS–table sync boundary, D25), D28 (this list view).