Readiness Library

Amazon Seller Barcode Planning: UPC, GTIN, FNSKU, and 2D Barcodes

A practical way to separate product identifiers, internal inventory fields, fulfillment labels, and future 2D barcode decisions before you print or relabel inventory.

Last reviewed: July 15, 2026

Retail packages with barcode labels prepared for a product identifier and label workflow review
Catalog field to label to fulfillment workflow

Short answer

Do not treat UPC, GTIN, SKU, and FNSKU as one barcode problem.

Amazon sellers often have two planning layers at once: the product identifier used in catalog and sales-channel data, and the physical label used in the current fulfillment workflow. Your internal SKU is a third layer for your own operation.

The useful first step is to map which identifier belongs to each variation, which barcode is present on the item, and which team or system reads it. Only then can you decide whether you need a label test, a printer workflow review, or a broader 2D barcode pilot.

Amazon seller barcode fields at a glance

The same physical product can have multiple identifiers with different jobs. Confirm final marketplace rules in your current Seller Central workflow.

Field or labelPrimary jobUsually managed byWhat to check before printing
SKUInternal inventory and variant controlYour businessWhether every sellable variation has a clear, stable internal code
GTIN / UPCExternal product identificationBrand owner through the relevant allocation processWhether the product record and packaging use the intended valid identifier
FNSKUAmazon fulfillment inventory identificationAmazon workflowThe active account preference, product workflow, and required unit labeling
2D barcodeA possible data carrier for richer product or operational dataBrand and workflow ownersWhether the data, print quality, scanner, software, and channel have a controlled test plan

Practical checklist

Six checks before you relabel inventory

01

Separate the identifier jobs

Keep the internal SKU, the product GTIN or UPC, and any Amazon fulfillment barcode as separate fields. They can relate to the same sellable unit without being interchangeable.

02

Check the active Amazon workflow

Review the barcode preference, listing workflow, and shipment instructions in the relevant Seller Central account before printing or covering labels.

03

Map every sellable variation

Confirm that size, color, pack count, and bundle variations are mapped to the intended product record and physical label. A packaging photo is not a field map.

04

Inspect visible barcodes

Record every scannable code already present on the product and outer packaging. The receiving workflow should not depend on a team member guessing which one to scan.

05

Run a physical label test

Test the actual label size, placement, print contrast, and scan result with a representative unit before a full prep run.

06

Keep 2D planning separate

A future 2D barcode pilot is a packaging and workflow decision. It does not automatically replace the current Amazon label process or the existing product identifier.

Map your marketplace label workflow before changing hardware

Use your channels, SKU count, current barcode type, scanner, printer, budget, and timeline to identify a general readiness path.

When to pause

Keep the current process while you clarify the workflow

  • Your current products, labels, and fulfillment workflow are operating without a packaging refresh.
  • You are not adding lot, batch, expiry, serial, or consumer-facing data to the product label.
  • You have not yet confirmed a specific retail partner or operational reason to introduce a 2D symbol.

When to test

Plan a limited label and scan pilot

  • You are redesigning packaging or adding a new sales channel.
  • You need variable data such as lot, batch, expiry, or serial values.
  • You need to confirm that the current printer, scanner, and software can handle an intended 2D symbol.

Related decisions

Keep product data, print quality, and scanning connected

Start with the GTIN vs SKU workflow guide when product variations and catalog fields are unclear. Use the full identifier comparison for the UPC and FNSKU roles, then use the barcode label printer checklist before treating a print problem as a barcode problem.

If your operation also receives, picks, or packs product internally, use the 2D barcode scanner checklist for small warehouses to document the actual device, decoded output, and application result.

Amazon seller barcode planning FAQ

Is a SKU the same as an Amazon FNSKU? +

No. A SKU is an internal code created by your business. An FNSKU is used within Amazon fulfillment workflows. Keep both fields distinct, even when they refer to the same product variation.

Can an Amazon seller use a UPC instead of an FNSKU? +

That depends on the current Amazon account, product, and fulfillment workflow. Check the active barcode preference and shipment guidance in Seller Central before printing or applying labels.

Does a GTIN replace the need for an internal SKU? +

No. A GTIN identifies a trade item in external systems. An internal SKU helps your team manage variants, picking, reporting, and inventory operations.

Do Amazon sellers need to move to 2D barcodes now? +

Not automatically. Treat 2D barcodes as a readiness topic that may become relevant for retail, variable-data labels, packaging updates, or a controlled test. Confirm current marketplace requirements in your own workflow.

Should I cover every barcode on the package? +

Do not make that decision from a generic guide. Record existing barcodes and follow the current instructions for the relevant listing and fulfillment workflow before changing packaging or applying labels.

What should I prepare before requesting a recommendation? +

Prepare your sales channels, SKU count, current product identifier, barcode preference, scanner and printer setup, label volume, budget, timeline, and the question that is blocking your next step.

Need one planning path for your Amazon label workflow?

Send the essentials once: your channels, SKU count, current labels, hardware, budget, timeline, and the question that is holding up the next step.

Disclaimer

This site is independent and not affiliated with GS1. It provides educational readiness guidance only, not legal, compliance, marketplace, retailer, or GS1 approval advice.