Documentation research checked 14 October 2026. Scope: GS1 Singapore explanation of global identifiers; no shipment inspected. No hands-on test or supplier audit is reported.
A receiving discrepancy can be a mismatch between levels of identification rather than a missing product. A pallet reference, a shipment reference and a consignment reference describe different groupings. GS1 Singapore’s shipping-management explanation gives purchasing teams a useful hierarchy for discussing these records without treating every identifier as a synonym for the whole delivery.
Three reference levels in the official explanation
The page identifies SSCC as the reference for an individual logistics unit, GSIN as the reference for a shipment that can contain several such units, and GINC as the reference for a consignment that can combine shipments. This explanation was read on 14 October 2026. No actual label, identifier allocation or shipment document has been inspected for this article.
Describe the mismatch before asking for a correction
Imagine a hypothetical delivery expected to contain several pallets. An internal workbook has one column called “shipping number,” and a clerk copies a pallet identifier into it. A later message uses a shipment identifier. Comparing the two strings alone suggests a discrepancy, but the first question should be which level each reference describes. They may be different references associated with the same movement rather than competing identifiers.
A clearer workbook uses separate fields for logistics unit, shipment and consignment, with links showing their relationships. The relationship fields must come from the relevant records or partner confirmation. Do not manufacture a grouping because several items arrived at a similar time. An unexplained link can create the same reconciliation problem as an unexplained number.
A short evidence map is more useful than a renamed column
For each reference, retain its type, source document, issuing party as recorded, document date and the grouping it describes. A packing record may list individual units while a transport message refers to a consolidated movement. Both can be useful evidence, provided the file explains their different scopes. Renaming every field “tracking number” discards that distinction.
In an enquiry, ask the supplier or logistics partner which references connect the proposed packing units with the relevant shipment records. Request the relationship, not simply another number. This makes it possible for the receiving team to identify what still needs explanation without claiming that the identifier itself proves a delivered quantity, physical condition or title to goods.
Identification and event evidence remain separate
An identifier tells the reviewer which unit or grouping a record concerns. It does not independently prove that an event occurred. Arrival, receipt and item counts need their own appropriate evidence. A correctly structured reference can help connect that evidence, but the reference should not be promoted into a delivery confirmation merely because it appears in an advance message.
The resulting purchasing record should preserve the hierarchy and explain the source of each relationship. This article provides no instructions for creating identifiers or producing a compliant label. Its practical value is narrower: it helps a buyer formulate a precise reconciliation question and prevents an individual logistics-unit reference from being copied into a field that is meant to describe the entire shipment or consignment.
Evidence and limits
Document reconciliation only, not barcode allocation, transport compliance, legal ownership or delivery assurance. No real shipment IDs used.
Leave a Reply