Check the menu, tables and channels, order handling and payment workflow before opening QR ordering to guests. A QR code is an entry point: a menu that opens does not prove the kitchen, printers or payments are ready.

Prepare a menu guests can use

Import a clear image or PDF, then check categories, dish names, prices, options and extras. Review the AI draft. Translation continues asynchronously after import confirmation; submitting a task does not mean every language is ready.

Your restaurant chooses the guest languages. Check each language you enable, including descriptions, options, prices and allergens. AI usage follows your plan.

  1. Check required choices, supplements and sold-out items.
  2. Preview enabled languages and fallback content on a phone.
  3. Keep the original menu for comparison.

Match table codes to the right service

Check the restaurant, table and ordering channel behind each QR code. Do not use a preview link as an operational table code. Review opening hours and enabled service channels.

Keep staff assistance available for guests who cannot use a phone. Show the team where to check table details and additions when several guests order at the same table.

Assign order handling, preparation and payment

Assign someone to review incoming orders. For KDS or kitchen printing, confirm the plan, stations, routing and enabled devices. Check guest bills and kitchen tickets separately: they serve different purposes.

Decide whether guests pay at the restaurant or through configured online payments. Confirm an independent card-terminal payment before recording it; recording is not automatic terminal integration. Payment-provider fees remain separate.

  1. Check POS sign-in, staff permissions and connectivity.
  2. Confirm how the kitchen receives options, notes and additions.
  3. Check the printer, document template and device executing print jobs.

Arrange a launch check before serving guests

Arrange a suitable test environment with support. Follow menu viewing, option selection, order submission, staff receipt and kitchen handling. Payment and refund checks need the appropriate test configuration.

The public demo shows the guest interface; it does not validate your printer, payment account or live order handling. After the checks, have the restaurant owner confirm readiness and agree what staff should do if connectivity or a payment result is unclear.

MenuSnap frequently asked questions

Does basic setup in around 10 minutes mean I can open immediately?

Around 10 minutes describes basic setup. Complex menus, translation review, devices, payments and staff preparation can take longer. Use your launch checks to decide readiness.

Must I enable both KDS and a printer?

No. Choose the workflow for each role. KDS and printing have their own plan, equipment and activation conditions.