Target EDI 850 Purchase Order Integration

Schema Reference

22 segments · X12 850 Purchase Order

ISA01 Authorization Information Qualifier

M ID 2-2

ISA02 Authorization Information

M AN 10-10

ISA03 Security Information Qualifier

M ID 2-2

ISA04 Security Information

M AN 10-10

ISA05 Interchange ID Qualifier

M ID 2-2

ISA06 Interchange Sender ID

M AN 15-15

ISA07 Interchange ID Qualifier

M ID 2-2

ISA08 Interchange Receiver ID

M AN 15-15

ISA09 Interchange Date

M DT 6-6

ISA10 Interchange Time

M TM 4-4

ISA11 Interchange Control Standards Identifier

M ID 1-1

ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

BEG01 Transaction Set Purpose Code

M ID 2-2

BEG02 Purchase Order Type Code

M ID 2-2

BEG03 Purchase Order Number

M AN 1-22

BEG04 Release Number

O AN 1-30

BEG05 Date

M DT 8-8

BEG06 Contract Number

O AN 1-30

REF01 Reference Identification Qualifier

M ID 2-3

REF02 Reference Identification

C AN 1-30

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

TD502 Identification Code Qualifier

C ID 1-2

TD503 Identification Code

C AN 2-80

TD505 Routing

C AN 1-35

TD512 Service Level Code

C ID 2-2

N9 Loop Repeat: 1,000

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

N903 Free-form Description

C AN 1-45

N1 Loop Repeat: 200

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N201 Name

M AN 1-60

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

PER01 Contact Function Code

M ID 2-2

PER02 Name

O AN 1-60

PER03 Communication Number Qualifier

C ID 2-2

PER04 Communication Number

C AN 1-80

PER05 Communication Number Qualifier

C ID 2-2

PER06 Communication Number

C AN 1-80

PO1 Loop Repeat: 100,000

PO101 Assigned Identification

O AN 1-20

PO102 Quantity Ordered

C R 1-15

PO103 Unit or Basis for Measurement Code

O ID 2-2

PO104 Unit Price

C R 1-17

PO105 Basis of Unit Price Code

O ID 2-2

PO106 Product/Service ID Qualifier

C ID 2-2

PO107 Product/Service ID

C AN 1-48

PO108 Product/Service ID Qualifier

C ID 2-2

PO109 Product/Service ID

C AN 1-48

PO110 Product/Service ID Qualifier

C ID 2-2

PO111 Product/Service ID

C AN 1-48

PO112 Product/Service ID Qualifier

C ID 2-2

PO113 Product/Service ID

C AN 1-48

PID Loop Repeat: 1,000

PID01 Item Description Type

M ID 1-1

PID02 Product/Process Characteristic Code

O ID 2-3

PID05 Description

C AN 1-80

MSG01 Free-Form Message Text

M AN 1-264

PKG Loop Repeat: 200

PKG01 Item Description Type

C ID 1-1

PKG02 Packaging Characteristic Code

O ID 1-5

PKG05 Description

C AN 1-80

N9 Loop Repeat: 1,000

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

N903 Free-form Description

C AN 1-45

SLN Loop Repeat: 1,000

SLN01 Assigned Identification

M AN 1-20

SLN03 Relationship Code

M ID 1-1

SLN04 Quantity

C R 1-15

SLN06 Unit Price

C R 1-17

SLN09 Product/Service ID Qualifier

C ID 2-2

SLN10 Product/Service ID

C AN 1-48

SLN11 Product/Service ID Qualifier

C ID 2-2

SLN12 Product/Service ID

C AN 1-48

SLN13 Product/Service ID Qualifier

C ID 2-2

SLN14 Product/Service ID

C AN 1-48

SLN15 Product/Service ID Qualifier

C ID 2-2

SLN16 Product/Service ID

C AN 1-48

PID01 Item Description Type

M ID 1-1

PID02 Product/Process Characteristic Code

O ID 2-3

PID05 Description

C AN 1-80

CTT Loop Repeat: 1

CTT01 Number of Line Items

M N0 1-6

CTT02 Hash Total

O R 1-10

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

How It Works

Automating Target EDI 850

Stacksync validates, transforms, and delivers your 850 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate

Transform

Route

Monitor

Stacksync automatically syncs incoming Target 850 Purchase Orders directly to your ERP or database. New orders appear in your system within seconds — no manual data entry, no CSV imports. Field mappings are configured once and every future PO flows through automatically.

Business unit variations

Target Global Sourcing

Target US Domestic Merchandise (DSD Direct To Store Delivery | Distribution/Fulfillment Centers | Indirect Domestic)

Target EDI 850 FAQ

Common questions about 850 Purchase Order transactions with Target.

How long does it take to set up Target EDI with Stacksync?

Most suppliers are fully connected and processing live Target EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Target?

No. Stacksync handles the entire EDI transport layer. We connect directly to Target's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Target compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Target?

Stacksync supports all EDI document types required by Target — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Target EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Target's EDI network and your system in real time.

What happens when Target updates their EDI specifications?

Stacksync monitors Target's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.