Build the evidence before disputing a courier weight charge
For e-commerce dispatch and logistics finance teams · Compare approaches
TL;DR — what you’ll learn
- Confirm parcel identity and measurement basis before disputing a weight difference.
- Recalculate actual versus volumetric weight using the contracted units, divisor and rounding rule.
- Keep original packing evidence, carrier measurements and the disputed invoice line together.
- Track an approved credit through to settlement; a closed support ticket is not proof that money was corrected.
Topics: weight discrepancy · courier weight dispute · volumetric weight evidence · parcel billing discrepancy

Illustrative 3PL warehouse dispatch and freight verification desk; not a client facility.
All quantities, amounts, product codes and events are illustrative teaching examples.
The courier bills 5.5 kilograms for a parcel that the warehouse recorded at 3.2 kilograms. The dispatch team sends a scale photograph and asks for a refund. The carrier responds that the shipment was billed on volumetric weight.
The useful comparison is between the same parcel, the same measurement basis and the same contracted charging rule. Actual weight alone cannot explain a charge based on dimensions. Equally, a volumetric calculation does not prove that the carrier measured the correct package.
Build the parcel identity first
Connect the order, air waybill or AWB, parcel sequence and packing record. A multi-piece shipment needs package-level evidence where the charging rule uses individual pieces. An image of one carton is not sufficient to explain the dimensions of another carton under the same order.
Retain the original measurement time, unit, packing configuration and relevant equipment record. If the parcel was repacked after measurement, identify which configuration was handed to the carrier. Preserve original images instead of replacing them with an annotated copy that loses the underlying evidence.
Shiprocket lists a weight-discrepancy report for courier-raised differences. Use such a report to locate cases, then obtain the supporting parcel and billing records needed to assess each one. Shiprocket — Choosing scheduled reports.
Reproduce the chargeable weight
Consider this illustrative contract, with fictional terms:
- Parcel dimensions: 40 × 30 × 20 centimetres.
- Actual packed weight: 3.2 kilograms.
- Volumetric divisor: 5,000 cm³ per kilogram.
- Chargeable weight: the greater of actual and volumetric weight, rounded up in 0.5-kilogram increments; an exact increment stays unchanged.
- Example freight rate: ₹60 per chargeable kilogram, excluding other charges and applicable tax.
The volume is 24,000 cm³. Volumetric weight is 24,000 ÷ 5,000 = 4.8 kg. The example rounding rule makes the chargeable weight 5.0 kg, giving ₹300 freight.
Scroll horizontally to see all columns.
| Basis | Expected from dispatch evidence | Carrier claim |
|---|---|---|
| Actual weight | 3.2 kg | Obtain carrier observation |
| Dimensions | 40 × 30 × 20 cm | Obtain carrier observation |
| Calculated chargeable weight | 5.0 kg | 5.5 kg |
| Freight under the example rate | ₹300 | ₹330 |
| Amount requiring explanation | ₹30 |
The divisor, rounding and price are teaching assumptions, not universal courier rules. The ₹30 is a proposed disputed amount only after the invoice, service and tariff scope are confirmed.
Check the aggregation level before applying rounding. In a separate illustrative two-piece case, each parcel has 2.1 kg of unrounded chargeable weight. Rounding each piece to 2.5 kg gives 5.0 kg in total. Summing first gives 4.2 kg, which rounds to 4.5 kg. The account rule determines the correct method; neither total can be selected merely because it is lower.
Also distinguish the chargeable-weight calculation from the price schedule. A tariff with a first slab and additional slabs will not necessarily equal kilograms multiplied by one rate. Preserve each step—measurement, weight selection, rounding and pricing—so the disputed ₹ amount follows the actual agreement.
Separate a measurement dispute from a rule dispute
If the carrier used 45 × 30 × 20 cm, the unrounded volumetric weight would be 5.4 kg under the fictional divisor, explaining a 5.5 kg billed slab. The next question is whether 45 cm correctly describes the parcel presented to the carrier.
If both parties agree on dimensions but used different divisors, the commercial agreement is the issue. If they agree on the divisor but one used millimetres as centimetres, the problem is a unit error. Give each case the right owner.
Scroll horizontally to see all columns.
| Difference | Investigation | Suggested owner |
|---|---|---|
| Different measured dimensions | Compare package identity, configuration and original evidence | Packing/dispatch lead |
| Different charging rule | Confirm service, zone, effective tariff and agreed factor | Logistics buyer |
| Incorrect unit or mapping | Reproduce the source-to-system conversion | Data/integration owner |
| Credit agreed but not received | Match adjustment reference to settlement or invoice | Finance |
Delhivery's B2B exception workflow includes measured-weight acknowledgement. That illustrates a carrier-specific operational decision; it should not be treated as the procedure or deadline for every courier account. Delhivery — B2B exceptions management.
Submit a case that can be reviewed
The case should state the parcel identity, disputed line, expected calculation, supporting measurements and the correction requested. Include the actual carrier requirement for evidence and submission timing. Avoid submitting a generic photograph bundle with no relationship to the charge.
Keep dispatch observations separate from the commercial conclusion. The packer can confirm what was measured; the authorised buyer or claims owner decides whether the evidence supports a dispute. If measurements are missing, mark the limitation and investigate the capture process rather than generating replacement evidence.
A practical workflow is: identify the billed parcel → compare measurements and rule → classify the difference → submit the evidenced case → record the decision → reconcile the financial outcome. An unsupported case returns to the evidence owner; it should not be marked “won” because a request was sent.
Fix repeated causes at packing
Review repeated differences by carton configuration, service, warehouse and measurement method. A recurring problem may come from outdated package dimensions, a repacking step after the scale or a unit conversion in the shipping interface.
Test a small packing change with comparable parcels and inspect the subsequent carrier records. Do not infer deliberate overbilling from a pattern before the evidence establishes the cause. Conversely, do not suppress valid disputes merely because most previous cases were rejected.
Measure unresolved disputed value, evidence completeness, decision time and credits actually reconciled. Keep rejected cases and their reasons in the analysis. Reporting only successful claims gives a misleading picture of the process.
Close the measurement and money loops
A weight dispute is resolved when the measurement basis and contract explain the charge, or an approved correction reaches the financial record. Better parcel evidence makes that decision faster and reveals which packing controls need attention.
Next actions
- Select a small completed set of weight disputes and identify every parcel and billed line.
- Recalculate them using the actual account tariff and units.
- Route measurement, commercial-rule and settlement differences to their owners.
- Follow agreed credits through the relevant invoice, wallet or bank settlement.
- Correct repeated capture or mapping errors at their source.
A weight-dispute assessment can focus on one carrier service and the point where packing measurements, tariff calculation or credit evidence diverge.
Discuss this workflow
Describe your current systems, the recurring exception and the outcome you need. Keep shipment, customer and financial records out of the initial message.
Draft an assessment emailReferences
Sources checked 15 October 2026. Vendor documentation supports platform facts; the worked examples and diagrams are original.
- Shiprocket — Choosing scheduled reportsAccessed 15 October 2026.
- Delhivery — B2B exceptions managementAccessed 15 October 2026.