Excerpt: Mixed-pallet receiving goes wrong when a multi-SKU pallet is put away whole. This guide gives a receiving checklist that breaks each pallet down by item, batch, and quantity before anything reaches a storage location.
The conclusion comes first: in mixed-pallet receiving, the breakdown has to happen at receiving, not after putaway. If a pallet holding four or five items goes straight to a high bay as one stock record, every later step — picking, cycle counting, returns — works from a record that was never true. My rule is simple. Receiving creates the detail first: item, batch, and quantity, matched line by line. Only then does the physical stock move, and no pallet moves to putaway with a single line still open.
Why mixed pallets break receiving accuracy
The trouble with a mixed pallet is not heavy lifting. It is missing information. A supplier loads for cube, not for your system. One pallet can hold five items, with two or three cartons of one item buried at the bottom where nobody can see them from outside. The delivery note often lists only total pallets and total cartons, not what sits inside each pallet. A receiver counts pallets, signs, and the system books whole pallets against the delivery note. From that first step, the book stock and the physical stock disagree.
I saw this in November 2024, at a third-party warehouse near Dongguan handling household goods for online sellers. A truck delivered 40 pallets, 9 of them mixed, with 1,860 cartons on the paperwork. The team signed by pallet count and put the mixed pallets away whole. Two weeks later, picking kept hitting shortages. A count showed three items with book stock but no stock in the recorded location, and one item with 214 extra cartons hidden at the bottom of somebody else's pallet. Fixing it took six people two full days to pull all nine pallets down and break them apart, and the customer charged a service credit for the disruption. The breakdown had been skipped at receiving, and every later team paid interest on it.
A second case came in March 2025, at a small California warehouse supplying independent online stores. A delivery of 22 mixed pallets of personal-care goods mixed two batches of the same item: the older batch in the middle layer, the newer batch on the outside. Receivers scanned only the outer cartons, so the system recorded the whole pallet as the newer batch. Three months later the older batch surfaced close to expiry, and returns plus replacement freight and labor cost close to 4,000 dollars. In mixed-pallet receiving, the error is often not quantity. It is item or batch, and a correct quantity does not rescue a wrong batch record.
I have seen this pitfall three times, and the root cause was the same each time: receiving tried to save time by pushing the breakdown downstream, where the team had no delivery note, no loading detail, and no record of the original pallet.
A receiving checklist for mixed pallets, step by step
This is the mixed-pallet receiving checklist I reuse across projects. Each step covers both the person and the system, and a missing step stops the line. Do not carry on past a gap and promise to fix it later.
- Get the pallet composition before unloading. Ask the supplier or the driver for a packing list per pallet, even a handwritten one. If no composition exists, open and verify before signing for the full truck. In the system, create one receiving task per pallet number, not one task per truck. One pallet is the unit of work.
- Give each pallet an identity, photograph it, then break it down. When a pallet reaches the receiving zone, take a photo of the whole pallet, with outer carton labels and any damage visible. Scan the pallet code to open a pallet record, then scan cartons one by one, top to bottom and outside to inside. One scan means one line in the system. Never move cartons first and scan later from memory.
- Sort by item, not by carton size. Each item gets its own pile, with a handwritten card showing item name, quantity, and batch. Different batches of the same item stay in separate piles, even if only one batch number differs. When sorting ends, two people cross-count: one calls the numbers, the other checks them against the system detail.
- Classify every variance on the spot. Shortage, overage, wrong item, wrong batch, and damage each have a destination. Overage goes to a hold zone and never merges straight into good stock. Shortage is recorded as a shortage, never covered quietly with stock from another pallet. Wrong item or wrong batch is photographed and held for a decision from purchasing or the supplier. Damage is isolated away from good stock. A pallet with an unclassified variance does not enter the putaway queue.
- Put away by the breakdown, not by the original pallet. Each item from the breakdown gets its own putaway task, assigned to that item's normal location. Putaway staff scan the location code and then the carton code, and the system releases the move only when item and quantity match.
- Close with three checks: system detail matches the physical piles, every variance has a recorded destination, and pallet photos are linked to the task number. Those three checks belong in the pre-go-live checklist for the receiving section. If one is missing, the shift supervisor does not sign off and the shift does not hand over.
That routine looks slower at the dock, and it is, measured narrowly. The honest comparison is the full cost of one mixed pallet, not the receiving shift alone. The table below compares the same kind of mixed-pallet work at the Dongguan site before and after the change, using that site's own two-week averages, not an industry benchmark:
| Step | Before: sign by pallet | After: break down at receiving |
|---|---|---|
| Time per mixed pallet at receiving | About 8 minutes | About 18 minutes |
| Pallets needing later rework | Around 3 in 10 | Below 1 in 10 |
| Time to resolve a variance found at count | Over 2 hours per pallet on average | Under 20 minutes per pallet on average |
| Picking errors linked to the error | 11 orders in one month | 2 orders the next month |
The counterintuitive point is that ten extra minutes at receiving is not a cost increase. It is hours of recount and complaint handling paid early, at a cheaper moment. Once recount overtime and misship compensation are combined for one pallet's full journey, breaking it down at receiving is the cheaper option. Breaking down to single units is overkill: my cutoff is carton and batch level, except for high-value or expiry-sensitive items.
Three ways mixed-pallet breakdown fails in practice
One failure is scanning only the outer layer. The outside of a mixed pallet is often one item, while the inside holds another, so an outer scan verifies only half a pallet. My hard rule is that breakdown must expose every layer, scanning must cover every pile, and sampling does not apply here. A mixed pallet gets a full check, every time.
A second failure is letting the system book whole-pallet stock first. Some systems default to booking a delivery note as whole pallets, and receivers confirm because it is faster. Splitting that record later needs transfer and breakdown documents, which cost more than creating the detail at receiving. Before go-live, change the receiving task template so mixed work is created by pallet and by detail line.
A third failure is letting variance stock drift into good stock. Two extra cartons, or goods swapped out for damage, tend to land on the nearest good pile when nobody is watching, and the record never explains them again. My fix is a marked hold zone in receiving. Variance stock goes there only, it is cleared once a week, and it leaves only with a record. Nothing leaves by hand without one.
In mixed-pallet receiving, there is no shortcut here, only a sequence: break it down clearly, then put it away. When the sequence is right, a mixed pallet behaves exactly like a single-item pallet in the system, and picking, counting, and returns can all work from the same detail. When the sequence is wrong, the larger the warehouse, the faster the unclear record grows.
By Lin Xiao, WMS Implementation Consultant








