Skip to content
Robnu
Shipping · Money guide

Weight freeze: the permanent fix for a SKU that keeps getting over-billed

Winning the same weight dispute every month is not a win — it is a subscription to unpaid admin. A weight freeze locks an agreed billable weight for a SKU so shipments stop being re-measured at all. Here's what freezing means, how sellers build the case, and what keeps a freeze from quietly falling apart.

Free during early access · Forever free under 25 orders/day
app.robnu.com/shipping/weight-freezeOne SKU's discrepancy charges, before and afterMonthly weight-discrepancy deductions on a repeat-overcharged SKU — illustrative ₹₹4k₹2k₹0JanMarJunAugWeight freeze appliedIllustrative — a freeze ends the repeat charge; the dispute wins before it built the case.
TL;DR
  • A weight freeze records an agreed billable weight for a SKU with the marketplace or courier, so each shipment stops being re-measured. It converts a monthly dispute ritual into a solved problem.
  • There is no instant application. Sellers get there with a consistent packaging spec, dated weight-and-dimension documentation, a stack of dispute wins on the same SKU, and a weight-verification request — the exact flow varies, so check the current process on your panel.
  • The freeze is only as durable as your packaging: change the box, the fill, or the bundle and the agreed figure stops matching reality. And while you wait for a freeze, keep disputing every wrong slab — each win is another page in the case.
What freezing means

From arguing per parcel to agreeing per SKU

Weight-discrepancy billing works parcel by parcel: a courier hub weighs or scans your shipment, the recorded figure lands in the marketplace's billing, and if it disagrees with reality you dispute that one shipment. For a SKU you ship daily in identical packaging, this is an absurd loop — the parcel is the same every time, but the argument restarts from zero every time. A weight freeze breaks the loop by moving the agreement up a level: the platform records the SKU's packed weight and dimensions once, and billing for that SKU runs off the agreed figure instead of a fresh measurement.

Why it matters is pure arithmetic. A repeat-overcharge SKU doing 200 shipments a month, over-billed by one slab a few dozen times, leaks a few thousand rupees monthly (illustrative — your rate card sets the slab gap). Disputing recovers most of it, but at the cost of hours of evidence work that never ends. The freeze recovers the same money and deletes the admin. For a two-person operation, the second half is worth more than the first.

app.robnu.com/protect/deductionsDeduction categoriesWhere money typically leaks · illustrativeSLA missDisputableQuality disputeDisputableMis-pickSunkLate ackDisputableRTO leakSunkSlip mismatchDisputableDISPUTE-READYRobnu surfaces them
Building the case

The path to a freeze, step by step

The exact panel flow varies by marketplace and changes over time — verify the current process before you file. The case you need to assemble does not change.

  1. 01

    Identify the repeat-overcharge SKU

    Pull three months of weight-discrepancy charges and group them by SKU. A freeze case is strongest where the pattern is boring: the same product, the same packed weight, billed above its slab again and again. One-off discrepancies scattered across SKUs are a different problem.

  2. 02

    Lock the packaging spec first

    A freeze is an agreement about a specific packed configuration. Before documenting anything, fix the spec: this box or poly, this fill, this tape pattern, nothing extra. If packing varies by who packed it, standardise first — evidence of an inconsistent parcel proves nothing.

  3. 03

    Document weight and dimensions, dated

    Photograph the packed parcel on a scale with the reading and SKU code visible, measure length, width, and height against a visible tape, and date every shot. Re-shoot when anything changes. This file is simultaneously your dispute evidence and your verification case.

  4. 04

    Dispute every wrong slab — and archive the wins

    Each reversed charge is the platform's own record agreeing your weight is right. Keep dispute IDs, resolution notes, and amounts in one per-SKU ledger. A verification request backed by a dozen documented wins reads very differently from a first complaint.

  5. 05

    Raise the weight-verification request

    Through seller support or the panel's weight-issue flow, ask for the SKU's weight to be verified and recorded, attaching the spec, the dated documentation, and the dispute history. Name the ask plainly: recurring wrong slab on an unchanged SKU, requesting verified billable weight.

  6. 06

    Keep the freeze valid

    Packaging changes void your case — a bigger box, new fill, a bundled freebie, even heavier festive wrapping shifts the packed weight away from the agreed figure and invites re-measurement. Write the spec down where the packing table can see it, and re-document before any deliberate change.

  7. 07

    While you wait, keep disputing

    A pending request pauses nothing. Every wrong slab that lands while you wait should still be disputed inside the window — the recoveries are real money, and every additional win lands on the same pile of evidence the verification decision will rest on.

app.robnu.com/protect/deductionsDeduction categoriesWhere money typically leaks · illustrativeSLA missDisputableQuality disputeDisputableMis-pickSunkLate ackDisputableRTO leakSunkSlip mismatchDisputableDISPUTE-READYRobnu surfaces them
The cost of not freezing

The repeat charge you keep winning is still costing you

Run the illustrative math on one SKU: 200 shipments a month, forty of them billed one slab high, a slab gap of ₹15–30 depending on your rate card. That is roughly ₹600–1,200 leaking every month from a single product — before counting the disputes you missed because the settlement line was small enough to skim past. Sellers who dispute diligently claw most of it back, but the claw-back has its own price: an hour or two of screenshots, forms, and follow-ups every month, forever, per SKU. Multiply by three or four problem SKUs and the admin alone justifies the freeze effort.

There is also a quieter cost: unresolved discrepancy patterns muddy every other audit. When a SKU's billing is noisy, a genuinely new problem — a courier re-rating parcels, a volumetric change, a packaging drift at your own table — hides inside the noise. Freezing your known-good SKUs shrinks the haystack, so the remaining flags on the settlement actually mean something.

Do not stop auditing after the freeze
A freeze fixes one SKU's billing, not the billing system. Keep reconciling every settlement — sellers report that when one leak closes, the next highest-volume SKU is where the wrong slabs show up next.
The Robnu way

The freeze case builds itself while Robnu runs your disputes

Everything a weight-verification request needs — the per-SKU charge history, the dispute record, the wins, the evidence — is exactly what Robnu produces in the course of protecting your settlements. It reconciles every AJIO and Meesho payout line, flags each weight-discrepancy charge against your documented SKU weights, and files the disputes with the evidence attached. Fully autonomous filing is rolling out; the rare claim still asks you for a single approval click.

By the time a SKU has earned a freeze, your dashboard already holds the case: every charge, every reversal, every amount, organised per SKU. You raise the verification request with a file instead of a complaint — and after the freeze, Robnu keeps watching so a packaging drift or a fresh re-rating never runs for months unnoticed.

app.robnu.com/ajio/ordersRobnuOpen ordersBatchesManifestsDocument pipelineSLA watchdogSettingsOpen ordersSynced from the marketplace · normalisedOrderSKUStageStatusManifestedManifestedConfirmedConfirmedSlip readySlip readyAwaitingAwaiting
FAQ

Weight freezes, answered

A weight freeze means the marketplace or its courier partner records an agreed billable weight for a specific SKU, so individual shipments of that SKU stop being re-measured — and re-disputed — one parcel at a time. Instead of arguing about grams on every settlement, the billing for that SKU runs off the frozen figure. It is the structural fix for the repeat-overcharge problem: the same product, the same packaging, billed at a wrong slab again and again, with you winning the same dispute every month.

There is no single button. Sellers typically get there through accumulated dispute wins on the same SKU plus a weight-verification request raised through seller support, where the platform confirms the SKU's packed weight and dimensions against your documentation. The exact flow, naming, and eligibility vary by marketplace and change over time — check the current process on your seller panel or with support. What stays constant is what wins it: a consistent packaging spec, dated weight and dimension evidence, and a history of resolved disputes in your favour.

Build the file before you ask. Photograph the packed parcel on a calibrated scale with the display readable, measure all three dimensions against a tape or ruler in the frame, and date the photos. Keep the SKU code visible in the shot. Add your packaging spec — box or poly type, fill material, tape pattern — and export the dispute history for the SKU showing every wrong slab that was later reversed. The stronger the pattern of documented wins, the harder the case is to refuse.

It stops the repeat kind — the same SKU billed above its real slab shipment after shipment. It does not make you immune: other SKUs can still be over-billed, a damaged or repacked parcel can genuinely weigh differently, and volumetric rating can still apply if a parcel bulks up. Treat the freeze as closing one leak permanently, then keep auditing the rest of the settlement. Sellers who stop checking after a freeze often find the charges migrate to their next-best-selling SKU.

Changing the thing that was frozen. The agreed weight is tied to a specific packed configuration — swap the box for a bigger one, add a rigid insert, change fill material, or bundle a freebie, and the frozen figure no longer matches what couriers actually handle. That mismatch invites re-measurement and can unwind the whole arrangement. If you need to change packaging, re-document the new spec the same way you built the original case, and expect to re-verify. Keep the spec written down so a new packer cannot break it by accident.

Robnu builds the case for you as a by-product of normal operations. It reconciles every settlement on AJIO and Meesho, flags each weight-discrepancy charge against your documented SKU spec, and files the disputes — fully autonomous filing is rolling out, and the rare claim still asks for one approval click. Over months this produces exactly what a verification request needs: a clean per-SKU history of charges, disputes, and wins, with the evidence attached. When you raise the freeze request, the file is already sitting in your dashboard.

Sources

Where this comes from

  • Marketplace seller-panel flows for weight-discrepancy disputes and weight-verification requests on AJIO and Meesho (flows vary by seller agreement and change over time — verify the current process on your panel).
  • Seller reports of repeat weight overcharges on unchanged SKUs and of verification outcomes: public seller community threads (Reddit r/IndiaBusiness, seller Facebook and Telegram groups), 2024–2026.
  • Standard courier practice of slab-based dead-weight rating and volumetric rating with the common /5000 divisor.
build c3ffebc77e7004ab28f3be8d8e290923969592fe · 2026-07-08T12:37:42+05:30