Line Haul and Zone Skipping for Indian Ecommerce

Most brands buy shipping as a single line item. One rate per zone, per 500g slab, adjusted for fuel and GST. That single rate hides four or five separate physical movements of the same box, and the cost of each movement is very different. Once you can see the movements, you can start paying for fewer of them.

How a parcel actually moves

A prepaid parcel leaving a Bhiwandi warehouse for a customer in Coimbatore passes through five distinct stages.

• First mile pickup, from your dock to the courier’s origin branch. Usually a 10 to 40 km run on a shared vehicle.
• Origin hub consolidation, where your parcel is sorted with tens of thousands of others by destination region.
• Line haul, the long trunk movement between hubs. Bhiwandi to Bengaluru to Coimbatore, by road on surface or by belly space on air.
• Destination hub sort, then a second sort at the local delivery branch that owns the customer’s pincode.
• Last mile, a rider running a beat of 60 to 120 stops.

Line haul is the cheapest stage per kg and the slowest in elapsed time. Last mile is the most expensive per parcel and the stage you control least. The sorts in between are where parcels get misrouted, crushed and delayed. Every extra touch adds a cost and adds a probability of failure. That is the whole basis of what follows.

What zone skipping actually is

Zone skipping means you buy the line haul yourself, in bulk, and hand the courier the parcel much closer to the customer. Instead of paying a per parcel national rate for the whole journey, you move 800 kg of Coimbatore bound parcels on your own truck to a point near Coimbatore, then pay only a local or regional rate for the final leg.

The arithmetic is not subtle. A national zone D rate for the first 500g commonly sits at Rs 55 to Rs 65 before fuel surcharge. A local or within city rate in the same slab is often Rs 28 to Rs 35. Full truck load line haul on a dense lane runs Rs 6 to Rs 10 per kg, with part load a few rupees higher. If your average billable weight is 600g, the line haul cost per parcel is under Rs 8. Rs 32 plus Rs 8 lands well below Rs 60, and you have removed two sorting touches from the journey.

The volume at which it starts paying

The break even is set by truck fill, not by total order volume. Parcels cube out long before they weigh out. A 19 foot container truck will hold roughly 700 to 900 typical D2C parcels but only 2 to 3 tonnes of them, so you are buying space, not weight.

A workable floor is 300 to 400 parcels per lane per dispatch, at three or more dispatches a week. Below that the truck runs half empty, the per kg rate rises to meet the courier rate, and the saving disappears into the cost of the person who has to bag and manifest everything. A brand doing 40,000 orders a month across 500 cities may still have no lane that qualifies. A brand doing 9,000 orders a month with a fifth of them going to one southern cluster has one immediately. Check your order file by destination cluster first.

Hub bypass versus direct injection

Two variants, routinely confused, with very different operating loads.

• Hub bypass. You keep one national courier but deliver consolidated bags to their destination hub instead of their origin branch. You skip their trunk network and their origin sort. Couriers price this as an injection discount, typically 15 to 25 percent off the standard zone rate. Low effort. One contract, one tracking system, one dispute process, one NDR workflow.
• Direct injection. You bypass the national courier entirely and hand parcels to a regional or city level last mile partner at destination. Cheaper again, often 30 to 40 percent below the national zone rate. Also much harder. You now own the line haul, the destination handover, a second integration, a second reconciliation, and an NDR process with a partner whose API may be a spreadsheet.

Start with hub bypass. It returns most of the saving with none of the new failure modes, and it proves your lane volumes are real before you commit to anything regional.

The transit time you give up

Zone skipping does not automatically cost you a day. It sometimes buys one.

The variable is your consolidation cut off. If your truck leaves nightly at 8 pm, an order picked at 4 pm loses nothing and gains two skipped sorts, so it can land earlier than the aggregator route. If your truck leaves on Monday, Wednesday and Friday, an order that misses Wednesday sits in your warehouse until Friday and loses 48 hours before it has moved a metre. Dispatch frequency, not distance, decides whether zone skipping helps or hurts your promise date.

Treat the promise date as part of the design. Widen the checkout date on non dispatch days, or keep a fallback aggregator route for orders that miss the truck.

Modelling it against your aggregator rate

Build the comparison per parcel, on one lane, from twelve weeks of your own shipment data. Four inputs.

• Current true cost. Actual billed rate per parcel on that lane, not the rate card. Add fuel surcharge at 10 to 12 percent, the weight discrepancy adjustments you failed to dispute, and forward plus return freight on RTOs.
• New cost. Line haul per kg times your average billable weight, plus the destination handover rate, plus loading labour, bagging material and transit insurance, plus the cost of orders that miss the truck.
• Failure cost. Assume your first quarter of a new destination partner runs one to two points worse on first attempt success. Price that at your RTO cost per order, not at zero.
• Fixed cost. Someone manifests, bags, labels, hands over and reconciles two invoices instead of one. Budget half a person per lane at minimum.

If the net saving is under Rs 8 per parcel, do not do it. The operational tax will eat it inside a quarter. If it is Rs 15 or more on a lane running 400 parcels a dispatch, that is roughly Rs 2.4 lakh a year on one lane, and it justifies a 60 day pilot with a defined exit. Run it on one lane only, keep the aggregator live in parallel, and compare delivered cost and first attempt success before you touch a second city.