Pallets: Move, Merge, Split — Without Losing the Audit Trail

Pallets in an ITAD warehouse are a working surface, not a permanent home. A pallet gets built at receiving, sits while testing happens, gets split when half the assets fail, gets merged with another pallet when both have similar grade-mix, and finally gets dismantled at outbound when the assets ship. The platform tracks every step.

Seven pallet types

Mixed (the default — anything goes), graded (assets sorted by grade band), category (laptops only, monitors only), client (single-client contents for traceability), recycling (downstream-bound), parts (harvested components), and quarantine (assets pending investigation or compliance hold). The type controls what actions are allowed: you can’t add a Grade D asset to a graded-A pallet.

Move, merge, split

From the pallet detail page (/core/pallets/[id]): Move changes the rack position and writes a movement row. Merge takes two compatible pallets and consolidates them, preserving both source IDs in the merge audit. Split takes one pallet and produces N new pallets with the assets divided as the operator selects — used when half the contents pass testing and the other half need re-work.

Movement history

Every pallet has a chronological history: where it’s been, what was added, what was removed, every move and merge and split. Useful for audits, for reconciling discrepancies, and for the day somebody asks "where did pallet PALL-2026-00123 actually go in March."

Pallet barcodes

Every pallet gets its own scannable Code128 ID. The scanner’s warehouse mode reads it and brings up the pallet detail. The receiving and outbound flows use it to attach assets to a pallet without typing.