What traceability information should I request with a packaging delivery?
Request a record that connects the received packaging and its lot identity to the order, SKU, approved revision, relevant production records and receipt location. Decide how that relationship survives splitting cartons, repacking and issuing stock. A code printed on a label is useful only if the parties can retrieve the information behind it.
This is an operational traceability guide for packaging procurement. It does not prescribe a new identifier standard, retention period or regulated-product system. Agree the required level with your trading partners and applicable requirements. PACKRIVA is a development and sourcing coordination partner, so the production and receiving parties must identify who creates, records and retains each part of the trace.
Distinguish a product identity from a production lot
A SKU identifies the item or variant in your system; a lot identifies a defined population connected to a production or handling record. An artwork revision identifies released content. An order identifies the purchase. These relationships can overlap without being identical: one order may contain multiple production lots, and one SKU can appear in successive lots made to different approved revisions.
GS1's traceability overview distinguishes tracking events such as receiving and shipping from the data describing those events. Use that distinction to decide what your records must answer. This guide does not require every project to adopt a particular barcode format or represent a simple internal spreadsheet as GS1 certification.
Agree the link between identity and evidence
Scroll horizontally to compare all columns.
| Relationship | Information to connect | Owner to confirm |
|---|---|---|
| Order/item | Purchase line, SKU/component and quantity unit | Buyer and selling party |
| Release | Specification, artwork and relevant approved changes | Buyer release coordinator |
| Production lot | Lot reference and retrievable production/material records | Responsible production partner |
| Dispatch | Lot allocation to cartons/pallets and shipped quantities | Packing/dispatch team |
| Receipt/movement | Received amount, location, status and later stock transfers | Receiving and inventory team |
The buyer does not necessarily need every confidential production detail copied onto the packing list. Agree which records must be immediately available, which are retained by the production partner, and how a trace request is answered. Make sure the lot reference points to a defined population rather than a code whose meaning changes between departments.
Preserve identity when stock is split
Ask whether cartons contain a single lot and variant or a documented mixture. If mixed packing is allowed, require a way to identify and count each included population. At receipt, capture the original references before replacing labels or moving packaging into internal bins. A warehouse bin name is a location, not automatically a replacement for production-lot identity.
When issuing part of a carton, keep the remainder's identity and record where the issued quantity went. If loose components are combined into a kit, decide which source references must follow the assembled stock. The packaging BOM guide defines component relationships; traceability records connect the actual supplied populations to those component definitions.
Hypothetical trace exercise: the same SKU has two revisions
Suppose a warehouse holds two deliveries of the same carton SKU, with a board change approved between them. A later assembly complaint concerns only one receipt. Try tracing that receipt back to the lot, change record and applicable approval. Then trace forward to identify stock remaining and quantities already issued. This is an illustrative exercise, not a claim that the change caused the complaint.
If both receipts were pooled under one unlabeled SKU bin, document the lost distinction and take a conservative scope decision with the responsible quality team. Do not reconstruct a convenient lot assignment from memory and present it as verified. A traceability gap is a fact to resolve, separate from the technical root cause.
Test retrieval before a problem occurs
Choose a received unit or carton and ask the relevant teams to retrieve the linked order, release and production references. Check a forward trace as well: can the receiving team identify where that population is held or has been issued? Record missing links, ambiguous counts and ownership gaps, then correct the workflow. Software alone does not create a relationship that nobody captured.
Keep status visible alongside identity. Received, awaiting inspection, held, released and rejected are different decisions; a lot label should not be mistaken for quality release. Link an actual deviation to the corrective-action record, retaining the original lot identifiers as the investigation develops.
Traceability enquiry checklist
- SKU/component structure and any required external identifier system.
- Lot definition, creator and mapping to approved specification changes.
- Required packing-list fields and mixed-lot packing rules.
- Receiving locations, partial-carton handling and stock-status workflow.
- Record owners, retrieval procedure and an agreed trace exercise.
Share those requirements with PACKRIVA before packing instructions are finalized. For a reorder, also provide the applicable change-control record so a familiar SKU does not hide a different material or artwork revision.