X12
Inbound

Ventura Foods X12 940 Warehouse Shipping Order

Ventura Foods, LLC
The EDI 940 (Warehouse Shipping Order) document is used by Ventura Foods for electronic data interchange. It enables automated processing and compliance with Ventura Foods's trading partner requirements.
17segments
3loops
5mandatory

Schema Reference

17 segments · X12 940 Warehouse Shipping Order

ISA ISA Interchange Control Header
Mandatory Max: 1
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
GS GS Functional Group Header
Mandatory Max: 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
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
W05 Shipping Order Identification
Mandatory Max: 1
W0501 Order Status Code
M ID 1-1
W0502 Depositor Order Number
M AN 1-22
W0503 Purchase Order Number
O AN 1-22
N1 Loop Repeat: 10
N1 Name
Optional Max: 1
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
N3 Address Information
Optional Max: 2
N301 Address Information
M AN 1-55
N4 Geographic Location
Optional Max: 1
N401 City Name
O AN 2-30
N402 State or Province Code
O ID 2-2
N403 Postal Code
O ID 3-15
G61 Contact
Optional Max: 3
G6101 Contact Function Code
M ID 2-2
G6102 Name
M AN 1-60
G6103 Communication Number Qualifier
C ID 2-2
G6104 Communication Number
C AN 1-80
G62 Date/Time
Optional Max: 10
G6201 Date Qualifier
C ID 2-2
G6202 Date
C DT 8-8
NTE Note/Special Instruction
NTE01 Note Reference Code
O ID 3-3
NTE02 Description
M AN 1-80
W09 Equipment and Temperature
Optional Max: 1
W0901 Equipment Description Code
M ID 2-2
W0902 Temperature
C R 1-4
W0903 Unit or Basis for Measurement Code
C ID 2-2
W0904 Temperature
C R 1-4
W0905 Unit or Basis for Measurement Code
C ID 2-2
W66 Warehouse Carrier Information
Optional Max: 1
W6601 Shipment Method of Payment
M ID 2-2
W6602 Transportation Method/Type Code
M ID 1-2
W6603 Pallet Exchange Code
O ID 1-1
W6604 Unit Load Option Code
O ID 2-2
W6605 Routing
O AN 1-35
LX Loop
LX Assigned Number
Optional Max: 1
LX01 Assigned Number
M N0 1-6
W01 Loop
W01 Line Item Detail - Warehouse
Optional Max: 1
W0101 Quantity Ordered
M R 1-15
W0102 Unit or Basis for Measurement Code
M ID 2-2
W0103 U.P.C. Case Code
C AN 12-12
W0104 Product/Service ID Qualifier
C ID 2-2
W0105 Product/Service ID
C AN 1-48
W0106 Product/Service ID Qualifier
C ID 2-2
W0107 Product/Service ID
C AN 1-48
G69 Line Item Detail - Description
Optional Max: 5
G6901 Free-form Description
M AN 1-45
W76 Total Shipping Order
Optional Max: 1
W7601 Quantity Ordered
M R 1-15
W7602 Weight
C R 1-10
W7603 Unit or Basis for Measurement Code
C ID 2-2
W7604 Volume
C R 1-8
W7605 Unit or Basis for Measurement Code
C ID 2-2
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Ventura Foods EDI 940

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

Validate
Transform
Route
Monitor
Stacksync processes Ventura Foods EDI 940 (Warehouse Shipping Order) documents automatically — syncing data to your system in real time with no manual intervention required.

Ventura Foods EDI 940 FAQ

Common questions about 940 Warehouse Shipping Order transactions with Ventura Foods.

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

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

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

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

What happens when Ventura Foods updates their EDI specifications?

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