Pooled pallets moving to your own sites and co-packers
Internal transfers and co-packer loads are easy to miss. How to record them so the right site carries the pallets.
Why they go missing
When pallets move from one of your sites to another, or out to a co-packer and back, the shipment often isn't treated as a customer load, so nobody declares it. The sending site keeps the pallets on its balance while the receiving site has them on the floor.
What to do
- Treat internal moves like customer shipments: declare them to the receiving site's account with a BOL.
- Agree with each co-packer who declares what, in both directions.
- In PalletAudits, mark your own sites and co-packers on the audit (or name them in the site's setup answers). Their loads are kept apart from customer loads and listed separately.
Find your missing pallets
PalletAudits matches every shipment to a declared transfer and lists what to declare, dispute and recount. Your first audit is free.
Run a free audit See a sampleMore guides
Lost pallet charges: what they are and how to reduce them
Shipping pooled pallets to customers outside the pallet network
Got a lost-pallet bill? What to check before you pay
Pallet rent and late declarations: how the days add up
Seven reasons a pooled pallet account drifts
Transfers credited to you that never arrived
General information, not advice about any specific contract. Your agreement with the pallet company sets the actual fees and deadlines.