Building a Shipping or Delivery Tracking App for a Small Business
Tracking, driver and dispatch apps are three different products. How to pick the one you need first and scope a release that ships in weeks.
"We need a shipping app" can mean three very different products. A customer-facing tracking app that shows where a parcel is. A driver app that tells couriers where to go and records proof of delivery. Or an operations tool that lets a small team create shipments, print labels and see what is late. Most small businesses need one of these first, not all three, and the quote changes a lot depending on which one you pick.
This guide walks through what each version needs, the parts that quietly drive cost and review time, and how to scope a first release that ships in weeks instead of quarters.
Start with who holds the phone
Customers. They want status, a reliable estimate and a way to reach someone. That means order lookup, a timeline of status events, push notifications on changes and, optionally, a live map in the final stretch. Customers rarely need an account for this. A tracking link or order number is often enough.
Drivers or couriers. They want a route, the next stop, the customer's instructions and a fast way to mark something delivered or failed. This is where location tracking, offline support and proof of delivery live, and it is usually the most expensive app of the three.
Your team. Dispatchers and owners want to create and assign shipments, see exceptions and answer "where is it?" without calling a driver. That is usually best as a web admin panel, not a phone app. Our guide on why your app needs an admin panel explains why this piece is easy to underestimate.
Features that matter in version one
- A clear status model. Created, picked up, in transit, out for delivery, delivered, failed, returned. Decide the states and who can change them before any screen is designed. Most bugs in delivery apps are really disagreements about status.
- Push notifications on status changes. Keep them few and specific. Out for delivery and delivered are the two people actually want. Our guide to push notifications people do not mute covers the rest.
- Proof of delivery. A photo, a recipient name and, where needed, a signature captured on the driver's phone, stored with the shipment and visible to your team.
- Barcode or QR scanning. Phone cameras handle common barcode formats well, which removes manual typing at pickup and drop-off.
- Offline tolerance. Drivers lose signal in basements, loading docks and rural roads. The app should record a delivery offline and sync it later without losing the photo.
Location tracking is where review time goes
Live tracking is the feature everyone asks for and the one app stores scrutinise most. Tracking a driver while the app is open is straightforward. Tracking in the background, with the screen off, is a separate permission on both platforms. Apple requires a clear purpose string and expects the app's description to explain why background location is needed. Google Play requires a background-location declaration and can reject apps that do not show a core need for it.
Two practical consequences. First, decide whether you really need continuous background tracking or whether updates at each stop, plus live location only during the active route, are enough. The second option is simpler to build, kinder to batteries and easier to get approved. Second, write the permission explanation early and keep it honest. Our guide to app store review rejections covers how vague permission requests turn into rejections.
Carrier integrations: build, connect or skip
If you ship through national carriers, you do not have to invent tracking. UPS, FedEx and USPS offer developer APIs for rates, labels and tracking events, and multi-carrier services such as EasyPost and Shippo wrap several carriers behind one integration. If you run your own couriers, you own the tracking data and need the driver app instead.
- Carrier shipments only: a customer app plus a carrier or multi-carrier integration may be all you need.
- Own fleet only: a driver app, a customer tracking view and an admin panel.
- Both: start with whichever carries most of your volume and add the other in a second phase.
Each integration has its own account setup, keys, rate limits and test environment. Treat every carrier as a separate line item when you compare quotes.
Backend choices that keep it simple
For most small operations, a managed backend such as Firebase covers authentication, a real-time database for shipment status, file storage for delivery photos and cloud functions for notifications and carrier webhooks. Real-time listeners make a status timeline update on the customer's screen without them pulling to refresh. Our Firebase backend planning guide walks through the data model questions to settle first.
Two decisions are worth making in writing before development starts: how long you keep location history and delivery photos, and who can see them. Location data is personal data, and your app's privacy disclosures in both stores must match what you actually collect. Our guide to privacy labels and data safety forms explains what those forms ask.
What drives the price
The same four questions decide most delivery-app quotes:
- How many apps? A customer app alone is far smaller than customer plus driver plus admin.
- Background tracking or stop-based updates? Continuous tracking adds engineering, battery tuning and review work.
- How many integrations? Each carrier, payment provider or point-of-sale system is its own project.
- Offline requirements? Reliable offline capture with photo sync takes deliberate design and testing.
Our breakdown of what a custom mobile app actually costs goes deeper on each driver. As a rule of thumb, scope the smallest version that removes your most expensive phone call, usually "where is my order?", and add the rest once it is working.
A realistic first release
- Customer tracking by order number or link, with a status timeline and two push notifications.
- A web admin panel to create shipments, assign them and mark exceptions.
- If you run couriers: a driver app with stop list, scanning, photo proof of delivery and offline sync, with live location only during active routes.
- One carrier or multi-carrier integration if you also use national carriers.
That scope answers the questions customers actually call about, gives your team one place to look and keeps app store review predictable. Everything else, route optimisation, ratings and loyalty, can follow once you have real delivery data.
CrateShip Studios builds custom and white-label Flutter apps for small businesses, with full source code included and accounts held in your name. If you are planning a tracking or delivery app, tell us what your drivers and customers do today and we will help you scope version one.
White-label Flutter apps, delivered in 30-60 days, from $2,500 - full source code included.
Get started