7 EDI 850 Purchase Order Integration

Schema Reference

18 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 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator 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 Interchange 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

BEG05 Date

M DT 8-8

BEG08 Invoice Type Code

O ID 3-3

BEG09 Contract Type Code

O ID 2-2

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

N9 Loop Repeat: 1,000

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-50

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

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

REF01 Reference Identification Qualifier

M ID 2-3

REF02 Reference Identification

C AN 1-50

TD502 Identification Code Qualifier

C ID 1-2

TD503 Identification Code

C AN 2-80

TD505 Routing

C AN 1-35

TD507 Location Qualifier

O ID 1-2

TD508 Location Identifier

C AN 1-30

PO1 Loop Repeat: 100,000

PO101 Assigned Identification

O AN 1-20

PO102 Quantity

C R 1-15

PO103 Unit or Basis for Measurement Code

O ID 2-2

PO104 Unit Price

C R 1-17

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

CTP Loop

CTP02 Price Identifier Code

C ID 3-3

CTP03 Unit Price

C R 1-17

SAC Loop Repeat: 25

SAC01 Allowance or Charge Indicator

M ID 1-1

SAC02 Service, Promotion, Allowance, or Charge Code

C ID 4-4

SAC05 Amount

O N2 1-15

CTB01 Restrictions/Conditions Qualifier

M ID 2-2

CTB05 Amount Qualifier Code

C ID 1-3

CTB06 Amount

C N2 1-15

QTY Loop

QTY01 Quantity Qualifier

M ID 2-2

QTY02 Quantity

C R 1-15

QTY04 Free-form Information

C AN 1-30

N9 Loop Repeat: 1,000

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-50

N903 Free-form Description

C AN 1-45

AMT Loop

AMT01 Amount Qualifier Code

M ID 1-3

AMT02 Monetary Amount

M R 1-18

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 7 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 7 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

7-Eleven

7-Eleven (Legacy ISA ID: 007347602SLND)

7-Eleven (Hawaii)

7 EDI 850 FAQ

Common questions about 850 Purchase Order transactions with 7.

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

Most suppliers are fully connected and processing live 7 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 7?

No. Stacksync handles the entire EDI transport layer. We connect directly to 7'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 7 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 7?

Stacksync supports all EDI document types required by 7 — 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 7 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 7's EDI network and your system in real time.

What happens when 7 updates their EDI specifications?

Stacksync monitors 7'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.