Case Study
Cinderhaven Provisions: 50 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 different outcomes for each partner. The pre-flight engine quantifies the gap before a single form goes out the door.
One product, four verdicts
Cinderhaven's Stone Ground Mustard (CHP-PS-001) is a Pantry Staples item listed with UNFI, KeHE, Walmart, and DTC. 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-PS-001's UPC (614140000103) has an invalid check digit — the last digit is 3, but should be 5. 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-PS-001 has a valid GTIN-14 (00614140000105), 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
READYRequires case-level GTIN-14 for new item setup
Valid GTIN-14, complete case dimensions, all required logistics and compliance fields present. UNFI reads the GTIN-14 column — the invalid consumer-unit barcode does not affect this submission.
KeHE
READYRequires case-level GTIN-14 for new item setup
Same pattern as UNFI. Both distributors share the case-level barcode requirement. A product that clears UNFI will clear KeHE on the barcode gate.
The full picture: 50 SKUs across four partners
Cinderhaven's product master contains 50 SKUs across five product lines: Artisan Sauces (10), Pantry Staples (10), Specialty Condiments (10), Dried Goods (10), and Snack Bites (10). The pre-flight engine validates every SKU against every partner's schema.
29
would bounce
Walmart
26
would bounce
Costco
26
would bounce
UNFI
26
would bounce
KeHE
Cinderhaven ships through 10 channels. This analysis covers four — the two largest retailers (Walmart and Costco) and the two largest natural-channel distributors (UNFI and KeHE). These four represent the critical path to national shelf presence. The remaining channels use overlapping but distinct schemas not yet modeled in the engine.
Where the gaps are
Club pack dimension gaps map exactly to case dimension gaps — the same 18 SKUs appear in both rows. Club pack measurements are derived from case dimensions; any gap in the source propagates to the derived fields. UPC-12 and GTIN-14 check-digit failures are independent — different SKUs fail each barcode standard.
The GTIN hierarchy mismatch
The product master stores two barcode columns: a 14-digit GTIN-14 for case-level identification and a 12-digit UPC-A for consumer-unit scanning. Both columns are fully populated — no blanks. But 10 UPC-12 values and 8 GTIN-14 values have invalid check digits, the kind of corruption that passes a column-count check but fails barcode validation.
This creates an asymmetry. Walmart reads the UPC-12 column and requires a valid consumer-unit barcode; 10 SKUs fail. Costco, UNFI, and KeHE read the GTIN-14 column and require a valid case-level barcode; 8 SKUs fail — a different set. The fix is straightforward — recalculate or re-source the corrupted check digits — but without a pre-flight check, the failure surfaces only when the form is rejected.
The shared-gap pattern
Costco, UNFI, and KeHE produce identical bounce counts: 26 of 50. All three read the same GTIN-14 column and share overlapping logistics requirements. The 26 failing SKUs are the same 26 across all three partners.
The practical consequence: fixing the product master for any one of these three partners substantially fixes it for the other two. Barcode corrections propagate across all three; case dimension cleanup propagates across all four. A brand that fails to recognize this pattern does the remediation work three times.
What rejection costs
Form rejection is not a paperwork inconvenience. It is a revenue event with compounding consequences. Using Walmart's 29-SKU bounce count as the worst-case baseline:
~$93K
Deferred revenue (illustrative)
At an illustrative velocity of $800/week/SKU across the launch set, a 4-week delay on 29 SKUs represents roughly $92,800 in deferred revenue. This is not lost revenue — it is revenue that arrives a month late, cascading through quarterly targets.
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.
$4,350–$14,500
Slotting exposure 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 29 bounced SKUs at a single retailer: 29 × $150 at the low end, 29 × $500 at the high end.
50–80 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 $2,250–$3,600 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 50 SKUs across five product lines with 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.