MesaFlow home
ManagerOwnerWaiterWalkthrough

How to Run Your First Test Order

A step-by-step dry run to verify table cards, menu ordering, waiter notifications, and kitchen flow before live service.

Who can do thisManagers, Waiters, and Owners.

Before you begin

  • At least one table configured with an assigned card or QR code.
  • At least one active menu section containing an available product.

Steps

  1. Open the test table menu

    Either tap the table NFC card with your smartphone, scan the table QR code, or open `/waiter/tables` on your computer and click the table label.

    The customer menu will open in the browser, showing the restaurant banner, categories, and dishes for that specific table.

  2. Add a dish and submit the order

    Select a product, choose any option (e.g. dressing or side), click "Add to Order", open the cart, and tap "Place Order".

    Notice the 60-second grace countdown overlay on the phone screen. Do not cancel the order; let the countdown finish or tap "Done".

  3. Observe the order on the Waiter Dashboard

    Open `/waiter` on another phone or computer screen.

    The ticket appears instantly in the "New" column with a green badge, indicating the table number, ordered dish, and elapsed time.

  4. Advance the order status

    Click on the order card or press the primary advance button on the ticket.

    If a kitchen screen is enabled, the ticket advances to "Accepted" and appears on `/kitchen`. On `/kitchen`, advance it to "Preparing" and then "Ready". When delivered, the waiter marks it "Completed".

  5. Test Call Waiter and Request Bill

    On the test customer phone, tap "Call Waiter" and then "Request Bill".

    Verify that the waiter screen displays the notification alert with table number and that the itemized bill screen appears on the guest’s phone.

What you should see

You have verified that the entire tap-to-order pipeline is functioning smoothly from customer phone to staff screens.

Good to know

  • Orders placed during testing can be marked as completed or canceled with the reason "Testing" to keep records clean.

Related guides