Work N Gear EDI 850 Purchase Order Integration

Schema Reference

17 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

REF01 Reference Identification Qualifier

M ID 2-3

REF02 Reference Identification

C AN 1-30

CSH01 Sales Requirement Code

O ID 1-2

ITD01 Terms Type Code

O ID 2-2

ITD02 Terms Basis Date Code

O ID 1-2

ITD03 Terms Discount Percent

O R 1-6

ITD04 Terms Discount Due Date

C DT 8-8

ITD05 Terms Discount Days Due

C N0 1-3

ITD07 Terms Net Days

O N0 1-3

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

TD501 Routing Sequence Code

O ID 1-2

TD502 Identification Code Qualifier

C ID 1-2

TD503 Identification Code

C AN 2-80

TD504 Transportation Method/Type Code

C ID 1-2

TD505 Routing

C AN 1-35

TD506 Shipment/Order Status Code

C ID 2-2

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

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

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

CTP Loop

CTP01 Class of Trade Code

O ID 2-2

CTP02 Price Identifier Code

C ID 3-3

CTP03 Unit Price

C R 1-17

SDQ01 Unit or Basis for Measurement Code

M ID 2-2

SDQ02 Identification Code Qualifier

O ID 1-2

SDQ03 Identification Code

M AN 2-80

SDQ04 Quantity

M R 1-15

SDQ05 Identification Code

C AN 2-80

SDQ06 Quantity

C R 1-15

SDQ07 Identification Code

C AN 2-80

SDQ08 Quantity

C R 1-15

SDQ09 Identification Code

C AN 2-80

SDQ10 Quantity

C R 1-15

SDQ11 Identification Code

C AN 2-80

SDQ12 Quantity

C R 1-15

SDQ13 Identification Code

C AN 2-80

SDQ14 Quantity

C R 1-15

SDQ15 Identification Code

C AN 2-80

SDQ16 Quantity

C R 1-15

SDQ17 Identification Code

C AN 2-80

SDQ18 Quantity

C R 1-15

SDQ19 Identification Code

C AN 2-80

SDQ20 Quantity

C R 1-15

SDQ21 Identification Code

C AN 2-80

SDQ22 Quantity

C R 1-15

CTT Loop Repeat: 1

CTT01 Number of Line Items

M N0 1-6

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Automating Work N Gear 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 Work N Gear 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

Work N Gear - DS

Work N Gear EDI 850 FAQ

Common questions about 850 Purchase Order transactions with Work N Gear.

How long does it take to set up Work N Gear EDI with Stacksync?

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

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

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

What happens when Work N Gear updates their EDI specifications?

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