Picture Janelle, a receiving lead at a Memphis cross-dock, looking down at a strip of shrink wrap caught under a pallet jack. Her handheld shows an advance ship notice for one pallet of 80 gift-kit cartons. The floor has two pallets, and the old label is still on one of them. If she receives the old code, the system could post 80 cartons against the first pallet and leave the second pallet available to be scanned again. She parks both pallets in an exception lane, calls the build station, and asks for the count and destination of each new load.
Reconcile physical logistic units first, then quantities and the electronic notice. Determine whether the original unit still exists, record how its cartons moved to any new units, and release only the units the downstream warehouse can identify and count. When the original pallet stays intact and only its location changes, keep the distinction between a movement event and a new logistic unit. Use the partner's written rules for assigning, printing and accepting identifiers and for correcting the advance ship notice, or ASN.
Decide what still exists on the floor
An SSCC, or Serial Shipping Container Code, identifies a logistic unit. A pallet or carton may be a logistic unit if it is managed separately in transport or storage. A GTIN identifies a trade item. A gift-kit SKU, purchase order, route or dock door is a separate piece of information. A carton can belong to a particular pallet without becoming the same thing as that pallet in the inventory record. Ask the partner what level will be scanned and recorded before accepting labels as evidence of inventory. GS1 US explains the 18-digit SSCC and its encoding in GS1-128.
Use the load as your starting point. Look for wrap or seals, count identifiable handling units, and compare the observed configuration with the current manifest. If the same 24 cartons stay on a wrapped pallet as it moves from Door 3 to Door 7, the contents and managed unit are intact. If 80 cartons from a single load are split onto two independently shipped pallets, the original unit has been taken apart. A pallet base can be reused without retaining the old load's identity. If a warehouse puts an extra transport label on an intact unit, the original SSCC must remain unchanged in the case covered by the GS1 guidance on adding or replacing a label segment. GS1 Logistic Label Guideline, sections 2.3 and 3.2.
The organization creating a logistic unit normally assigns its SSCC from its own GS1 Company Prefix under the guideline. Confirm which party is responsible for assignment in the actual cross-dock or rebuild agreement and who has authority to print. Do that before the shift, while a supervisor can still test the partner's receiving interface. The receiving team can use a temporary internal hold tag to identify where a pallet sits. A temporary tag stays outside the production SSCC namespace. Do not use the old barcode as a shortcut to accept two loads or turn an internal location number into a partner-facing SSCC.
Write a practical definition of intact for the program. It can include unchanged carton membership, agreement between the seal and unit record where seals are used, and no intervening disposition or repack event. Specify how to handle a torn label, fresh wrap, a substituted pallet base and an authorized inspection. A damaged label might require a controlled reprint for the same verified unit. A rebuild might require different identifiers. If an operator cannot prove which happened, preserve the evidence and hold the unit while the shipper checks its build log. The next person should be able to tell whether the question is identity, count, condition or paperwork.
Record what moved before making the old label unreceivable
Capture a single event record for the work. Give it an event ID, record the original unit, the build site and location, event time with an offset or UTC, operator role, planned and physical quantities with their unit of measure, and the new units and destinations. Record the exact label print and verification evidence, reason for the change and who acknowledged the handoff. Keep evidence pointers in the authorized warehouse system. The ledger should allow a receiver to trace a new pallet to the old one and an auditor to trace the old pallet to every descendant or held balance. Where both partners already exchange visibility events, their implementation may use the aggregation concepts in GS1 EPCIS. The fields here describe an operating record that can also be implemented in a partner-approved system without EPCIS.
When a parent is consumed, close its live receiving eligibility in the system that will otherwise accept the barcode. Keep its historical identity and contents record available to lookup. A parent that is closed at the cross-dock but still open on the receiver's latest ASN can still create a problem. Account for both ends. On the floor, remove, cover or mark the old scannable label according to the partner's procedure once identity and chain of custody are recorded. A photo for the incident record should be labeled as evidence. Put new scannable labels on the new units where operators can reach them, and scan each printed code back to its exact record before staging.
A split may leave some goods loose, damaged or reserved. Keep those cartons out of the new-unit totals and show them in an explicit remainder or exception bucket. Count at the same level on both sides. If the plan uses 80 cartons and a warehouse inventory report uses 400 individual kits, connect those figures only through the verified pack size. If carton sizes vary, count or reference carton-level composition for the affected units. For a mixed load, reconcile by SKU and lot where the contract requires it, since matching the overall total could hide an item swap. Have the checker confirm physical count and condition before the dock supervisor releases the load.
| Event | Required evidence | Receiving effect |
|---|---|---|
| Inspect original unit | Observed SSCC, expected notice version, time, location, pack unit and count | Hold if the physical configuration differs from the expected record |
| Split or rebuild | Input and output unit references, allocation by carton or item, remainder, operator and checker | New units become eligible only after labels and electronic records are reconciled |
| Retire parent from receipt | Old SSCC, event ID, label action, reason and downstream acknowledgment | Old identity stays searchable but cannot create a new receipt for the consumed load |
| Move intact | Same SSCC, origin and destination locations, time, seal or membership evidence where required | Changes location or custody without posting another inbound receipt |
| Receive or quarantine | Latest accepted ASN revision, new SSCC, observed and accepted quantities, exceptions and receipt ID | Posts only the agreed accepted quantity and keeps the rest visible |
Worked decision one: split 80 cartons and reject an old-label scan
Return to Janelle's two pallets. The shipper's original notice expects P-Old with 80 cartons. The runbook uses short aliases for readability. Production scans use the assigned 18-digit SSCCs. The build station confirms it made two separately managed units after the original pallet was opened. P-East contains 48 cartons, and P-West contains 32. The dock lead compares the carton records against both destinations and confirms there is no loose balance. The count equation is 80 in, 48 east, 32 west, zero held. If 48 and 31 had been counted during the build, one carton would remain unresolved. The supervisor would keep that carton on the exception ledger while verifying whether there was a count error, a hold, a damage write-off or an unauthorized move.
For the complete split, the authorized issuer assigns and verifies the new identifiers. Janelle records the old-to-new allocations, confirms the old load cannot be received, and checks that its label is no longer a candidate for scanning on the freight. Before departure the shipper sends the corrected ASN through the mechanism agreed with the receiving warehouse. The revised data lists 48 cartons against P-East and 32 against P-West. The old notice and corrected notice both remain in history. The receiving team confirms which notice is active in its WMS. A gateway acknowledgment alone might only establish delivery to the gateway. If the partner requires application acceptance, record that separately before treating the old notice as superseded.
When the second station sees a scan of P-Old, the receiver should get a stop or exception state tied to the split event. The clerk can use that scan to find the two new identities and verify the label evidence. The scan itself should post zero inventory. If the new pallet lacks its assigned label, have the authorized team reprint and verify the existing new identity only after it confirms the exact unit. If there is any chance of two physical units bearing the same ID, hold both. Use counts, carton allocation, print logs and routing evidence to determine which labels are valid, and verify the current WMS transactions before restoring eligibility. Creating two more codes in a hurry would leave downstream teams with extra identities to unwind.
Now suppose the new records reach both destinations but the receiver for P-West finds 31 usable cartons and one carton crushed at the corner. The dispatch count is still 32. The receiving record distinguishes 32 physically observed, 31 accepted and one damaged on hold. P-East accepts 48, so downstream accepted stock is 79 and the held balance is one. Nothing is missing from the overall physical count. The receiving advice or agreed discrepancy message identifies the affected unit and one damaged carton. The exception closes when the partner acknowledges how the held carton will be replaced, returned, reworked or otherwise disposed of and the appropriate stock record reflects that disposition. If only 31 cartons had physically arrived, report a one-carton shortage rather than a damaged on-hand balance.
Worked decision two: move an intact pallet without receiving it again
A separate pallet carries 24 cartons of a different kit. Its label is readable, its agreed seal check passes, and the shift record shows no break or repack. It moves intact from a staging lane to a different dock and then onto the correct trailer. The partner accepts the existing identifier for that move. Post a location or custody change against the same SSCC, verify the loading scan and preserve the one 24-carton record. A second dock scan can be a legitimate event at a different point. It should not add 24 cartons to inventory merely because a scanner read the same code again. The 24-carton unit stays outside the 80-carton split reconciliation and has its own expected receipt.
If the label was torn when the forklift picked it up, verify the human-readable code, original build record and carton membership or seal evidence before asking the authorized printer for a replacement. Match the reprint to the same intact unit and ensure the damaged label cannot be read separately if it could cause confusion. If a carton has been removed and another substituted, stop applying the intact example. The shipper and receiver should verify which changes constitute a newly built unit in their procedure, record the membership change, and confirm identity and ASN treatment before release. A claim that the old SSCC survives every repack would be as risky as assigning a new code for every dock movement.
The next shift needs enough context to resolve a late message. Keep the last known physical location, the load event, the expected receiving notice and any device retry ID together. If a clerk at Door 7 scans the same intact pallet after the supervisor at Door 3, the system should allow the real move while preventing another inbound transaction. A workable rule distinguishes a scan observation from a stock posting. The receiving endpoint can treat the same receipt request identifier as a replay and return the existing transaction outcome. A new scan at a later stop may carry a separate event ID with a different business step, even though the pallet identity is unchanged.
Handle discrepancies without making a second problem
Give each held unit a visible location, an owner and a precise condition for release. A scanner warning alone is easy to lose in a busy shift. Separate the physical hold from the transaction hold. If inventory is already posted in error, look up the actual receipt identifier and reconcile whether inventory is available for picking before initiating the approved adjustment. Record which quantities were reversed, which were left in place, and which notice or unit record was corrected. Do not delete the receipt history to make the new scan appear clean. An operator investigating later should see the first error and the corrective action in order.
If the carrier arrives before the corrected notice, the receiver can still record a physical observation and preserve a custody trail under the partner's fallback rules. The stock posting stays held until the receiver can match each valid unit to the accepted electronic record or until an authorized manual exception explicitly covers the case. If the revised notice was sent but its result is uncertain, check the outbound message ID, gateway and application acknowledgments, and the receiver's active reference before sending anything again. The trading partners' contract should say how to handle freight without an accepted notice. GS1's receiving guidance describes advance notice matching, inspection and receiving advice.
A damaged, unreadable or mismatched barcode is not sufficient evidence that a new logistic unit exists. Preserve a photo or other approved evidence, record the readable text if available, and trace back to the authorized issuer and build event. If the scanner reports a code that differs from the printed number, isolate the source label and verify the printer and scanner settings before reprinting. Keep old scans available for audit without letting them create postings. When two shipments share a dock, use destination, purchase order or partner shipment reference as corroboration. Those fields help determine where to investigate, but the receiver still needs the exact logistic-unit identity or an explicitly approved exception.
At receiving, reconcile the quantities that each system actually represents. The shipping team can confirm what it loaded. The carrier can confirm custody events. The receiver can confirm observed, accepted and held quantities, and the stock system can confirm the transactions posted. These totals answer different questions. If the dispatch notice has 80, dock observations add to 80 and usable stock is 79, the difference belongs on the damage record, not in a fabricated shortage. For corrections involving a substitution, verify the affected SKU and lot and ensure the count, contents and ownership of the affected cartons are consistent before releasing stock to fulfillment.
Test the handoff before a live cross-dock shift
Give the shipper, dock lead and receiver a shared acceptance scenario. Start with a legitimate single unit and a notice that the receiver can read. Split it into two managed outputs and verify that the receiver can see both new identities. Scan the retired label once, then scan a valid child twice as a replay of the same receipt request. Verify the first produces no receipt and the second does not add more stock. Next use a separately authorized movement of an intact unit and check that its location changes without adding to the original receipt. Keep the old notice, revised notice, event IDs, observed and accepted totals, and the recorded transaction count together so two people can reproduce the outcome.
Before running those tests, put a copy of the agreed partner mapping beside the device. The person who prints labels should see how a printed code reaches the ASN, while the person who accepts freight should see where that notice becomes active. Give both people access to the test's event IDs and receipt IDs. If the test system accepts a corrected notice but the production mapping uses a different versioning rule, have the integration owner resolve that difference before release. Keep the test freight and all its sample identifiers out of the live receiving queue.
Run one count mismatch all the way to closure. If the notice expects 32 and 31 arrive, verify that the system shows one missing and that the receiving advice reaches the party who can act. In a separate damage case, keep the 32 observed, 31 accepted and one held figures distinct. Have the receiver record whether it accepted the revised notice and whether a dispute remains open. For any replay, capture the original receipt ID and the retry response. A passing test demonstrates that the retained history explains what happened and that the live inventory reflects what the receiver authorized. Set a named escalation path for the next shift if the WMS cannot show both.
Plan the physical handoff with Giftpack
For the broader receiving, storage, pick-pack and service-level agreement, use the corporate gift warehousing guide. Keep this article’s split-unit reconciliation test attached to that wider operating agreement.
Janelle can now release the 48- and 32-carton units against the corrected notice once their labels and counts are verified, and keep the old code searchable without making it receivable. If the second station finds damage, the affected carton has a specific owner and disposition path. The 24-carton intact move remains a separate event. When the work includes outsourced kitting, storage or delivery, bring the same acceptance test to the conversation with Giftpack, whose help center describes those fulfillment services. Ask which partner owns label issuance, how its receiving team handles a revised notice, and what evidence it can return for the exact unit and quantity. Confirm those capabilities for the engagement before promising the handoff to a customer.
For a new kit project, Giftpack’s custom merchandise service is a starting point for discussing products, packaging, production and delivery. Bring the proposed pallet and receiving scenarios to that conversation. Confirm the exact warehouse, identifier and integration responsibilities for the project; the service page does not establish that a particular WMS message flow is already configured.