Table QR and direct online ordering solve different customer jobs. A clear distinction prevents wrong kitchen routing, missing table information and delivery handover confusion.
Table QR: the guest is seated in your restaurant
The guest scans a code at the table. Depending on the business configuration, the QR can show only a menu or allow customers to submit an order. In a menu-only setup, staff or a captain records the food order. The order is associated with the table and kitchen preparation; payment or settlement may happen later.
Direct Order: the guest is ordering for pickup or delivery
The customer opens an ordering link outside the table context, selects items, provides the required contact and fulfillment details, and submits the request. The business should confirm availability and review the order before preparing it. Pickup and delivery require different handover steps.
Comparison: questions to settle before enabling either flow
| Decision | Table QR | Direct ordering |
|---|---|---|
| Service location | Seated table | Pickup or delivery destination |
| Identifying context | Table reference | Customer and fulfillment details |
| Staff responsibility | Table service and settlement | Acceptance, packing and handover |
| Kitchen routing | Table-specific ticket | Pickup/delivery ticket |
| Completion | Bill and vacate table | Handover and completed status |
Test the whole lifecycle, not only checkout
- Create a test item with a valid positive channel price.
- Place one table order and verify its table label, quantities, notes and KDS ticket.
- Place one direct pickup order and verify the correct handover path.
- Place one delivery order and verify contact, charges, business acceptance, rider handover and final status.
- Retry a submission once, and check the customer total matches the saved merchant total.
Release note: The V58.1 staging QA identified a Direct Order retry-response amount discrepancy. Verify the deployed fix before using a retry journey as proof of production readiness.