A Courier Management System Built Around the COD Money Trail
Shipment intake, driver runsheets, client portals and zone pricing for last-mile operators in Egypt and the Gulf, with cash reconciliation at the core.
A courier company rarely loses money on the tracking page. It loses it in the gap between what drivers collected in cash yesterday and what the accountant can prove today. COD reconciliation is where courier operations bleed money and client trust, and it is the part most off-the-shelf shipping tools treat as an afterthought. We build the system the other way round: the cash ledger comes first, and intake, runsheets, tracking and portals hang off it. Web Pioneer has built custom operational systems from Cairo since 2014 (commercial registration 206687), for courier and last-mile operators who need Arabic and English handled properly on the office screens and on the driver's phone.
The money trail first
Every shipment carries an expected-cash figure from intake to settlement. Drivers close out daily against a shipment-level ledger, so a missing 200 EGP surfaces that evening, not at month end.
One system, not five tools
Intake, dispatch, tracking and client statements read from one database. No re-typing between an Excel sheet, a WhatsApp group and an accounting file that never quite agree.
Bilingual by default
RTL office screens, bilingual client portals, and waybills that print correctly in either language. Our own builds are Arabic-first by habit, not as a bolted-on translation file.
Yours at final payment
The contract states that source code, database, server access and any app store accounts move to you when the last invoice clears. We also sign an NDA before you send us client data.
The modules, in the order that matters
COD ledger and driver settlement
Each delivered shipment posts an expected amount; each driver closes the day against it, short or over. Client settlements are generated from the same ledger, so what you pay out always ties back to specific waybills.
Shipment intake
Bulk Excel upload for the client who will never change, a REST API for the one who runs WooCommerce, and a manual entry screen for the walk-in. All three land in the same queue with the same validation.
Driver runsheets
Dispatch builds a runsheet by zone, prints it or pushes it to the driver's phone, and gets back statuses, failure reasons and collected cash. End-of-day closing takes minutes instead of an argument.
Client portal with live tracking
Each client logs in to their own shipments, COD statements and pickup requests, plus a public tracking link they can give their customers. Fewer 'where is my order' calls to your operations room.
Zone pricing engine
Per-client rate cards by zone, weight and COD fee, with effective dates so a price change on the first of the month does not corrupt last month's invoices.
Driver mobile app
A native app (Android first, since that is what drivers actually carry) for runsheets, proof of delivery photos and cash confirmation. Priced separately as an app build, see the note under pricing.
What a courier system costs
| Scope | Price range | Typical timeline |
|---|---|---|
| Core operations build: intake, runsheets, tracking | from $3,000 | typically 8-12 weeks |
| Full platform: adds COD ledger, client portals, zone pricing | $4,500 – 8,000 | 12-20 weeks in most projects |
| Large integrated: multi-branch, accounting sync, client APIs | from $8,000 | 20+ weeks |
A native driver app prices like an app MVP, $3,000 – 4,500 over 8-12 weeks, and we usually build it in parallel with the COD module so drivers are confirming cash against real ledger entries before launch. Every quote is itemised per module against a written scope document, and our published pricing and the Trust Center are open reading before you commit to anything.
How a build actually runs
- First conversation: we walk through your operation from intake sheet to cash drawer, and you will hear plainly whether a custom build is not worth it yet for your volume.
- Scope on paper: a written document lists every module, screen and acceptance criterion, and payments are split into instalments, each released only against work you can actually test.
- Test environment early: the system goes up on a private URL loaded with your real zones and a sample of real shipments, so dispatchers are poking at it weeks before go-live.
- Parallel run: one branch or one client runs on the new system alongside your old process until a full COD cycle, collection to client settlement, reconciles cleanly.
- Transfer and training: when the last invoice is settled, the code, database and server credentials pass into yours per the contract, with a recorded walkthrough so new staff can be trained without us.
Frequently asked questions
Our COD problem is drivers and clients disputing amounts. How does the system handle that?
Every cash event is recorded at shipment level: expected amount at intake, confirmed amount at delivery, driver closing at end of day, client settlement at cycle end. A dispute becomes a lookup of one waybill's history rather than a shouting match over a spreadsheet total. During the parallel run we deliberately reconcile a full cycle before you switch over.
Do you build the driver app as well?
Yes, and we recommend Android first because that is what sits in drivers' pockets. It is scoped and priced as a separate app build ($3,000 – 4,500, typically 8-12 weeks) running in parallel with the web system, sharing the same API and cash ledger.
Can our e-commerce clients push shipments in automatically?
That is the point of the intake API. Clients on WooCommerce or a custom store can create shipments, fetch statuses and pull COD statements without emailing your team a sheet. Clients who prefer Excel keep uploading Excel; both routes go through identical validation.
We already use a tracking tool. Why replace it?
Often you should not, and we will say so on the first call. Replace it when the tracking tool has become a front for a back office still run on paper and phone calls: that is when the ledger, runsheets and settlements need to live in one system. Tracking is the easy part; the money trail is the hard part.
Who owns the system when it is finished?
You do. The contract names you as owner of the source code, database, designs and any store or server accounts once the final instalment is paid, and we hand over credentials at that point rather than hosting you hostage. Company facts and registration details are published at /company/facts if you want to check exactly who is on the other side.
Stop reconciling COD in spreadsheets
Send us your current intake sheet and a rough daily shipment count on WhatsApp, and back comes a module-by-module scope and a fixed quote. Meetings run on your timezone; for Gulf clients that is a one-hour difference from our Cairo office.
