X12 transaction code
EDI 120 Vehicle Shipping Order (X12 120)
EDI 120 is the X12 Vehicle Shipping Order transaction set, used when a vehicle is ready to be assigned for transport or service. A vehicle manufacturer, the manufacturer's agent, or another carrier sends the 120 to the carrier responsible for shipping or servicing the vehicle.
- Standard
- X12
- Code
- 120
- Partner references
- 1
At a glance
EDI 120 at a glance
What the 120 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 120 Vehicle Shipping Order |
|---|---|
| Business record | Vehicle movement order |
| Who sends it to whom | 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 is sent | 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. |
| Match on | Vehicle identification number, movement order and destination |
| Partner references | 1 trading partner in this directory |
| Related documents | X12 928 Automotive Inspection Detail |
Key segments in an EDI 120
The business segments in the one partner document reference listed below. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BVP | Beginning Segment for Vehicle Shipping Order | To indicate the beginning of the Vehicle Shipping Order Transaction Set. | 1 of 1 |
| G62 | Date/Time | To specify pertinent dates and times. | 1 of 1 |
| VC | Motor Vehicle Control | To define motor vehicle identification and logistics. | 1 of 1 |
| VC1 | Vehicle Detail | To define motor vehicle characteristics. | 1 of 1 |
| N1 | Name | To identify a party by type of organization, name, and code. | 1 of 1 |
| N2 | Additional Name Information | To specify additional names or those longer than 35 characters in length. | 1 of 1 |
| N3 | Address Information | To specify the location of the named party. | 1 of 1 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 1 of 1 |
Stacksync connects EDI documents such as the X12 120 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 120 mapping and validation
X12 120 Vehicle Shipping Order is used when a vehicle is ready to be assigned for transport or service. Preserve vehicle identification number, movement order and destination so the vehicle movement order in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | vehicle movement order vehicle identification number, movement order and destination |
|
| Update the receiving system | Processing the vehicle movement order ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the vehicle movement order Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 928 Automotive Inspection Detail
vehicle inspection result: vehicle condition is inspected.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a vehicle is ready to be assigned for transport or service. Name the operational owner of the vehicle movement order and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map vehicle identification number, movement order and destination. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic vehicle movement order data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful vehicle movement order processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 120 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic vehicle movement order data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out vehicle movement order without processing it twice.
Document structure
X12 120 Vehicle Shipping Order at the element level
The X12 120 reference contains 14 segment entries and 62 data elements; 34 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Find your trading partner for X12 120
1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 120 Vehicle Shipping Order appears in this catalog
The largest groups of classified 120 catalog entries are in automotive.
By industry
- automotive 1 channel
FAQ
EDI 120 questions
What is an EDI 120?
EDI 120 is the X12 Vehicle Shipping Order transaction set. Trading partners use it when a vehicle is ready to be assigned for transport or service. It carries the data for the vehicle movement order, and your system matches it on vehicle identification number, movement order and destination.
Who sends an EDI 120 and who receives it?
A vehicle manufacturer, the manufacturer's agent, or another carrier sends the 120 to the carrier responsible for shipping or servicing the vehicle. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 120 sent?
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. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 120?
The one partner document reference listed here includes BVP (Beginning Segment for Vehicle Shipping Order), G62 (Date/Time), VC (Motor Vehicle Control), VC1 (Vehicle Detail), N1 (Name), N2 (Additional Name Information). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 120 and EDI 928?
The 120 carries the vehicle movement order and is used when a vehicle is ready to be assigned for transport or service. The 928 carries the vehicle inspection result and is used when vehicle condition is inspected.
What should I map for X12 120?
Start with vehicle identification number, movement order and destination and the target vehicle movement order. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 120 error handling?
Change a vehicle destination after allocation and route the change for dispatch review. Submit the same vehicle movement twice and prevent duplicate transport work. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 120?
The directory on this page links 1 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
