Nordstrom sells through three channels — full-line stores, Rack, and .com dropship — and each one orders differently, ships differently, and can charge you back differently. Nordstrom supplier compliance (covering ASN, ticketing, and packing deductions) is therefore really three overlapping rule sets, and the suppliers who stay clean are the ones whose EDI layer knows which channel every document belongs to. Here's the channel-aware view of Nordstrom compliance; the requirements baseline is in the Nordstrom EDI requirements guide.
Channel context starts at the order
The inbound 850 declares its channel through its PO pattern, and everything downstream must honor it. Wholesale orders flow toward DC shipments and consolidated ASNs; dropship orders each carry a consumer's ship-to and demand a per-order ASN. Item identity is apparel-grade throughout: Nordstrom style/SKU plus UPC, with size and color expanding at the line level. Practical consequence — your cross-reference isn't one table but a matrix across style, color, and size, and a gap anywhere in it surfaces later as a mispicked carton or an unmatchable invoice line.
Size-level truth in the ASN
The 856 is where Nordstrom's packing enforcement bites. The document uses pick-and-pack hierarchy with carton contents described at the size level, GS1-128 labels must match the ASN's carton serials exactly, and the ASN transmits at shipment, ahead of the DC appointment. Apparel receiving scans cartons against the document; a size run that got consolidated in packing but not in the ASN reads as a packing violation even though every unit eventually arrived. The architecture that survives this is familiar but non-negotiable: carton contents captured at pack-out, labels and ASN rendered from that single record, transmission triggered by ship-confirm.
Ticketing and the invoice: the other two pillars
Ticketing deductions live mostly in the physical world — the right tickets on the right goods — but the data that drives ticketing comes from the same item matrix your EDI documents use, which is one more reason to keep it authoritative. The 810 has two rules of its own: markdown and advertising allowances ride as itemized SAC segments rather than disappearing into unit prices, and the invoice mirrors the 856 as shipped or it short-pays. Billing from shipment data — never from the order as originally cut — makes the second rule self-enforcing.
Dropship deductions compound quietly
Watch the .com channel's arithmetic. Wholesale gives you a handful of ASNs a week to get right; dropship gives you one per consumer order, and a systematic defect — a missing tracking reference, a ship-to formatting problem — repeats itself on every order until fixed. Because each individual deduction is small, the pattern can run for weeks below anyone's attention threshold while the total grows. Put dropship deductions on their own report, watch rates rather than amounts, and treat any recurring code as an engineering fix with a deadline. Small-per-event problems at high frequency are still big problems; they just hide better.
A channel-aware prevention plan
- Tag every order with its channel at intake, and validate downstream documents against that channel's rules.
- Maintain the style/color/size matrix as operational data with a change process, not an onboarding artifact.
- Single-source cartons: pack-out record → labels, packing list, ASN.
- Fire ASNs on ship-confirm — wholesale before the appointment, dropship per order.
- Monitor 997s for silent failures and keep timestamped evidence; disputes backed by carton-level ASN data succeed.
On EDISQ, all three Nordstrom channels ride one connector, and the meter doesn't care how many programs you run: 25 documents free per month, then from $0.50 down to $0.10 per document across marginal volume tiers, with connectivity, maps, and validation built into the rate. No setup or mapping charges — all three channels count as one live partner on the Production plan's $100/month minimum, applied to usage — the arithmetic is at pricing.
FAQ
What do Nordstrom chargebacks cover?
Nordstrom supplier compliance issues deductions for ASN, ticketing, and packing failures. On the EDI side, the 856's size-level carton accuracy carries the most weight.
Do Nordstrom's channels have different EDI rules?
Yes — full-line stores, Rack, and .com dropship ride different PO patterns. Dropship adds per-order ASNs with customer ship-tos on top of wholesale flows.
How should allowances appear on a Nordstrom invoice?
As itemized SAC segments — markdown and advertising allowances are broken out, never netted into unit prices. The invoice must mirror the 856 as shipped or it short-pays.
What makes apparel ASNs harder than other categories?
Size and color expand at the line level, and carton contents must be described at that size level. Receiving scans against the document, so the detail has to be real.