Plan restaurant orders from the floor to shift close

Evaluate the workflow before choosing hardware: who can change a ticket after the kitchen receives it, when is stock deducted, and how is a refund reconciled? Turn the answers into written acceptance criteria. A product page does not establish support for a printer, payment gateway, or delivery provider.

Prepare a small menu with prices, taxes, and stock units. Use test data to run dine-in, pickup, and delivery orders, then change and void an item after sending it to the kitchen. Agree who sees each change and who approves refunds. Identify devices and service providers before estimating integration and training costs.

Shift acceptance checklist: test a missing ingredient, recipe change, split payment, and refund. Reconcile the till total with payments, refunds, and invoices; explain discrepancies rather than hiding them with manual adjustments. Test a printer outage and retry so a duplicate receipt does not become a new order. If offline work is essential, test disconnection and recovery on the proposed devices; do not assume support. Review access permissions for discounts, voids, and recipe changes, then export sales and stock samples and open them independently. These are evaluation requirements to apply to any system you choose. Review invoicing, integrations, and hardware costs with the relevant parties before contracting. For central accounting or an unsupported delivery provider, agree which system owns orders, payments, and stock, and how repeated notifications are handled, before developing the connection.