Courier and parcel business software runs a high-volume, low-value-per-unit network: booking at counters and franchises, manifesting between hubs, line-haul movement, delivery runs with attempts and outcomes, returns to origin, COD collection and remittance up the chain, settlement between branches, and the unit economics that decide whether the network is viable. With Pentoggle, a courier operator can describe how the network actually works and generate the starting application around it.
The economics of this business are unlike the rest of logistics. A transporter's problem is a hundred trips worth thousands each. A courier's problem is a hundred thousand shipments worth a hundred each, where a single re-attempt can consume the margin on several of them.
Many courier businesses already run Tally for accounting. That stays where it is. What is often still managed outside it is the network: what each branch booked, what is in transit between hubs, what failed delivery and why, and how much COD money is sitting in branches that has not come up.
Key takeaways
- The unit of cost is the delivery attempt, while the unit of revenue is the shipment. First-attempt success rate is therefore the strongest lever on margin in the business.
- COD money moves through the network before it reaches the company, which makes remittance ageing a control question rather than an accounting one.
- Booking branch and delivery branch both incur cost on the same shipment, so settlement between them decides whether branch-level profitability means anything.
- Failure reasons matter more than failure counts, because they separate problems you can fix from problems the consignee owns.
- A useful number is first-attempt delivery rate, read alongside cost per shipment.
How a courier business makes money
Revenue is per shipment, priced on weight, distance and service level, with volumetric weight applying to bulky items. Corporate and e-commerce accounts are contracted at negotiated rates with volume commitments. Retail counter bookings pay list price. COD shipments may carry a collection fee on top of freight.
Cost is where the business is decided, and almost all of it is per touch rather than per shipment. Pickup, booking, bagging, line-haul, hub handling, delivery run, and each additional delivery attempt. A shipment delivered first time consumes one delivery cost. The same shipment delivered on the third attempt consumes three, plus two failed-attempt records, plus a customer service interaction, plus in some cases a return to origin, which is a whole second journey with no revenue at all.
That structure means volume alone does not produce profit. A network can grow shipments steadily and lose money if the attempt ratio drifts, and the drift is invisible in any report built around shipments rather than attempts.
The spreadsheet is often not the problem
A booking register at each branch and a consolidated sheet at head office can run a small network.
The trouble starts at identifiable points.
When shipments are counted but attempts are not
The branch delivered nine hundred shipments this month. It made eleven hundred and forty delivery attempts to do it. Only the first number is in the report, and the second is the one that cost money.
When COD sits in branches
Cash collected at delivery accumulates at branch level and comes up on its own rhythm. Total COD outstanding across the network, and how old each branch's balance is, are questions a spreadsheet answers slowly and late.
When a shipment is between branches
Booked at one branch, in transit, and not yet received at the delivery branch. During that window it belongs to nobody's register, which is exactly when customers ask about it.
When the network grows past head office
Twenty branches and franchises each maintaining their own record means head office consolidates rather than knows, and consolidation always lags.
What courier and parcel software holds
Booking
Consignor, consignee, weight and dimensions, service type, freight terms, COD amount where applicable, and the tracking number.
Branch and franchise network
Branches, franchises, their service areas, rate arrangements and settlement terms.
Manifests and line-haul
Bags and shipments moving between hubs, with despatch and receipt confirmed at both ends.
Delivery runs and attempts
Shipments assigned to a delivery person, each attempt recorded with outcome and reason for failure.
COD collection and remittance
Amount collected, held at branch, remitted upward, and reconciled against the shipments it belongs to.
Returns to origin
Undelivered shipments moving back, with the reason and the cost recorded.
Branch settlement
Revenue shared between booking and delivery branches, franchise commissions, and what each owes the other.
Unit economics
Cost per shipment and per attempt against revenue per shipment, by branch and by account.
Attempts, not deliveries
The single most useful change a courier business can make to its reporting is to count attempts.
A delivery attempt has a cost whether or not it succeeds. The delivery person travelled, the shipment was carried, the time was spent. A first-attempt delivery consumes one unit of that cost. A third-attempt delivery consumes three, and has also generated two customer service contacts and occupied hub space for two extra days.
Most courier reporting counts deliveries and treats failures as an operational annoyance rather than a cost line. Inverting that makes the economics legible. If a branch delivers nine hundred shipments using eleven hundred and forty attempts, its attempt ratio is about 1.27, and any improvement in that ratio drops straight to margin without a single additional shipment being sold.
The reason to record the failure reason and not just the failure is that reasons sort into different owners.
Consignee not available, premises closed and consignee refused are consignee-side. They are addressed with better delivery-window information, a call before the run, or a change of service terms for that account.
Address incomplete and consignee not traceable are booking-side. They originate at the point the shipment was accepted, frequently with a corporate account whose address data is poor, and they are fixed upstream.
Out of delivery area, vehicle breakdown and time exhausted are yours. They are routing, resourcing and planning problems.
A failure count tells you the branch is struggling. A failure reason distribution tells you which of the three conversations to have, and they are entirely different conversations.
COD is other people's money in your branches
A COD network collects cash at the door and moves it up through the same structure that moves parcels down. Structurally this is a large number of small collections held briefly by a large number of people, which is a control problem regardless of how trustworthy anyone is.
Three things need to be visible and usually are not.
Total COD outstanding across the network. Not what was collected this month, but what has been collected and not yet remitted, right now.
Ageing by branch. A branch remitting every second day and a branch remitting every eleventh day may report the same monthly total while representing very different exposures.
Reconciliation to shipments. Each collection belongs to a specific shipment with a specific amount. Remittance reconciled in bulk against a branch total will balance while individual discrepancies pass through unnoticed.
The other half is the outward obligation. COD collected belongs to the consignor and has to be paid over to them on agreed terms. A business holding COD beyond its agreed remittance terms is effectively using money that is due to the consignor for longer than agreed, so the exposure should be treated as a deliberate working-capital and control issue rather than something that happens by accident.
Because the collection is recorded at the door, the same phone entry that records the delivery should record the amount collected. Splitting the two creates a reconciliation task that would not otherwise exist.
Workflows this business depends on
- Last-Mile Delivery Software, for the delivery run itself.
- Proof of Delivery Software, captured at the door alongside COD.
- Shipment Tracking Software, for the status customers and consignors expect.
- Route Planning and Optimization Software, for sequencing delivery runs.
- Delivery Management Software, for the operational picture across runs and branches.
- E-commerce Logistics Software, where marketplace accounts and returns dominate the volume.
Why courier businesses choose Pentoggle
Attempts counted, not just deliveries
Every attempt recorded with its outcome and reason, so the ratio that decides margin is visible by branch and by account.
COD tracked to the shipment
Collected, held, remitted and reconciled per shipment rather than per branch total, with ageing across the network.
Built for the branch and franchise network
Booking branch, delivery branch, franchise commissions and settlement between them.
Built for the phone
Delivery outcome, failure reason, COD and POD recorded at the door in one entry.
Sits around your accounting
Tally and comparable systems continue handling accounting, invoicing and GST. Pentoggle adds the operational layer around bookings, manifests, attempts and remittance.
A useful number for a courier business
First-attempt delivery rate, read alongside cost per shipment.
First-attempt rate is the cleanest lever in the business because it improves cost without requiring a single extra shipment, and because it improves customer experience at the same time, which is rare.
Read cost per shipment beside it, because the two together show whether an improvement is real. A branch that lifts its first-attempt rate by calling every consignee before delivery has improved one number and added a cost that may exceed the saving. Only the pair shows the net effect.
Segment by account as well as by branch. Corporate and e-commerce accounts frequently differ enormously in first-attempt rate because of address data quality, and an account that looks profitable at contracted rates can be loss-making once its attempt ratio is counted. That is a rate renegotiation supported by evidence rather than by assertion.
Ready to build software for your courier network?
Your report says you delivered nine hundred shipments.
It does not say you drove out eleven hundred and forty times to do it.
Describe how your branches, manifests and delivery runs actually work to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.