The Product Data Fields Retailers Actually Care About — And Most Brands Get Wrong

The Six-Month Sale That Ended in a Data Rejection

Every experienced CPG sales leader has a version of this story. You spend six months getting in front of the right buyer. You build the relationship. You earn the category review invitation. You present well — the brand story is compelling, the velocity data is strong, the pricing is competitive. The buyer is engaged. At the end of the meeting, they say: "Send over your item setup package and we will get this into the next review cycle." You send it the next day, confident it is complete.

Two weeks later, you get it back. The category team has flagged errors in the case dimensions. The net weight does not match what is on the submitted label. The pallet configuration is either missing or inconsistent with the case count. The GTIN format does not pass the retailer's validation check. The submission is rejected and queued for resubmission after corrections — which means it goes back to the start of the review process, not into the current cycle.

You did not lose the sale. You lost the slot. In a planogram-driven retail environment, where shelf reset windows happen on fixed schedules — typically twice a year in most grocery categories, once a year in some club and specialty channels — missing a reset window because of a data error means waiting for the next one. In many categories, that is twelve months of distribution revenue your product did not generate, twelve months of velocity history your brand did not build, and twelve months of competitive position your brand did not occupy on the fixture. The relationship cost — the buyer who has now made a mental note about this vendor's operational competence — is harder to quantify but compounds in every subsequent commercial interaction.

Every one of those errors was preventable. Not with effort or attention that the team could not spare, but with the same data that was already somewhere in the organization, managed in a system that validates it before it reaches the retailer portal and does not permit incomplete submissions to proceed. The data existed. The governance to make it reliable did not.

The UPC Fields That Generate the Most Catalog Conflicts

There is a quiet body of knowledge that lives in the retailer operations teams at Walmart, Kroger, Target, Costco, and Whole Foods Market — a running inventory of the data fields that CPG vendors consistently get wrong. Nobody publishes this list formally. But the pattern across returned submissions is consistent enough that you can reconstruct it from the error codes and the conversations that experienced sales operations professionals have with buyers' category admin teams.

Case UPC, inner pack UPC, and item UPC are the three fields most frequently submitted with errors, and the three fields whose errors have the most consequential downstream effects. These fields must be distinct from each other — the case UPC identifies the shipping case, the inner pack UPC identifies a sub-case configuration if one exists, and the item UPC identifies the consumer unit. They must follow GS1 format standards — twelve digits for UPC-A, properly check-digit validated, issued from a GS1-registered company prefix. And they must be consistent across every submission a brand makes to every retailer — the same UPC submitted to Walmart must be the same UPC in the distributor's item master and the same UPC on the Amazon catalog record.

Brands that use the same UPC for the case and the consumer unit — a shortcut sometimes taken when a brand has a limited UPC portfolio or is reusing historical barcodes — create catalog conflicts that can get their items merged with the wrong product in the retailer's system, prevent accurate receiving reconciliation, and in the Amazon context, cause ASIN merge events that transfer review history to unrelated products. Brands with duplicate UPCs across different products — another common legacy issue from early-stage brand building — create a category of problems that cannot be resolved without a systematic GTIN remediation project and new item setups across every affected retailer account.

The prevention discipline is straightforward: purchase GTINs directly from GS1, maintain a complete registry that maps every UPC to its specific product and pack configuration, and validate the registry against every active retail item setup before any new submission. In Brandhubify, UPC uniqueness and GS1 format compliance are validated at the point of data entry, preventing the error from entering the product record rather than surfacing it at the point of retailer submission.

Net Weight, Gross Weight, and the Receiving Discrepancy Cascade

The distinction between net weight, drained weight, and gross weight is legally precise and commercially critical — and it is the field confusion that generates the most receiving discrepancies in food and beverage categories at grocery and club channel retailers. The confusion is understandable: all three measurements sound like they are describing the same thing, and in some product categories, two of them are numerically close. The difference matters enormously to the retailer's receiving and freight billing infrastructure.

Net weight is the weight of the product itself, excluding packaging. This is the consumer-facing weight declaration on the label, regulated by FDA and Health Canada's Consumer Packaging and Labelling Act. Drained weight applies specifically to products packed in liquid — canned vegetables, canned fish, olives in brine — and represents the weight of the solid product after the packing liquid is removed. Gross weight is the total weight of the packaged unit including all packaging materials: the product, the container, the label, the protective film, and any secondary packaging included in the consumer unit. Retailers use gross weight — specifically, case gross weight — for freight billing calculations, receiving weight validation, and warehouse slot weight assessments.

Brands that populate the gross weight field with the net weight — either from misunderstanding or from copying the labeled weight directly — generate freight billing discrepancies on every single shipment to every retailer that uses submitted gross weight for billing reconciliation. A case submitted at 22 pounds gross weight that actually weighs 24 pounds at the distribution center's receiving dock generates a freight billing adjustment and a potential receiving discrepancy deduction on that shipment. Multiplied across hundreds of shipments per year and dozens of SKUs with the same error, the financial impact is significant — and the tracing is difficult because the error code is "receiving discrepancy," not "wrong weight field submitted."

The correction requires two things: accurate measurement of actual case gross weight from the production line — not from the spec sheet or the packaging design, but from a physical measurement of the actual finished production unit — and a product record system that treats case gross weight as a distinct, validated field separate from net weight, with a cross-validation rule that flags any submission where gross weight is equal to or less than net weight (which is physically impossible). Both requirements are straightforward. Neither is met by default in a spreadsheet-based data management approach.

Pallet Configuration — The Field Nobody Fills In From Physical Evidence

Tier and High — TI/HI in industry shorthand — describe the structural configuration of a full pallet of your product: Tier is the number of cases in each horizontal layer, and High is the number of layers stacked vertically to build the full pallet. This information is used by every distribution center in the retail supply chain to plan inbound receiving operations, warehouse slot allocation, storage capacity utilization, and outbound pick-and-pack workflows. Wrong TI/HI data causes receiving teams to build pallets incorrectly, creates physical instability in the distribution center, generates incorrect slot allocation decisions, and produces compliance chargebacks at retailers that have formal receiving compliance programs.

Walmart and Target both operate formal pallet compliance programs with financial penalties per non-compliant pallet received. The penalty structure at Walmart for pallet configuration violations ranges from hundreds to thousands of dollars per occurrence, depending on the severity and frequency. For a brand shipping multiple SKUs to a high-volume Walmart distribution center, systematic TI/HI errors are systematic chargeback generators — running quietly in the background of every shipment cycle until someone traces the deduction back to the root cause.

TI/HI data is routinely submitted incorrectly for a structural reason that has nothing to do with effort or diligence: it lives in the warehouse operations team's institutional knowledge and nowhere else. The warehouse team knows how pallets are actually built because they build them. The person filling in the item setup form — typically in the sales operations, e-commerce, or supply chain planning function — does not have this knowledge on hand. They estimate, or they leave the field blank, or they copy the figure from another product in the catalog that happens to be a similar size but is not the same case configuration. The error enters the retailer's system and waits for the first shipment to surface it as a compliance event.

The fix requires a single process change: every item setup submission must be validated against a physical pallet build by the warehouse team before the submission is finalized and submitted. The supply chain team documents the actual TI/HI from the physical build. The product record is updated with the validated measurement. The item setup form is generated from the product record. No estimation, no copying from comparable products, no blank fields. The process change is minor. The chargeback reduction is material and immediate.

Lead Time, Country of Origin, and the Fields That Live Nowhere Reliable

Lead time and minimum order quantity are two of the simplest fields in a product record — they require no measurement, no calculation, and no technical expertise to populate. They are almost always wrong in brands managing product data without a governed system, because they live in the ERP and nobody synchronizes the ERP to the commercial item master when these values change. The disconnect is structural and predictable.

A buyer who commits shelf space and builds a promotional calendar based on a four-week lead time, and then discovers after the first purchase order that the actual lead time is eight weeks — because a manufacturing shift or a supply chain change six months ago extended the production cycle, and nobody updated the item master that went to the retailer — is not going to absorb that surprise without commercial consequence. The trust deficit that a lead time error creates is disproportionate to the error itself, because lead time is a commitment that the buyer built commercial plans around. Getting it wrong signals something broader about the brand's operational reliability.

Country of origin has transformed from a secondary administrative field to a commercially and legally significant data point in a very short time. With Section 301 tariff structures applying significant cost implications to products sourced from China, USMCA compliance requirements for preferential trade treatment on North American-sourced products, and individual retailer sourcing policies that affect promotional support eligibility and shelf placement priority, CoO accuracy now affects margin, regulatory compliance, and commercial relationship quality simultaneously. Brands that have moved manufacturing — from China to Mexico, from Vietnam to the US, from any jurisdiction to any other — without updating their country of origin data across all retailer systems and distributor item masters are carrying regulatory exposure that they may not be aware of until a trade compliance audit, a deduction dispute, or a chargeback surfaces it.

The organizational discipline these fields require is not technical. It is a process commitment: when lead time changes, the product record is updated before the next commercial submission. When country of origin changes, the product record is updated and the change is logged with a timestamp and an approver. In a governed PIM, this discipline is enforced through field ownership assignments and change notification workflows. The ERP integration surfaces field discrepancies automatically. The product record always reflects commercial reality, because the system is designed to keep it there.

Brandhubify

Is your catalog running this risk right now?

Most teams don't realize how much revenue is sitting in unoptimized, stale, or non-compliant listings. Let us show you exactly where the gaps are.

Book a free catalog audit →

What the Buyer Sees — And What It Signals About Your Organization

Retail category managers and their operations teams have reviewed thousands of new item submissions across hundreds of brands. The pattern recognition they develop is fast and accurate. A submission with incorrect dimensions and missing pallet configuration does not fail solely on its technical merits — it communicates something about the organizational maturity of the brand behind it.

Buyers use submission data quality as a proxy for overall vendor operational reliability. The reasoning is logical and borne out by experience: a brand that sends a clean, complete, properly formatted item submission on the first attempt has demonstrated that it has organized internal processes, that it has managed retailer data requirements before, and that it will be a straightforward vendor to work with across the full commercial lifecycle — shipping accurately against purchase orders, managing claims and deductions professionally, and communicating proactively when anything changes.

A brand that sends an incomplete submission is signaling the inverse. The buyer's mental note about this vendor — "we should expect operational challenges" — is not explicit and may never surface in a formal conversation, but it informs every subsequent commercial decision. Promotional support allocation. New item prioritization in the next category review. Line review recommendations to the category director. The quality of the initial data submission is the first tangible evidence of how the brand runs its business, and it is evaluated accordingly.

The GDSN requirement compounds this dynamic as a growing number of retail chains — Walmart, Kroger, Albertsons, and Target most prominently in North America — progressively require suppliers to participate in GDSN-compliant data exchange. GDSN is the GS1-managed global standard for product data synchronization, and participation requires that your product data meets specific field completeness, formatting, and GS1 compliance standards. Brands that build their product data infrastructure on GS1-compliant, GDSN-ready foundations today will not face a rebuilding project when their retail partners formally require participation. The brands already receiving this requirement from their retail accounts are discovering that it is not negotiable. You comply, you invest in compliance, or you do not ship. The brands that have made the investment are positioned as the operational partners that category managers want to do business with.

The Pre-Submission Validation Process That Eliminates Rejection Cycles

The operational intervention that eliminates the majority of new item submission rejections is not more careful manual review by the team preparing the submission. It is a pre-submission validation process that checks every field automatically against the retailer's known requirements before any human submits the form — and blocks the submission if required fields are missing, formats are wrong, or values fail logical cross-checks.

The required field validation catches the most common errors: empty fields where values are mandatory, text in numeric fields, numeric values in fields that require specific unit formats, and UPC fields that fail the GS1 check-digit validation algorithm. These are errors that a human reviewer would catch if they reviewed every field of every submission against every retailer's requirements document — which is not a realistic expectation at any scale above ten SKUs.

The logical cross-validation catches the errors that field-level validation misses: case gross weight that is equal to or less than net weight (physically impossible), case dimensions that produce a volume inconsistent with the stated case count (a case of twelve 12-ounce cans that has submitted dimensions too small to contain twelve 12-ounce cans), and TI/HI values that produce a pallet case count inconsistent with the case dimensions and standard pallet footprint. These cross-checks require the system to evaluate multiple fields in combination — something spreadsheet-based review processes never do systematically.

The channel-specific template validation catches the errors that are unique to a specific retailer's requirements: fields that are required for Walmart submissions but optional for Amazon submissions, attribute formats that differ between Kroger's item portal and Target's Partners Online, and GDSN field requirements that apply to EDI-connected retailers but not to smaller specialty retailers. Brandhubify's retailer-specific templates embed these requirements directly into the validation layer, so submissions are validated against the specific channel's actual requirements — not against a generic completeness checklist. The result is that submissions leaving the system are ready for retailer acceptance, not for rejection and resubmission. The rejection cycle that currently costs brands weeks per new item introduction is eliminated structurally, not managed heroically.