Atlas · Canada, United States, international · Updated November 9, 2026

Freight Data Exchange Atlas

Orders, statuses, manifests, invoices: every shipment triggers dozens of data exchanges between shippers, brokers, carriers, customs and software. This atlas shows who sets the rules, who exchanges what with whom, and over which channel, in Canada and the United States.

By Alexandre Cavalier, Opsivia Conseil · Published

Key points

  • EDI, under the ASC X12 standard in North America, remains the main channel between large shippers, carriers and freight payment providers.
  • API standards are arriving one mode at a time: NMFTA's DSDC for trucking, DCSA for container shipping, IATA's ONE Record for air cargo.
  • Authorities set which data must be reported (manifests, declarations, safety). The format of business-to-business exchanges is set by voluntary standards published by US or international bodies.
  • Between brokers and small carriers, much of the exchange still runs on email, PDF, portals and phone calls.
  • Freight platforms now expose MCP servers so that AI agents can quote, book and track shipments.

Who sets the rules

Three levels coexist. Regulation is mandatory: it sets which data must be reported to authorities, and when. Standards are voluntary: they set the format of business-to-business exchanges. Associations represent the industry to both.

Who sets the rules
CanadaUnited StatesInternational
Regulation mandatory Sets which data must be sent to authorities, and when.
Transport Canada Federal trucking framework, including hours of service and the electronic logging device (ELD) requirement for federally regulated carriers, enforced since January 2023.
CCMTA Canadian Council of Motor Transport Administrators. Coordinates the provinces and maintains the National Safety Code.
Quebec: CTQ, SAAQ, MTMD Heavy vehicle owner and operator registry (CTQ), carrier safety monitoring and roadside enforcement (SAAQ), transport policy (MTMD).
CBSA Advance electronic manifest (ACI eManifest) and, since October 21, 2024, CARM for accounting and payment of duties and taxes.
USDOT · FMCSA USDOT number, operating authority, broker registration, ELDs and hours of service.
CBP ACE electronic manifest: at least 1 hour before the truck arrives, 30 minutes for FAST shipments.
STB · FMC Economic oversight of rail (STB) and ocean shipping (FMC).
IMO · ICAO Global rules for shipping and civil aviation.
European Union · eFTI From July 9, 2027, Member State authorities must accept freight information shared through certified eFTI platforms.
Standards voluntary Set the format of business-to-business exchanges.
GS1 Canada Product and logistics unit identifiers: GTIN, SSCC, GLN.
No Canadian body identified for transportation data-exchange standardsWe have not identified a Canadian body that publishes data-exchange standards specific to road freight. Canadian companies use US and international standards.
ASC X12 Transportation EDI messages: 204, 990, 214, 210, 211, 856, 820, 997.
NMFTA SCAC codes and NMFC classification. Its DSDC council publishes open API standards for less-than-truckload (LTL) and full truckload (FTL).
GS1 US Same identifiers as GS1 Canada, plus the EPCIS traceability standard.
UN/CEFACT EDIFACT, the EDI standard used mainly outside North America.
DCSA Container shipping API standards: track and trace, booking, electronic bill of lading.
IATA ONE Record, the preferred data-sharing standard for air cargo since January 1, 2026.
Agentic AI Foundation (Linux Foundation) new Has governed the Model Context Protocol (MCP) since December 2025.
Associations influence Represent the industry to regulators and standards bodies.
Canadian Trucking Alliance Represents carriers to governments.
Quebec Trucking Association (ACQ) Voice of Quebec carriers.
CIFFA · Canadian Society of Customs Brokers Freight forwarders and customs brokers.
ATA American Trucking Associations.
TIA Transportation Intermediaries Association: brokers and 3PLs.
FIATA International Federation of Freight Forwarders Associations.

The players and their exchanges

Select a player to see what it does, example companies, and every flow it sends or receives. All of this information is also available as text below the map.

  • EDI (X12, EDIFACT)
  • API
  • Manual: email, PDF, portal, phone
  • AI agents (MCP)

The channel shown is the most common one today. The same exchange can use several channels depending on company size.

Shipper

Manufacturer, retailer, distributor

Role
Owns the goods and buys transportation. Runs the tenders and pays the invoices.
What it does
  • Runs annual bids and awards lanes
  • Sends daily load tenders
  • Tracks deliveries and manages exceptions
  • Audits and pays freight invoices
Examples
  • USWalmart
  • CALoblaw
  • CACanadian Tire
  • CAMetro
  • CASaputo
  • USProcter & Gamble
Formats used
Large shippers often require X12 EDI from their partners. Smaller shippers mostly use email and phone.
Outgoing flows (7)
  • Bid and tender Broker · 3PL EDIX12 204 → 990 · portal · email
  • Tender and acceptance Trucking carrier EDIX12 204 → 990 · DSDC booking API
  • Advance ship notice Consignee EDIX12 856 (ASN)
  • Commercial invoices and delegation Customs broker ManualEmail · delegation in the CARM portal
  • Shipping instructions Freight forwarder ManualEmail, portal or forwarder API
  • Orders to ship TMS · ERP APIERP ↔ TMS integration
  • Delegates tasks AI agents AI agents (MCP)Commercial AI assistant or in-house agent
Incoming flows (2)
  • Statuses and proof of delivery Trucking carrier EDIX12 214 · DSDC visibility API
  • Predicted arrival times and alerts Visibility APIAPI or portal

Consignee

Distribution center, plant

Role
Receives the goods. Controls the docks, and therefore delivery appointments.
What it does
  • Receives the advance ship notice (ASN)
  • Assigns delivery appointments
  • Signs the proof of delivery and records exceptions
Examples
  • Retailer distribution centers
  • Customer plants
Formats used
X12 856 for the ship notice. Site-specific appointment portals.
Incoming flows (2)
  • Advance ship notice Shipper EDIX12 856 (ASN)
  • Appointment and delivery Trucking carrier ManualSite portal, email

AI agents

Assistants that quote, book and track

Role
Software acting for a shipper or broker. They use MCP servers exposed by some freight platforms.
What it does
  • Request and compare quotes
  • Book shipments on negotiated rates
  • Surface delays and exceptions
Examples
  • USMCP server)
  • USMCP server)
  • USClaude · ChatGPT · Copilot
Formats used
MCP (Model Context Protocol), on top of each platform's APIs. No shared data model across platforms so far.
Outgoing flows (2)
  • Quoting and booking Broker · 3PL AI agents (MCP)Platform MCP servers (e.g. Shipwell)
  • Quoting, booking, tracking Freight forwarder AI agents (MCP)Flexport MCP server (September 2026)
Incoming flows (1)
  • Delegates tasks Shipper AI agents (MCP)Commercial AI assistant or in-house agent

Broker · 3PL

Buys and resells capacity

Role
Intermediary between shippers and carriers. May own no trucks, but carries the relationship and the risk.
What it does
  • Receives loads from shippers
  • Finds a carrier on load boards or in its network
  • Sends the rate confirmation
  • Verifies carrier identity and insurance
  • Pays the carrier and invoices the shipper
Examples
  • USC.H. Robinson
  • USTQL
  • USRXO
  • USUber Freight
  • USEcho Global Logistics
  • CATraffix
Formats used
X12 EDI with large shippers; PDF and email with small carriers. Some large brokers have started integrating DSDC APIs.
Outgoing flows (2)
  • Posts loads, searches trucks Load board APILoad board portal or API
  • Rate confirmation Trucking carrier ManualPDF by email · X12 204 with large carriers
Incoming flows (3)
  • Bid and tender Shipper EDIX12 204 → 990 · portal · email
  • Statuses and documents Trucking carrier ManualPhone, email, tracking app · X12 214 with large carriers
  • Quoting and booking AI agents AI agents (MCP)Platform MCP servers (e.g. Shipwell)

Load board

Marketplace for loads and trucks

Role
Matches available loads with empty trucks, and publishes spot rate indexes.
What it does
  • Posts loads from brokers and shippers
  • Posts carrier capacity
  • Publishes spot rates by lane
Examples
  • USDAT
  • USTruckstop
  • CALoadlink
Formats used
Web portals and proprietary APIs.
Incoming flows (2)
  • Posts loads, searches trucks Broker · 3PL APILoad board portal or API
  • Searches for backhaul freight Trucking carrier ManualPortal, mobile app

Freight forwarder

Organizes international shipments

Role
Organizes international shipments end to end and consolidates freight from several customers.
What it does
  • Books with ocean carriers and airlines
  • Sends house bills of lading to CBSA
  • Coordinates trucking before and after the main leg
Examples
  • INTKuehne+Nagel
  • INTDHL Global Forwarding
  • INTDSV
  • USExpeditors
  • USFlexport
Formats used
DCSA APIs and EDIFACT with ocean carriers, ONE Record with airlines, ACI eManifest with CBSA.
Outgoing flows (2)
  • House bills of lading CBSA EDIACI eManifest: EDI or portal
  • Booking and instructions Ocean · rail · air APIDCSA APIs · EDIFACT IFTMIN · ONE Record (air)
Incoming flows (3)
  • Shipping instructions Shipper ManualEmail, portal or forwarder API
  • Container statuses Ocean · rail · air APIDCSA track and trace · X12 315 · EDIFACT IFTSTA
  • Quoting, booking, tracking AI agents AI agents (MCP)Flexport MCP server (September 2026)

Trucking carrier

Full truckload (FTL) and LTL

Role
Performs the transportation. It exchanges data with more partners than any other actor.
What it does
  • Accepts or declines tenders
  • Issues the bill of lading and shipment statuses
  • Sends the manifest to CBSA and CBP before the border
  • Invoices and follows up on payments
  • Keeps its safety file current (CTQ, SAAQ, FMCSA)
Examples
  • CATFI International
  • CAMullen Group
  • CABison Transport
  • CADay & Ross
  • CAGroupe Robert
  • CAPurolator
  • USJ.B. Hunt
  • USSchneider
  • USKnight-Swift
  • USOld Dominion
Formats used
X12 EDI (204, 990, 214, 210) at large carriers. In the field, many smaller carriers mostly use email, PDF and phone.
Outgoing flows (8)
  • Statuses and proof of delivery Shipper EDIX12 214 · DSDC visibility API
  • Searches for backhaul freight Load board ManualPortal, mobile app
  • Statuses and documents Broker · 3PL ManualPhone, email, tracking app · X12 214 with large carriers
  • Appointment and delivery Consignee ManualSite portal, email
  • Pre-arrival manifest CBSA EDIACI eManifest: EDI or portal, at least 1 hour before the border
  • Pre-arrival manifest CBP EDIACE eManifest: 1 hour before arrival, 30 minutes for FAST
  • Compliance and safety Road safety ManualCTQ registry, SAAQ file, USDOT number, inspections
  • Freight invoices Freight audit and payment EDIX12 210 · DSDC invoice and documents API
Incoming flows (6)
  • Tender and acceptance Shipper EDIX12 204 → 990 · DSDC booking API
  • Rate confirmation Broker · 3PL ManualPDF by email · X12 204 with large carriers
  • Appointments and container availability Port · terminal ManualPort or terminal portal
  • Position and hours of service Telematics · ELD APITelematics API · ELD
  • Messages to partners EDI integration EDIX12 over VAN, AS2 or SFTP · 997 acknowledgment
  • Payment after audit Freight audit and payment EDIX12 820 · funds transfer

Ocean · rail · air

Long-haul multimodal

Role
Carriers in other modes, connected to trucking for the first and last miles.
What it does
  • Confirm bookings
  • Publish container statuses
  • Issue bills of lading, increasingly in electronic form
Examples
  • INTMaersk
  • INTMSC
  • INTCMA CGM
  • INTHapag-Lloyd
  • CACN
  • CACPKC
  • CAAir Canada Cargo
  • CACargojet
Formats used
DCSA for ocean, ONE Record for air, X12 and EDIFACT for rail and older flows.
Outgoing flows (2)
Incoming flows (1)
  • Booking and instructions Freight forwarder APIDCSA APIs · EDIFACT IFTMIN · ONE Record (air)

Port · terminal

Interface between modes

Role
Loads and unloads vessels and trains, and manages truck access.
What it does
  • Publishes container availability
  • Assigns truck appointments
  • Exchanges stowage plans with ocean carriers
Examples
  • CAPort of Montreal
  • CAPort of Vancouver
  • CAPort of Halifax
  • CAPort of Prince Rupert
Formats used
EDIFACT with ocean carriers (BAPLIE, COARRI); portals for truckers.
Outgoing flows (1)
  • Appointments and container availability Trucking carrier ManualPort or terminal portal
Incoming flows (1)

Customs broker

Clears goods for the importer

Role
Prepares and submits customs declarations on behalf of the importer, who delegates that authority in CARM.
What it does
  • Classifies goods and calculates duties and taxes
  • Submits Commercial Accounting Declarations (CAD) in CARM
  • Prepares release before the truck arrives
Examples
  • CALivingston International
  • CAFarrow
  • CACole International
  • UScustoms)
Formats used
CARM accepts portal, EDI and API submissions. On the US side, ACE.
Outgoing flows (2)
  • Declaration and payment of duties CBSA APICARM: CAD by portal, EDI or API
  • US import entry CBP EDIACE (ABI)
Incoming flows (1)
  • Commercial invoices and delegation Shipper ManualEmail · delegation in the CARM portal

CBSA

Canada Border Services Agency

Role
Controls what enters Canada and collects duties and taxes.
What it does
  • Receives ACI eManifest data at least 1 hour before a truck arrives
  • Receives house bills from freight forwarders
  • Collects duties and taxes through CARM, since October 21, 2024
Examples
  • ACI eManifest
  • CARM
Formats used
ACI eManifest: EDI or the eManifest Portal. CARM: portal, EDI or API.
Incoming flows (3)
  • Pre-arrival manifest Trucking carrier EDIACI eManifest: EDI or portal, at least 1 hour before the border
  • Declaration and payment of duties Customs broker APICARM: CAD by portal, EDI or API
  • House bills of lading Freight forwarder EDIACI eManifest: EDI or portal

CBP

US Customs and Border Protection

Role
The US counterpart of CBSA for trucks entering the United States.
What it does
  • Receives ACE manifests at least 1 hour before arrival (30 minutes for FAST)
  • Runs the FAST and C-TPAT programs
  • Receives entries from US customs brokers
Examples
  • ACE
  • FAST
  • C-TPAT
Formats used
ACE eManifest: EDI or the ACE portal.
Incoming flows (2)
  • Pre-arrival manifest Trucking carrier EDIACE eManifest: 1 hour before arrival, 30 minutes for FAST
  • US import entry Customs broker EDIACE (ABI)

Road safety

CTQ, SAAQ, Transport Canada, FMCSA

Role
Authorizes carriers to operate and monitors their compliance.
What it does
  • Registers carriers (in Quebec, with the CTQ)
  • Assesses carrier safety records
  • Enforces hours of service and ELD use
Examples
  • CACTQ
  • CASAAQ
  • CATransport Canada
  • USFMCSA
Formats used
Government portals and forms.
Incoming flows (1)
  • Compliance and safety Trucking carrier ManualCTQ registry, SAAQ file, USDOT number, inspections

TMS · ERP

Plans and executes

Role
Software that plans shipments, selects carriers and tracks execution, at the shipper, broker or carrier.
What it does
  • Creates shipments from orders
  • Optimizes and assigns loads
  • Generates EDI messages or calls APIs
Examples
  • USOracle OTM
  • USBlue Yonder
  • USManhattan Associates
  • USe2open
  • CADescartes
  • USTrimble TMW
  • USMcLeod Software
  • INTSAP
Formats used
X12 EDI and, increasingly, APIs.
Outgoing flows (1)
Incoming flows (1)
  • Orders to ship Shipper APIERP ↔ TMS integration

EDI integration

Translation and routing

Role
Translates internal data into EDI messages and routes them between partners.
What it does
  • Maps each partner according to its implementation guide
  • Routes messages over value-added networks (VAN), AS2 or SFTP
  • Monitors functional acknowledgments (997)
Examples
  • USSPS Commerce
  • CAOpenText
  • USOrderful
  • USStedi
  • USKleinschmidt
  • CADescartes
Formats used
X12, EDIFACT, AS2. Much of the cost comes from partner-specific setup.
Outgoing flows (1)
  • Messages to partners Trucking carrier EDIX12 over VAN, AS2 or SFTP · 997 acknowledgment
Incoming flows (1)
  • Outbound messages TMS · ERP EDIInternal file → X12

Visibility

Real-time multi-carrier tracking

Role
Aggregates positions and statuses from many carriers into a single view for the shipper.
What it does
  • Collects GPS positions and statuses
  • Predicts arrival times
  • Alerts on delays
Examples
  • USproject44
  • USFourKites
  • USTrimble Visibility
Formats used
Proprietary APIs. The DSDC in-transit visibility API aims to standardize this flow.
Outgoing flows (1)
  • Predicted arrival times and alerts Shipper APIAPI or portal
Incoming flows (1)

Telematics · ELD

Truck data

Role
On-board devices and apps that produce position, hours of service and engine data.
What it does
  • Records hours of service (mandatory)
  • Transmits truck position
  • Feeds visibility platforms
Examples
  • CAGeotab
  • CAIsaac Instruments
  • USSamsara
  • USMotive
Formats used
Proprietary APIs. ELDs are governed by regulation.
Outgoing flows (2)

Freight audit and payment

Validates and pays invoices

Role
Checks freight invoices against rates, then pays carriers on the shipper's behalf.
What it does
  • Matches invoice, rate and proof of delivery
  • Disputes non-compliant surcharges and accessorials
  • Pays and provides cost allocation data
Examples
  • USU.S. Bank Freight Payment
  • USCass Information Systems
Formats used
X12 210 and 820. The DSDC invoice and documents API targets this flow.
Outgoing flows (1)
Incoming flows (1)
  • Freight invoices Trucking carrier EDIX12 210 · DSDC invoice and documents API

The four exchange channels

EDI

Structured messages under a standard (X12 in North America, EDIFACT elsewhere), exchanged over value-added networks (VANs), AS2 or SFTP. It is the most widespread channel between large companies, and it is robust. However, each partner publishes its own implementation guide, which makes every integration partly unique.

API

Real-time exchanges through web requests, usually in JSON. Faster and simpler to build than EDI. Without a common standard, each platform defines its own: this is what DSDC for trucking, DCSA for ocean and ONE Record for air cargo aim to fix.

Manual

Email, PDF, web portals, phone. Still very common between brokers and small carriers, and for delivery appointments. This channel costs rekeying, delays and errors, and makes it harder to verify who a partner really is.

AI agents (MCP)

The Model Context Protocol lets an AI assistant use a platform's functions: quoting, booking, tracking. It runs on top of existing APIs and does not define what a bill of lading or a tender is. Since December 2025, it has been governed by the Linux Foundation's Agentic AI Foundation.

Flow register

The 32 exchanges shown on the map, with their purpose, channel, and the messages or standards used.

From → ToPurposeChannelMessages and standards
Shipper to Broker · 3PL Bid and tender EDI X12 204 → 990 · portal · email
Shipper to Trucking carrier Tender and acceptance EDI X12 204 → 990 · DSDC booking API
Trucking carrier to Shipper Statuses and proof of delivery EDI X12 214 · DSDC visibility API
Broker · 3PL to Load board Posts loads, searches trucks API Load board portal or API
Trucking carrier to Load board Searches for backhaul freight Manual Portal, mobile app
Broker · 3PL to Trucking carrier Rate confirmation Manual PDF by email · X12 204 with large carriers
Trucking carrier to Broker · 3PL Statuses and documents Manual Phone, email, tracking app · X12 214 with large carriers
Shipper to Consignee Advance ship notice EDI X12 856 (ASN)
Trucking carrier to Consignee Appointment and delivery Manual Site portal, email
Trucking carrier to CBSA Pre-arrival manifest EDI ACI eManifest: EDI or portal, at least 1 hour before the border
Trucking carrier to CBP Pre-arrival manifest EDI ACE eManifest: 1 hour before arrival, 30 minutes for FAST
Shipper to Customs broker Commercial invoices and delegation Manual Email · delegation in the CARM portal
Customs broker to CBSA Declaration and payment of duties API CARM: CAD by portal, EDI or API
Customs broker to CBP US import entry EDI ACE (ABI)
Shipper to Freight forwarder Shipping instructions Manual Email, portal or forwarder API
Freight forwarder to CBSA House bills of lading EDI ACI eManifest: EDI or portal
Freight forwarder to Ocean · rail · air Booking and instructions API DCSA APIs · EDIFACT IFTMIN · ONE Record (air)
Ocean · rail · air to Freight forwarder Container statuses API DCSA track and trace · X12 315 · EDIFACT IFTSTA
Ocean · rail · air to Port · terminal Stowage plans EDI EDIFACT BAPLIE, COARRI
Port · terminal to Trucking carrier Appointments and container availability Manual Port or terminal portal
Trucking carrier to Road safety Compliance and safety Manual CTQ registry, SAAQ file, USDOT number, inspections
Telematics · ELD to Trucking carrier Position and hours of service API Telematics API · ELD
Telematics · ELD to Visibility GPS positions API Proprietary APIs
Visibility to Shipper Predicted arrival times and alerts API API or portal
Shipper to TMS · ERP Orders to ship API ERP ↔ TMS integration
TMS · ERP to EDI integration Outbound messages EDI Internal file → X12
EDI integration to Trucking carrier Messages to partners EDI X12 over VAN, AS2 or SFTP · 997 acknowledgment
Trucking carrier to Freight audit and payment Freight invoices EDI X12 210 · DSDC invoice and documents API
Freight audit and payment to Trucking carrier Payment after audit EDI X12 820 · funds transfer
Shipper to AI agents Delegates tasks AI agents (MCP) Commercial AI assistant or in-house agent
AI agents to Broker · 3PL Quoting and booking AI agents (MCP) Platform MCP servers (e.g. Shipwell)
AI agents to Freight forwarder Quoting, booking, tracking AI agents (MCP) Flexport MCP server (September 2026)

What we observe

EDI is not going away; APIs are being added

Large shippers still require EDI from their partners. Standardized APIs are being added one flow at a time, starting where real time matters most: visibility, appointments, quoting. Both channels will coexist for years.

Standards come from elsewhere

The formats used by Canadian carriers and shippers are published by US or international bodies. Canada-specific requirements (Canadian customs, taxes, provincial identifiers, French) are therefore handled in each integration.

Authorities are opening their channels too

Since October 2024, CARM has accepted accounting declarations by portal, EDI or API. ACI eManifest, on the carrier side, works through EDI or the eManifest Portal.

The middle of the chain is still manual

Between brokers and small carriers, rate confirmations often travel as PDFs by email and tracking happens by phone. This is where rekeying and errors concentrate.

AI agents are arriving before the rules that frame them

Platforms such as Flexport and Shipwell expose MCP servers for quoting and booking. We have not yet identified an industry standard that defines an agent's identity, its mandate, or proof of what it committed to.

Frequently asked questions

What is EDI in transportation?

Electronic data interchange (EDI) is a standardized format that lets two companies' systems exchange documents without rekeying. In North America, transportation uses the ASC X12 standard: for example, message 204 for the load tender, 990 for the response, 214 for statuses and 210 for the invoice.

Should APIs replace EDI?

Not in the short term. Most large shippers still require EDI, and the two channels will coexist. APIs mainly bring real time and simpler integration. It makes sense to add them first where timing matters, such as visibility or appointments.

What is NMFTA's DSDC?

The Digital Standards Development Council is a council of the National Motor Freight Traffic Association, the organization behind SCAC codes and the NMFC classification. It publishes open API standards for less-than-truckload (LTL) and full truckload (FTL): electronic bill of lading, in-transit visibility, quoting, booking, invoicing.

What is ACI eManifest?

It is the requirement to send cargo and conveyance data to the Canada Border Services Agency (CBSA) before arriving at the border. For highway carriers, CBSA must receive it at least one hour before arrival. Data is sent through EDI or the eManifest Portal.

What is CARM?

The CBSA Assessment and Revenue Management system. Since October 21, 2024, it has been the official system for declaring and paying import duties and taxes. The Commercial Accounting Declaration (CAD) replaces the former B3 form, and can be submitted by portal, EDI or API.

What is MCP, and what does it change for transportation?

The Model Context Protocol is an open protocol that lets an AI assistant use a software application's functions. Freight platforms already use it to let agents quote, book and track shipments. It relies on existing APIs: without well-structured data underneath, an agent does no better than a person.

Where should a carrier start?

With an inventory: which partners exchange what with you, over which channel, and how much rekeying that represents. The inventory shows which flows to automate first, and which ones an email still handles well.

Method and sources

This page is based on the official websites of the organizations listed, the public specifications of the standards, and our work with carriers and shippers in Quebec. Companies named are examples of major players, with no ranking and no commercial relationship implied. The formats shown are the most common ones; individual business relationships may differ. Spotted an error? Email us: alexandre@opsivia.com.

  1. CBSA – Commercial reporting requirements (ACI eManifest)
  2. CBSA – CARM: schedule and features
  3. CBP – Truck electronic manifest (19 CFR 123.92)
  4. Transport Canada – ELD questions and answers
  5. Commission des transports du Québec
  6. NMFTA – DSDC API standards
  7. ASC X12
  8. DCSA – Track & Trace
  9. IATA – ONE Record (December 10, 2025 release)
  10. European Commission – eFTI Regulation
  11. Linux Foundation – Agentic AI Foundation announcement
  12. FreightWaves – Flexport MCP server
  13. Shipwell – MCP server
  14. GS1 Canada

Where do your own data exchanges stand?

Opsivia maps a carrier's or shipper's EDI, API and manual exchanges, measures what they cost in rekeying and delays, and builds a realistic roadmap.

Let's talk about your project

Contact us to discuss your logistics and transportation needs

Send us a message

Book an appointment

Choose a time that works for you to discuss your project.