Order Management (OMS) & 4-Tab Deep Dive
How managers inspect live tickets, transfer tables, apply adjustments, step-back statuses, and issue voids.
How It Works
Tab 1 — Overview: Displays the order header (table label and server name), print action buttons (Thermal Bill and UniBill PDF), itemized line items with variant sizes, customer cooking notes, tax breakdowns, and grand totals.
Tab 2 — Operations: Contains operational escape hatches: (1) 1-Tap Table Transfer to migrate tickets to a new table, (2) Forward action buttons (Confirm, Cook, Ready), (3) Reopen Order button for served tickets, (4) Status Step-Back buttons to reverse accidental clicks, and (5) Danger Zone to void orders with mandatory written reasons.
Tab 3 — Adjustments: Manages server attribution (served_by_name), voluntary staff tips (0%, 5%, 10%, 15%, Custom), and custom fees (packaging, delivery surcharges). Displays a red lock banner if the order was paid online or settled over 2 hours ago.
Tab 4 — Timeline: An immutable chronological audit ledger (serve_logs) recording exact timestamps, staff names, and roles for every lifecycle event (e.g. order placed, cooking started, ready marked, served, paid, table transferred, voided).
What You Need to Do (Step-by-Step)
- 1. Open OMS Modal for Active Order
Navigate to Dashboard -> Orders or Manager -> Orders. Click on any active order row to open the 4-tab modal.
- 2. Perform 1-Tap Table Transfer
To move diners, click the "Operations" tab. Enter the destination table label (e.g. T2) and tap "Transfer". Both the ticket and add-on tabs move instantly.
- 3. Reverse a Premature Status Click
In the Operations tab, tap "↩️ Back to Cooking" if dishes need more time, or "↩️ Back to Pending" if waiter review is needed.
- 4. Assign Server or Add Packaging Fees
Open the "Adjustments" tab. Update the Assigned Server Name, pick an inline tip chip, or add custom delivery/packaging fees.
- 5. Inspect Timeline Event Audit Trail
Click the "Timeline" tab to review the exact minute-by-minute audit history of who created, cooked, served, and adjusted the ticket.
Key Screen Controls & Options
Action: Moves all active tickets and add-on rounds to a new table label (e.g. Table 4 to Table 12).
Action: Reverts ticket status safely. Back to Cooking preserves inventory without double-deducting.
Action: Cancels the ticket, restocks claimed inventory, and logs the void reason in the manager audit register.
Action: Updates which waiter receives commission, tips, and shift credit for that table.
- Transferred tables reflect new seating numbers on KDS tickets immediately.
- Inventory records adjust automatically without double-counting.
- Serve logs record the manager’s name and timestamp for every adjustment.
- All state transitions validate valid starting statuses, preventing corrupted order flows.
- Order Voids strictly require a written audit reason. The system blocks submission if the reason field is blank.
- Orders marked Paid cannot receive line item edits without a formal manager void.
⚡ Common Floor Scenarios & Edge Cases
What to do: MintLight will alert you that the destination table has open tickets. Settle or transfer the existing table first, or combine items.
What to do: This indicates the order was paid via online gateway or settled over 2 hours ago. Amounts are locked to prevent financial tampering.
📋 Real-World Shift Walkthrough
Diners at Table 2 ask to move outside to Patio Table P1. Manager Sarah opens the order in OMS, clicks "Operations", types "P1" into the New Table field, and clicks "Transfer". Instantly, Table 2 turns Green (Available) for new guests, Table P1 turns Red with the active pasta order, and the kitchen KDS ticket updates to show "P1" without reprinting.