How to Audit Courier Weight Discrepancies: A Step-by-Step Practical Guide

Courier weight disputes are the most recoverable leak in Indian e-commerce logistics, because unlike most operational losses they leave a paper trail on both sides. The courier states a billed weight. Your catalogue states dimensions. When those two disagree by more than sorting-scanner variance, you have an arithmetic case rather than an opinion — and arithmetic cases get paid.

The reason most brands never file is not that the disputes are weak. It is that the discrepancy is small per parcel, invisible at the invoice line level, and only becomes material when aggregated across thousands of shipments. That is an audit problem, not a logistics problem.

How Billable Weight Is Actually Computed

Express couriers bill on the greater of two numbers: the parcel's physical dead weight, and its volumetric (dimensional) weight. Volumetric weight converts the space a parcel occupies into a weight equivalent, because a large light box costs a courier the same cargo capacity as a small heavy one.

The standard courier formula uses a cubic divisor of 5000:

Volumetric weight (kg) = (Length cm × Width cm × Height cm) ÷ 5000

A 30 × 25 × 10 cm carton gives 7,500 ÷ 5000 = 1.5 kg volumetric. If the item inside weighs 600 g, you are billed on 1.5 kg, and that is correct — not a discrepancy. Air freight commonly uses a 6000 divisor instead; a courier quietly applying a more aggressive divisor than your contract specifies is a separate finding, which is why the contracted divisor belongs in your audit inputs rather than being assumed.

What Separates a Discrepancy From Normal Variance

This is where most home-grown audits fail. Conveyor dimension scanners have real measurement variance: polybags bulge, bubble wrap compresses unevenly, cartons are measured at speed. If you flag every gram of difference you will generate a dispute list your courier correctly ignores, and you will burn the credibility you need for the disputes that are real.

Kepler's weight-reconciler engine resolves this with a two-gate test: a discrepancy must fail on both a ratio and an absolute gram threshold before it is flagged.

Both gates must fail together, and the reason is worth understanding because it determines whether your audit is usable. A ratio test alone over-flags small parcels: a 50 g item billed at 120 g is a 2.4× ratio and 70 g of money, which is scanner noise. An absolute test alone over-flags heavy parcels: 200 g of variance on a 5 kg carton is well within normal measurement error. Requiring both filters the list down to discrepancies that are simultaneously large in proportion and large in cash.

Volumetric Discrepancy Calculator

Illustrative model. The figures below are calculated from the inputs you enter, not measured results from a customer engagement.

Two Findings That Are Not About Weight At All

The same reconciliation pass catches two adjacent leaks that most weight audits miss entirely:

• Dead freight on cancelled shipments — an AWB with status CANCELLED_BEFORE_PICKUP that still carries a freight charge. The courier never moved the parcel. These are the cleanest disputes you will ever file and they are usually invisible because the AWB does not appear in your delivered-orders report.
• Excess surcharge anomalies — surcharges above a threshold applied to shipments outside a special zone. Special-zone surcharges are contractual and legitimate; the same surcharge on a metro-to-metro lane is not.

A Worked Example

The Inputs You Need

The audit joins two datasets on SKU and AWB. Both are usually already exportable:

1. A catalogue file — SKU, dead weight in grams, and length/width/height in centimetres. This is the piece most brands lack, and its quality caps the quality of everything downstream. Measure the packed parcel, not the bare product.
2. A courier invoice export — AWB, order number, SKU, courier, billed weight, billed freight, surcharges, zone, invoice date, and shipment status.

Two practical warnings. Catalogue dimensions drift as packaging changes and nobody updates the master, so a large share of apparent discrepancies on a first run are stale catalogue data rather than courier error — re-measure your top SKUs before filing anything. And shipment status must distinguish CANCELLED_BEFORE_PICKUP from RTO_DELIVERED, because the first is a clean dispute and the second is a legitimate charge.

Filing the Dispute

Couriers generally accept disputes within a fixed window from the invoice date, and that window is short. Practical sequence:

1. File in batches, not individually. A single AWB gets a template reply; 240 AWBs in one schedule with ratios and gram excesses gets a reconciliation meeting.
2. Lead with the dead-freight lines. They are indisputable and they set the tone for the rest of the schedule.
3. Attach the catalogue evidence — dimensions, the divisor applied, expected billable weight, billed weight, and the difference. Show the arithmetic rather than asserting the conclusion.
4. Track resolution rate per courier. A courier that settles 80% of filed discrepancies is worth more than a marginally cheaper rate card that settles nothing.

Related Guides

• Configuring Shiprocket Multi-Courier Routing & Shipping Rate Rules: Operator Tutorial
• Courier SLA Breach & Late Delivery Guide: How to Claim 100% Freight Refunds on Delayed Shipments
• The Ultimate Guide to E-Commerce Profit Leak Audits: Recovering Courier Overcharges & Hidden Fee Creep