Your New SKU Breaks for 90 Days. Almost None of It Is Your Carrier's Fault.

A new SKU launch is not a supplier-performance problem. For roughly the first 90 days it is a setup problem.

Four things are un-dialled: routing, the 3PL's grip on the label spec, which DC serves which store cluster, and an item master nobody has finished trusting.

None of those are your carrier failing at their job. Every one is configuration you own. A carrier failure can be escalated. A configuration error has to be fixed by you.

What is not dialled in yet

Routing has not been proven

For the first loads, the route a SKU takes is an assumption, and Walmart codes it failing: WM-RTG, unauthorized carrier, not usually disputable. Home Depot gives you 48 business hours to file on its routing code, and Costco prices a missed appointment as a routing event too.

The 3PL is still learning the label spec

Your 3PL learned the label spec for the products it shipped last month, and your new SKU is not one of them. Nearly every code that catches this is marked not usually disputable: WM-LBL for an unscannable GS1-128 label, COST-SSCC for an SSCC label where both carton sides are required, HD-DQC for a GTIN or UPC data failure.

A dispute cannot make a barcode scannable. Walmart's document set for a labelling violation is label artwork approval, GS1 barcode verification and carton label photos: evidence you needed before the load, not the argument you need after it.

Nobody knows which DC maps to which store cluster

Every DC has its own appointment rhythm and its own idea of which store cluster it feeds, and in month one your team learns that by missing. Walmart's scheduling penalises arriving early exactly like arriving late, at 3% of cost of goods, under WM-OTIF.

No retailer publishes a DC-to-store-cluster map, and neither does our source material. The only reliable reference is the receiving record from the first loads, which is precisely the artefact nobody archives in month one.

The item master is not yet trusted

The retailer received your item before your team finished trusting it, and the mismatch is discovered at the DC, in cartons, not in a spreadsheet. A quantity your system says and the pallet does not produces WM-ASN, an SSCC mismatch, quantity discrepancy, or missing carton, and WM-CTN when the carton count disagrees with the pack list. The item master is a chargeback generator before it is a record, and item master data hygiene is what prevents it.

The codes that cluster here

Four of those twelve are marked not usually disputable, and the 90-day window is what manufactures them. No filing recovers a bad label.

The fill-rate codes are the ones that hide inside a successful launch. Kroger prices case fill at a fixed dollar amount, $50 to several hundred per violation regardless of product value, and a short-shipped carton can trigger a case-fill deduction and an ASN accuracy deduction at once, because the ASN described a full load and the truck did not carry one. One physical event, two filings, and the second is the one nobody planned.

Walmart's three-month grace period is narrower than it reads

First-time Walmart suppliers get a three-month grace period where OTIF fines are waived. Two edges to it.

The grace is written against OTIF, and it is not a general amnesty. In the same penalty structure, ASN and labelling failures are priced at $50 to $500 per incident. Our source data does not say whether the grace extends to those codes, and you should not plan on it.

Check tenure before you dispute, not after. And file in the right queue regardless. OTIF and compliance chargebacks are accounts-receivable deductions and go through HighRadius, not the AP Disputes Portal in Retail Link. File an OTIF dispute in APDP and it is auto-denied while the original 30-day clock keeps running.

What a malformed 856 actually looks like

A broken ASN fails on structure, not on meaning. Parsing stops at a missing BSN, a BSN with no transmitted date and time, a missing TD1 carton count, a missing PRF purchase-order reference, an absent LIN or SN1 item loop, and an SN1 missing for its LIN. Each halts the parse before a line item is extracted, which is why an 856 that looked clean on your vendor console can be worth nothing at the DC.

Two details make it worse in month one. The SKU is read off LIN by qualifier, and the qualifiers that resolve are VN, BP, IN and VC; anything else lands as UNKNOWN, and an ASN whose every line reads UNKNOWN matches nothing. DTM 035 is the actual arrival; DTM 017 is an estimate and never one.

The 856 log and the 997 acknowledgment the retailer returns are the difference between a timing argument and an opinion. The 997 nobody archives is the one teams find too late: pull both from the first load, not the first dispute.

The shape of the 90 days

Week one

• Item master data records and GS1 GTIN or UPC documentation sit in one place and match the retailer's copy; label artwork is approved and verified against the template actually in use. Home Depot's DQC filing asks for both, and is not usually disputable.
• ASN logs and 997 acknowledgments are written somewhere that outlives the launch. Costco expects its 997 back within 24 hours of receiving any EDI document.

By day 30

• The first receiving records have been compared against what the ASN claimed, on the earliest loads rather than the latest.
• Every reason code seen so far has been checked for whether it is disputable at all, so nobody spends a week on a packet for WM-LBL.
• Three consecutive loads agree on carton count, quantity and SSCC.
• Someone has written down the date each portal counts from, which differs by retailer and is not the remittance date in most cases.

By day 90

• The 3PL's label spec for this SKU is the default, not an exception somebody remembers, and the appointment window is read before dispatch, not learned from a deduction.
• Case fill holds above 95%, the line where KRG-CFR and WM-OTIF fire, and the number that proves the item master and the physical product agree.
• Retention outlasts the longest window you sell into: 180 days at Kroger and at Albertsons, not the 30 days that dominates most people's mental model.
• The deduction memo date, not the remittance advice, is what the team watches.

Every deadline in that list is in the dispute window table.

Month one is expensive not because the SKU is hard to ship, but because you launch, the 3PL confirms the first ASN, and everyone goes back to work.

The date on the deduction memo is the clock, and Walmart's OTIF window runs about 30 days from the invoice date. Find the oldest open memo in the portal this week: that is the one that decides whether your first 90 days cost you 3% of cost of goods on the affected cases, or nothing at all.