To start and identify an interchange of zero or more functional groups and interchange-related control segments
Rivian Automotive, Inc X12 928 Automotive Inspection Detail
X12 928 (Automotive Inspection Detail) 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
- 8
- Loops
- 1
- X12 928
- All partners ↗
Transaction context
Where 928 Automotive Inspection Detail 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 928
partners across the Stacksync network trade 928
channels network-wide carry 928
Most common alongside 928
The 928 reports motor vehicle inspection results among parties in the finished-vehicle supply chain. One transaction can cover multiple vehicles: the BIX beginning segment carries identifying numbers and dates, an optional TI segment identifies origin and destination carriers, equipment, and seal status, and each VC loop identifies a vehicle with up to 99 ID inspection detail segments. Interested parties use it to record vehicle condition at inspection points as vehicles move between manufacturers and carriers. An automotive manufacturer, inspection agency, or carrier sends the 928 to other interested parties in the finished-vehicle distribution chain.
When it fires: A vehicle inspection is completed at a point in the distribution chain, such as a carrier handoff, and the results must be reported electronically to the manufacturer, carrier, or other interested parties.
Common 928 rejection causes
- Missing or invalid carrier identification in the TI segment, which prevents the receiver from attributing inspection results to the correct leg of the move.
- Vehicle identification errors in the VC loop, so inspection detail cannot be matched to the vehicle record in the receiver's system.
- Loop-limit violations: the base standard allows up to 36 VC loops per transaction and 99 ID segments per vehicle, so larger inspection batches must be split across transactions.
- Missing mandatory BIX data (identifying numbers and dates), which fails syntax validation before any inspection content is processed.
Specification summary
X12 928 Automotive Inspection Detail at the element level
The X12 928 specification defines 9 segments carrying 43 data elements, 35 of which are mandatory.
- Segments
- 9
- Data elements
- 43
- Mandatory elements
- 35
| Segment | Elements | Mandatory |
|---|---|---|
| BIX | 6 | 4 |
| VC | 4 | 1 |
| ID | 3 | 3 |
Key identifiers in 928
- Transaction Set Purpose Code
- Standard Carrier Alpha Code
- Date
- Inspection Location Type Code
- Vehicle Identification Number
- Damage Area Code
- Damage Type Code
- Damage Severity Code
Full segment guideline — 8 segments 1 loop · X12 928 Automotive Inspection Detail
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 transmit identifying numbers, dates, and other basic data relating to the transaction set
To identify origin and destination carriers, equipment carrying shipment, date shipped, seal status, and equipment type
VC Loop Repeat: 21
To define motor vehicle identification and logistics
To report the inspection results on automotive vehicles
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
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 VE Vehicle Shipping Order 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 928 FAQ
Common questions about 928 Automotive Inspection Detail on the Rivian Automotive, Inc channel.
What is X12 928 Automotive Inspection Detail?
X12 928 (Automotive Inspection Detail) is the EDI transaction set used to exchange automotive inspection detail data. Rivian Automotive, Inc's Rivian Automotive, Inc channel requires it from trading partners.
Does Rivian Automotive, Inc Rivian Automotive, Inc require 928 for trading partners?
Yes, Rivian Automotive, Inc (Rivian Automotive, Inc) supports X12 928 Automotive Inspection Detail. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Rivian Automotive, Inc 928 with Stacksync?
Most companies go live with Rivian Automotive, Inc 928 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 928 on Rivian Automotive, Inc?
On Rivian Automotive, Inc, X12 928 is typically exchanged alongside 214 Transportation Carrier Shipment Status Message, 120 Vehicle Shipping Order, 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.
