What do UAE logistics companies build first?
Almost always a driver app, because the driver is where parcels, proof and cash change hands, and it is where paper run sheets and WhatsApp photos break down first. Dispatch tools, merchant portals and analytics follow once the driver side produces reliable data.
The pattern is familiar across UAE last-mile operators: a growing courier or a retailer with its own vans runs for a year on spreadsheets and WhatsApp groups, then a disputed delivery or a cash shortfall shows how little evidence exists. The first project that pays for itself is the one that records every handover with a timestamp, a location and a photo or signature.
A logistics app development company in Dubai should help you sequence the build around that pain, rather than selling a "complete platform" on day one. We usually recommend three phases: driver app and simple dispatch first, merchant integrations and tracking links second, then route optimisation and analytics once you have months of real delivery data to tune against.
- Phase 1: driver app, run sheets, proof of delivery, cash per parcel, basic admin.
- Phase 2: merchant portal and API, recipient tracking links, COD settlement statements.
- Phase 3: route optimisation, capacity planning, performance dashboards.
What should a UAE delivery driver app include?
A driver app needs a clear run sheet, fast scanning, one-tap navigation, proof capture, failed-delivery reasons, cash entry and reliable offline behaviour. Everything else is secondary. Drivers use the app hundreds of times a day, so each extra tap costs real minutes across a fleet.
Design for the conditions: gloves in cold stores, bright sun on the windscreen, one hand holding a parcel, and a phone that may be three years old. Big buttons, high contrast, sound and vibration feedback on scans, and a layout that works in portrait on a dashboard mount.
Start of shift
Login, vehicle check, load scan of every parcel against the manifest, with missing or extra items flagged before the van leaves.
On the road
Next stop, navigation hand-off to Google Maps or Waze, recipient call and WhatsApp buttons, and the building or landmark notes captured at booking.
At the door
Scan, choose proof type, capture photo, signature or OTP, record cash collected, and move to the next stop in one flow.
End of shift
Returned parcels scanned back in, cash declared and counted at the depot, and a shift summary both sides can see.
Driver apps are built in Flutter or React Native; see our Android and iOS app services for how we publish them under your accounts.
Photo, signature or OTP: which proof of delivery works best?
Use a combination based on parcel value and payment type: photo for leave-at-door parcels, signature for business deliveries, OTP for high-value or prepaid items, and GPS plus time on every proof. No single method settles every dispute.
A photo proves where the parcel was left but not who received it. A signature proves someone accepted it, though scribbles on a phone screen are hard to read. A one-time code sent to the recipient's phone and read out to the driver proves the right person was present, which is why many merchants require it for electronics and luxury goods. GPS and timestamps support all three by showing the driver was really at the address when the proof was captured.
The rules should live in the dispatch settings, not in drivers' heads. For example: OTP required above a certain declared value, photo mandatory for leave-at-door, signature for business addresses. The driver app then asks for the right proof automatically.
- Store proof images compressed but readable, with the parcel ID and timestamp stamped on them.
- Keep the GPS accuracy value, not just coordinates, so weak fixes can be judged fairly.
- Give merchants access to proofs through their portal instead of email requests.
- Set a retention period for photos and signatures, agreed with your lawyer.
How does cash-on-delivery collection work in a logistics app?
Each COD parcel carries an expected amount; the driver records what was collected, the app totals it through the shift, and the depot confirms the handover so cash moves from driver to cashier to bank with a record at every step. Merchants then receive settlement statements listing each parcel and the amount remitted.
COD is still common in UAE ecommerce, and it is where many courier businesses lose money quietly. Short payments, change disputes, cash left in vans overnight and delayed merchant remittances add up. The app cannot stop dishonesty, but it can make every discrepancy visible on the same day it happens.
Driver side
Expected amount shown, actual amount entered, partial payment and refused-to-pay reasons, and a running cash total on the home screen.
Depot side
Cashier counts and confirms per driver, differences logged with a reason, and a daily summary for the finance team.
Merchant side
Statements by period listing parcels, COD collected, fees deducted and the transfer reference.
Where drivers also accept card on delivery with a portable terminal, the app records the terminal reference instead of cash. For merchant-side checkout options, see payment gateway integration in the UAE.
Route optimisation for UAE deliveries: when it helps and when it doesn't
Route optimisation helps most when drivers have many stops with time windows and capacity limits; with a dozen stops in one tower cluster, a driver's local knowledge often beats the algorithm. Start by grouping stops by area and letting experienced drivers reorder, then add optimisation where the data shows wasted kilometres.
When you do optimise, the engine can be a commercial routing API from a mapping provider or an open-source solver such as Google OR-Tools or VROOM running on your own server. Commercial APIs are simpler to maintain and charge per request; open-source solvers cost more to set up but nothing per route. The right choice depends on your volume.
UAE specifics matter: toll gates in Dubai and Abu Dhabi, restricted truck hours and routes in some areas, and lane restrictions for delivery motorcycles in Dubai from November 2025. Your operations team knows these rules; we build them in as constraints and zone settings rather than guessing.
- Time windows promised to recipients or merchants.
- Vehicle capacity by weight, volume or parcel count.
- Driver shift start and end points.
- Priority parcels and same-day cut-offs.
- Areas or times when certain vehicles should not be routed.
Sending WhatsApp tracking links to recipients
Recipients in the UAE answer WhatsApp faster than calls from unknown numbers, so a tracking link sent on WhatsApp cuts failed deliveries. The message says the parcel is out for delivery and links to a page showing the driver's approach, where the recipient can drop a location pin or add instructions.
On the official WhatsApp Business Platform, messages that start a conversation outside the 24-hour customer service window must use pre-approved templates, and delivery updates fit the "utility" template category Meta describes for transactional messages (Meta template documentation). We set up the templates, the sending logic and the fallback to SMS if a number is not on WhatsApp.
The tracking page itself is a lightweight web page, not an app, so recipients need nothing installed. It shows only what they need: status, estimated arrival window and the driver's first name. It stops showing the driver's position once the delivery is complete.
For two-way conversations and rescheduling by chat, see our guide to WhatsApp chatbot development in Dubai.
UAE addresses without street numbers: capturing locations that drivers can find
Capture a map pin plus building name, flat or villa number and landmark notes for every address, because many UAE addresses are described rather than numbered. In Dubai, Makani numbers identify building entrances and can be stored where customers provide them.
The best source of a precise location is the recipient. The tracking link lets them drop or correct a pin before the driver arrives, and the app remembers corrected pins for future deliveries to the same customer. Over time, your address data becomes one of the most valuable things the platform holds.
For drivers, the app shows the pin, the notes and a one-tap call or WhatsApp button, then hands off to their preferred navigation app. We avoid building turn-by-turn navigation ourselves; mature navigation apps do it better and drivers already trust them.
- Store pins as coordinates with accuracy, not as text.
- Keep delivery notes per address, visible to the next driver.
- Flag addresses with repeated failed attempts for a call before dispatch.
How should a delivery app handle no signal?
It should keep working: scans, proof photos, signatures and cash entries are saved on the phone and synced automatically when the connection returns, in the order they happened. Drivers should never see "network error" at a customer's door.
Underground car parks, service lifts and some warehouse areas routinely drop mobile signal in the UAE, so offline-first design is not optional. The app downloads the day's run sheet at shift start, keeps a local queue of events, and uploads them with their original timestamps. Conflicts, such as dispatch reassigning a parcel the driver already delivered offline, are resolved by rules we agree with your operations team.
Stored on the phone
Run sheet, recipient details for today's stops, pending proofs and cash entries, all encrypted and cleared after sync and shift end.
Synced when online
Events uploaded in order, photos compressed first, with a visible counter so drivers know what is still waiting.
Integrating a logistics app with ecommerce clients
Merchant integration is what turns a courier into a platform. Your clients should be able to send orders automatically, get tracking numbers back and see proof and COD status without phoning your team.
We usually build three doors in: a CSV upload for small merchants, plugins or webhooks for Shopify and WooCommerce stores, and a documented REST API for larger clients and marketplaces. All three create the same parcel records inside your system.
- Order import: CSV template, platform webhooks, REST API with API keys per merchant.
- Labels: printable labels with barcodes generated on booking.
- Status sync: updates pushed back to the merchant's store so their customers see progress.
- Proof and COD: available in the merchant portal and by API.
- Accounting: invoices and remittance data exported for your finance system.
If your clients need help with their own stores, our Shopify developer guide for Dubai and WooCommerce development in Dubai cover the merchant side.
How much does logistics app development cost in Dubai?
With BtechWaleTech, a driver app with proof of delivery, COD and offline sync starts from US$600, and a full platform with dispatch, merchant portal and settlement starts from US$900. Quotes from other developers vary widely, mostly because some include integrations, settlement and offline handling while others list them as "phase two".
The questions that change the price most:
- How many merchant integrations are needed at launch?
- Is route optimisation needed now, or is grouping by area enough?
- How complex is COD settlement: one merchant or hundreds?
- Do you need a merchant portal, or only an internal admin?
- How many user roles: driver, dispatcher, cashier, merchant, customer service, management?
- Is a customer-facing app needed, or is a tracking link enough?
Running costs are separate: hosting, maps and routing usage, message fees, Apple's US$99 yearly developer membership and Google Play's one-time US$25 registration. Compare other app budgets in our mobile app cost guide for Dubai.
How long does a logistics app take to build?
A driver app with basic dispatch takes about 6–10 weeks. A platform with merchant integrations, settlement and optimisation is delivered in phases over several months. The most important thing is getting a pilot group of drivers on the app early, because real routes expose problems no test plan predicts.
We run pilots with two or three drivers on real deliveries while the rest of the fleet continues as before. Feedback from the pilot shapes the final weeks: button placement, proof rules, how cash entry works when a recipient pays part in cash and part by card.
Weeks 1–2
Process mapping with dispatch, depot and finance; screens for the driver app agreed.
Weeks 3–7
Driver app, backend, admin panel, offline sync; weekly test builds.
Weeks 7–10
Pilot with real drivers, fixes, then rollout to the fleet in groups.
Technology choices for a UAE delivery platform
We build driver apps in Flutter or React Native, which gives Android and iOS from one codebase, and backends as a conventional API with PostgreSQL and a job queue. Local storage on the phone uses an encrypted database so offline data is protected if a phone is lost.
Background location needs care. Google Play only allows background location when it is part of an app's core functionality, and developers must complete a declaration in Play Console, show a prominent in-app disclosure before the permission request and supply a short demonstration video. Live tracking of drivers during a shift qualifies, and we prepare the paperwork as part of the build. We also track only during active shifts, which protects drivers' privacy and battery life.
Hosting runs on your own cloud account. If you prefer data in the country, AWS, Azure and Google Cloud each have regions in the UAE.
- Mobile: Flutter or React Native with encrypted local storage.
- Backend: Node.js or Python, PostgreSQL, Redis, background workers.
- Maps: your choice of mapping provider, with geocode caching to control cost.
- Messaging: WhatsApp Business Platform templates plus SMS fallback.
- Monitoring: crash reporting, uptime checks and sync-failure alerts.
Recipient data, driver privacy and the UAE PDPL
A logistics platform holds names, phone numbers, addresses, photos of doorways and drivers' location histories, so privacy design matters. The UAE Personal Data Protection Law, Federal Decree-Law No. 45 of 2021, has applied since January 2022 and gives people rights over their data (UAE government summary).
The build supports your obligations: recipient data used only for delivery, proof photos cropped to the parcel where possible, driver tracking only during shifts, retention periods you set, and access by role so a merchant sees only its own parcels. Legal review of your policies is for your own lawyer.
Working with a logistics app team in India from the UAE
India is 1.5 hours ahead of the UAE, which puts us in step with your operations day: when your morning dispatch starts at 7 am, it is 8:30 am here, and we are online for launch-week issues well into your evening. We communicate through a shared WhatsApp group and video calls, with screen recordings from drivers welcomed when something goes wrong on the road.
You receive an itemised quote in USD, and payments go by Wise or bank wire, with AED possible through Wise. Nothing is billed before your written approval. Your company owns the store listings, cloud account, maps keys and code repository from the start.
What we cannot do from India: ride along with drivers, install hardware in vans or supply scanners and printers. We will specify compatible devices and test with the models you buy.
The first two weeks
Days 1–4: video walkthroughs with dispatch, a driver and finance, plus sample manifests and COD statements. Days 5–10: driver app screens approved, backend skeleton, first test build installed on a pilot driver's phone.
Red flags when choosing a logistics app development company in Dubai
The biggest risk in logistics software is an app that works in the office and fails on the road. Ask any developer, including us, how they handle each of these:
- No offline mode, or offline mode described as "coming later".
- Proof of delivery stored as loose photos without parcel ID, time and location.
- COD treated as a single field with no depot handover or merchant settlement.
- No pilot with real drivers before full rollout.
- Apps published under the developer's accounts.
- No plan for Google Play's background-location declaration.
- A quote with no line for integrations, even though your clients use Shopify or WooCommerce.
A proposal that answers each point in writing is worth more than a lower headline price. Our comparison with Dubai app development companies explains how to read app proposals generally.
Worked example: a hypothetical 25-van courier in Dubai Investments Park
Say a courier with 25 vans works for about 40 online shops, most on Shopify, and a large share of parcels are COD. Today it prints run sheets, drivers send photos in WhatsApp groups and cash is counted at night against a spreadsheet. This is an illustration, not a client story.
Phase one would be a driver app with load scanning, photo and OTP proof, COD entry and offline sync, plus an admin panel for dispatchers and a depot cash screen. Phase two adds a Shopify connection so merchants' orders arrive automatically, a merchant portal with proof and COD statements, and WhatsApp tracking links to recipients. Phase three adds route optimisation for the busiest zones once there is enough data to measure the gain.
The measures that show whether it worked are practical: fewer failed first attempts, fewer disputed deliveries, cash differences caught the same day, and less time spent answering merchant calls.
Checklist before you commission a logistics app in the UAE
Gather these before the first call and the quote will be faster and more accurate:
- A sample day's manifest and run sheet.
- The proof rules you want by parcel type and value.
- How COD cash moves today, from driver to bank.
- Which platforms your merchants use, and whether any need an API.
- The phones your drivers use, and whether scanners are involved.
- Who will own the Google Play, App Store, cloud and maps accounts.
- Two or three drivers willing to pilot the app.