ERPNext for couriers who settle COD before the
morning meeting.
Driver session closes at the desk. Corporate billing built from confirmed deliveries. Routes assigned by zone, not by guesswork.
6 wks
Typical go-live
5 min
COD reconciliation
Auto
Corporate billing
Common Challenges
The problems every UAE courier company faces.
COD that reconciles itself. Corporate billing that doesn't take three accountants and a spreadsheet. Routes that don't get re-explained on WhatsApp every morning. The patterns are the same across every UAE courier we work with.
COD collections reconciled manually every evening
Drivers return with cash and a paper manifest. Someone spends an hour cross-referencing deliveries against the system. Disputes happen daily. Unreconciled amounts carry forward and grow.
How we solve it
Each driver has a delivery session in ERPNext. Deliveries confirmed digitally. COD collected is recorded per shipment. Session close reconciles what was collected against what was expected, automatically, in minutes.
Shipment status not visible to corporate clients in real time
Operations teams spend hours answering status calls. Corporate clients have no self-serve visibility. Billing disputes arise because clients cannot verify delivery confirmations before the invoice arrives.
How we solve it
Shipment status updated at each scan or driver confirmation in ERPNext. Corporate clients can access their own delivery reports. Invoices generated only against confirmed deliveries. No disputes over unverified shipments.
Route planning and driver assignment done over WhatsApp
Dispatch managed informally. Drivers take wrong routes. Deliveries in the same area split across different drivers. Fuel costs high, coverage inconsistent, and there is no record of what was assigned to whom.
How we solve it
Delivery routes configured in ERPNext with zone-based driver assignment. Each shipment assigned to the correct driver by delivery area. Dispatch manager sees all active routes and delivery status on one screen.
Corporate client billing delayed because data is not consolidated
Monthly billing for corporate accounts requires manually pulling delivery data, calculating chargeable shipments, and building an invoice in Excel. It takes days and errors are common.
How we solve it
Corporate contracts configured in ERPNext with rate cards per shipment type, weight band, or zone. Billing runs automatically on a weekly or monthly cycle against confirmed deliveries. Invoice generated in one click.
How It Works
Your delivery cycle inside ERPNext.
From shipment booking to corporate invoice, every step in one system.
Booking
Shipment created with sender, receiver, weight, and COD amount. Service type and zone assigned.
Pickup
Driver confirms pickup. Shipment status updated. COD expected amount recorded.
Hub Sort
Shipment received at hub. Sorted by delivery zone. Outbound manifest created.
Dispatch
Driver manifest issued. Route confirmed. Delivery sequence optimised by zone.
Delivery
Driver confirms delivery. POD captured. COD collected and recorded per shipment.
Billing
Corporate client invoice generated from confirmed deliveries. COD reconciled per driver session.
ERPNext Modules
What we configure for courier.
These are the modules that matter for a UAE courier business, configured for your delivery workflow, COD operations, and corporate billing.
Shipment Management
Shipment lifecycle from booking through delivery confirmation, with status updates at every scan point.
- Shipment creation with sender, receiver, weight, and service type
- Status updates at pickup, hub receipt, out for delivery, and delivered
- Proof of delivery capture with signature or photo confirmation
COD Reconciliation
Driver-level cash collection tracked per delivery and reconciled at session close, with discrepancy alerts and escalation workflow.
- COD amount recorded per shipment at delivery confirmation
- Driver session close reconciles collected vs expected cash
- Discrepancies flagged and assigned for follow-up immediately
Route & Zone Management
Delivery zones configured with driver assignment, route sequencing, and capacity management per vehicle or driver.
- Zone-based automatic driver assignment at dispatch
- Daily route summary per driver with delivery list
- Capacity management by shipment count or weight per vehicle
Corporate Billing
Rate cards per corporate client with automated billing cycles and invoice generation against confirmed deliveries only.
- Client-specific rate cards by zone, weight, or service level
- Automated weekly or monthly billing cycle per client
- Invoice generated from confirmed deliveries, not estimates
Returns Management
Failed delivery and return workflows with reason codes, re-attempt scheduling, and return-to-sender processing.
- Failed delivery reason codes recorded at driver session
- Re-attempt scheduling triggered automatically
- Return-to-sender process with cost recovery from shipper
Hub & Warehouse Operations
Inbound sort, manifest creation, and outbound dispatch managed within ERPNext for hub-based courier operations.
- Inbound shipment receipt and sort by zone
- Driver manifest creation from daily dispatch queue
- Hub transfer tracking for multi-hub networks
Client Result
A real courier implementation.
The Situation
Luxury LS called me with a brief that felt impossible. They were starting a courier service, Luxury Express, from zero. No couriers, no customers, no routes. They wanted the entire digital backbone built before the first shipment was ever picked up. A rider app. A customer portal. Bulk shipment upload. Live tracking. ERPNext as the core. Ten-plus couriers across the GCC. Thirty thousand shipments per month. And the timeline was narrow. I'd never built courier software. I had no app developer. I knew none of it.
What We Did
After the first meeting, before the contract was signed, I hired a fresh app developer. No project to put him on yet, just a feeling that if this came through, I'd need someone the next morning. The deal closed a couple of weeks later. We delivered the first version of the rider app in weeks: pickup flow, delivery confirmation, POD capture, COD handling. Then the customer portal: booking, bulk Excel upload, live tracking. Then the ERPNext core: billing, COD reconciliation, driver payroll. Luxury Express went live with no paper, no spreadsheets, no WhatsApp coordination. Day one was digital. That hire I made before the deal? He's still my lead app developer. Sometimes the best decisions are the ones you can't justify yet.
Outcomes
Operations launch
Digital from day one — no paper process
Target scale
30,000 shipments per month, infrastructure ready
Time to first app
Weeks from developer hire to working rider app
New industry
Courier built from zero with no prior experience
Questions
Questions courier companies ask us.
How does COD reconciliation work in ERPNext for courier businesses?
Each driver operates a delivery session in ERPNext. When they confirm a delivery, the COD amount collected is recorded against that shipment. At end of day, the driver closes their session and ERPNext automatically reconciles what was expected — the sum of all COD shipments on their manifest — against what was recorded as collected. Any difference is flagged as a discrepancy and assigned for follow-up. The whole process takes minutes instead of hours.
Can we set different rate cards for different corporate clients?
Yes. ERPNext pricing rules allow you to configure client-specific rate cards with rates varying by zone, weight band, service level, or any combination. When a shipment is booked for a corporate client, the correct rate is applied automatically. Billing at end of cycle pulls confirmed deliveries and applies the contract rate to generate the invoice. No manual calculation required.
How do we handle failed deliveries and re-attempts?
When a driver marks a delivery as failed, they select a reason code — no one home, address not found, refused, and so on. ERPNext creates a re-attempt task for the next working day and notifies the relevant team. If a maximum number of attempts is reached, a return-to-sender workflow is triggered. Return costs can be configured to be recovered from the shipper or written off based on your contract terms.
Can corporate clients view their delivery status themselves?
Yes. ERPNext has a customer portal where corporate clients can log in and view their own shipments, delivery statuses, and confirmed delivery reports. This reduces the volume of status calls to your operations team and gives clients the visibility they expect. The portal only shows the client their own data.
How long does implementation take for a courier company?
Typically 5 to 7 weeks for a courier business with standard pickup, delivery, and COD workflows. Complexity around multi-hub operations, integrations with e-commerce platforms, or custom corporate billing structures can extend this. We scope accurately during discovery so there are no surprises.
Courier & Delivery ERP
Send us a day from dispatch.
Send us a typical day from your dispatch. Number of drivers, COD ratio, corporate clients on monthly billing. We'll show you how ERPNext would handle that exact day.
We typically respond within a few hours during UAE business hours.