CHENGBRIDGE / BUYER GUIDE

Carton IDs vs Product SKUs: Keep Shipment Packages Traceable

Warehousing & Consolidation

Use the SKU to identify the product or variant and a carton ID to identify the physical package. Link them in a carton-to-content register so receiving and consolidation teams can tell which package arrived, which one is on hold and where its contents went if it was repacked.

Decide which physical units need separate IDs

Start with the decisions people will make when handling the goods. If two cartons contain the same SKU and either carton could be received, held or repacked separately, give each carton its own reference. The product code tells the handler what the cartons contain. The package reference tells them which carton a decision applies to.

Before suppliers print labels, agree with the parties handling the goods which physical units need separate tracking and what reference they will use to identify each one. Keep the agreement focused on package identity. Product master data and carrier tracking are separate matters.

Hypothetical example. Two cartons arrive in the same supplier delivery with the same SKU and quantity. The receiving team holds one carton and clears the other for consolidation. Recording the hold against the SKU leaves both cartons matching the description. Recording it against the held carton’s ID lets the next handler identify the package that should stay on hold.

Confirm whether the receiving partner requires GS1 labels

A buyer’s internal carton reference and an SSCC serve within different identification arrangements. GS1 identifies the SSCC as the identifier for a logistics unit within its standardised logistic label system. Treat an internal reference as an SSCC only if it meets the applicable GS1 requirements. GS1’s explanation of the logistic label

If a trading partner requires GS1 labels, confirm the applicable allocation and label requirements through GS1 and the receiving partner before suppliers print. Confirm any expectations for certification, label validation or scanning-system integration separately within the agreed scope.

Build a register that answers receiving questions

For each package, record the agreed package reference, the supplier delivery it belongs to and the SKU, quantity and counting unit for each item inside. Use a separate content line for each SKU in a mixed carton and repeat the same package reference on those lines. Count the distinct package references when checking how many cartons the register describes. Use the content lines when checking what is inside each carton.

Use measured or confirmed information. If a quantity or counting unit is unclear, record the question and who needs to resolve it. Link the register to the current packing list so the receiver can use the delivery reference to find the relevant cartons and then look up their contents. Packing-list handover guide

Record field What the handler should be able to establish What to resolve if unclear
Package reference Which physical unit the entry describes Confirm the reference with the parties handling the unit.
Supplier delivery Which arrival the package belongs to Check the reference against the current packing-list handover.
SKU, quantity and counting unit What the package contains and how the quantity is expressed Confirm the details for each content line, including every SKU in a mixed carton.
Hold or ready status Which carton is held and which is ready Confirm the status against the specific package reference.
Package change Which earlier reference connects to each replacement package Confirm the replacement references and what went into each package.

Keep the history when a carton is opened or split

Check whether the original record still describes the physical result after a carton is opened. If the contents are split or moved into replacement packages, agree how the handlers will create replacement references, record the resulting contents and link the new records back to the earlier reference. Keep the earlier record so someone looking up the original carton can follow where its contents went. Reusing an old label can obscure that movement if it leaves the receiver with a reference that appears to describe the original package.

Hypothetical example. The contents of a mixed carton are split between two replacement cartons. Record each replacement reference with the SKUs and quantities it now contains, and link both back to the original carton reference. A handler can then start with the original delivery record, find both replacements and check which one contains the SKU they need. Confirm who may authorise the repacking and what materials are needed as separate decisions.

Review the record with the people receiving the goods

Before routine use, give the receiving parties a small illustrative record and ask them to follow it as they would during handover. Can they match a reference to one physical package, find all its contents and distinguish a held carton from ready stock? If the record includes a split, ask them to trace the original reference to the replacement packages. This is a review of whether someone can follow the record. Successful scanning and software integration would require separate confirmation.

Use the table as a repeatable review. For each unresolved item, record the current reference, the confirmed information, the open question, the decision owner and the next action. Leave approval open until it is confirmed. If the uncertainty is about which product or variant a code represents, resolve it through SKU mapping. SKU mapping guide

ChengBridge provides this as general buyer guidance. Confirm the requirements and agreed scope for your actual goods, and seek professional advice where needed. Discuss consolidation requirements and share your package identification needs before the goods move. Consolidation requirements and share your package identification needs.

PUT THE GUIDE INTO PRACTICE

Tell us what your next order needs.

Share the product, quantities, destination and support you need. We will discuss a suitable service scope.

Scroll to top