The challenge
A delivery and e-commerce business in Thailand wanted its own parcel delivery software with a driver app, built around how its office and drivers work.
Office staff had to book parcels, hand them to drivers and know where each one stood. Drivers needed to confirm they had the right package, find the next drop and prove it had been delivered.
Thai addresses added their own layer. Every order had to fit the country's structure of provinces, districts and sub-districts, and pickup points had to be managed alongside them.
The business also wanted a record of the distance and fuel behind each run, captured by drivers on the day rather than reconstructed later.
What we built: parcel delivery software with a driver app
We built two connected parts that share one set of orders.
The web admin panel. Office staff enter sender, receiver and parcel details for each order. They manage:
drivers and other users;
provinces, districts, sub-districts and pickup points, so every order follows the Thai address structure;
driver records with license details, attachments and a status of pending, approved, on hold or barred.
Only approved drivers go out on deliveries.
The Android driver app. It lists the parcels to deliver and shows the route to the next order. A QR scan confirms the package and shows its delivery address.
At the door, the driver marks the order complete and the customer signs on the phone. If the drop fails, the order stays pending, with a reason recorded.
Mileage and fuel. At the start and end of each run, drivers photograph the odometer and their fuel receipts. Those photos sit with the run in the system.
Both the admin panel and the driver app include delivery reports.
How it works day to day
Follow one driver through a morning. She opens the app and photographs her vehicle's odometer and fuel receipt before setting off. The app lists the parcels assigned to her, and she scans each one's QR code to confirm it is the right package and check where it is going.
The app shows the route to her first drop. At the door, the customer signs on her phone and she marks the order complete.
At the next address nobody answers, so she marks that order pending and records why. Office staff see both outcomes without calling her.
At the end of the run, she photographs the odometer and fuel receipt again. The distance and fuel for the day sit with her run instead of on a slip of paper.
The result
Staff can now book a parcel, assign it to a driver and check its status in one system. Every completed drop carries a signature, and every pending one carries a reason. Mileage and fuel evidence arrives as photos on the day, not as paper at the end of the month.
This was the first part of a wider platform for the same business. A warehouse system, a partner shop portal and a shopping app followed.
What the research says
Most phones in Thailand run Android. Android held 73.96% of Thailand's mobile operating system market in September 2026, and iOS 26.01%, according to web analytics firm Statcounter (Statcounter). An Android driver app covers the phones most drivers are likely to carry.
One language family across the stack. GitHub's Octoverse 2025 report found that TypeScript overtook Python and JavaScript in August 2025 to become the most used language on GitHub (GitHub Octoverse 2025). The admin panel, driver app and API here are all built in that JavaScript family, with React, React Native and Node.js. One team can maintain every part.
Personal data is costly to lose. IBM's 2026 Cost of a Data Breach report puts the global average cost of a breach at $4.99 million (IBM). Delivery records hold names, addresses and signatures, which is one reason only drivers an admin has approved go out on deliveries.
Where AI fits next
The drivers and office do not use AI today, but the run data opens a few doors. A model could read fuel receipts and odometer photos so staff only check the figures. It could suggest the order of drops for each driver from the day's addresses, and summarize pending reasons to show which areas fail most often.
Planning something similar?
Before you build parcel delivery software for your own fleet, it helps to answer four questions:
What counts as proof of delivery for your customers: a signature, a photo or both?
How will drivers confirm they have the right parcel before they leave?
Which costs, such as fuel and mileage, must be evidenced per run?
Which parts of a wider platform, such as a warehouse or shop app, might come next?
Weighing a courier package against your own build? Our custom versus off-the-shelf guide helps. You can also read how we approach custom software and driver and field apps, and see our e-commerce and delivery work.
Other projects like this one are collected on our operations and logistics page.
