X12
Inbound

Google X12 945 Warehouse Shipping Advice

Google
The EDI 945 (Warehouse Shipping Advice) document is used by Google for electronic data interchange. It enables automated processing and compliance with Google's trading partner requirements.
31segments
5loops
6mandatory

Schema Reference

31 segments · X12 945 Warehouse Shipping Advice

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
W06 Warehouse Shipment Identification
Mandatory Max: 1
W0601 Reporting Code
M ID 1-1
W0603 Date
O DT 8-8
W0604 Shipment Identification Number
O AN 1-30
W0611 Transaction Type Code
O ID 2-2
N1 Loop Repeat: 10
N1 Name
Mandatory 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
N2 Additional Name Information
Optional Max: 1
N201 Name
M AN 1-60
N202 Name
O AN 1-60
N3 Address Information
Optional Max: 2
N301 Address Information
M AN 1-55
N302 Address Information
O AN 1-55
N4 Geographic Location
Optional Max: 1
N401 City Name
O AN 2-30
N403 Postal Code
O ID 3-15
N404 Country Code
O ID 2-3
N405 Location Qualifier
C ID 1-2
N406 Location Identifier
O AN 1-30
PER Administrative Communications Contact
Optional Max: 5
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
PER07 Communication Number Qualifier
C ID 2-2
PER08 Communication Number
C AN 1-80
N9 Reference Identification
Optional Max: 10
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-30
N903 Free-form Description
C AN 1-45
N904 Date
O DT 8-8
N905 Time
C TM 4-8
N906 Time Code
O ID 2-2
G62 Date/Time
Optional Max: 5
G6201 Date Qualifier
C ID 2-2
G6202 Date
C DT 8-8
G6203 Time Qualifier
C ID 1-2
G6204 Time
C TM 4-8
G6205 Time Code
O ID 2-2
NTE Note/Special Instruction
Optional Max: 20
NTE01 Note Reference Code
O ID 3-3
NTE02 Description
M AN 1-80
W27 Carrier Detail
Optional Max: 1
W2701 Transportation Method/Type Code
M ID 1-2
W2702 Standard Carrier Alpha Code
C ID 2-4
W2703 Routing
C AN 1-35
W2706 Equipment Initial
O AN 1-4
W2707 Equipment Number
O AN 1-10
W2708 Shipment/Order Status Code
O ID 2-2
W6 Special Handling Information
Optional Max: 1
W601 Special Handling Code
M ID 2-3
W28 Consolidation Information
Optional Max: 1
W2801 Consolidation Code
M ID 1-1
W2802 Weight
C R 1-10
W2803 Weight Qualifier
C ID 1-2
W2804 Weight Unit Code
C ID 1-1
LX Loop Repeat: 1
LX Assigned Number
Optional Max: 1
LX01 Assigned Number
M N0 1-6
MAN Marks and Numbers
MAN01 Marks and Numbers Qualifier
M ID 1-2
MAN02 Marks and Numbers
M AN 1-48
MAN03 Marks and Numbers
O AN 1-48
MAN04 Marks and Numbers Qualifier
C ID 1-2
MAN05 Marks and Numbers
C AN 1-48
N9 Reference Identification
Optional Max: 10
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-30
N903 Free-form Description
C AN 1-45
N904 Date
O DT 8-8
N905 Time
C TM 4-8
N906 Time Code
O ID 2-2
W12 Loop Repeat: 1
W12 Warehouse Item Detail
Optional Max: 1
W1201 Shipment/Order Status Code
M ID 2-2
W1202 Quantity Ordered
O R 1-15
W1203 Number of Units Shipped
O R 1-10
W1205 Unit or Basis for Measurement Code
O ID 2-2
W1207 Product/Service ID Qualifier
C ID 2-2
W1208 Product/Service ID
C AN 1-48
W1217 Product/Service ID Qualifier
C ID 2-2
W1218 Product/Service ID
C AN 1-48
W1221 Product/Service ID Qualifier
C ID 2-2
W1222 Product/Service ID
C AN 1-48
G69 Line Item Detail - Description
Optional Max: 5
G6901 Free-form Description
M AN 1-45
N9 Reference Identification
Optional Max: 10
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-30
N903 Free-form Description
C AN 1-45
N904 Date
O DT 8-8
N905 Time
C TM 4-8
N906 Time Code
O ID 2-2
QTY Quantity
Optional Max: 10
QTY01 Quantity Qualifier
M ID 2-2
QTY02 Quantity
C R 1-15
MEA Measurements
Optional Max: 5
MEA02 Measurement Qualifier
O ID 1-3
MEA03 Measurement Value
C R 1-20
AMT Monetary Amount
Optional Max: 1
AMT01 Amount Qualifier Code
M ID 1-3
AMT02 Monetary Amount
M R 1-18
W27 Carrier Detail
Optional Max: 1
W2701 Transportation Method/Type Code
M ID 1-2
W2702 Standard Carrier Alpha Code
C ID 2-4
W2703 Routing
C AN 1-35
W2706 Equipment Initial
O AN 1-4
W2707 Equipment Number
O AN 1-10
W2708 Shipment/Order Status Code
O ID 2-2
LS Loop Repeat: 1
LS Loop Header
Optional Max: 1
LS01 Loop Identifier Code
M AN 1-6
LX Loop Repeat: 1
LX Assigned Number
Optional Max: 1
LX01 Assigned Number
M N0 1-6
N9 Reference Identification
Optional Max: 10
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-30
N903 Free-form Description
C AN 1-45
N904 Date
O DT 8-8
N905 Time
C TM 4-8
N906 Time Code
O ID 2-2
LE Loop Trailer
Optional Max: 1
LE01 Loop Identifier Code
M AN 1-6
W03 Total Shipment Information
Optional Max: 1
W0301 Number of Units Shipped
M R 1-10
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 Google EDI 945

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

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

Google EDI 945 FAQ

Common questions about 945 Warehouse Shipping Advice transactions with Google.

What is a Google EDI 945 Warehouse Shipping Advice?

The Google EDI 945 Warehouse Shipping Advice is an X12 transaction set used to exchange Warehouse Shipping Advice data electronically between trading partners. As a inbound document, it standardizes the communication of Warehouse Shipping Advice information between Google and their suppliers, carriers, or partners. Stacksync processes Google 945 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Google's requirements in real time.

What is a Google EDI 945 Warehouse Shipping Advice?

The Google EDI 945 Warehouse Shipping Advice is an X12 transaction set used to exchange Warehouse Shipping Advice data electronically between trading partners. As a inbound document, it standardizes the communication of Warehouse Shipping Advice information between Google and their suppliers, carriers, or partners. Stacksync processes Google 945 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Google's requirements in real time.

How does Stacksync automate Google EDI 945 Warehouse Shipping Advice transactions?

Stacksync handles Google EDI 945 Warehouse Shipping Advice transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 945 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Google 945 document meets their specific formatting requirements before transmission or after receipt.

How does Stacksync automate Google EDI 945 Warehouse Shipping Advice transactions?

Stacksync handles Google EDI 945 Warehouse Shipping Advice transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 945 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Google 945 document meets their specific formatting requirements before transmission or after receipt.

What are common Google EDI 945 errors and how do I fix them?

Common errors in Google EDI 945 Warehouse Shipping Advice transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Google 945 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

What are common Google EDI 945 errors and how do I fix them?

Common errors in Google EDI 945 Warehouse Shipping Advice transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Google 945 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

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

Most Google EDI 945 Warehouse Shipping Advice integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Google's 945 format and your system, running test transactions, and completing Google's certification process if required. Stacksync includes pre-built mappings for Google's most common 945 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

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

Most Google EDI 945 Warehouse Shipping Advice integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Google's 945 format and your system, running test transactions, and completing Google's certification process if required. Stacksync includes pre-built mappings for Google's most common 945 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize Google EDI 945 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Google EDI 945 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Google updates their 945 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Can I customize Google EDI 945 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Google EDI 945 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Google updates their 945 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate Google EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding