creekpos · Classic Desktop
Kitchen progress, service timing and cleaning · Classic Desktop
This guide uses fictional training data. Available controls depend on your enabled features, plan and permissions.
Prepared against the tested 13 October 2026 build; check your deployed build before following a new control.
Who can use this
Waiter / kitchen / cashier
Required tools
Tables, kitchen and service lifecycle. Requires the appropriate enabled features and entitlement; this guide does not add plan inclusions.
Before you begin
If a control is absent, check role, branch, enabled features and entitlement. If an order or price changed, refresh and review again. Do not repeat an uncertain financial action with a new request.
Classic Desktop kitchen tickets and held orders are separate from online immutable visit/service events. Do not claim the browser cleaning roster or staff performance dashboard exists in the native program. A cloud-connected restaurant may use the online kitchen and waiter workspaces alongside its till.
Steps
- Open Tables and inspect the held order for the selected table.
- Review the ordered items before completing payment. Do not recreate a held order after an uncertain save.
- Complete the native receipt and verify the table/order state.
- SaaS kitchen action timing, waiter notifications and the cleaning lifecycle are not classic Windows controls. Use the Online workflow for those operations.
Check the result
Review the saved record and its audit/stock/payment state before continuing. A preview, queued request or accepted send is not proof of completed delivery or settlement.
Edition differences and limits
Classic Desktop kitchen tickets and held orders are separate from online immutable visit/service events. Do not claim the browser cleaning roster or staff performance dashboard exists in the native program. A cloud-connected restaurant may use the online kitchen and waiter workspaces alongside its till.