Choose pallet and carton identifiers that survive a split

A pallet is received as one unit, then opened to fulfil three orders. The outbound cartons inherit the pallet number in a free-text field. At the next handover, nobody can tell whether a scan refers to the original pallet, one carton or the goods left behind.

Choose identifiers for physical handling units and record changes in their membership. The original pallet's history should remain discoverable, but its identity must not be copied onto several independently moving cartons.

Separate the unit from what it contains

A handling-unit identifier answers “which physical logistic unit?” Item, lot, quantity, owner and status describe its contents. Location and shipment are relationships that can change.

GS1's Logistic Label Guideline uses the SSCC to identify logistic units. If partners exchange GS1 labels, follow the applicable GS1 allocation and label requirements; an internal nickname is not automatically a compliant SSCC. GS1 Logistic Label Guideline — release 1.3, July 2019

In the examples below, P-40 and C-41 are deliberately simple internal teaching identifiers, not valid GS1 codes. A production design needs the chosen identifier scheme, issuing authority, uniqueness rules and partner expectations.

Do not encode an assumption that the unit always belongs to one destination. A pallet may be held, moved, split or returned. Making the destination part of the only identity can force a false new history every time the plan changes.

A split that preserves all twelve cases

An illustrative pallet P-40 arrives with twelve sealed cases of one item and lot, owned by one client. The warehouse dismantles this logistic unit and creates three outbound cartons plus a new reserve unit R-44, each containing whole cases for this example. The original P-40 remains a historical identity.

Five + three + two + two = twelve. All four resulting units have their own identities. P-40's content history records the transfer of all twelve cases to these units; it does not continue to claim custody of goods now recorded elsewhere.

The two residual cases remain traceable to P-40 through the split event, even though their current unit is R-44. Reusing the physical pallet does not require reusing its former logistic-unit identity: the reusable pallet asset and the assembled load are different records.

Record the split event with source identity, destination identities, quantities, unit, item, lot, owner, operator and event time. If several lots share a parent, store content lines per lot rather than inferring that every child contains all of them.

Membership changes need an event history

GS1 EPCIS provides a standard framework and artefacts for visibility-event exchange. Where partners use it, agree event semantics and supported versions before mapping local split records to their messages. GS1 — EPCIS and CBV artefacts

A local implementation can begin with an immutable movement ledger and current membership view. The ledger explains what happened; the current view answers where each quantity is now. Do not make an old parent-child relationship look current after the child has departed.

A useful trace query should answer both directions:

A query that returns only the immediate parent is incomplete if the unit was repacked several times. Follow the chain while retaining the event dates so a historical answer does not become a current-location claim.

Reprint without duplicating stock

If C-42's label is damaged while the same carton remains intact, the approved reprint process can reproduce its existing identity. Record the reason, operator and print attempt. Check that the old label cannot be reused to identify a second physical carton.

If C-42 is opened and its contents divided into two new units, create the required new identities and transfer the contents. Reprinting C-42 twice would create ambiguity, not traceability.

At the scanner, an unreadable code should lead to an authorised identity-recovery path. Let the operator search with supporting fields and obtain the required confirmation. Generating a new unit automatically because a scanner failed can strand the original stock in the system.

Make a split transaction recoverable

Before confirming the split, validate that the source contains the requested quantities and that destination identities are unused. Commit the content transfer and its history as one consistent operation where the system supports it. Concurrent attempts must not allocate the same source cases twice.

If printing fails after the content transaction succeeds, recover the existing destination identities and print their labels. Do not run the split again. If the transaction never committed, the recovery screen should show that no new units exist. An uncertain outcome requires a lookup by the operation reference.

Include a table of unresolved operations: source reserved, split committed, labels pending, physical verification pending or complete. The warehouse supervisor owns physical reconciliation; integration support owns message recovery. Neither should repair a discrepancy by inventing a balancing unit.

Demonstrate the chain before changing labels at scale

A manual unit register may work for low volumes if identifiers are controlled and transactions are promptly recorded. Native WMS handling-unit functions are preferable when splits are frequent. An extension needs to preserve the WMS's unit and content rules rather than maintaining a competing inventory ledger.

Test a split with a residual balance, a multi-lot parent, a printer failure and a return of one child. Confirm that quantities reconcile and that a reviewer can navigate from either the returned child or the original parent to the relevant evidence.

The assessment should focus on the split and recovery screens, plus the identifiers your trading partners actually accept. A more elaborate barcode does not repair a missing membership transaction.

Let identity stay stable while the contents change

The practical result is a traceable chain of physical units and content movements. It supports investigation without pretending that an opened pallet and three departing cartons are the same object.

Next actions

1. Choose the unit identity scheme and document partner requirements.
2. Define how splits, residual stock, repacks and reprints are recorded.
3. Run the twelve-case example through both forward and backward queries.
4. Test printer failure and concurrent splits before wider use.