Reconcile bags and consignments at a PTL hub handover

Three bags leave a PTL hub and three bags arrive at the next hub. The bag-level report shows a complete handover. One bag has a seal exception and contains fewer expected pieces plus a parcel from another route.

Reconcile the bag and its membership at the relevant handover. Bag count establishes one level of custody. Piece identities establish which consignments actually moved. Neither a matching bag count nor a seal observation proves the contents by itself.

Define the unit beneath the consignment

A consignment may contain several physical pieces. Record the relationship between consignment, piece, bag, vehicle and journey leg. If a bag holds only some pieces of a consignment, the receiving hub needs that allocation rather than a single header-level “received” status.

GS1's Logistic Label Guideline describes unique logistic-unit identification. A bag or handling-unit identifier can link movement records, while the system still needs an explicit record of its contents. GS1 Logistic Label Guideline — release 1.3, July 2019

Use an immutable identifier for the bag instance and a membership version. A reusable bag asset may be used for many trips; its asset tag alone must not make yesterday's contents appear in today's handover.

Three bags and two missing expected pieces

The following illustrative manifest contains forty consignments, each with exactly one piece. This simplifying assumption does not apply to a normal multi-piece consignment.

All three bags arrived. The physical count is thirty-nine, but the shortage against expected identities is two, not one. One unrelated piece also needs an investigation.

The reconciliation is forty expected = thirty-eight matched + two missing. Physical custody is thirty-nine = thirty-eight matched + one unexpected. These two equations answer different questions and should both appear in the handover record.

If one of the two expected pieces is later found in an adjacent staging position, matched receipt becomes thirty-nine and the unresolved expected shortage falls to one. The unrelated piece remains a separate custody exception until its rightful journey is established.

Preserve the seal observation without overinterpreting it

Record the expected seal reference, observed seal reference, visible condition, observer and time under the site's procedure. Preserve supporting images where appropriate and link them to the bag instance.

A broken or mismatched seal can justify enhanced review. It does not establish when contents changed or who is responsible. An intact seal also does not prove that the origin packed the expected pieces.

If the bag must be opened or repacked, record the original observation first where operationally appropriate, then create the new membership and seal record. Do not overwrite the previous seal field with the replacement and lose the exception.

Make the handover a set comparison

Collect the origin's approved manifest version and dispatch confirmation, then compare them with destination observations. Classify expected-and-found, expected-but-missing and found-but-unexpected identities.

A duplicate scan of one piece should not increase the received quantity. Two physical pieces carrying the same identifier require an identity exception; software deduplication alone cannot decide which one belongs.

GS1 EPCIS can support structured visibility-event exchange between partners. Agree how aggregation, separation and correction events map to the local bag process before relying on them for reconciliation. GS1 — EPCIS and CBV artefacts

Handle a split without stranding the history

If bag B-2 is opened and its pieces are distributed into two onward bags, record each piece's new membership and the event that ended the old membership. The investigation should still trace a piece back to B-2 at the earlier handover.

Do not mark every consignment in B-2 as forwarded merely because one onward bag departs. Confirm piece-level allocation and the relevant vehicle departure. For a multi-piece consignment, preserve partial progress.

Late manifest messages need version handling. A correction received after the bag arrives may explain an origin data error, but it should not silently erase the original discrepancy. Show the original manifest, corrected scope, authorisation and effect on the reconciliation.

Choose a control that exposes the unexplained pieces

A structured scan register can work for a small hub if identifiers and memberships are reliable. Native hub software should demonstrate bag closure, reopen, split and partial receipt. An integration must preserve those relationships rather than flattening everything into one consignment status.

Test the forty-piece example, a duplicate scan, an unexpected identity and a multi-piece consignment split across bags. The acceptance condition is a complete accounting of expected and physically observed pieces, with an owner for every difference.

Measure unresolved pieces, time to establish custody and repeated membership errors. A 100% bag-receipt rate should not be presented as a 100% consignment reconciliation rate.

For a hub-handover assessment, begin with one route and the point where bag membership is currently lost between systems or paper manifests.

Reconcile the contents that the next hub must handle

A reliable handover preserves both container-level custody and piece-level identity. That makes the next sorting decision possible while the unresolved seal or shortage remains visible.

Next actions

1. Map consignment pieces to bag instances and manifest versions.
2. Compare expected and observed identity sets at one handover.
3. Preserve seal changes and split history.
4. Assign separate actions to missing, unexpected and unidentified pieces.