Verify the restaurant online store
For the manager maintaining a restaurant's retail or product catalogue. The
Shop guest flow is different from table ordering and a staff-built Counter
bill. Use the configured website or
terminal Order Link and verify the intended location
rather than inventing a URL.
Browse as a guest
Check the restaurant identity, enabled store entry, product catalogue, photos,
names, categories, prices, and availability. Departments and sub-aisles organise
the products; configured Occasions are separate groupings. All clears the
category filter. Search and browser navigation should return the intended
results; a hidden or filtered product is not proof it was deleted.
| Product detail | Check before service |
|---|
| Photo/name | Correct product and useful fallback when no image exists |
| Pack/variant | Actual pack sold, not a similarly named size |
| Retail price | Correct currency and amount |
| Unit price | Correct comparison unit where displayed |
| Sale price | Current and original amounts match the intended offer |
| Dietary/allergen markers | Follow verified product information; a display marker is not certification |
| Scale badge | Identifies a by-weight product with its weight-selection flow |
| Unavailable | Guest cannot add it; check saved availability and menu context |
Open a product for its details and choices, or use + for a supported quick
add. In-trolley quantity controls let the guest adjust or remove lines. Check
choices, defaults, quantities, and the resulting subtotal—not only the card
price.
By-weight products
The weight selector offers gram presets (currently 100, 150, 200, 250 g), custom
gram entry with displayed minimum/step, optional Thin/Medium/Thick cut, and a
preparation note. The current custom control starts at 50 g in 10 g steps. The
displayed Add price is an estimate; the screen says final price is confirmed at
the counter by weight.
Separate weight/cut selections can form separate trolley lines. Verify that
staff can distinguish them and use the supported weighing/price workflow. Do not
treat an estimate as proof of the final charged amount or kitchen facts.
Trolley and checkout
Desktop shows the trolley beside products; mobile offers a bottom summary and
View trolley sheet. Review lines, quantities, subtotal, and Checkout.
The trolley explains that delivery or pickup is selected at checkout.
Verify the restaurant actually enables the intended fulfilment option, due time,
address where required, and payment method. Complete the supported flow and
inspect the resulting order and actual payment state. A successful product add,
checkout click, or confirmation page alone does not establish preparation or
handover.
Resolve a mismatch
Check location, catalogue/menu placement, active and sold-out state, order type,
schedule, price basis, product/pack, choices, and sync. Use
Menu availability,
Payment recovery, and Orders. A
Counter ordering link is not a workaround for a missing Shop catalogue.
Test through an agreed safe workflow, without real guest payments or unannounced
kitchen tickets. Escalate with product, location, intended channel, weight/unit,
step, observed state, and exact error, keeping guest addresses and payment data
out of public captures.