Checking a container against its packing list by barcode

The day a container is opened is the cheapest day on which to find a problem. The goods have not yet blended into stock, the container and its seal are still there, and the supplier's records are fresh. If a short shipment or a mix-up is found only at the next stock count, nobody can tell whether the supplier loaded too little or the warehouse lost something. Cross-checking the packing list, carton marks and barcodes keeps such problems out on the day of receipt.

Three sources, three different statements

• The packing list is what the supplier says was loaded: carton number ranges, SKUs, number of cartons, pieces per carton and total pieces.
• The carton marks are printed on the outside and usually give an item number, a carton number, quantity and weight. They tell you what the carton says it is.
• The barcodes on the products or inner packs show what is actually inside.

All three must agree. A packing list that matches the carton marks only shows the supplier is consistent with itself, so open some cartons and check the barcodes against the contents.

Preparation before opening

• Get the packing list electronically in advance and turn it into a table with one row per SKU: cartons, pieces per carton and total pieces.
• Check it against the code mapping table so every SKU has a matching code in your system. Any that do not must be created that day.
• Clear a receiving area separate from existing stock.
• Print internal carton labels in advance, with the batch number if you use one.
• Divide the work: one person opens cartons, one scans, one records and one photographs and supervises.

Steps on site

1. Before opening the doors, photograph the container, check that the seal number matches the documents and file the photos.
2. Unload in stages, placing each stage in the receiving area, stacked by SKU.
3. Count the cartons of each SKU and compare with the packing list.
4. Open at least one carton per SKU, scan the inner-pack barcode, and confirm the barcode matches the SKU and the pieces per carton agree with the marks and the packing list.
5. Record exceptions: short, over, mixed-up, damaged, or a barcode that does not fit the SKU. Photograph each one.
6. Book what was actually received, not what the packing list says. Put the differences on a pending list for someone to take up with the supplier or forwarder. The time allowed for raising a claim is set by your contract, so sooner is better.

Keep a receiving record with one row per SKU: packing-list cartons, cartons received, pieces per carton, cartons opened, barcode match, exception notes and photo references. Fill it in while unloading, not afterwards from memory. It is also your strongest evidence with the supplier or forwarder.

An example that a total alone would miss

Suppose the packing list shows 600 cartons: 120 of C-2205 LED strip, 80 of B-0360 Bluetooth earbuds and 400 of other SKUs, with 10 pieces in every carton.

After unloading, the carton count is 600, not one fewer, which looks like a perfect match. But checked SKU by SKU, 120 cartons carry C-2205 marks, and opening a sample shows that 2 of them actually hold earbuds with the B-0360 barcode. By contents, there are only 118 cartons of C-2205 and 82 of B-0360.

If this goes unnoticed and the goods are booked per the packing list, the books show 20 pieces of C-2205 more than exist and 20 of B-0360 fewer. Equal and opposite, they look like two unrelated problems at the next count and take long to trace. Found on the day, the fix is to book the physical quantities and tell the supplier about the wrong marks on two cartons.

Why the same day matters

• The goods are not mixed into stock, so it is obvious which cartons belong to this delivery.
• Once the goods are in stock and mixed with existing items, a short shipment can no longer be told apart from an internal loss.

Not every carton has to be opened. Each SKU needs at least one check of barcode against contents, plus a complete carton count.

In short

Check the packing list, carton marks and barcodes against one another, and do it the same day. The code mapping table and internal labels that InventoryHub uses can be set up at receiving, so every later count carries on with the same codes and nothing is left unmatched.