Revenue leakage is billable work performed but never invoiced — pallets received, storage days accrued, orders picked and kitting jobs completed that never make it onto a client’s bill. Industry estimates put typical 3PL leakage at 3–15% of revenue; best-in-class operators hold it under 0.1%. The gap is almost never about rates. It’s about capture — whether each billable event is recorded when the work happens, or reconstructed at month-end from memory and packing slips.
What counts as leakage — and what doesn’t?
Underpricing is not leakage. If your rate card charges too little per pallet, that’s a commercial problem you can see and renegotiate. Leakage is work done at agreed rates that never gets billed at all — and it’s invisible on the P&L, because it never appears as a cost. The labour was paid, the racking was occupied, the forklift moved; the revenue line simply never happened. That invisibility is why it persists: nobody gets a variance report for invoices that were never raised.
Where does the money actually hide?
Leakage concentrates in four places — the same four categories every 3PL rate card is built from.
| Category | Typical US-published rates | How it leaks |
|---|---|---|
| Receiving | $25–50 per pallet | Container destuffed, counted informally, never billed — if it isn't captured at the GRN, it rarely gets captured at all |
| Storage | $8–25 per pallet/mo | Missed snapshots, and long-term surcharges agreed in the rate card but never applied |
| Pick & pack | $2–5 per order + $0.30–0.75 per item | Per-item charges dropped when someone keys totals from packing slips on the 31st |
| VAS | kitting $1–3/kit · returns $3–7/unit | The likeliest to vanish — kitting, labelling and returns happen off the standard flow, so no document reminds anyone to bill them |
RATES: PUBLISHED US ANCHORS, JULY 2026 — INDIA PER-PALLET BENCHMARKS REMAIN UNPUBLISHED
The 3–15% range is the best-documented figure in this field, and it is still a range — leakage is by definition the work nobody wrote down, so nobody can count it precisely. Treat the band as the shape of the problem rather than a measurement of your floor. Your own number is the one worth having, which is what the calculator is for.
Why does month-end reconstruction guarantee it?
Because reconstruction is recall, and recall loses exactly the charges that matter. On the 31st, someone walks the floor for storage counts, keys pick totals from three-week-old packing slips, and tries to remember which client asked for the relabelling job in week two. Everything on the standard flow mostly survives; everything off it — the extra destuff, the rush kitting, the returns processing — quietly doesn’t. The tell is how long billing takes: a month that can only be closed over days is a month that was rebuilt rather than recorded, and rebuilding is exactly where the off-flow work gets dropped. Fast billing isn’t the cause of a clean invoice — it’s the symptom of capture happening during the work instead of after it.
What does best-in-class look like?
Under 0.1% leakage — and the mechanics are unglamorous: every operation writes its own billing event against the client’s rate card as it happens. The GRN prices the receiving, the storage snapshot runs on schedule, each pick accrues its per-item charge, each VAS task carries a client and a rate. Month-end becomes a review of captured events, not archaeology. That’s the entire design premise behind Binsy — the full breakdown is in the complete guide, and you can put your own volumes against the 3–15% band in the leakage calculator.
From reading to the rack.
Bring one client's rate card and one month of invoices. We'll walk your flow through Binsy and show where the billing events would have written themselves.
Book a walkthrough