# Restaurant QR ordering checklist

VASUYASHII | Reviewed 28 September 2026

A blank worksheet for comparing an agreed software demo. The rows describe questions to test, not a promise that every feature is included.

[Current service scope](https://www.vasuyashii.com/services/restaurant-qr-ordering)

## Prepare the session

Use synthetic records and role labels. Do not put student or patient details, client names, contact information, bank details, credentials or live invoices into this worksheet or the public enquiry form.

- Session date: ______
- Demo/product version: ______
- Business alias: ______
- First workflow to evaluate: ______
- Reviewer role: ______

- Service model and approximate table/outlet count: ______
- Synthetic menu categories and sample items: ______
- Existing POS and printer names only: ______
- Menu ownership, staff training, connectivity fallback and support scope: ______

## Record the demonstration

Result choices: Not reviewed / Shown with sample data / Needs configuration / Needs confirmation / Out of scope. A shown result applies only to the tested version and scenario.

| Workflow | Ask to see | Result | Evidence reference or gap | Next action / owner role |
|---|---|---|---|---|
| Browser entry | Open a sample table QR in the intended phone browsers; confirm that the menu and table context are correct. | Not reviewed | — | — |
| Menu changes | Change a sample price or availability setting and check what a new customer session displays. | Not reviewed | — | — |
| Order journey | Create a sample basket and submit it once; inspect the staff order record and the permitted status changes. | Not reviewed | — | — |
| Order exceptions | Request the agreed behavior for duplicate submission, cancelled items and interrupted connectivity. Record gaps instead of assuming support. | Not reviewed | — | — |
| Payment route | Separate pay-at-counter, UPI display and gateway checkout. Record the merchant-account owner, onboarding, fees and verification needed for the chosen route. | Not reviewed | — | — |
| POS and kitchen | List the exact POS, kitchen ticket, printer and settlement connections required; ask which are demonstrated, custom work or out of scope. | Not reviewed | — | — |

## Scope and quotation

- Included configuration and modules: ______
- Custom work and exclusions: ______
- One-time, recurring and third-party costs: ______
- Data transfer and verification responsibility: ______
- Hosting, backup and restore responsibility: ______
- Training and support coverage: ______
- Acceptance criteria and responsible role: ______

## Decision

- Findings still requiring evidence: ______
- Next step: Further demo / Scoped pilot / Proposal review / Not a fit
- Decision date and role: ______

A QR menu, ordering workflow, payment gateway and restaurant POS are separate capabilities. A demonstration does not mean a restaurant is already able to accept live payments.

Keep completed worksheets in your private project workspace. Use the public enquiry only for a non-sensitive summary of your requirements.