A digital channel is an extension of the restaurant.
Menu, order, customer, fulfillment, and branch context must reach the same operation.
What happens, and what does it mean?
A new entry point should not create a second version of the truth.
How does the capability work inside operations?
FoodTech Online connects brand experience to menu, branch, execution, and customer context by agreement.
FoodTech Online
What it adds
Branded Android and iOS experience
Ordering link and QR that open the right channel
Branch selection and independent menus
Dine-in, pickup, takeaway, and delivery journeys
Order status, offers, loyalty, and wallet
Scheduled orders, bookings, and catering
Delivery zones, availability times, and policy-governed publishing
Electronic payment when LuxPay and a provider are available
How it appears in operations
How does this appear in daily work?
Financial confirmation for scheduled catering
Different branch menu
Campus-cafeteria or service-area QR
In-app loyalty offer
Available in
Compatible plans
- Add-on for Growth Flex and Pro Branch
- Scale
- Enterprise
Connects with
Products it connects with
- Menu Engineering
- LuxPay
- FoodTech Loyalty
- FoodTech Fleetly
FAQ
What you need to know
Can FoodTech Online run on its own?
FoodTech Online has a clear role on its own, while its value expands when connected to the relevant FoodTech products under the selected plan and integrations.
Is every capability immediately available?
Availability depends on product state, plan, market, and enabled integrations. We label the current state and never present work in progress as generally available.
How do we begin?
We map the real operating flow first, then agree the starting point, configuration, integrations, and rollout scope.
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
How does a digital order reach the kitchen?
It carries context from choice through fulfillment.
FoodTech Online
See how this product takes shape inside your operation.
Menu, order, customer, fulfillment, and branch context must reach the same operation.