Every Indian retail chain that ships its own online orders eventually asks the same question: hire riders and run a delivery fleet in-house, or keep paying courier aggregators like Delhivery, Shiprocket and Ecom Express a fee per shipment. Get the timing wrong in either direction and the cost shows up in the same place, your delivery margin. Tie up cash in vehicles and salaries you cannot fill with volume, and fixed cost eats you. Stay on aggregators past the point where your own density supports a fleet, and you keep paying a markup you no longer need to pay. There is no universal answer, but there is a clear way to work out which model fits your order volume, geography and store footprint right now.
What Is the Real Difference Between an Own Fleet and a Courier Aggregator?
An own fleet means your business directly employs riders, owns or leases the two-wheelers, and manages routing and payouts in-house. A courier aggregator means you hand every shipment to a third-party logistics company that picks up, moves and delivers it for a price set by its own network, charged per shipment. The practical difference is how the cost behaves. An own fleet is a fixed-cost model: you pay for rider and vehicle capacity whether you use it fully or not. A courier aggregator is a variable-cost model: you pay only for what you actually ship, at a rate the aggregator can offer because it spreads its hub and line-haul infrastructure across thousands of other shippers.
How Much Does an Own Delivery Fleet Actually Cost?
The real cost of an own fleet is rarely the rider's monthly payout alone. It is rider pay plus two-wheeler EMI or lease, fuel, third-party insurance, periodic maintenance, a dispatcher or route planner to assign orders, and uniforms or safety gear if you want a consistent brand experience at the doorstep. All of this is committed whether a rider delivers 10 orders that day or 40. That is why the number that actually matters is not cost per rider, it is cost per delivered order at your current density, and that number only looks good once a rider's daily order count climbs high enough to spread the fixed cost thin. A single store doing a handful of online orders a day will almost never clear that bar. A cluster of stores in the same city, feeding one rider pool, often will.
When Does a Courier Aggregator Make More Financial Sense?
A courier aggregator wins whenever your order volume is too low, or too scattered across pincodes, to keep a rider pool busy. It also wins when you are testing demand in a new city and do not yet know if volume will justify a permanent rider team there. Because an aggregator pools demand from thousands of shippers, it can offer a marginal price per shipment that an individual retailer below a certain density cannot beat by hiring directly. The tradeoff is less control: you inherit the aggregator's own cost structure, including weight discrepancy charges when a courier's scanned weight does not match what you billed for, and you inherit its network gaps, which is exactly how serviceability gaps in certain pincodes turn into RTO losses you never see coming until the return hits your warehouse.
Own Fleet vs Courier Aggregator: Side by Side
| Factor | Own Fleet | Courier Aggregator |
|---|---|---|
| Cost structure | Fixed, committed monthly | Variable, per shipment |
| Upfront investment | Vehicles, hiring, training | None, pay as you ship |
| Delivery control and branding | Full control of rider experience | Depends on aggregator SLA |
| Best suited for | Dense single-city or cluster orders | New cities, thin or scattered demand |
| Weight and RTO disputes | None, you control both ends | Recurring, needs active tracking |
| Scaling up volume | Slow, needs more hiring | Instant, aggregator absorbs it |
| Scaling down volume | Expensive, fixed cost stays | Instant, cost drops with volume |
How to Decide Which Model Fits Your Chain
Run the comparison on your own numbers before committing either way. The decision holds for one season at most, so revisit it as volume changes.
- Calculate your current cost per delivered order under the aggregator model, including the weight discrepancy and RTO charges you have actually been billed in the last two quarters, not the headline rate card.
- Map your order volume by pincode for the same period, and separate pincodes where you already run three or more physical stores from pincodes where you have none.
- Estimate the fixed monthly cost of a small rider pool, two to four riders plus a dispatcher, only for the dense pincodes identified above, and divide by the order volume those pincodes actually generate.
- Compare that per-order cost against your current aggregator cost for the same pincodes. Switch only the pincodes where the own-fleet number comes out lower, and leave everything else on the aggregator.
- Pilot the switch for 60 to 90 days with one rider pool before expanding it, and re-run the full comparison every peak season, since order density during a festive period can justify a fleet that does not pay for itself the rest of the year.
Why Most Growing Indian Chains End Up Running Both
The retailers who get this right rarely pick one model for the whole business. They run an own fleet for the two or three cities where they already have multiple stores and dense order volume, often using the nearest store as the dispatch point rather than a separate warehouse, the same logic covered in ship from store versus warehouse delivery decisions. Everywhere else, they stay on one or more courier aggregators and let their order management system route each shipment to whichever aggregator is actually performing in that pincode that week, the same automated switching described in how chains use delivery partner auto-switching to cut RTO losses. The split is not permanent. As a new city's order volume grows, the dispatcher reviews whether it has crossed the density needed to justify its own rider pool, using the same per-order comparison above.
What This Decision Means for Your Margin
Delivery mode is not a logistics detail, it is a line item that moves gross margin as directly as product cost does. A retailer who understands what a courier aggregator actually does with a shipment between pickup and delivery can negotiate harder on rate cards and catch billing errors before they compound. A retailer who tracks cost per delivered order by pincode, rather than looking only at a blended average across the whole chain, is the one who spots the moment a city has quietly become cheap enough to bring in-house. Neither model is free of operational work. The fixed-cost fleet needs a dispatcher watching rider utilisation daily, and the aggregator model needs someone reconciling weight and RTO charges every billing cycle. Skip either and the savings on paper never show up in the bank account.
Stock movement between a central warehouse and a city dispatch point, whether run by your own fleet or handed to an aggregator for the first leg, still falls under the GST e-way bill value threshold rules set by the Central Board of Indirect Taxes and Customs, so the compliance paperwork does not disappear just because the vehicle is yours. On the payment side, as cash-on-delivery volumes shrink and prepaid and UPI-on-delivery collection grows under the digital payments push the Reserve Bank of India has been driving, the reconciliation burden on an own fleet's cash collection shrinks too, which narrows one more gap between the two models over time. Industry bodies such as the Retailers Association of India have repeatedly flagged last-mile delivery cost as one of the hardest line items for omnichannel retailers to control, precisely because it depends on decisions like this one made city by city rather than once for the whole chain.
