Inbound Restaurant Ordering: Multilingual Mobile Order Checklist

Confirm languages and screen coverage

The Kantan Chumon pricing page lists Japanese, Chinese, English, and Korean support. Confirm whether confirmation, errors, sold-out notices, and checkout guidance are also translated.

Review dish names, ingredients, cooking methods, and proper nouns rather than relying entirely on automatic translation.

Standardize menu information

Use consistent fields for name, tax-inclusive price, portion, ingredients, spice, images, and service time.

Explain Japan-specific dishes briefly and make sets and surcharges explicit.

Handle allergens and dietary needs

When cross-contact cannot be excluded, state that clearly. Only display halal, vegetarian, or vegan claims that the restaurant can verify.

Provide a way to ask staff and avoid treating the system as a safety guarantee.

Explain payments and checkout

Show accepted cards, mobile payments, cash, service charges, seating charges, taxes, and split-bill rules before completion.

When ordering and payment are separate, clearly distinguish order completion from payment completion.

Prepare staff exceptions

Plan for unsupported languages, changes, receipts, and customers who cannot use the device. Use simple reference sheets and escalation rules.

Translated ordering does not eliminate questions during food delivery and checkout.

Measure and improve

Review language usage, abandonment, staff calls, cancellations, and review comments rather than only counting foreign-language orders.

Update languages, images, descriptions, and prices as visitor patterns change.

Schedule a quarterly content review so translations, payment details, allergen notes, and staff guidance remain aligned with the live menu and actual service process.

Test the experience with real language and service exceptions

Machine-translated menu names are not enough for reliable inbound service. Review ingredient names, allergens, religious or dietary restrictions, portion descriptions, spice levels, set-menu rules, taxes, service charges, and payment instructions with a fluent reviewer. Use photographs consistently, but do not rely on images when sizes or included items differ. Staff should be able to identify the language selected by the guest and locate the same item on their own screen.

Test situations that commonly require human help: a guest without mobile data, a group sharing one device, a failed payment, a sold-out item, a request to remove an ingredient, a table move, and a refund. Provide a visible assisted-order route and simple multilingual guidance for emergencies. Review support logs and abandoned orders by language after launch. A multilingual screen is successful only when it reduces confusion without excluding guests who cannot complete the digital flow.

Place short multilingual instructions at the entrance and table, including how to request staff assistance. Review whether the translated flow remains usable on smaller screens and whether confirmation messages clearly show quantity, price, taxes, and order status before payment.

Frequently asked questions

Official sources

• Wiz — Kantan Chumon official page
• funfo official site
• Kantan Chumon — restaurant POS features