Mobile apps for transport and courier companies — customers, drivers, dispatcher
Looking for someone who builds the mobile app for your transport or courier company and already speaks your vocabulary? That's me. I've built three transport apps with real users in production: colet.app (a courier-management SaaS with 1000+ orders processed weekly, 5 connected order sources, a WhatsApp AI agent and a complete dispatcher panel), Ami Tour App (RO-UK courier on React Native with digital requests and AWB tracking), RO-VA Tours (multi-platform iOS, Android and PWA for parcel and refrigerated transport RO↔UK). Customer app, driver app, web dispatcher panel, integrations with invoicing systems and international AWB — all in one package. From RON 7,000 (about €1,400).
The real problem: generic apps know nothing about AWB, customs or dispatcher work
Take a moment and look at the tools your company uses today. Orders come in on WhatsApp and the phone — the secretary writes them down in Excel or directly on WhatsApp Web. Drivers get the addresses in the morning, when they get into the truck, by voice messages or SMS. The dispatcher has WhatsApp, Excel, Google Maps and a paper notebook open at the same time, with international AWB numbers scribbled in. The end customer has no place to check where their parcel is, so they call ten times a day. Your company processes hundreds of weekly orders on tools designed for something else.
Now try to find a ready-made app that solves your exact problem. Search Google for “courier company app”, “parcel transport app”, “TMS for small companies”, “transport dispatcher software”, “driver routing app”. You'll see either enterprise software for DPD/GLS that costs tens of thousands of euros a year, or generic delivery apps (Glovo, Tazz) that aren't for you, or invoicing-system extensions with no client tracking. Nothing in between for a company with 5–50 drivers running regular routes.
A generic order/delivery app doesn't know how to do the things that actually matter in transport: AWB scanning with the phone camera and validation of international format (UK, IT, DE), order assignment to a driver with two-way confirmation, route optimization with 25+ stops via Google Maps with reordering by constraints (refrigerated in the morning, fragile in the evening), proof of delivery with digital signature or photo + GPS + timestamp, per-trip reporting with a financial module that calculates settlements automatically, plus integration with electronic customs for international routes. These are the differences between a “nice app” and an “app that works for you”.
Plus the scaling part. If you want to sell the same platform to other transport companies (SaaS model), you need a multi-tenant architecture with strict data isolation — each company sees only its orders but shares the same infrastructure. That's not done from a template — it's built from the start with Row Level Security on Postgres, with per-organization authentication, with each company's own branding. And that's exactly what I did with colet.app, where setting up a new company takes under 30 minutes.
That's what I build for transport companies: industry-specific apps, not recolored templates. Cross-platform on React Native or Capacitor, full backend included (database, API, authentication, integrations), publishing in the App Store and Google Play. Pricing starts at RON 7,000 (about €1,400) for a customer app with orders and tracking, going up to RON 12,000–15,000 or more for a complete platform with customer + driver app + dispatcher panel + WhatsApp AI agent + customs/invoicing integrations. Payment is simple: 50% on confirmation, 50% on delivery. For the hub with site + SEO + GMB + app together, see /transport-ro-uk.
What you get from me — a complete app stack for your transport company
I don't just build the customer mobile app and leave you to find someone else for the driver app or the dispatcher panel. The package includes the entire mobile ecosystem, from the end user to the hand of your dispatcher.
Customer app with pickup request and tracking
Pickup request with parcel photo upload, address pre-filled from history, per-route price calculation before confirmation, real-time tracking with a branded link per company (your customer gets an SMS with a URL that shows your colors), push notifications at every status change, complete order history, optional online payment. Available on iOS and Android from one codebase.
Driver app with optimized routes and AWB scanning
Daily routes optimized through Google Maps API (in colet.app: 25+ stops per run, automatic reordering by constraints like refrigerated or fragile), AWB scanning with the phone camera (international format validation for UK/IT/DE), proof of delivery with digital signature or photo plus GPS and timestamp, offline mode for areas without signal, switching between runs if the driver works for multiple clients. A big “delivered” button that works with winter gloves on.
Web dispatcher panel with financial module
Automatic order sorting by route and priority, drag-and-drop assignment to drivers and trucks on the map, financial module that calculates per-trip settlements (including bonuses, balances, weekly reports), full per-customer history, complete event log per order (when picked up, when sorted, when assigned, when delivered), integration with your invoicing system. Everything the dispatcher does on Excel today, automated and error-free.
WhatsApp AI agent for automatic order intake
The customer sends you a WhatsApp message like “1 parcel 5kg, pickup today from Iași center, delivery to Manchester next week”. The AI agent automatically extracts the address, weight, route, date and creates the order in your system. Tech used in colet.app: WhatsApp Cloud API + Claude Haiku. That means you don't lose orders just because the secretary didn't get to write them down.
Multi-tenant architecture for SaaS platforms
If you want to sell the same platform to other transport companies (SaaS model), I build the architecture with strict data isolation from the start — Row Level Security on Postgres, per-organization authentication, each company's own branding (logo, colors, tracking links), independent settings. Each company sees only its orders but shares the infrastructure. In colet.app, setting up a new company takes under 30 minutes.
Transport-specific integrations
Integration with common Romanian invoicing systems (SmartBill, FGO, Saga, Oblio), integration with international AWB tracking systems, integration with electronic customs for non-EU routes, integration with payment systems (Stripe, Netopia, Romcard), plus integration with your own systems via API if you already have something internal.
Role-targeted push notifications
Notifications that actually reach the right person at the right moment. For the driver: new order assigned, route priority change, customs alert. For the dispatcher: driver stuck in traffic for more than X minutes, delivery confirmed, weekly settlement ready. For the customer: parcel picked up, in transit, out for delivery, delivered, plus delivery confirmations with a photo. No silent notifications nobody sees.
Store publishing and OTA updates
I handle the entire publishing process: developer account (or we use yours), screenshots, store-search-optimized description, privacy forms, code signing, Apple and Google review. For Capacitor-based apps, logic and content changes reach users in minutes via OTA, without waiting two weeks for Apple review. Critical for active fleets where you can't pause operations.
When needed: I add advanced components without sending you to another vendor — multi-vehicle route optimization with constraints (kg/m³ capacity, time windows, refrigerated truck), public API architecture if you want to offer integration to your partners, separate panel for major B2B customers with multi-account support, plus monthly maintenance adapted to your volume.
Transparent pricing
Official pricing, exactly as it appears on the pricing page. Payment is split in two: 50% on confirmation, 50% on delivery. All packages include a free consultation, 3 design directions to choose from, 30 days of free support and legal invoicing.
Why me, not a generalist developer or a capital agency
There are mobile developers everywhere. Very few have actually worked in transport and know exactly why a driver needs a big “delivered” button you can press with winter gloves on, or why the dispatcher needs to see in the panel whether a driver is stuck at customs. Here's what you get when you work with me.
Three transport apps shipped with real users
Not my first project in the niche. colet.app (SaaS platform for courier companies with 1000+ orders processed weekly, 5 connected order sources, 25+ stops per route, 100% automated financial management, new-company setup in under 30 minutes), Ami Tour App (RO-UK courier on React Native with digital requests and AWB tracking), RO-VA Tours (multi-platform iOS/Android/PWA for parcel and refrigerated transport RO↔UK). Plus collaboration with RegExpress on Romania–Italy routes.
End-to-end mobile stack in one hand
I build the entire stack — customer app, driver app, web dispatcher panel, server, database, integrations (WhatsApp Cloud API, Google Maps API, invoicing systems). You don't go hunt for two or three more vendors after I'm done. With colet.app, the entire stack was built solo: React, TypeScript, Supabase, Google Maps API, WhatsApp Cloud API, Claude Haiku, Capacitor, iOS.
Solo, accelerated by AI — fair pricing
I work alone, accelerated by AI (Claude Code and similar tools). You pay for the work, not for offices in Pipera, not for project managers. That means fast delivery (3–5 weeks for a standard app, 6–10 weeks for a complete platform with dispatcher and WhatsApp agent), direct communication and an honest quote based on the real complexity of your project.
I speak your vocabulary
I already know what AWB, ePOD, multi-tenant, refrigerated, sorting, per-trip settlement, proforma invoice for export, electronic customs mean. You don't need to explain to me what a consolidated run is or why a driver needs an offline mode. That cuts weeks off the initial discussion — we go straight to specifics.
Real case: colet.app, technical perspective on the app side
Here I go into the technical detail of the colet.app application — not just what it does, but how it's built, so you can see the level we work at for a transport company.
Small and mid-sized courier companies that processed orders on Excel and WhatsApp, with no tracking for the end customer, with dispatchers losing hours daily on manual sorting. We needed a platform that scales across multiple companies with slightly different flows, with fast setup for a new company, with multiple integrations (WhatsApp, Google Maps, invoicing) and with strict data isolation between companies.
Three integrated mobile/web pieces: the customer mobile app (Capacitor + React, parcel requests with photo upload, real-time tracking with branded link per company, optional online payment), the driver mobile app (Capacitor + React, Google Maps routes with 25+ stops automatically reordered, AWB camera scanning, delivery confirmations with signature and GPS), the web dispatcher panel (React + TypeScript, automatic sorting, driver assignment, financial module). On the back: Supabase (Postgres with Row Level Security for per-company isolation, authentication, server-side functions), WhatsApp Cloud API for automatic order intake via a Claude Haiku AI agent, Google Maps API for routing. Entire stack built solo.
Numbers verifiable directly on the colet.app portfolio page: 5 order sources connected to a single platform (admin, driver, company website, customer mobile app, WhatsApp AI agent), 25+ stops per route optimized with Google Maps, over 1000 orders processed weekly, 100% automated financial management (settlements, balances, weekly reports), new-company setup in under 30 minutes. Multi-tenant with Row Level Security: each company sees only its data but shares the infrastructure. Plus the other two apps shipped (Ami Tour App on React Native, RO-VA Tours multi-platform iOS/Android/PWA) — each built on similar principles.
How I work — the process for a transport app
The process is adapted specifically for transport-app projects. Here's how a typical engagement runs, from the first message to your app in production with real users.
Initial conversation focused on operations
30 minutes by phone or on Google Meet. You tell me your real volume (orders per week, active drivers, main routes, seasonality), current tools (WhatsApp, Excel, existing software), the daily problems that hurt the most. I tell you straight whether an app is the right answer (sometimes just a web panel without an app solves a lot, sometimes just a WhatsApp agent is enough to start) and estimate the real cost. Free, no obligation.
Flow map and prototype
I start from your real flows — how you receive the order, how you assign it, how the driver delivers it, how settlement works, how you handle exceptions (customer refusal, return, delivery to a different address). You get a functional map with three perspectives (customer, driver, dispatcher) and a prototype you can open on your phone, before any code is written.
Weekly sprints with TestFlight and Internal track
I work in one-week cycles. At the end of each week you have the app on your phone (TestFlight for iOS, Internal track for Google Play) plus a link to the dispatcher panel if the project includes it. Your dispatcher tests in parallel with me. Payment is split in two: 50% on confirmation, 50% on delivery — bank transfer, legal invoice.
Beta testing with two-three real drivers and the dispatcher
Before official publishing, the app goes through real testing with your team — two-three drivers on real routes, the dispatcher on full shifts, a few trusted customers placing orders. You tell me what doesn't work in real conditions (poor signal, gloves, sun on screen), I adjust. This stage is included, not billed separately.
Publishing, training and 30 days of active support
I publish the app in the App Store and Google Play (Apple and Google reviews take 1–7 days), set up OTA for fast updates, hook up monitoring for errors. Then I train your team — dispatcher, drivers, secretary. The first 30 days after publishing are included — fixes, adjustments, 24/7 monitoring of critical errors, no extra cost.
Frequently asked questions
How much does a complete app for a transport company cost?
From RON 7,000 (about €1,400) for a customer app with pickup request and tracking. From RON 12,000–15,000 for a complete platform with customer app + driver app + dispatcher panel + WhatsApp agent + basic integrations. For multi-tenant SaaS platforms with multiple companies and own branding, the exact price is set after the first call based on complexity. Payment is split in two: 50% on confirmation, 50% on delivery.
Can I integrate the app with my existing invoicing system?
Yes. I integrate with most common invoicing systems used in Romania (SmartBill, FGO, Saga, Oblio etc.), with international AWB tracking systems, with payment systems (Stripe, Netopia, Romcard) and with electronic customs for non-EU routes. If you have a non-standard or internal system, we can integrate via API. We discuss specifics on the first call.
Does the app work offline for drivers in areas with no signal?
Yes. For the driver app, critical flows (viewing the planned route, marking delivery with photo and signature, AWB scanning) work even without signal. Data syncs automatically when the phone is back online. Important for international routes and rural areas.
Can I start with a simple app and add dispatcher and WhatsApp agent later?
Yes, that's the approach I recommend for smaller companies. We start with the basic customer app (pickup request + tracking) at RON 7,000, see if users adopt it, then add the driver app, dispatcher panel, WhatsApp agent one at a time. Each new module costs less than building it from scratch, because we use the same infrastructure (server, authentication, database).
How long does the complete platform take to build?
3–5 weeks for a standard customer app. 6–10 weeks for a complete platform with customer app + driver app + dispatcher panel. For multi-tenant SaaS platforms with WhatsApp AI agent, 8–12 weeks. We start within 24–48h of confirmation. You get weekly demos on TestFlight and Internal track.
Do you work with transport companies outside Suceava county?
Yes, no problem. Most of the collaboration runs online — Google Meet, email, TestFlight links, WhatsApp messages. For companies in the Moldova region (Iași, Botoșani, Bacău, Vaslui) I'm close enough to come on site at no cost. For companies in the rest of the country we work online — I have clients much further (HarmonicSAR in Italy, RO-VA Tours on RO-UK routes), so distance isn't a problem.
Read more
Let's build your transport app — the first chat is free
Tell me your volume (orders per week, drivers, routes) and what tools you use today. Within 24 hours you get a written quote with the app structure, the price and the delivery timeline. No obligation, no aggressive follow-up calls.