Oct 11, 2026Quality Inspection Guides

Barcode Inspection: What Scanning Can and Cannot Verify | G&D

Learn what barcode scanning during product inspection can verify, how it differs from formal barcode verification, and what buyers should provide.

Barcode Scanning During Product Inspection: What It Can and Cannot Verify

“The barcode scans, so does that mean it is correct?”
Not necessarily. A scanner may read the printed code successfully while the code still belongs to another color, size, model, or packaging level. It may also decode the expected number without proving that the number is registered to the correct company or connected to the correct marketplace listing.
A barcode scan can show whether a sampled code can be read by the scanner used and what data it decodes. The decoded value can then be compared with the buyer’s approved barcode-to-SKU list. It does not by itself prove identifier ownership or registered GS1 data, formal barcode print-quality grade, marketplace association, or readability under every scanning condition.
The inspection scope therefore needs to define more than “check barcode.” It should state which code is being checked, where it should appear, which product it belongs to, and what reference should be used for comparison.

What Can Barcode Scanning During Product Inspection Verify?

During an on-site product inspection, the inspector can scan selected retail units, inner boxes, or master cartons using the available scanning device.
A successful scan confirms two practical points:
  1. The scanner used during the inspection could read the sampled barcode under the conditions at the factory.
  1. The scanner displayed a decoded value that could be recorded and compared with the buyer’s reference information.
The second step is essential. A beep from the scanner does not show whether the decoded number is the correct number for that product.
If the buyer provides an approved barcode list showing the product, SKU, color, size, capacity, and expected code, the inspector can compare the scanned value with that list. Without this reference, the report may only confirm that the barcode produced a readable value.

Barcode Scanning Is Not Formal Barcode Verification

A normal barcode scanner and a barcode verifier perform different jobs.
A scanner attempts to read and decode the symbol. It can show that a particular device successfully read the barcode and can display the encoded data.
Formal barcode verification measures symbol quality against applicable standards using suitable verification equipment and methodology. The current GS1 General Specifications distinguish between a scanner and a verifier and explain that verification is a technical measurement process.
For linear barcodes, ISO/IEC 15416:2025 specifies a methodology for measuring and grading barcode print quality. ISO/IEC 15415:2024 covers print-quality testing for two-dimensional symbols.
An ordinary handheld scanner used during a factory inspection is not a barcode verifier. A code that scans successfully has passed that particular scan attempt; it has not automatically received an ISO print-quality grade.
The reverse also deserves attention. One failed scan does not immediately explain the cause. The problem may involve printing, contrast, damage, label position, scanner compatibility, surface shape, lighting, or the barcode type enabled on the device. The inspector should record the conditions and result rather than describe every failed scan as formal non-compliance.

Seven Barcode Checks Buyers Should Distinguish

Barcode Check
What It Can Confirm
What It Cannot Confirm
Visual label check
Label presence, visible damage, obvious printing problems, HRI text, and comparison with approved artwork
Encoded data or scanner readability
Scanner readability check
The sampled barcode can be decoded by the scanner used under the inspection conditions
Readability by every scanner, warehouse, or retail system
Decoded-data check
The exact value returned by the scanner
Whether that value belongs to the correct product
SKU and product match
The decoded value agrees with the buyer’s barcode-to-SKU list for the identified product
Database ownership or marketplace listing association
Placement check
The label position agrees with the supplied artwork or placement requirement
Formal symbol-quality grade
Formal barcode verification
Symbol quality measured and graded using appropriate verification equipment and methodology
Product identity or data ownership unless separately checked
Database or marketplace validation
The identifier or listing information returned by the relevant external system
Physical print quality or correctness across uninspected units
These checks may be combined, but they should not be described as if they prove the same thing.
For example, a visual check may confirm that a barcode label is present on the retail box. Scanning may confirm that it decodes to 1234567890123. SKU comparison may confirm that this value is assigned in the buyer’s list to the 500 ml black bottle. Formal verification and external database checks remain separate activities.

How an Inspector Checks a Barcode Against the Correct SKU

The inspector first identifies the sampled product from its model, color, size, capacity, packaging, or other SKU information.
The next step is to photograph the product and its barcode label together where practical. This helps show which physical item carried the code.
The barcode is then scanned, and the decoded value is recorded. That value is compared with the approved barcode-to-SKU matrix supplied by the buyer.
For a complete comparison, the inspector needs to answer:
  • Which product or packaging level was checked?
  • What barcode was physically applied?
  • Did the scanner read it?
  • What value appeared after scanning?
  • Does that value match the approved code for the identified SKU?
  • Is the label in the approved location?
  • Were any other visible barcodes present?
Without the approved matrix, the inspector should not guess which barcode belongs to which product.

Example: Barcode Inspection for a Multi-SKU Bottle Order

Consider a hypothetical order of stainless steel water bottles:
SKU
Product Variant
Approved Barcode
BTL-500-BLK
500 ml black bottle
EAN A
BTL-500-WHT
500 ml white bottle
EAN B
BTL-750-BLK
750 ml black bottle
EAN C
The inspector selects samples from the available shipment according to the agreed inspection scope.
For one selected unit, the inspector confirms that the product is the 500 ml black version, photographs the bottle and retail packaging, scans the label, and records the decoded value. The result is then compared with EAN A in the buyer’s approved list.
The same process is repeated for the selected white 500 ml and black 750 ml bottles. This can identify a situation where EAN A scans correctly but has been placed on the 750 ml bottle, or where both 500 ml colors unintentionally carry EAN B.
The report can show the product variant, barcode label, decoded value, comparison result, and any mismatch found.
This process still does not prove that every bottle carries the correct barcode. It also does not confirm GS1 ownership, formal barcode print quality, or the relationship between the EAN and an external marketplace listing unless those separate checks have been specifically arranged.

Common Barcode Problems Found During Product Inspection

A barcode check may identify several different problems:
  • The barcode does not scan with the device used.
  • The barcode scans but returns the wrong encoded value.
  • The correct barcode has been placed on the wrong SKU.
  • Two different SKUs unintentionally carry the same barcode.
  • The factory used an outdated version of the label artwork.
  • A required barcode or FNSKU is missing.
  • An FNSKU does not match the current buyer-provided FNSKU or approved label reference.
  • Another sticker covers part of the barcode.
  • The symbol is scratched, folded, blurred, cut off, or poorly printed.
  • The label is positioned differently from the approved artwork.
  • The retail-unit barcode does not agree with the carton information.
  • The human-readable text below the barcode does not agree with the approved information or decoded value.
A visible print defect does not always cause a scan failure. A barcode with a minor cosmetic mark may still scan, while a clean-looking code may fail because of its dimensions, contrast, surface, or printing characteristics. The report should separate visual findings from actual scan results.

What If a Product Has Multiple Barcodes?

One retail package may carry several codes:
  • A manufacturer UPC or EAN;
  • An Amazon barcode such as an FNSKU;
  • A retailer-specific label;
  • A logistics code;
  • A carton barcode;
  • A serial-number or authentication code.
These codes may serve different systems and packaging levels. The inspector needs clear instructions showing which code belongs on the product, retail package, inner box, and master carton.
Amazon’s current FBA product barcode requirements distinguish manufacturer barcodes from Amazon barcodes such as FNSKU. Because the required code depends on the product, seller setup, and shipment instructions, the buyer should provide the current label file and state which codes should remain visible or be covered.
During inspection, selected units can be compared with those supplied instructions. Physical scanning does not independently confirm marketplace association or shipment acceptance.

How Many Units Should Have Their Barcodes Scanned?

Barcode checks during a sampled product inspection are normally sample-based unless another scope is agreed.
Possible approaches include:
  • A defined quantity for each SKU or barcode;
  • Scanning every unit in the main inspection sample;
  • A buyer-defined quantity based on the order risk;
  • Additional samples from different cartons or production batches;
  • An expanded check after a mismatch is found;
  • A separately agreed 100% barcode scan where operationally feasible.
There is no universal barcode quantity that suits every order. An order with one product and one barcode presents a different risk from an order containing many colors, sizes, bundles, and marketplace labels.
A 100% check requires access to every unit, sufficient time, and clear data-recording rules. It must also define the purpose of the check.
100% scan/readability check ≠ 100% barcode-to-SKU correctness check
Scanning every unit means each barcode is subjected to the agreed scan using the specified device or method under the inspection conditions. It does not prove readability under every scanner or operating condition.
To verify barcode-to-product correctness on every unit, the process must also identify each physical SKU or product and compare its decoded value with the approved barcode-to-SKU matrix.
Whatever quantity is used, a sampled barcode check does not prove that every unit in the shipment carries the correct code.

What Barcode Scanning Cannot Prove

Unless additional checks are specifically arranged, ordinary on-site scanning does not automatically prove:
  • That a GTIN is licensed to the correct company;
  • That the code and product information are registered correctly with GS1;
  • That the symbol meets an ISO barcode print-quality grade;
  • That a marketplace links the code to the intended listing or will accept the shipment;
  • That every warehouse or retail scanner will read the code;
  • That every unit in the shipment carries the same correct barcode;
  • That the label meets all regulatory requirements.
For UPC, EAN, and other GS1 identifiers, ownership and available product information can be checked separately through Verified by GS1. That database check is different from scanning the physical label at the factory.
Formal print-quality verification is also a separate activity. It requires appropriate equipment, methodology, and defined acceptance requirements rather than an ordinary scanner and a successful beep.

Why Barcode and SKU Matching Matters for E-Commerce Orders

Barcode mismatches are particularly relevant when one order contains several colors, sizes, capacities, bundles, or private-label versions.
A warehouse may use the scanned code to identify where stock should be stored. A fulfillment system may use it to connect the physical unit with an online SKU. If a readable barcode is attached to the wrong color or bundle, the code can work technically while directing the wrong product through the fulfillment process.
For an e-commerce order, the inspection scope may therefore need to connect four elements:
Physical product → SKU → barcode → packaging level
An E-commerce Product Inspection can include this comparison when the buyer provides the required product and barcode references. It does not replace marketplace-side validation.

What Evidence Should Appear in the Inspection Report?

A useful barcode result should show what was actually checked rather than only stating “barcode PASS.”
Depending on the agreed scope, the report may include:
  • Product and SKU identification;
  • A photograph of the barcode label;
  • The decoded value;
  • The approved value used for comparison;
  • The scan result;
  • The quantity checked for each SKU or barcode;
  • The product, retail, inner-carton, or master-carton level;
  • Label placement observations;
  • Details of mismatches or unreadable codes;
  • Limitations, such as unavailable references or a barcode type unsupported by the available scanner.
This evidence allows the buyer to distinguish a readability result from a product-matching result.

What Should Buyers Provide Before Inspection?

Before the factory visit, provide:
  • SKU or model number;
  • Approved barcode number or encoded value;
  • Barcode type where relevant;
  • Product, color, size, or capacity linked to each code;
  • Approved artwork or label file;
  • Required label location;
  • Retail packaging configuration;
  • Current FNSKU or marketplace label instructions where applicable;
  • Inner-carton and master-carton barcode requirements;
  • The required scanning quantity or sampling approach;
  • Any specific device, application, or data-recording method required.
These requirements can be organized in a barcode-to-SKU matrix and included in the product inspection checklist.
The purpose is to give the inspector a clear expected result for every code. “Scan barcode” is not enough when several products, labels, or packaging levels are involved.

Frequently Asked Questions

Does a barcode that scans mean it is correct?

No. It means the scanner used could decode the symbol. The returned value must still be compared with the approved value for the correct product and SKU.

Is barcode scanning the same as barcode verification?

No. Scanning reads and decodes a barcode. Formal verification measures and grades barcode quality using appropriate verification equipment and an applicable methodology.

Can an inspector check whether a barcode belongs to the correct SKU?

Yes, if the buyer provides an approved barcode-to-SKU list. The inspector can identify the sampled product, scan the code, and compare the decoded value with the expected value.

Can barcode inspection verify an FNSKU?

The inspector can compare its presence, placement, readability, and decoded value with the buyer-provided FNSKU or approved label reference. Marketplace association requires separate platform-side validation.

Does scanning prove GS1 compliance?

No. These are separate checks. Identifier ownership and available registered data require a reference or database check such as Verified by GS1. Symbol print quality requires formal verification using appropriate equipment and methodology. Placement, dimensions, and other symbol requirements must be compared with the applicable specification. Physical SKU matching requires the buyer’s approved barcode-to-SKU matrix.

How many products should have their barcodes scanned?

The quantity should be agreed according to the number of SKUs, barcode types, order risk, inspection time, and purpose of the check. There is no universal quantity for every inspection.

Can barcode scanning be included in a pre-shipment inspection?

Yes. Barcode presence, readability, decoded value, SKU matching, and label placement can be included in a Final Random Inspection when the scope and reference information are confirmed in advance.

Does a sampled barcode check cover the entire shipment?

No. It provides information about the selected samples. If every unit must be checked, the buyer should define whether the required scope is a 100% readability scan or a 100% barcode-to-SKU comparison.

Define the Barcode Check Before the Visit

If barcode, SKU, or labeling accuracy is important to your order, provide the approved barcode list, artwork, product mapping, and packaging requirements before inspection.
A clear scope allows the report to show not only whether the barcode scanned, but whether the decoded value was found on the correct product.