GBCORP BLOG · IT SERVICES

Courier App Development: Dispatch, Drivers and Proof

Published May 7, 2022 · 6 min read

A courier business has three users who never meet: the customer who books, the driver who carries, and the dispatcher who keeps the day moving. Courier app development is really three apps that share one order, and the engine for that already exists.

Courier App Development: Dispatch, Drivers and Proof

Courier app development is often quoted as a year-long project because it has three surfaces and a lot of moving parts. The parts are the same for every courier: book, price, assign, collect, track, deliver, prove, invoice. GBCORP runs them as a white-label delivery engine, so a courier business configures its zones, prices and drivers and is live in days, and commissions custom work only for what is genuinely different about its operation.

Three users, one order

UserWhat they doWhere
CustomerBook a pickup, get a price, pay, track live, receive proof of delivery, view historyApp and web
DriverSee assigned jobs, navigate, scan or photograph at pickup and drop, collect signatures, update statusDriver app
DispatcherIncoming jobs, assignment by zone or manually, live map, exceptions, invoicing, reportsConsole

Pricing that matches the business

By zone, by distance, by weight or size, by urgency, by time window, or a combination. Business customers on account with monthly invoices; walk-in customers paying by card through the courier’s own gateway. Surcharges for waiting, failed delivery and returns. All of this is configuration in GBCORP’s engine, which is what keeps the launch to days rather than months.

Tracking and proof

Live location for the customer while the job is active. Status changes at each step with a timestamp. Photo, signature or code at delivery. A proof-of-delivery document e-mailed from the courier’s own domain and stored against the job. Disputes fall away when the proof is a tap and not a phone call.

Where custom work is worth it

Route optimisation across hundreds of stops a day. Integration with a customer’s warehouse or e-commerce system so orders arrive without re-typing. Multi-leg journeys through hubs. Temperature or chain-of-custody records. Each is scoped in a week and quoted per release on top of the engine, and most courier businesses need one of them, not all.

Checklist before launch

  • Zones drawn with prices, minimums and hours; surcharges written down.
  • Vehicle types and what each can carry.
  • Drivers with phones, and whether they are staff or partners paid per job.
  • Account customers listed with billing terms; a payment-gateway account for card customers.
  • Proof-of-delivery rule: photo, signature, code or all three.
  • The three numbers to watch: on-time rate, failed deliveries, jobs per driver per day.

The numbers to expect

White-label: live within days, flat monthly plan, no per-job fee. Custom extensions: scoped in a week, quoted per release. Courier businesses that move bookings from phone and messages to the app typically see dispatcher time per job fall by more than half in the first quarter, because the booking arrives complete and the proof arrives itself.

Business customers and accounts

Most courier revenue comes from a few business customers who send parcels every day: clinics, retailers, law firms, e-commerce sellers. The app gives each an account with saved addresses, negotiated rates, a booking screen their staff can use without training, and a monthly statement generated automatically. Where the customer runs an online shop, orders arrive by API and the courier never re-types an address. The console shows revenue by account and the jobs that were late for each, which is the conversation a courier wants to have before the customer has it.

The dispatcher’s day

Bookings arrive complete: pickup, drop, size, time window, price already agreed. The board sorts them by zone and window. Assignment is automatic by zone with a manual override, and the map shows every driver live. Exceptions surface on their own: a failed pickup, a customer not answering, a driver running late against the window. The dispatcher works the exceptions rather than the whole list. Proof of delivery arrives from the driver’s phone and the job closes itself. At the end of the day the report shows on-time rate by zone and jobs per driver, and the invoices for account customers are already drafted.

Drivers as staff or partners

A courier with its own vans assigns jobs to employees and pays wages. A courier working with independent drivers offers jobs, lets drivers accept them, and pays per job with a statement at the end of the week. Many run both. The driver app handles either: jobs can be assigned or offered, earnings are shown per job and per period, and the console produces the payout report. Ratings from customers and lateness by driver sit beside earnings, so the dispatcher knows whom to offer the urgent job. All of it is configuration, and the choice can change per zone or per time of day.

What changes in the first quarter

Week one, bookings arrive complete and the phone rings less. Month one, proof of delivery ends the dispute calls and account customers stop asking where their parcel is. Month two, the on-time report by zone shows where the promised windows are wrong and the prices are corrected. Month three, the courier reads jobs per driver per day and plans the fleet from data rather than feel. The wish list for custom work, if any, is short and specific by then, which is when it is worth quoting.

Questions we hear first

Can drivers use their own phones?

Yes. The driver app runs on any modern iOS or Android phone.

Can business customers book by API?

Yes. Account customers can integrate their systems so orders arrive without re-typing.

Does it work across cities and countries?

Yes. Zones, currency, tax and payment provider are configured per market, and the app is multilingual.

What does it cost?

A flat monthly plan; customised or more complex functionality is quoted separately before any work starts.

Where to start

The GBCORP White-Label Delivery App carries the courier engine; the GBCORP white-label app range shows the customer portal and console beneath it. For the food and retail side of delivery, read building an app like DoorDash.

GBCORP operates across 17 countries on 4 continents through six pillars: AI & IT, Innovation, Sustainability, Infrastructure, Business Lounge, and EV's & Solutions.