How to Set Up EDI with Target (Step by Step)

Of the major retail EDI programs, Target's is the one suppliers stand up fastest — X12 004010 over plain SFTP, clear specs, and a testing cycle that rewards preparation. With certified maps the technical work fits in 1–2 days. Here's the sequence that gets a Target connection from zero to production, and the two monitors that keep it healthy afterward.

Before day one

Three prerequisites come from outside the EDI project. You need an active vendor relationship with Target and your vendor identifiers in hand; you need items set up on Target's side, because every order line will arrive carrying a DPCI (Target's department-class-item number) alongside the UPC; and you need to know which ship-to locations your program covers. If any of these are missing, the technical setup will finish and then wait.

The build, in four moves

1. Open the pipe. Target trades over SFTP — EDISQ provisions the connection, so this is configuration rather than infrastructure work. No VAN contract, no certificate exchange.
2. Attach your ERP. Whether you run NetSuite, Dynamics 365 Business Central, or another of the 30+ supported systems, the connector maps Target's documents onto your sales orders, shipments, and invoices so nothing is re-keyed.
3. Populate the cross-references. The item table holds DPCI ↔ UPC ↔ your SKU; the location table holds Target's ship-to numbers; and the map is configured to echo the REF*DP department number from each 850 onto everything you send back. Gaps here are the number-one cause of a rocky first week.
4. Wire the outbound triggers. The 855 confirms what you can ship. The 856 must generate at truck departure from real ship-confirm data, carrying the shipment→order→pack→item hierarchy and SSCC-18 serials that match your carton labels. The 810 builds from the same shipment record so it matches as shipped.

Test the scenarios Target will throw at you

The sandbox should replay Target's actual patterns before certification: an order with items you haven't mapped (to prove the gap gets flagged, not silently dropped), a shipment where quantities changed at pick (the SN1 segments must tell the truth), and a full order-to-invoice pass where the TDS total reconciles exactly. Target certifies each document type in a short loop; setups that arrive having already passed these scenarios usually certify in a single attempt.

Go-live, plus the two monitors

Turn on production and immediately enable acknowledgment tracking — every document you send should produce a 997, and silence is an alarm, not an absence of news. Second, watch ASN timing against ship-confirm events, because the DTM windows on Target orders start the OTIF clock at order receipt and the deduction program scores late 856s. Suppliers who go live with these monitors on rarely meet Target's compliance team; the deeper background on what gets deducted and why is in the Target EDI requirements post.

Plan for the order that changes

One flow deserves explicit setup attention because it only appears after go-live: Target actively revises open orders with the 860 PO change — quantity revisions, date shifts. Configure your ERP integration to apply an 860 to the existing sales order rather than creating a duplicate, and decide during setup who gets notified when a change arrives against an order that has already been picked. Suppliers who skip this step handle their first 860 as a fire drill; suppliers who wire it in handle it as routing.

Cost of running it

Target volume bills the same as everything on EDISQ — by the document, nothing else. Twenty-five documents a month cost nothing; after that the price starts at $0.50 and thins out to $0.10 as volume rises, applied marginally per tier. Connectivity, certified Target maps, testing, and monitoring are all in the base price, with no setup or mapping fees to layer on top — going live is a $100/month Production minimum applied in full to usage, Target included as your first live partner. Ladder and calculator live at pricing.

FAQ