In this article, learn about:
The six data domains that together make up a retailer-ready product record
Which identifiers retailers check automatically before an item goes live
The compliance and digital-asset fields that hold an item in pending status
A retailer-ready product record is comprised of six separate data domains, all of which are necessary. Skip any one of them, and it could result in a scenario in which a product is sitting on your dock while the retailer’s ordering system still has no record that it exists.
Some suppliers can clear their item setup on the first attempt, while others spend weeks in revision cycles. The difference generally comes down to whether suppliers work from one complete list or fill in a form field by field. This article is intended to help suppliers understand what each domain contains, and what specifically goes wrong when something in it is missing or incorrect.
What Does a Complete Product Record Include?
Retailers collect item data through vendor portals, item setup templates, or a shared data pool, and the field names vary from one retailer to the next.
Data domain | What it covers | What breaks when it is missing or wrong |
Identifiers | GTIN, the UPC at the each level, the case code (GTIN-14), your internal stock-keeping unit (SKU), and the GS1 company prefix those numbers were issued from | The setup is rejected outright, or the item is created against the wrong brand owner and has to be rebuilt |
Descriptive content | Product title, marketing copy, feature bullets, brand name, and category or classification codes | The item lists with the wrong attributes, performs poorly in the retailer’s own site search, or routes to the wrong merchandising team |
Pricing | Unit cost, case cost, suggested retail price, and any promotional or allowance terms | Invoices stop matching the purchase order (PO), which becomes a pricing deduction after the goods have already shipped |
Physical and logistics specs | Each and case dimensions, weight, case pack quantity, pallet configuration, and shelf life where it applies | The warehouse management system assigns the wrong slot, pallets do not build to spec, and receiving flags an exception |
Compliance documentation | Country of origin, Harmonized Tariff Schedule (HTS) classification, safety data sheets, and any category-specific certifications | The item sits in pending status, or clears setup and is then held at the border |
Digital assets | Product images at the retailer’s required resolution and background, lifestyle photography, and documents such as spec sheets | The item can’t go live on the retailer’s ecommerce site even when every other field has been accepted |
Those domains are independent of one another. A perfectly licensed GTIN does not compensate for a missing image, and a complete image set does not rescue a case weight that was entered in the wrong unit.
Why Case Pack Data Is a One-Time Decision
One field inside the logistics domain behaves differently from the others, and first-time suppliers are regularly caught by it: Case pack quantity is not an editable value. Under the GS1 GTIN Management Standard, a change to the number of items in a case requires a new GTIN for that case and for every packaging level above it, rather than an update to the existing record.
The reason is that downstream systems treat the case-level barcode as a promise about quantity. A retailer’s receiving scanner and its replenishment algorithm both read that number and assume it resolves to a fixed count. Changing the count behind an existing GTIN breaks that assumption, which surfaces later as receiving discrepancies and short-shipment claims rather than an error at the moment of the change.
Which GTIN Requirements for Retailers Get Validated Before Setup?
Out of the six domains, identifiers are the one that major retailers now check automatically, before a human reviews anything. Three identifier validations are worth discussing specifically.
The GS1 Global Registry Brand-Owner Check
Retailers increasingly compare the brand owner recorded in the GS1 global registry against the company applying for onboarding. This is the mechanism that makes cheap resold barcodes a genuine liability. Codes bought from a third-party reseller are still registered to the company that originally licensed the prefix, so the registry contradicts your application. Licensing directly from GS1 US avoids the problem, either through a company prefix or, for brands launching with one or two products, a single GTIN at a flat fee.
Related Reading: GS1 Standards for New Suppliers: GTINs, UPCs, and Case Codes
Amazon’s GTIN-14 Gold List
Amazon maintains a registry of valid case-level codes, informally called the gold list. A case code that scans cleanly but is not registered on that list will fail at receiving and trigger a compliance chargeback.
Walmart’s Tiered GTIN Requirement
Walmart requires a distinct GTIN at every level of the packaging hierarchy: the each, the warehouse pack, the case pack, and the pallet. A single code covering the whole hierarchy no longer satisfies the requirement. Walmart also specifies how those codes are carried, accepting ITF-14 or GS1-128 formats on the vendor pack carton, with print quality and placement requirements attached to each.
Related Reading: What Are Walmart’s GTIN Standards?
What Is Verified by GS1?
Beyond the identifier itself, trading partners can check six attributes recorded against each GTIN through the Verified by GS1 program. Those attributes are:
Brand name
Product description
Product image URL
GS1 Global Product Classification code
Net content and unit of measure
Target market
Validation rules check that the data for a GTIN is complete and correctly formatted, not that the values are factually accurate. A record can pass every rule and still carry a net content figure that contradicts what is printed on the package. It’s generally best practice to treat Verified by GS1 as a completeness check that catches blank and malformed fields, and review accuracy yourself.
Where Do Retail Item Setup Requirements Fail?
Identifier problems are noticeable, because the rejection comes with a reason attached. The compliance and digital-asset domains can be unnoticed when they fail, which is why they account for so many items stuck in pending status.
Compliance fields carry consequences outside the retailer’s system. Country of origin and HTS classification set duty treatment. A wrong classification does not surface at setup, but rather appears later as a customs hold, or as a duty bill that does not match the quote. Codes supplied by an overseas manufacturer are a common source, since they often come from that country’s tariff schedule rather than the United States schedule.
Digital assets fail for narrower reasons that are easy to miss in a spreadsheet. Retailers specify image resolution, background treatment, aspect ratio, and how many angles they need. A good photograph of the product can still fall outside those limits.
Classification codes behave the same way. An item filed under a plausible but incorrect category will list, then underperform in the retailer’s site search.
These fields deserve the same scrutiny as the identifiers, even though nothing in the setup process marks them as risky.
Frequently Asked Questions
Is a UPC the same thing as a GTIN?
A UPC is one type of GTIN. GTIN is the umbrella term for the family of GS1 identifiers, and the 12-digit UPC used in North America is formally a GTIN-12. Case codes are GTIN-14s. The terms are related but not interchangeable, and applying a consumer UPC to a shipping carton is a recurring source of compliance fines.
How many GTINs does one product need?
One for every variation and every packaging level. A shirt in three sizes and three colors is nine distinct items at the each level, and each of those needs a case code as well if it ships by the case. Retailers like Walmart extend that requirement through the warehouse pack and pallet levels.
Can I reuse a GTIN from a product I discontinued?
GS1 standards generally prohibit it. A GTIN assigned to a product is permanent, and reassigning one leaves outdated descriptions and attributes sitting in retailer systems where they can overwrite the new product’s data.
What does complete product data for retailers look like in practice?
It means every one of the six domains is populated and verified before the item is submitted, rather than populated to the minimum the form will accept. The retail product record checklist that works is the one you run through once, in full, instead of returning to it one rejected field at a time.
Want To Go Deeper on Any Single Domain?
Each of these six domains has its own rules and its own failure modes. The Supply Chain Source carries the detailed guides on identifiers, compliance, and packaging. It also covers the electronic data interchange (EDI) transactions these fields feed into, plus vendor guides for the specific retailers you are onboarding to.
Accurate item data is what those transactions run on. The work you put into the record before your first PO is work you avoid repeating on every order after it.
This article is general information about retail item setup practices. Tariff classification and country-of-origin determinations carry legal consequences and should be confirmed with a licensed customs broker or qualified trade counsel.