Receiving at a sporting-goods DC is a scanning operation: cartons stream past readers, and the 856 is the answer key they're checked against. That's the whole logic of Dick's Sporting Goods vendor compliance — ASN and ticketing deductions land wherever the physical world and the document disagree. For Dick's Sporting Goods suppliers, prevention means making disagreement structurally impossible. (Requirements first? Read the Dick's Sporting Goods EDI requirements guide.)
Three PO types, three rule sets
Orders arrive as distinct types — basic replenishment, seasonal sets, and dropship — each carrying its own rules through the same document format. A validation layer that doesn't know which type it's looking at will approve documents that the program then rejects. On every type, item identity is the Dick's SKU plus UPC cross-reference, with size and color runs expanding at the line level of the 850. The size-run expansion deserves respect: it's the source data for the carton-level detail the ASN must later contain, so anything lost at order intake becomes unfixable by shipping time.
The classic apparel deduction, and its cure
Ask anyone who audits sporting-goods compliance where deductions cluster and you'll hear the same answer: label/ASN mismatch. The GS1-128 label on the carton says one serial; the MAN segment in the ASN says another; the deduction writes itself. The cure is not more careful people — it's fewer independent systems. One pack-out record per shipment, captured as cartons are actually packed at the size level, rendering both the physical labels and the 856. Add the timing rule — the ASN transmits before freight arrival, so generation hangs off ship-confirm — and the two most-cited deduction causes disappear together.
Ticketing and the invoice's quiet trap
Ticketing deductions punish product that shows up wearing the wrong tickets; the data feeding your ticket printing should be the same style/size matrix feeding your EDI documents, or the two will diverge. On the billing side, the 810 has one rule that regularly surprises new vendors: markdown and program allowances ride as itemized SAC segments, broken out explicitly — not netted into unit prices. An invoice that nets them balances from your point of view and mismatches from the program's, which is the expensive kind of correct.
Dropship widens the surface
If your Dick's relationship includes the dropship program, note how it changes the compliance statistics: instead of a few large shipments per week, you're producing many single-customer shipments per day, each with its own ASN and its own opportunity for a mismatch. A defect rate invisible on DC freight becomes a visible pattern at dropship volume. The same architecture covers it — type-aware validation, one carton lineage, event triggers — but the exceptions queue matters more, because no human can eyeball every order. Automate the flow completely and reserve people for the orders the system flags.
Prevention as a checklist
- Type-aware validation: every outbound document checked against the rules of its PO type before transmission.
- One carton lineage: pack-out record → labels, packing list, ASN, invoice.
- Ship-confirm triggers: ASNs fire when freight departs, never on a schedule.
- Acknowledgment watch: a missing 997 is retransmission time, not a mystery for month-end.
- Evidence discipline: keep timestamps and carton-level content; disputes with documentation succeed, disputes with indignation don't.
EDISQ ships all five as configuration, and prices the running system at document granularity: 25 free monthly, then a per-document rate from $0.50 easing to $0.10 in the highest band, calculated on marginal tiers. There are no mapping or setup invoices — connectivity included — and going live is the Production plan's flat $100/month minimum, applied in full to usage, first live partner included. The ladder is spelled out at pricing.
FAQ
What does Dick's Sporting Goods charge suppliers back for?
Dick's Sporting Goods vendor compliance issues ASN and ticketing deductions. The classic trigger is a GS1-128 carton label that disagrees with the ASN's serials.
Do all Dick's POs follow the same rules?
No — basic replenishment, seasonal sets, and dropship arrive as distinct PO types with different rules. Documents must be validated against the right type.
How detailed must the Dick's ASN be?
Pick-and-pack hierarchy with size-level carton contents, transmitted before freight arrival. Scan-based receiving reconciles physical cartons against it.
How are allowances handled on a Dick's invoice?
Markdown and program allowances ride itemized SAC segments — never netted into the unit price. Netting them is an invoice mismatch waiting to be found.