Why Is My Delivery Cost Higher Than the Rate Card Quoted?

A rate card is not a price. It is a floor. Nobody at a courier or 3PL is lying to you when they hand you a number per kg, but almost nobody who signs that card ends up paying it, because the card only prices one input out of six that determine your actual invoice.

If you run a D2C brand shipping through your own website, and your monthly courier bill runs 20 to 40% above what the rate card implies, that gap is not a billing error. It is a structural feature of how Indian courier pricing works, and it will not close itself with a sharper negotiation. It closes with a different set of decisions upstream of the invoice.

The rate card prices one variable. Your invoice has six.

The number on a rate card is almost always the base rate per kg for a given zone. That is one input. The bill you actually pay is the base rate multiplied and stacked against five more variables the card does not show you: chargeable weight (the higher of actual or volumetric weight), fuel surcharge, COD handling, RTO and reverse pickup, zone reclassification by pin code, and GST applied at the end.

Volumetric weight is the one that catches most finance leads off guard. Indian couriers bill on whichever is higher between actual weight and volumetric weight, calculated as length times width times height in centimetres, divided by 5000. A 1 kg product shipped in an oversized box routinely bills as 2 to 3 kg. [Guessing on your specific SKUs, directional across the industry] Nobody renegotiates a rate card for this. They just quietly pay more for the same product, every month, because nobody audited the box.

Where quick commerce logistics in India actually loses the plot

Fuel surcharge and COD handling

Fuel surcharge is typically 10 to 25% of the base rate and resets monthly against diesel prices. COD handling adds Rs. 20 to 80 flat or 1 to 2% of order value. Neither is hidden exactly, they are usually disclosed in the contract's fine print, but they rarely show up in the headline number a sales team quotes when they are trying to close you.

RTO is a cost multiplier, not an edge case

RTO is the one line item that changes the whole shape of the bill. A returned COD order is not a discount, it is a second forward shipment charged in reverse. On a book running 15 to 25% RTO, which is common for COD-heavy D2C categories, you are paying full courier economics twice on every fourth or fifth order, for zero revenue. We have written before about why RTO reduction is the delivery cost lever most finance teams underweight, and it holds true here: RTO is not a delivery problem, it is a cost multiplier hiding inside a rate card that never priced for it.

Zone reclassification by pin code

Zone classification is the quiet one. A rate card is signed against a zone map, but every shipment is reassessed at the pin code level. Out-of-delivery-area (ODA) pin codes carry an additional Rs. 30 to 100 per shipment that does not exist on the original card. If your D2C order density is spread across tier 2 and tier 3 pin codes, this line item alone can move your average cost per order by a meaningful margin without a single rate ever changing.

The gap between the rate card and the invoice, line by line

Directional ranges below are drawn from published 2026 courier and 3PL rate structures across Delhivery, DTDC, and comparable players. Treat them as a framework for auditing your own invoice, not as guaranteed figures for your account.

Directional ranges based on published 2026 courier rate structures. Your actual figures depend on your carrier contract, category, and pin code mix.

Why this hits D2C fulfilment harder than it hits marketplace sellers

A brand selling through its own website carries the full weight of every one of these six variables, because there is no marketplace absorbing volume-based rates on your behalf. This is also precisely why D2C fulfilment through your own channel is worth defending: it is the only setup where the brand keeps first-party customer data and the full margin on every order, instead of splitting both with a quick commerce platform. The delivery cost conversation and the customer data conversation are not separate. They are the same trade-off, seen from two different line items.

Hyperlocal delivery through a dark store network changes the shape of this cost stack in a specific way: it shortens the zone (most orders stay within a single city's dark store radius instead of crossing a national zone map), which removes ODA surcharges and long-haul fuel surcharge stacking almost entirely. It does not remove volumetric weight or COD handling, but it takes two of the six variables largely off the table for same-day and 60-minute delivery orders.

What actually closes the gap

1. Audit packaging against volumetric weight before renegotiating rates. A box resized from 35x25x15 cm to 28x20x12 cm can drop a shipment a full billing slab.
2. Treat RTO as a cost line, not an operations metric. Every percentage point of RTO reduction is a percentage point of avoided double-shipping, not just a customer experience win.
3. Map your order density against ODA pin codes before signing a new rate card. A card that looks cheap on paper can be expensive in practice if a third of your orders fall outside serviceable zones.
4. Ask for the fully loaded number, not the base rate. A courier quoting Rs. 45/kg without disclosing an 18% fuel surcharge and COD fee is quoting you a number nobody actually pays.

None of this is exotic. It is the same audit discipline covered in our piece on recovering failed deliveries before they become RTOs, applied one layer earlier, at the packaging and zone-mapping stage rather than the post-dispatch stage.

Where Zippee fits into this

Zippee does not quote a rate card and hope the gap stays small. As quick commerce-as-a-service infrastructure operating dark stores across 21+ cities including Delhi NCR, Mumbai, Bengaluru, and Hyderabad, the cost structure is set upstream of the shipment: inventory sits inside the delivery radius, so zone reclassification and long-haul fuel surcharge stacking are structurally reduced rather than negotiated down after the fact.

Full-time delivery riders (not gig workers) run fixed-radius routes instead of variable long-haul lanes, which keeps last-mile delivery cost predictable order over order instead of resetting against a fuel index every month. And because fulfilment runs through the brand's own D2C channel, brands like HealthKart, Epigamia, Supertails, and Clinikally keep first-party customer data and pricing control, the two things a rate card can never restore once they are gone.

This is also where NPS improves in a way a lower per-kg rate never delivers on its own: a same-day or 60-minute delivery window backed by a dark store network, rather than a national zone map, removes the two most common sources of delivery-cost surprise (volumetric misclassification and ODA reclassification) at the same time it removes the customer's biggest complaint, which is not knowing when the order will actually arrive.

The takeaway

A rate card was never designed to be the final number. Treating it as one is how brands end up surprised every month by an invoice that was, in fact, entirely predictable to anyone who read past the first line. Zippee is built as fulfilment infrastructure, not a vendor quoting a card and hoping the gap stays small: dark stores, full-time riders, and a brand's own D2C channel, working together so the invoice looks like the quote.

If you're ready to turn your fulfillment into a competitive advantage, join our waitlist.