Delivery is the last promise inside the order.
Assignment, state, handoff, and completion continue what began at ordering.
Product offer
SAR 80 / month
per delivery captain when billed annually
A focused captain license connected to assigned tasks, route, and delivery state under fleet policy.
What happens, and what does it mean?
The order loses meaning if its context disappears after leaving the branch.
How does the capability work inside operations?
Fleetly connects delivery tasks to the order within enabled scope and integration.
FoodTech Fleetly
What it adds
Drivers, fleet, and tasks
Assignment, zones, and states
Location where available
Proof of delivery
Interrupted work and safe sync
Delay alerts and driver performance
How it appears in operations
How does this appear in daily work?
Branch task linked to order
Update after connection returns
Delay alert for operations lead
Available in
Compatible plans
- Paid-plan add-on
- Scale
- Enterprise
Connects with
Products it connects with
- FoodTech POS
- Kitchen Display
- FoodTech Online
- FoodTech BI
FAQ
What you need to know
Can FoodTech Fleetly run on its own?
FoodTech Fleetly 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
What should travel with the order?
Destination, state, owner, and available completion proof.
FoodTech Fleetly
See how this product takes shape inside your operation.
Assignment, state, handoff, and completion continue what began at ordering.