Skip to main content
Brands & ManufacturersPrinter Partners
GCC / EN:UAE/KSA/QA/KW/OM/BH
AIQR LogoFree GS1 QR codes

Traceability & logistics

Why Warehouses Scan a Carton or Pallet Instead of Every Unit

Scanning one pallet label can receive hundreds of units, but only if aggregation data is trusted. Why warehouses work this way, and when they still open and scan.

Updated 4 min readbeginner

The short answer

Opening every case to scan every product would make warehouses far slower and would damage packaging. Instead, the warehouse scans the SSCC on a pallet or carton label and relies on the aggregation record, sent by the shipper, to know what is inside. That trade-off only works when the aggregation data is accurate, so warehouses still open and scan when a label is damaged, a seal is broken, counts disagree or the product carries extra risk.

  • One scan of a pallet's SSCC, matched against the shipping notice and aggregation data, can receive hundreds of units into stock.
  • The warehouse is trusting the shipper's packing records. That trust is earned by how carefully the packing line captured them.
  • Physical exceptions such as broken wrap, damaged cases or mismatched counts are the signal to open and scan.
  • Once a pallet or case is broken down, the warehouse becomes responsible for recording the change.

A truck backs up to a distribution centre with 26 pallets on board, each holding several hundred bottles of perfume. Nobody at the dock opens the cases. Someone scans a label on each pallet, the screen turns green, and the stock appears in the system. This article explains why that works, what is being trusted, and when a warehouse decides it should not be.

The arithmetic of receiving

Imagine scanning every unit. A pallet of 48 cases, 12 bottles each, means 576 scans, plus cutting and re-taping 48 cases. Multiply by 26 pallets and a single delivery takes most of a shift, with cardboard damaged along the way.

Scanning the SSCC on each pallet label instead means 26 scans. That difference is why warehouses work at the highest level of packing they can trust: pallet if possible, case if the pallet has to be broken, unit only when necessary.

The SSCC is the 18-digit number that identifies one logistic unit; see what is an SSCC? for its structure and rules.

What one scan actually does

The scan itself only reads a number. The work happens in the records behind it:

  1. Before arrival, the shipper sends a shipping notice listing the SSCCs being shipped and, for each, what it contains.
  2. At the dock, staff scan each pallet's SSCC. The system matches it to the notice: expected, unexpected or missing.
  3. On a match, the warehouse receives everything the notice says the pallet contains: product GTINs, quantities, batches and, where provided, unit serial numbers.
  4. The pallet is put away in a location, and the system now knows which products are in that location.

The contents listed in step 3 come from aggregation: the parent-child records made when the factory packed units into cases and cases onto pallets. The packing side of the story is in how individual products become cartons and pallets.

What the warehouse is trusting

When a receiving clerk accepts a pallet on one scan, they are trusting three things they cannot see:

  • That the packing line recorded what it physically packed. If a rejected unit was listed but never packed, or a hand-replaced unit was packed but never listed, the record is wrong from the start.
  • That nothing changed in transit. The pallet left the factory intact and arrived intact.
  • That the label belongs to the pallet. It was not swapped or reapplied to a different load.

The first point is the one brands control. It is why careful lines read every unit going into a case rather than assuming, and why rework has to go through the system. The data side is covered in what is aggregation in traceability?

When warehouses still open and scan

Good warehouses trust aggregation data by default and verify it by exception. Typical triggers for opening a pallet or case:

  • Physical damage. Torn stretch wrap, crushed corners or a broken seal mean contents may have shifted, fallen out or been tampered with.
  • Label problems. An SSCC that will not scan, appears twice, or is not on the shipping notice.
  • Count mismatches. The notice says 48 cases and the pallet clearly has 47; or a quick weight check is out of range.
  • New or unreliable suppliers. Until a supplier's records have proved accurate, receiving may include sampling.
  • High-value or high-risk goods. Fragrances, electronics and other products attractive to counterfeiters or thieves are often sampled more heavily.
  • Regulated or recall-sensitive stock. Where a specific batch is under recall or hold, staff may check cases to confirm what is present.
  • Random audits. A small share of perfect-looking deliveries is opened to keep everyone honest and measure how accurate the data really is.

When a check finds a difference, the receiver records the actual contents and reports the discrepancy. Over time, a supplier whose pallets always match earns lighter checks.

After receiving: breaking things down

Pallets rarely leave a distribution centre the way they arrived. A store order might need four cases, not 48. When the warehouse picks those four cases, the original pallet is effectively broken down. If the cases go onto a new mixed pallet for the store, that new pallet gets a new SSCC from the distributor, and a new aggregation record links it to the cases on it.

This is where traceability often weakens. The factory recorded its hierarchy carefully; the warehouse now has to record its changes just as carefully, or the chain from bottle to store is broken. The GLN of each site, the GS1 number for a location, typically appears in these shipping and receiving records so each step has a "where"; see what is a GLN?

Why this matters to brands

For a brand, warehouse practice is the reason unit-level data is only as useful as case- and pallet-level data. If a distributor receives by pallet and ships by case, the brand can still trace a bottle to a store, but only through those case and pallet records. A strong traceability programme therefore starts with accurate aggregation at the factory and agreed recording rules with distributors, rather than more scanning at every step.

The story continues from the distributor's dock to the shelf and the shopper in from carton to consumer.

Frequently asked questions

Does scanning a pallet label prove the pallet's contents are correct?

No. It proves which pallet arrived. Whether the contents match the record depends on how accurately the shipper captured aggregation, and on nothing being added or removed in transit. That is why physical checks still happen on exceptions and on samples.

What is a shipping notice?

A message the shipper sends before the goods arrive, listing what is being shipped, often down to the SSCC of each pallet and its contents. Receiving staff scan the arriving labels and match them against it.

Do warehouses need serialized products to work this way?

No. Pallet and case receiving by SSCC works for products identified by GTIN and batch alone. Unit serials only add value if someone downstream needs to know exactly which units moved.

Why not just weigh the pallet to check it?

Some warehouses do, as a quick plausibility check. A weight check can catch a missing case, but it cannot tell you which serials or batches are present.

Sources and further reading

Standards references last reviewed 1 October 2026.