One visible state from new to completed
Incoming tickets enter as new and can move through in progress, ready, and completed. Elapsed time stays visible so the team can distinguish a fresh order from one that needs attention. A new-order sound can call attention to incoming work without making staff watch an idle screen.
Route the view by preparation station
Filter the display for kitchen, bar, grill, bakery, cold, or expo work. Each ticket carries the customer or cashier context, line items, modifiers, quantities, and kitchen notes needed to prepare it. The station filter reduces noise while the underlying order remains part of the same operation.
Bump forward and recover a paid ticket
Staff can advance a ticket through the workflow as preparation progresses. Completed paid-sale tickets can be recalled one step when a bump happens too soon. Pending and QR-originated fires continue forward through their defined flow, preserving the distinction between an active order and a completed sale.
Connected to the order that created it
The kitchen display is not a detached order board. Restaurant tickets can carry the product, modifier, table, customer, cashier, and source context established upstream, while the resulting sale continues into inventory and reporting. Availability and routing depend on the restaurant configuration used by the merchant.
Use the actual workflow, inspect the resulting record, and ask how the behavior is configured for your locations. Availability can depend on enabled modules, hardware, and payment setup.
Move from the feature to the operation
LiftedPOS is designed so this capability does not sit alone. It shares customer, employee, product, location, transaction, and reporting context with the rest of the system. That is the difference between checking a feature box and removing a handoff from the day.