TPCx reaches end of life December 2026 | Don't wait until partners go dark | Plan Your Migration →
Comparatio logo
How EDI Builds · Interactive 3D story

How EDI builds a heavy truck

Follow one Class 8 sleeper tractor from a fleet’s purchase order to a delivered truck. Along the way, 16 trading partners exchange the documents that spec it, change it, sequence its axles onto the line and pay for it: X12, EDIFACT and JSON, plus PDFs that Comparatio PDF Import turns into EDI. All of it passes through Comparatio.

  • 16 trading partners
  • 22 EDI document types
  • 10 chapters, under five minutes
Play the 3D story

Companies, people and figures in this story are illustrative. Open full screen

Chapter by chapter

One truck. Built to order, sequenced and paid by EDI.

From the first 850 to the last 820, every document in this build ran through one Comparatio hub: translated, validated, acknowledged and logged. A ship notice without engine serials was stopped before the engines reached the dock, and the PDFs from partners without EDI arrived as EDI too.

  1. 01

    Spec’d to order

    Day 1 · 07:10

    A heavy truck is built to order, so it starts with a spec, not a stock unit. Caprock Freight Lines orders 120 sleeper tractors with an X12 850; every line carries the spec code for engine, transmission, axles and paint. A dealer in Amarillo orders two units through the API as JSON. A small hauler emails a PDF purchase order, and Comparatio PDF Import turns it into an 850 too.

  2. 02

    The change order

    Day 10 · 14:20

    Plans change. Caprock moves 40 tractors to mountain routes in Colorado and sends an 860 PO change: those units now need the 505 hp engine rating and a lower 3.36 rear-axle ratio. The ERP passes the engine part straight to Caldera Diesel as its own 860. Caldera accepts with an 865, and only then does Ironridge confirm to Caprock with an 865. Nobody re-types a spec sheet.

  3. 03

    The plan

    Day 10 · MRP run

    The ERP explodes 125 tractors into parts and sends every supplier a rolling forecast. It is one schedule in three formats over five protocols: X12 830 over AS2, VAN and SFTP, JSON over the API for the telematics maker, and EDIFACT DELFOR over OFTP2 for the transmission plant in Germany. Gulf Coast Hose & Fitting has no EDI at all. It answers Ironridge’s emailed PO with a PDF acknowledgment that becomes an 855.

  4. 04

    Frame rails

    Week 6 · Monday · 06:00

    Every truck starts as two steel rails. Calumet ships heat-treated rails by train: a 404 rail bill of lading to the railroad, an 856 to Ironridge, and 214 status when the cars arrive. The rails are bolted to crossmembers upside down, because it is easier to set axles on top of a frame than to lift them into it. Each receipt posts an 861, and tire sets are staged at the 3PL with a 943 and 944.

  5. 05

    Axles in sequence

    Week 6 · Monday · Just in sequence

    Axles arrive in the order the trucks are built. The plant sends Red River Axle an 866 production sequence, and every rack comes with an 856 whose REF*JH names the build slot each axle belongs to. Our tractor, sequence 004417, gets the 3.36 ratio from the change order. Then the whole chassis is rolled over 180°: the frame flip, the signature moment of every truck line.

  6. 06

    Powertrain

    Week 6 · Tuesday · 10:40

    The transmissions sailed from Bremerhaven three weeks ago. Haldenwerk’s EDIFACT DESADV reached the ERP as an 856 the day they shipped, and ocean 315 events tracked the containers to Houston. Caldera’s engine ship notice is another story: its 856 arrives without engine serial numbers, which Ironridge needs for the VIN record, emissions certification and warranty. Comparatio rejects it, returns an 824, and the corrected ASN arrives eight minutes later.

  7. 07

    Cab marriage

    Week 6 · Tuesday · 13:15

    The painted cab comes over from Ironridge’s own paint shop and is lowered onto the chassis, followed by the hood, fuel tanks, exhaust stacks and fifth wheel. For tomorrow’s wheels, the 3PL picks tire sets on a 940 and confirms with a 945, and Blackland Freight’s TMS takes the shuttle load as a JSON 204 and 990. Gulf Coast’s emailed PDF packing slip arrives as an 856, and the telematics maker’s ship notice comes in as JSON.

  8. 08

    Wheels & first start

    Week 6 · Wednesday · 09:30

    Ten wheels go on: two steer tires and eight drive tires in duals, staged by the 3PL and logged on its 846 inventory advice. At the last station the truck starts for the first time: lights, brakes, a roller dyno and an emissions check. Our engine’s serial, on file thanks to the corrected 856, is tied to the VIN for certification. The ERP marks the tractor built and sends Caprock an 870 order status.

  9. 09

    Deliver

    Week 6 · Thursday · Denton → Lubbock

    Finished tractors are driven to their owners. The plant tenders the load to Longhorn Driveaway with a 204 and gets a 990 back. Caprock receives an 856 listing every VIN, and 214 status messages follow the saddle-mounted convoy to Lubbock. The dealer’s two units get their ship notice as JSON.

  10. 10

    Get paid

    Week 10 · Settlement

    Money moves on EDI as well. Ironridge invoices Caprock with an 810, and Mesa Commercial Finance, which finances the fleet, pays with an 820 remittance that names the invoice. The dealer’s units are paid off its floorplan line the same way. Most suppliers don’t invoice at all: under evaluated receipt settlement, Ironridge pays from its own 861 receipts and sends each an 820. Gulf Coast’s PDF invoice becomes an 810 and is matched like any other.

What would this look like with your trading partners?

Bring your partner list and the documents you exchange today, and we’ll talk through how they would run through Comparatio.