Customers should see what they are approving.
Items, changes, total, and payment state create a review moment before completion.
What happens, and what does it mean?
The display earns trust through clarity, not through more promotional messages.
How does the capability work inside operations?
FoodTech shows customer-safe order context within enabled hardware and features.
Customer Display
What it adds
Items, quantities, prices, and modifiers
Discount, tax, and total where configured
Payment QR where the enabled flow supports it
Digital receipt or related message where supported
How it appears in operations
How does this appear in daily work?
Review an add-on before payment
QR shown to the customer
Digital receipt after a supported transaction
Available in
Compatible plans
- FoodTech Free
- Growth Flex
- Pro Branch
- Scale
- Enterprise
Connects with
Products it connects with
- FoodTech POS
- LuxPay
- QR Code & Payment Link
- FoodTech Loyalty
FAQ
What you need to know
Does Customer Display require an app on the customer phone?
No. The secure payment link can open in the browser, while app and NFC paths are used only when supported and enabled.
Does the customer display expose internal data?
No. It shows only customer-safe invoice context such as items, total, and payment status, never internal permissions or sensitive operating data.
How is payment confirmed?
FoodTech does not close the invoice from the customer screen alone. It waits for a trusted provider result, then updates the order and receipt.
Does the operation need a permanent internet connection to keep moving?
Connectivity should add capability, not become the operation’s power switch. Where Offline mode is supported, core work continues locally, events are retained, and synchronization resumes when connectivity returns. Operations that require live verification, including some payment or sensitive actions, remain Online by design. Offline scope varies by product, device, and activation; the goal is to keep work moving even when the network does not.
What if the internet is available — but slower than the operation?
FoodTech does not assume a perfect network. Where supported, every action does not wait for a full server round trip: local state, asynchronous (Async) synchronization, and safe retries keep work moving without duplicating operations. The team can continue what is safe to continue while the system catches up with the network; payments and other sensitive actions still require explicit verification when needed.
Before you start
What needs review before payment?
Items, modifiers, total, and transaction state.
Customer Display
See how this product takes shape inside your operation.
Items, changes, total, and payment state create a review moment before completion.