Skip to main content

Pilot Session Validation

Use this section on a laptop, desktop, or second tablet while the operator uses Dineax on the mobile or POS device. The purpose is to keep the instructions off the operator's active screen so they can perform the workflow without switching between a guide and the app.

This guide is for supervised pilot validation only. It does not approve production launch, unsupervised outlet operation, broad printer compatibility, customer online payment, offline-first operation, cutter or cash drawer use, or all-device support.

RoleDevicePurpose
OperatorMobile, tablet, or POS terminalPerforms the workflow in Dineax.
SupervisorLaptop or second tabletReads this validation guide and records pass/fail notes.
Technical observerLaptop or support workstationWatches API/app/printer behavior and captures evidence.

Keep the documentation website open on the supervisor device. Keep Dineax open on the operator device.

Session Flow​

Follow the pages in this order:

  1. Preflight
  2. Dineax Admin validation
  3. Dineax POS manager validation
  4. Dineax POS operator validation
  5. Kitchen validation
  6. Dineax Order validation, if included
  7. Dineax Console validation, if included
  8. Evidence and Go/No-Go

What To Record​

For every step, record:

  • Passed, Blocked, or Not in pilot scope.
  • The app used.
  • The role used.
  • The outlet context.
  • Any order, bill, receipt, or payment reference visible to the operator.
  • Any printer, payment, access, or workflow issue.
  • A photo or screenshot only when it is sanitized and approved for evidence.

Do not record passwords, tokens, customer phone numbers, account identifiers, or internal support details.

Stop Conditions​

Pause the pilot session if any of these occur:

  • The operator cannot sign in with the assigned pilot account.
  • The wrong tenant or outlet appears.
  • Billing totals are wrong.
  • Payment is recorded with the wrong amount or method.
  • Receipt output does not match the app receipt.
  • Receipt print failure cannot be recovered safely.
  • A user can access a workflow that is outside their assigned role.
  • The operator cannot complete the staff-operated flow with supervision.

When a stop condition occurs, move to Evidence and Go/No-Go and record the issue before continuing.