Demand can begin anywhere.
Table, home, car, kiosk, or counter: Nexora turns each starting point into an order reaching the same operation.
FoodTech Nexora
Everything you need to know. Without the complexity.
Why now?
The problem is clear. The opportunity is clearer.
Nexora carries choice, fulfillment method, and payment state into execution. NexoraStation continues the journey at the service point.
- 01Table, home, car, kiosk, or counter: Nexora turns each starting point into an order reaching the same operation.
- 02A different entry point should not break branch, menu, fulfillment, or payment context.
From intent to execution · Nexora
Intent can begin anywhere. Order context must arrive intact.
At the table, at home, or at pickup, Nexora carries selection, customization, and service method into an order the restaurant can execute.
The journey is configured for the branch, menu, and channel. The order then continues into kitchen, payment, and operational state.Begins in the guest’s channel
The entry point follows the branch service model, from scan to kiosk or home ordering.
Stays with the choice
Size, modifiers, notes, and fulfillment method travel with the same order.
Starts from an understood order
NexoraStation continues the journey inside the restaurant, so the team sees what is needed and its state.
Returns to the operating picture
Order, payment, and customer state become part of understanding what happened.
Guests see what can be ordered in this branch and channel. Options and modifiers stay explicit through submission.
- Items, prices, and available product information
- Size and modifier choices inside the order path
- A journey configured for branch, channel, and fulfillment
Where supported by the selected market and provider, payment stays tied to the amount, order, and state. Confirmation remains part of the same journey.
- Payment tied to order and amount
- State confirmation through the available integration
- Continuity into execution and settlement
FoodTech Nexora
Demand does not begin in one place. It should never get lost on the way.
Give every customer the shortest path from intent to order while branch, payment, and execution stay connected from the start.
Ordering from the table
The table can know order context before the guest begins choosing.
Guests scan the table code to open the menu associated with branch and service point, customize items, and send the order into execution with table context intact.
Best for
- Restaurants
- Cafes
- Food halls
- Hotels
- Hospitality lounges
What improves?
- Table context inside the order
- Digital menu from one source
- Choices reach execution
- Payment from the channel when available
- 01Scan table code
- 02Load branch and table
- 03Choose and customize
- 04Send to execution
- 05Pay or request bill when supported
- 06Follow status
The order can connect to LuxPay according to enabled payment methods, business policy, and available integration.
The order carries table, branch, and choices into execution without manual re-entry.
A journey for every selling point
Table, home, vehicle, or kiosk; one experience that adapts to the moment.
Designed around how you sell
Your business does not need another channel. It needs a channel connected to operations.
Restaurants and cafes
Table, home, pickup, vehicle, and kiosk become different entry points into one operation.
Bakeries and desserts
Scheduled ordering, pickup, and seasonal channels can connect with production and availability when enabled.
Supermarkets and grocery
Scanning, basket, catalog, and ordering points stay tied to branch and product context.
Retail and specialty stores
Catalog, scanning, ordering, and pickup use the same product definition and branch context.
Hotels and hospitality
Ordering from table, room, or service point can carry location context to the team that will execute it.
Universities and events
Distributed QR, kiosk, or pickup points can sit above one shared operation.
Nexora × LuxPay
Payment state returns to the order that created it.
LuxPay links the payment session to order, branch, channel, and amount through the enabled integration, and Nexora updates order state according to the result returned by the supported provider.
- 1Create order and amount
- 2Open enabled payment method
- 3Receive provider result
- 4Update payment state
- 5Continue order into execution
- 6Show receipt when supported
Operating reality
A different entry point should not break branch, menu, fulfillment, or payment context.
How the capability works
Nexora carries choice, fulfillment method, and payment state into execution. NexoraStation continues the journey at the service point.
FoodTech Nexora
What it adds
Table QR and branded ordering links
Pickup, takeaway, and pre-order journeys
Digital menu updated from the connected catalog
Customer context and payment where enabled and permitted
Connection to the execution flow for the selected branch
A digital menu that reduces the need for shared printed menus on tables
How it appears in operations
Practical scenes for every business model.
Table QR order
Pickup order for a selected branch
Pre-order with a defined fulfilment time
A table QR opens the menu on the guest’s device, with one-source updates instead of reprinting when items or prices change.
Available in
Plans
- FoodTech Free within limits
- Growth Flex
- Pro Branch
- Scale
- Enterprise
Connects with
Connected ecosystem
- FoodTech POS
- NexoraStation
- Menu Engineering
- Smart Catalog
- LuxPay
- Kitchen Display
- Inventory
- FoodTech CRM
- FoodTech BI
FAQ
What you need to know
How is Nexora different from a traditional menu app?
A menu app mainly displays products. Nexora understands entry point, branch, table or vehicle, and fulfillment, then connects choice to payment, execution, stock, and customer context.
Does every channel require a separate app?
No. Table, Home, Scan, Pickup, Drive, Kiosk, and Anywhere are experiences inside one platform using the same product and policy source with different context.
How does payment work with LuxPay?
Nexora binds the payment session to order, branch, channel, and amount, then waits for a trusted LuxPay or enabled-provider result before accepting payment or starting paid fulfillment.
Is Nexora only for restaurants?
No. Restaurants use menu, table, and kitchen journeys, while retail uses catalog, scan, and pickup. Hotels, campuses, and events create Anywhere points by place.
Is Nexora Kiosk available now?
Nexora Kiosk is presented as coming soon and should not be treated as generally available until supported hardware and payment activation are announced.
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.
FoodTech Nexora
Turn the next customer touchpoint into an executable order.
Table, home, car, kiosk, or counter: Nexora turns each starting point into an order reaching the same operation.