Phantom 3PL storage: billed pallets and bins that don't exist

Why your storage bill can rise while inventory is flat#

On pallet, bin or location pricing, storage bills occupied locations (and any reserved for you or inside a minimum number of positions), so the bill can rise with flat units if locations stay recorded after the stock has gone. Among charges billed every month whether or not you ship, storage is one of the largest and a common place for billing errors. A phantom location bills every period until its record is fixed; under a daily average, it bills every day it stays.

Count errors can come from system set-up and process rather than intent (Why 3PL billing errors happen, and why they keep coming back). Correct reasons for a rise, such as new SKUs or lots, are in Verifying storage counts against inventory snapshots.

Where phantom pallets and bins come from#

Phantom locations come from records that keep a location on your account after your stock has gone, show another client's stock as yours, or count the same stock twice. The 3PL's location report lists what each location held on a date.

In some billing setups, a location assigned to your account stays on it after it empties, until someone removes it. After a move, stock can stay recorded in its old location too, for example when the move is entered as a new putaway rather than a transfer.

One warehouse management system (WMS) lets the 3PL edit a recurring storage quantity before invoicing² and apply manual recurring storage "on top of any automated charges"³. If a billed quantity differs from the snapshot, ask what each line counts and why.

Extra locations that are billed correctly#

A correct bill can show more locations than your units seem to need:

• Pick plus reserve. A SKU can hold stock in a pick location and in reserve at the same time; under per-location or per-pallet pricing, each occupied location is billed.
• Lots and expiry dates. Where each lot or expiry date gets its own pick location, one SKU with three live lots can take three locations.
• One SKU per location, which many ecommerce 3PLs require.
• Partial pallets. A pallet position is billed in full however full; half-pallet rates exist but are uncommon (Partial pallets and rounding: how 3PLs count a "pallet").
• Over-height pallets, usually billed as two positions or at a tall-pallet rate.
• Reserved locations, such as dedicated pick faces, which bill whether or not they hold stock. A contract can also bill the greater of occupied positions or a minimum number of positions⁵.
• Any-point occupancy. One WMS's storage-by-location setting bills a location for a day, week or month if it held stock at any point in it¹.
• Initial storage on new receipts, when the contract adds it on top of the period's count.
• Status storage (quarantine or returns) billed on its own line, if that stock isn't also in the general count.

How to find phantom locations on your invoice#

Match every billed location to the 3PL's snapshot for the date or dates your contract counts, then test what's left against records the 3PL didn't create. The test depends on the unit and count method (How storage is measured: snapshot, average, peak or billing-day count):

• One-day count on pallet, bin or location pricing. A count can bill the period ahead, under way or just ended, so pull the snapshot the invoice used. Flag other-owner locations, duplicate records (the same pallet ID or LPN twice) and zero-quantity locations not reserved for you or inside a minimum number of positions. In a floor lane holding several pallets, match pallet IDs instead. Then compare each SKU's location total with your own expected on-hand at this 3PL (your own PO or ASN receipts less shipments, removals and agreed adjustments), on the same date and in the same unit of measure:

  SKU location total in the snapshot − your expected on-hand = units to explain

  Settle any unit variance first (How to reconcile 3PL inventory to your ERP, step by step), then look for the rest in extra locations.

• Daily average or proration. Check each day's snapshot: a phantom location present 10 days of a 30-day month adds a third of a position.

• Peak. One day of phantom stock can raise the whole period's quantity.

• Any-point occupancy. Use movement history: a location that held nothing all day, week or month shouldn't bill for it¹.

• Initial plus recurring. Check the receipts report for pallets on both lines in one period, unless the contract adds the receipt charge on top.

• Cubic foot. On cubic foot storage, phantom on-hand inflates the billed cube (almost always WMS dims × quantity on hand), so check on-hand by SKU before dims (Why accurate product weights and dims drive everything downstream).

• Square foot. Compare billed with contracted area; no location check applies.

About a quarter of Implentio customers' 3PL contracts with storage charges have at least one storage line with a dollar amount and no quantity. Ask for the count and locations behind such a line first.

Proving a billed location is empty#

The strongest proof is the 3PL's own snapshot showing a billed location with zero quantity, another owner or a duplicate record, since its record then contradicts its bill. When the snapshot shows stock you believe left, it can't settle the question: the snapshot and the invoice come from the same system, so their agreement proves the arithmetic, not the location.

Pair it with records the 3PL's location data doesn't drive: BOLs, carrier scans and disposal certificates dated before the count, backed by your removal or transfer instructions. Under IWLA's standard terms for merchandise warehouses (2026 revision), where a contract adopts them, goods leave only on the customer's instructions⁴. If your ERP's on-hand comes from the 3PL's inventory feed, it mirrors the 3PL's records and isn't independent evidence.

If the snapshot itself is in doubt, ask for a cycle count of the disputed locations, or observe one (Observing or auditing a count yourself). A count shows today's stock; pair it with movement history since the count date.

Getting it fixed: the credit and the cause#

Ask for a credit on every invoice still inside its dispute window, listing each location ID, the reason and the amount, plus a fix for each cause so the locations don't bill again:

• Emptied locations: remove them from the count and from your account.
• Moved stock: complete or reverse the move record.
• Another client's stock: reassign it to its owner.
• Stock that left, or a duplicate receipt: post the removal, transfer or adjustment, or reverse the duplicate receipt record.
• Two lines: correct the billing setup so the stock counts once.

Then check the next invoice for the same location IDs. Locations holding your stock that weren't billed are undercharges; see Not every variance is an overcharge: undercharges, manual items and special projects. For the dispute itself, see How to dispute a 3PL invoice: process and etiquette.

What good looks like#

Good storage billing lets you tie every billed location to a dated record:

• Storage detail by location ID, location type and owner comes with every invoice.
• The contract states the unit, count method, count day, the period each count bills, and whether any locations are reserved for you, and lists them.
• Emptied locations drop out of the next count.
• Moves and removals are recorded the day they happen.
• The 3PL answers questions with location IDs and movement history.