Article6 min readUpdated
Delivery Tracking App Design for Logistics and Drivers
Delivery tracking app design guide: the customer tracking screen, driver app, proof of delivery and dispatcher dashboard, with common mistakes to avoid.
By Tithi Mondal, UI/UX Designer
Picture a small courier business in Durgapur with 12 drivers. Customers call all day to ask "Where is my parcel?" Drivers call back to ask for the address again. The owner tracks everything in a notebook and a WhatsApp group. An app can remove most of these calls, but only if each of the three users gets a screen made for them.
Delivery tracking app design is the design of the screens that show where an order is, who is carrying it, when it will arrive and how its delivery is confirmed. It covers the customer view, the driver view and the office view of the same order.
For food delivery specifically, read my article on food delivery app UI/UX design. This article covers parcels, goods and logistics in general.
Who uses a logistics app, and what does each person need?
Each person needs one answer fast. The customer needs "When will it come?" The driver needs "Where do I go next?" The dispatcher needs "What is going wrong right now?"
| User | Main question | What the screen must give |
|---|---|---|
| Customer or receiver | When will it arrive? | Status, expected time, driver call button |
| Sender or shop owner | Was it delivered? | Order list, proof, failed delivery reason |
| Driver | What do I do next? | Next stop, address, call, navigate, confirm |
| Dispatcher | What needs action? | Late orders, unassigned orders, failed deliveries |
Mixing these users into one app with one menu is a common mistake. Build separate apps, or separate sections chosen by login role, and keep each simple. See admin dashboard UI/UX design for the office side.
What should an order tracking screen show?
The order tracking screen should show the current stage, the expected delivery time and one clear action. A map is helpful only in the last stage, when the driver is close.
Build the screen in this order, top to bottom:
- A headline status in plain words: "Out for delivery" or "Arriving by 4 pm".
- A stage line with 4 to 5 steps: Placed, Picked up, In transit, Out for delivery, Delivered. The current step is clear and past steps are ticked.
- A map, only after the driver is on the way, with the driver's name and a call button.
- Order details: what, from whom, to which address.
- A help button that opens WhatsApp or a call with the order number already included.
Write a time range, not a false exact minute. "Between 3 and 5 pm" is more honest than "3:12 pm". If the parcel is delayed, say so and give a new time. People forgive delay when they are told. They do not forgive silence.
Many tier-2 and tier-3 customers prefer status updates by SMS or WhatsApp rather than opening an app. Send a link that opens the tracking page without a login. See notification UX for push, SMS and WhatsApp.
How should a driver app be designed?
A driver app should show one task at a time, use very large buttons, and work with poor network. A driver is often on a bike, holding a parcel, in sunlight, with one free hand.
Rules I would follow:
- One stop on screen. Show the next delivery with name, address and phone. Do not show a long list unless the driver asks.
- Three main buttons: Call, Navigate and Delivered. Each at least 48 pixels high, with labels, not only icons.
- Navigation hand-off. Open the phone's maps app with the address, rather than building a map from scratch.
- Offline first. Let the driver mark a delivery with no network and send it later. Show a small "will sync" note.
- High contrast. Dark text on a light background for daylight. A dark mode can help at night. See dark mode UI design guide.
- Language choice. Hindi, Bengali or other local languages in the driver's own words. See regional language app design in India.
- Low battery and data use. Many drivers use mid-range phones with limited storage.
The day plan matters too. At the start of a shift, the driver sees "14 parcels, 3 pickups" and a start button. At the end, a short summary of delivered, failed and cash collected. If the business collects cash on delivery, the app must record how much the driver holds, because that number causes arguments if it is vague.
How does proof of delivery work?
Proof of delivery is the record that shows a parcel reached the right person. The usual choices are an OTP from the receiver, a photo of the parcel at the door, a signature on the screen, or a combination. The right choice depends on the value of the parcel and your business rules.
How each works in the design:
- OTP (one-time password). The receiver gets a code by SMS. The driver types it in. This is quick and hard to fake, but it fails if the receiver has no signal.
- Photo. The driver takes one picture. The app must say "Photo saved" clearly and compress the file for slow networks.
- Signature. A box on the screen for the receiver to sign with a finger. Good for business parcels.
- Received by. A name field if someone else took the parcel, such as a neighbour or a guard.
Failed deliveries need a screen too. Offer short reasons: "Receiver not available", "Address not found", "Refused", "Phone not reachable". Let the driver add a photo, and let the dispatcher reschedule in one step. Which proof is required for which parcel is a business decision. A designer should ask for it before drawing the screen.
What does the dispatcher or admin panel need?
The dispatcher panel should be an action list, not a map. A map with 40 moving dots looks impressive and helps nobody.
Give the dispatcher these views:
- Needs attention: late, unassigned and failed orders at the top.
- Assign in bulk: select many orders, pick a driver, done.
- Driver list: name, current stage, deliveries done today.
- Search by order number or phone number. See search and filter UX design.
- Daily report: delivered, failed, pending and cash collected.
Plan the roles early. A dispatcher, an owner and a branch manager may need different permissions. Each role should see only what it needs.
What mistakes do logistics apps make?
Most mistakes come from designing the app around the map and not around the task.
- Too many statuses. Fifteen internal stages confuse the customer. Show 4 or 5 and keep the rest internal.
- No driver call button. The customer then calls the office.
- Small buttons. A driver with a parcel in one hand will mis-tap.
- Needing constant internet. Network drops in lanes, lifts and basements.
- No failed delivery flow. The app only knows success.
- Login walls for tracking. The receiver should not need to install an app or create an account.
- No empty and error states. See empty states, loading and error screens.
Map the flow before drawing screens. My own process has five stages: Understand, Map the flow, Wireframe, Design the interface, and Prototype and hand off. See the mobile app design process.
If you are planning a delivery or logistics product, you can explore my mobile app design service or start a conversation through the contact section.
Frequently asked questions
What should a delivery tracking screen show?
The current status in plain words, a time range for arrival, a stage line with four or five steps, order details and a help button. Show a map only when the driver is close.
How do drivers confirm delivery in an app?
Common options are an OTP from the receiver, a photo, a signature or a received-by name. The business decides which proof is needed for which parcel.
Should the driver app work offline?
Yes. Network is weak in many lanes and buildings, so drivers should be able to mark a delivery with no signal and let the app sync later.
Do customers need to install an app to track a parcel?
They should not have to. A tracking link sent by SMS or WhatsApp that opens without login works better for most receivers.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.