To start and identify an interchange of zero or more functional groups and interchange-related control segments
Rivian Automotive, Inc X12 120 Vehicle Shipping Order
X12 120 (Vehicle Shipping Order) is the EDI transaction exchanged between Rivian Automotive, Inc (Rivian Automotive, Inc) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 12
- Loops
- 2
- X12 120
- All partners ↗
Transaction context
Where 120 Vehicle Shipping Order fits on Rivian Automotive, Inc
- Rivian Automotive, Inc channels
- 1 of 1
- Trading partners
- 1
- Channels
- 1
1 of Rivian Automotive, Inc's 1 channel carries 120
partners across the Stacksync network trade 120
channels network-wide carry 120
Most common alongside 120
The 120 notifies a carrier of the impending arrival of a motor vehicle the carrier is to ship to a destination or perform a service on. It identifies the vehicle by VIN and carries dealer or destination information, ship dates, and party detail, so finished-vehicle carriers can plan pickup and delivery in the outbound vehicle logistics chain. A vehicle manufacturer, the manufacturer's agent, or another carrier sends the 120 to the carrier responsible for shipping or servicing the vehicle.
When it fires: A vehicle comes off the production line or is released for movement, and the shipper must instruct a carrier to transport it to a dealer or other destination.
Common 120 rejection causes
- Destination party segments (N1 through N4) omitted when no dealer code can be supplied in VC04, leaving the carrier without a usable delivery address.
- Invalid or mistyped vehicle identification numbers in the VC motor vehicle control segment, which prevents matching the order to the physical unit.
- Missing or inconsistent dates, such as the G62 notification date or the DTM02 estimated ship date, leaving the carrier unable to schedule the move.
Specification summary
X12 120 Vehicle Shipping Order at the element level
The X12 120 specification defines 14 segments carrying 62 data elements, 34 of which are mandatory.
- Segments
- 14
- Data elements
- 62
- Mandatory elements
- 34
| Segment | Elements | Mandatory |
|---|---|---|
| BVP | 8 | 3 |
| VC | 4 | 1 |
| N1 | 4 | 1 |
| N2 | 1 | 1 |
| N3 | 2 | 1 |
Key identifiers in 120
- Vehicle Production Status
- Identification Code Qualifier
- Identification Code
- Vehicle Identification Number
- Entity Identifier Code
- Name
- Address Information
Full segment guideline — 12 segments 2 loops · X12 120 Vehicle Shipping Order
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of the Vehicle Shipping Order Transaction Set
G62 Loop Repeat: 99
To specify pertinent dates and times
VC Loop Repeat: 999
To define motor vehicle identification and logistics
To define motor vehicle characteristics
To identify a party by type of organization, name, and code
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify additional names or those longer than 35 characters in length
To specify the location of the named party
To specify the geographic place of the named party
Trading partners
10+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
TR Transportation Carrier Shipment Status Message AU Automotive Inspection Detail PU Purchase Order Change Request Buyer Initiated PU Purchase Order IN Invoice PU Purchase Order Acknowledgment SH Ship Notice Manifest MO Motor Carrier Load Tender MO Motor Carrier Freight Details And Invoice RE Response To A Load Tender
No trading partner matches your search.
Browse the full directory
Rivian Automotive, Inc Rivian Automotive, Inc EDI 120 FAQ
Common questions about 120 Vehicle Shipping Order on the Rivian Automotive, Inc channel.
What is X12 120 Vehicle Shipping Order?
X12 120 (Vehicle Shipping Order) is the EDI transaction set used to exchange vehicle shipping order data. Rivian Automotive, Inc's Rivian Automotive, Inc channel requires it from trading partners.
Does Rivian Automotive, Inc Rivian Automotive, Inc require 120 for trading partners?
Yes, Rivian Automotive, Inc (Rivian Automotive, Inc) supports X12 120 Vehicle Shipping Order. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Rivian Automotive, Inc 120 with Stacksync?
Most companies go live with Rivian Automotive, Inc 120 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 120 on Rivian Automotive, Inc?
On Rivian Automotive, Inc, X12 120 is typically exchanged alongside 214 Transportation Carrier Shipment Status Message, 928 Automotive Inspection Detail, 860 Purchase Order Change Request Buyer Initiated, 850 Purchase Order. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Rivian Automotive, Inc EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
