Map one complete order
Choose a realistic dine-in order with a menu choice and preparation note. Ask the counter to enter it, the kitchen to prepare it, and a cashier to inspect its document and collection status. Repeat for takeaway or delivery if relevant. This reveals whether information survives the handovers.
Test the actual price
Use a worked example to review choices, discounts, tax and service charges. Check rounding in your currency. Ask which reward and discount combinations are supported and what happens when staff reopen a review after the menu changes.
Separate invoice and collection
An invoice records a charge; payment records collection. Test an unpaid order, an eligible partial or split collection and a supported correction. Ask what confirms a gateway payment. A customer QR screenshot is never bank confirmation.
Give every role a task
Have a cashier, manager and kitchen operator use their own accounts. Check both allowed work and restricted branch or settings access. Test revocation as well as a valid account.
Use the real equipment
Try your intended tablet, phone, counter screen and printer. A browser print dialog does not replace a real ticket emerging from the device. Check the process for an internet outage; browser access alone does not imply offline operation.
Confirm scope in writing
Record plan limits, enabled modules, taxes, support and migration work. Menuji implements bounded workflows with remaining development and external acceptance work. Ask about the deployed version and exact requirement rather than assuming every addon name means complete coverage.