Target runs one of the cleanest EDI programs in retail: clear specs, consistent enforcement, and a compliance program that deducts with precision. That consistency is good news — Target compliance is a checklist, and here it is.
The document set
Target trades on X12 4010 over SFTP — no VAN, no AS2 ceremony:
- 850 Purchase Order in. Two Target-specific rules matter from day one: the REF*DP department number must be echoed on every downstream document, and items arrive identified as both DPCI (Target's department-class-item number) and UPC — your cross-reference must hold both.
- 860 PO Change in. Target actively uses change requests — quantity revisions, date shifts. Your system must update the existing order, not create a duplicate.
- 855 Acknowledgment out, confirming what you'll ship.
- 856 Advance Ship Notice out — the document Target enforces hardest.
- 810 Invoice out — matched against PO and ASN; totals reconcile to the penny or the invoice short-pays.
- 997 both directions, automatic.
The ASN rules that carry deductions
Target's vendor compliance program (OTIF plus ASN accuracy) concentrates on four things, all visible in its 856 requirements:
- BSN timing — the ASN transmits at truck departure, carrying shipment ID and timestamp. Late ASN, deduction.
- The HL hierarchy — shipment → order → pack → item, exactly as physically packed. Target's receiving operation scans against the ASN; a hierarchy that reflects the PO rather than the actual cartons fails at the dock.
- MAN / SSCC-18 — every carton's GS1-128 label serial must match the MAN segment in the document. Generate labels and ASN from the same carton data or they will drift.
- SN1 honesty — shipped quantities as shipped. Short-shipping without reflecting it in the ASN is a deduction on top of the fill-rate hit.
The DTM ship/cancel window on the 850 drives the OTIF clock, so the compliance story starts at order receipt, not at shipping.
Invoices: as shipped, to the penny
Target's AP matching is strict and literal. The BIG segment must reference the original PO exactly; IT1 lines must match the 856 as shipped — not the 850 as ordered; TDS totals reconcile to the penny. The practical rule: build the 810 from the same shipment data that built the ASN. One lineage, no variances, no short-pays.
The setup path
Target's testing cycle certifies each document type before go-live. With EDISQ's certified Target maps the sequence is short:
- Connect your system — NetSuite, Dynamics 365 Business Central, QuickBooks, or 33 others.
- Load the cross-reference — DPCIs, UPCs, department numbers, ship-to locations. The wizard flags gaps.
- Run Target scenarios in sandbox — 850 in through 856/810 out, including 860 changes, validated end to end.
- Certify and go live — usually a single testing pass, one to two days on the EDI side.
Pricing is the standard EDISQ ladder: first 25 documents monthly free, then from $0.50 per document, decreasing with volume. SFTP connectivity is included; there are no Target-specific fees.
Target rewards suppliers who get the details right the first time — the deduction column stays empty, and the buyer relationship starts from "their EDI just works." That's an entirely achievable reputation to have.
FAQ
Which EDI documents does Target require?
850 purchase order and 860 change requests in; 855 acknowledgment, 856 ASN, and 810 invoice out; 997 both directions. Target trades on X12 4010 over SFTP.
What is a DPCI?
Target's internal item identifier (department-class-item). POs carry both DPCI and UPC; your cross-reference must speak both, and downstream documents must echo the right one.
Does Target fine suppliers for EDI errors?
Yes — through vendor compliance deductions tied to OTIF and ASN accuracy: late ASNs, hierarchy errors, label mismatches, and short-ships without notice all carry deductions.
How long does Target EDI setup take?
With pre-built maps, the EDI side is typically a day or two — connection, cross-reference, sandbox testing, certification. Partner paperwork sets the overall calendar.