X12 transaction code
X12 120 Vehicle Shipping Order
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 120
- Trading partners
- 1
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 |
- Vehicle Production Status
- Identification Code Qualifier
- Identification Code
- Vehicle Identification Number
- Entity Identifier Code
- Name
- Address Information
Trading partners that support X12 120
1 partner, 1 channel. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 120 Vehicle Shipping Order
120 is used most heavily in automotive.
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. 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.
By industry
- automotive 1 channel
FAQ
X12 120 questions
What is X12 120 Vehicle Shipping Order?
X12 120 (Vehicle Shipping Order) is an EDI transaction set defined by ANSI ASC X12 for exchanging vehicle shipping order between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 1 Stacksync trading partner supports this code across 1 channel.
Which trading partners use X12 120?
1 Stacksync partner accepts X12 120: Rivian Automotive, Inc. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 120 with my ERP?
Stacksync handles the full X12 120 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
