Case Study
Cinderhaven Provisions: 90 SKUs, Four Partners, One Product Master
A specialty food brand preparing to launch across Walmart, Costco, UNFI, and KeHE discovers that the same product master produces four different outcomes. The pre-flight engine quantifies the gap before a single form goes out the door.
One product, four verdicts
Cinderhaven's Harissa Paste (CHP-0057) is listed with UNFI, Whole Foods, and Walmart. Its product master record has case dimensions, case weight, brand owner, and country of origin. On paper, it looks complete. The pre-flight engine tells a different story.
Retailer pair: Walmart vs Costco
Walmart
NOT READYRequires consumer-unit UPC-12 for Item 360
CHP-0057 has an all-zeros UPC (000000000000). Walmart's Item 360 system will reject this on ingestion. The valid GTIN-14 is irrelevant — Walmart indexes on consumer-unit barcode.
Costco
READYRequires case-level GTIN-14 for warehouse receiving
CHP-0057 has a valid GTIN-14 (00850074000576), complete case dimensions, case weight, brand owner, and country of origin. All required fields are present and correctly formatted.
Distributor pair: UNFI vs KeHE
UNFI
NOT READYRequires valid UPC-12 for new item setup
Same failure as Walmart. UNFI's new item form indexes on consumer-unit UPC. An all-zeros barcode will not pass intake validation.
KeHE
NOT READYRequires valid UPC-12 for new item setup
Same pattern as UNFI. Both distributors share the consumer-unit barcode requirement. The shared-gap pattern between UNFI and KeHE means fixing one fixes both.
The full picture: 90 SKUs across four partners
Cinderhaven's product master contains 90 SKUs across three product lines: Artisan Sauces (30), Specialty Condiments (30), and Pantry Staples (30). The pre-flight engine validates every SKU against every partner's schema. The results are sobering.
46
would bounce
Walmart
43
would bounce
Costco
46
would bounce
UNFI
46
would bounce
KeHE
Where the gaps are
Note: Case dimensions and case weight gaps are perfectly correlated — the same 29 SKUs are missing all four logistics fields. These are products that have never been weighed or measured at the case level. UPC-12 count includes 3 empty and 3 all-zeros (000000000000) barcodes.
The GTIN hierarchy mismatch
Every Cinderhaven SKU has a valid GTIN-14. Zero have missing GTIN-14s. But 6 SKUs are missing a valid UPC-12 — 3 are empty, 3 contain an all-zeros placeholder that no scanner will recognize.
This creates an asymmetry. Costco requires case-level GTIN-14 for warehouse receiving; all 90 SKUs pass. Walmart, UNFI, and KeHE require consumer-unit UPC-12; 6 SKUs fail immediately, before any other validation runs. The fix is straightforward — assign valid UPCs to six products — but without a pre-flight check, the failure surfaces only when the form is rejected.
The distributor shared-gap pattern
UNFI and KeHE produce identical bounce counts: 46 of 90. Both distributors require the same core fields — UPC-12, case dimensions, case weight, brand owner, country of origin. The overlap is structural, not coincidental. Both operate warehouse-distribution networks that need the same logistics and compliance data to receive, store, and ship product.
The practical consequence: fixing the product master for UNFI simultaneously fixes it for KeHE. One remediation effort covers both distributors. A brand that fails to recognize this pattern does the cleanup work twice.
What rejection costs
Form rejection is not a paperwork inconvenience. It is a revenue event with compounding consequences. For a brand of Cinderhaven's size, the arithmetic is concrete.
4–6 weeks
Delay per rejection cycle
Each rejected form triggers resubmission, re-review, and re-approval. At an illustrative velocity of $800/week/SKU across the launch set, a 4-week delay on 46 SKUs represents roughly $147,000 in deferred revenue.
6–12 months
Wait if the reset window closes
Major retailers reset shelf planograms on fixed cycles. Miss the submission deadline and the next window is 6 to 12 months away. For a brand scaling from DTC into national retail, this is the difference between launching this year and launching next year.
$150–$500
Slotting fee per SKU per retailer
Slotting fees are typically non-refundable and paid before the product ships. If the item setup form bounces and the shelf space is reallocated, the fee is sunk. Across 46 bounced SKUs at a single retailer, illustrative slotting exposure ranges from $7,000 to $23,000.
80–120 hrs
Rework labor across four partners
Diagnosing rejections, re-collecting data, re-filling forms, and re-submitting across four partners is not one task — it is four parallel tasks with different contacts, different portals, and different turnaround times. At $45/hour blended ops cost, that is $3,600–$5,400 in labor alone.
The engine behind the findings
Every number on this page was produced by the same validation engine available in the readiness tool. The partner schemas that define what each retailer and distributor requires are visible in the schema diff view. Both run entirely in-browser — no data leaves your machine.
Readiness Tool
Drop your own product master, pick a partner, and get a plain-English verdict on which fields will bounce and why. Runs entirely client-side via Pyodide.
Schema Diff
Compare item-setup field requirements across partners. Retailer vs retailer, distributor vs distributor — see where the schemas align and where they diverge.
Cinderhaven Provisions is a case-study dataset. The product master contains 90 SKUs with 25 columns and reflects realistic data gaps observed in specialty food operations. Margin-impact figures are illustrative and based on plausible industry ranges for a brand at this scale.