Choose a bounded service
Start with one branch, a short representative menu and a quieter period. Record the deployed version, enabled modules and settings. Keep a workable fallback while the team evaluates the process.
Prepare roles and test data
Use individual staff accounts with appropriate roles. Clearly label test dishes and orders. Avoid placing real guest information, API credentials or sensitive payment details into informal screenshots and support messages.
Complete the journey
Enter an order with notes and choices, inspect kitchen work, complete preparation, issue the supported document and inspect collection status. Test guest request, staff acceptance and receipt recovery separately if customer QR ordering is needed.
Try the exceptions
Pause an item, make an eligible queued change and inspect an allowed correction. Test supported reward, refund and split combinations. Record a missing business requirement as a gap instead of inventing a workaround.
Use controlled real-world checks
Print an actual KOT and invoice on the planned devices. Arrange merchant setup and any live transaction verification through the agreed process. Bank verification is required for manual QR; a screenshot is not money received.
Decide explicitly
Review findings with the owner, counter and kitchen team. Confirm essential scope and commercial terms in writing. Use help.menuji.com for core guides and ask support about version differences before replacing a critical existing process.