--- title: "EDI 120 Vehicle Shipping Order: X12 120 Guide | Stacksync" description: "EDI 120 is the X12 Vehicle Shipping Order, used when a vehicle is ready to be assigned for transport or service. See its key segments and mapping checks." canonical: https://www.stacksync.com/edi/x12/120-vehicle-shipping-order last_modified: 2026-09-29 --- X12 transaction code # EDI 120 Vehicle Shipping Order (X12 120) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md 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 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) 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. **X12 120 Vehicle Shipping Order summary** | | | | --- | --- | | 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](https://www.stacksync.com/edi/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](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/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. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **vehicle movement order** vehicle identification number, movement order and destination | Define which combination of vehicle identification number, movement order and destination identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the vehicle movement order** ID assigned by the receiving system and processing result | Change a vehicle destination after allocation and route the change for dispatch review. Submit the same vehicle movement twice and prevent duplicate transport work. | | Check the processing result | **Processing status for the vehicle movement order** Original document reference and matching response | Reconcile the vehicle movement order with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### 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](https://www.stacksync.com/edi/x12/928-automotive-inspection-detail) **vehicle inspection result:** vehicle condition is inspected. ### Implementation steps 1. #### 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. 2. #### 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. 3. #### 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. 4. #### 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. ### Related documents and resources - [X12 928 Automotive Inspection Detail](https://www.stacksync.com/edi/x12/928-automotive-inspection-detail) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) 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 **Segments with elements marked mandatory in this reference** | 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 ## Find your trading partner for X12 120 1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context. - [Rivian Automotive, Inc](https://www.stacksync.com/edi/rivian-automotive-inc) [Rivian Automotive, Inc](https://www.stacksync.com/edi/rivian-automotive-inc/rivian-automotive-inc/x12-120-vehicle-shipping-order) 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 Partner entries with the most listed channels - [Rivian Automotive, Inc](https://www.stacksync.com/edi/rivian-automotive-inc) 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. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)