What Target expects in the 860
Target trades on X12 4010 over SFTP. Target's 860 follows the standard X12 layout — no partner-specific companion-guide quirks are curated for this document yet. The certified base map covers the standard requirements, and validation still runs against the 860 spec before anything transmits.
How EDISQ maps it
The certified Target 860 map loads when you enable the partner — fields auto-map from NetSuite, QuickBooks, Dynamics, and 33 other systems, validation runs against Target's spec before transmission, and the sandbox replays Target test scenarios until everything passes.
Common rejection reasons
Nearly all 860 rejections trace to reference data, not syntax: identifiers that don't match Target's cross-references, echoed fields dropped from the original PO, or timing that misses the program window. EDISQ flags each before Target ever sees the document.
Sample Target 860
A representative 860 interchange addressed to Target — envelope, body segments, and control totals:
1ISA*00* *00* *ZZ*ACMESUPPLY *ZZ*TARGET *260101*1200*U*00401*000000001*0*P*>~ 2GS*PC*ACMESUPPLY*TARGET*20260101*1200*1*X*004010~ 3ST*860*0001~ 4REF*ZZ*SAMPLE 860 DOCUMENT~ 5DTM*097*20260101~ 6SE*4*0001~ 7GE*1*1~ 8IEA*1*000000001~
FAQ
Which 860 version does Target use?
X12 4010, delivered over SFTP. The certified map tracks Target's current companion guide.
How do I test a Target 860?
The sandbox generates realistic Target 860 scenarios against your live mapping — free, unlimited, invisible to Target.
What does it cost?
Per document only: first 25/month free, then from $0.50, decreasing with volume. No partner or mapping fees.