ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 127 — Vehicle Buying Order

The 127 transmits a vehicle order from a dealer or fleet buyer to an OEM or distributor: configuration, quantity, requested delivery.

Purpose

The 127 is the EDI used between dealers and OEMs (Ford OASIS, GM SPAC, Toyota TINS) for dealer order allocations and fleet orders; it carries the vehicle configuration (build code, option packs), quantity, delivery target, program code (fleet, demo, customer order).

It integrates with OEM allocation systems (Ford DOES, GM DBS) and Distributor Management Systems. Acknowledged by 997; business confirmation — dealer slot accepted, build week assigned — flows through 128 (Dealer Information) or directly in the DMS.

Envelope structure

The 127 travels within the three X12 envelope levels (ISA/IEA, GS/GE with functional group VB, and ST/SE). Didactic example in release 004010:

x12 example-127.x12 
ISA*00*          *00*          *ZZ*DEALERAUSTIN  *ZZ*FORDOEM        *260514*1200*U*00401*000000127*0*P*>~
GS*VB*DEALERAUSTIN*FORDOEM*20260514*1200*1*X*004010~
ST*127*0001~
BEG*00*SA*VB-2026-0042**20260514~
N1*BY*ACME FORD AUSTIN*92*DLR-345~
N1*SH*FORD MOTOR COMPANY*92*OEM-FORD~
LX*1~
N9*ZZ*BUILD-F150-XLT-4X4-V8~
QTY*ZZ*5~
DTM*002*20260801~
N9*ZZ*PROGRAM-CUSTOMER-ORDER~
SE*9*0001~
GE*1*1~
IEA*1*000000127~

Common segments

  • Header — ST, BEG (Beginning Segment for Purchase Order).
  • Buyer / Seller — N1*BY (Buying dealer), N1*SH (Shipping OEM).
  • Line — LX loop per configuration: N9*ZZ (OEM-specific build code), QTY*ZZ (quantity), DTM*002 (delivery target).
  • Program — N9*ZZ (program code: customer-order, demo, fleet, stock).
  • Summary — SE.

Common pitfalls

  • OEM-specific build code: Ford WERS, GM BFD, Toyota Build Sheet — without a match against the OEM database, the 127 is rejected at configuration validation.
  • Allocation vs order: sending a 127 does not guarantee allocation; OEMs hold monthly per-dealer quotas. A 127 over allocation becomes a waitlist, not a confirmed order.
  • Customer order vs stock: a customer order (vehicle for an identified buyer) has a different priority from a stock order; wrong program code = incorrect prioritization.

Documentation

The code 127 and the name Vehicle Buying Order are public and listed on x12.org/products/transaction-sets. The complete structure of loops, qualifiers and code lists is distributed by DISA via the proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.