Return behavior has a reason.
Preference, timing, service, and a relevant reward can make the next visit easier.
What happens, and what does it mean?
Points record a mechanism. They do not explain why a customer comes back.
How does the capability work inside operations?
FoodTech connects loyalty rules with customer identity and order behavior under enabled policy.
FoodTech Loyalty
What it adds
Earning rules by spend, item, or eligible event
Point value and redemption limits
Rules by branch, period, or permitted segment
Awarded, redeemed, and available value in customer context
CRM and self-ordering links where enabled
How it appears in operations
How does this appear in daily work?
Points by purchase amount
Branch campaign
Reward for a first self-order
Available in
Compatible plans
- Core in Growth Flex
- Pro Branch
- Scale
- Enterprise
Connects with
Products it connects with
- FoodTech CRM
- FoodTech Wallet
- FoodTech Nexora
- FoodTech Online
FAQ
What you need to know
Can FoodTech Loyalty run on its own?
FoodTech Loyalty 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
Which behavior is worth rewarding?
The behavior that creates value for the customer and the business.
FoodTech Loyalty
See how this product takes shape inside your operation.
Preference, timing, service, and a relevant reward can make the next visit easier.