Descartes overview
Descartes Systems Group, Inc. is headquartered in Waterloo, Ontario, Canada, with offices across the Americas, Europe, the Middle East, Africa, and Asia Pacific. The company was founded in 1981 and went public in 1998 on the Toronto Stock Exchange; it is now publicly traded on both NASDAQ (DSGX) and TSX (DSG). CEO Edward J. Ryan leads the company per the most recent April 23, 2026 Idelic acquisition press release.
Descartes describes itself as the operator of "one of the world's largest logistics networks." The Global Logistics Network connects 26,000 customers and 200,000 connected parties across 160+ countries, carrying 24+ billion messages annually and managing 1+ billion shipping routes per Descartes-authored material. The GLN is the messaging fabric connecting shippers, forwarders, carriers, customs brokers, and government agencies; Descartes operates the network and provides the messaging plumbing.
The technical authority signal is regulatory and trade-compliance depth. Descartes' Broker & Forwarder Enterprise Systems product covers shipment management, customs compliance, accounting, and CRM for freight forwarders. Global Trade Intelligence provides export controls, sanctions and denied-party screening, import classifications, tariffs, Free Trade Agreement data, and global trade data. AEI (Advance Electronic Information) handles global air cargo security filings. Global Air Messaging Gateway, built on the GLN, provides air-freight-specific messaging. This is a multi-product platform with module activation per customer scope.
The freight-forwarding-relevant subset of the broader Descartes acquisition stack includes the GLN messaging backbone, Broker & Forwarder Enterprise Systems, Customs Compliance, Global Trade Intelligence, GF-X for air cargo booking, Datamyne for trade data, and MacroPoint for tracking. The portfolio is broader than the freight-forwarding-relevant subset; Section 2 details the integration architecture forwarders work with in practice.
API capabilities and constraints
Descartes' integration surface is multi-layered. The platform exposes four distinct integration channels that together cover forwarder-side data exchange, regulatory filing, and carrier-side execution.
Layer 1: Descartes Broker & Forwarder Enterprise Systems API surface. Forwarder-side reads and writes against the shipment management module: bookings, shipping instructions, BL drafts, container assignments, customs filings, milestone events. Specifics including developer portal URL, authentication mechanism, base URL, and sandbox availability are not surfaced clearly in public material; the gap is flagged inline at the end of this section.
Layer 2: Global Logistics Network (GLN) as messaging backbone. Cloud-based logistics messaging system connecting 26,000 customers and 200,000 connected parties in 160+ countries, carrying 24+ billion messages annually and managing 1+ billion shipping routes per Descartes-authored material. The GLN maintains interconnects to 26 general and logistics-specific messaging networks per Descartes' own white paper. It supports industry-standard messaging formats across all transportation modes: EDI for participants with sophisticated connectivity, portal and e-form alternatives for participants without. The GLN is the differentiator. This is a network-of-participants architecture, not a single-TMS-to-carrier API. The Descartes Broker & Forwarder Enterprise Systems product is what forwarders use as their TMS layer; the GLN is the messaging fabric underneath.
Layer 3: Customs and trade compliance modules. Descartes Customs Compliance handles customs filings across multiple jurisdictions. Global Trade Intelligence provides export controls, denied-party screening, import classifications, tariffs, Free Trade Agreement (FTA) data, and global trade data. AEI handles global air cargo security filings. Global Air Messaging Gateway, built on the GLN, provides air-freight-specific messaging. Multi-product platform with module activation per customer scope.
Layer 4: Carrier-side integration via GLN messaging plus EDI fallback. GLN supports industry-standard EDI message formats. For carriers and trading partners that do not have sophisticated connectivity capabilities, the GLN offers portal and e-form alternatives per Descartes' own white paper. This is a similar pragmatic-engineering approach to handling uneven carrier API exposure that other TMS platforms address through portal automation. Specific per-carrier integration mechanism breakdown (which carriers go through native GLN, which through portal/e-form fallback, INTTRA usage if any) is implicit in the GLN architecture but not enumerated in public material.
For ops automation, this multi-layered architecture means forwarder-side data exchange runs through the Broker & Forwarder Enterprise Systems API plus GLN messaging, while carrier-side execution runs through GLN messaging where carriers participate and EDI/portal/e-form alternatives where they don't. The integration breadth across regulatory, carrier, customs, and trade-intelligence modules is the load-bearing technical authority.
How Expedion integrates
Expedion agents read shipment state from Descartes via the Broker & Forwarder Enterprise Systems API surface. Booking references, BL drafts, SI fields, container assignments, customs filing status, and milestone events are pulled against the customer's Descartes account using forwarder-issued credentials.
Agents execute carrier-side workflows through Descartes' GLN messaging plus carrier-side variance handling. Where carriers participate in the GLN with sophisticated connectivity, agents work through GLN messaging. Where carrier-side execution requires portal-specific knowledge that GLN doesn't fully cover (Maersk's HS-code enforcement at SI submission, MSC's character validation and ICS2 filing modes on myMSC, COSCO's lack of confirmed DCSA conformance, COSCO's portal-only flows for Chinese-origin documentation), Expedion agents handle the variance per workflow against each carrier's portal directly.
Completed events write back to Descartes via the Broker & Forwarder Enterprise Systems API and GLN messaging so the system of record stays current. Customs filing status flows back through the Customs Compliance and AEI modules; denied-party screening and trade-intelligence data continue to flow through Global Trade Intelligence. Authorization is forwarder-provided: agents use customer-supplied Descartes credentials and carrier-portal credentials with explicit, auditable scope. No credential reuse across forwarder accounts.
Workflows automated on Descartes
Five Phase 1 workflows on Descartes. Each row is a workflow; the integration mechanism describes how Expedion agents bridge between Descartes' Broker & Forwarder Enterprise Systems API plus GLN messaging surface and each carrier's execution channel. Descartes' GLN supports EDI and industry-standard messaging formats for carriers that participate; portal and e-form alternatives serve carriers and trading partners without sophisticated connectivity per Descartes' own architecture documentation.
Where carrier-side execution requires portal-specific knowledge that GLN doesn't fully cover (Maersk's HS-code enforcement at SI submission, MSC's character validation, COSCO's lack of confirmed DCSA conformance), Expedion agents handle the variance per workflow. Customs filings flow through Descartes' Customs Compliance and AEI modules; denied-party screening continues to flow through Global Trade Intelligence.
| Workflow | Descartes integration | Carrier execution | Coverage |
|---|---|---|---|
| Booking | Broker & Forwarder Enterprise Systems API: create/read booking records. GLN messaging for carrier-side booking events | GLN messaging where carriers participate with sophisticated connectivity; carrier portal where carriers haven't published APIs (many Indian and Southeast Asian shipping lines, spot products like Maersk Spot, CMA CGM SpotOn, GreenX) | Full |
| Shipping Instructions | Broker & Forwarder API: SI field exchange. GLN messaging for SI submission events | Carrier portal SI submission with carrier-specific validation. Maersk HS enforcement, MSC character rules, ICS2 filing modes (F10, F11, F12/F13, F14/F15/F17) handled at the carrier-side layer | Full |
| Bill of Lading | Broker & Forwarder API: House BL creation, draft BL events | Carrier portal amendment and telex release flows; eBL platform integration not specified in Descartes public material | Full |
| Documentation | Broker & Forwarder API + GLN messaging + Customs Compliance + AEI modules: document attachment, customs documentation, denied-party screening, trade-intelligence integration | Carrier portal VGM, DG declarations, advance manifest filings (AMS, ACI, ICS2). Descartes Customs Compliance handles US ACE/AES, EU customs, and other jurisdictional filings directly | Full |
| Tracking | GLN messaging for shipment tracking events; underlying pattern (DCSA T&T v2.2 direct, INTTRA pass-through via GLN interconnects, or independent aggregator) not publicly specified | DCSA T&T API per carrier (v2.2 on 6 of 7 Tier 1; COSCO via SynCon Hub plus third-party aggregators) | Full |
Onboarding timeline
Descartes implementation depends on module scope and integration breadth. Multi-week to multi-month implementations are typical for enterprise multi-module deployments. Descartes is a multi-product platform with module activation per customer scope; smaller deployments activating fewer modules implement faster than full-stack deployments covering Broker & Forwarder Enterprise Systems plus Customs Compliance plus Global Trade Intelligence plus GLN messaging plus AEI together. Specifics depend on customer scope and are outside Expedion's surface area.
Expedion onboarding sits on top of an existing Descartes deployment. The typical engagement runs five to seven business days from kickoff to first agent in supervised production, covering Broker & Forwarder Enterprise Systems API access provisioning, GLN messaging configuration mapping, customer-specific custom-field reconciliation, carrier credential provisioning, and a supervised validation period across booking, SI, BL, documentation, and tracking workflows on the carriers in scope.
The first onboarding step is Broker & Forwarder Enterprise Systems API access. The forwarder enables API access for Expedion's agent layer. GLN messaging configurations, Customs Compliance setup, denied-party screening data feeds, and AEI filing rules are typically already deployed for Descartes customers; agent integration runs against the existing configuration rather than provisioning new regulatory connections.
Pricing and counter-positioning
Descartes' own positioning describes pricing as "pay as you use," with a component architecture that lets customers choose how much to deploy across modules and the GLN messaging backbone. The structural implication for forwarders running Descartes: pricing scales with usage in the integration and messaging layers.
Descartes describes its pricing model as "pay as you use" in company white-paper material, with messaging-layer fees that can scale with the volume of GLN traffic a customer generates. The structural implication is direct: when a Descartes customer processes more shipments through manual ops work, GLN messaging fees grow. When automation reduces manual processing, those fees contract. The math of a usage-based pricing model on the integration layer creates this alignment with manual processing volume. Expedion's headcount-budget pricing creates the opposite alignment: when automation reduces ops headcount load, the customer's value from Expedion grows directly. Forwarders running Descartes can stack Expedion on top without changing the TMS, because the two pricing models work together when aligned to different customer-value axes. Specific per-message GLN fee schedules are not published publicly; the structural argument here is directional, anchored on Descartes' own "pay as you use" framing, not on quantified fees.
Related pages
Carriers Expedion automates on Descartes: Maersk, MSC, CMA CGM, Hapag-Lloyd, ONE, COSCO, and Evergreen.
Hubs: Carriers hub · Solutions hub · Integrations hub
Solutions on Descartes: Bill of Lading · Shipping Instructions · Booking · Documentation · Tracking
Other TMS integrations: CargoWise · GoFreight · Magaya · Logi-Sys · ShipThis · No TMS
Frequently asked questions
Does Expedion replace Descartes?
No. Expedion runs on top of Descartes as the agent execution layer. Descartes stays the system of record; agents read from Descartes via the Broker & Forwarder Enterprise Systems API and GLN messaging, execute carrier-side workflows where carrier APIs aren't fully covered by GLN, and write events back. Customs Compliance, denied-party screening, and Global Trade Intelligence data continue to flow through the existing Descartes modules. There is no data migration, no replatforming, and no parallel TMS to maintain.
How does Expedion handle Descartes' GLN messaging architecture?
Agents use GLN messaging where carriers participate in the network with sophisticated EDI connectivity. Where carrier-side execution requires portal-specific knowledge that GLN doesn't cover (carrier-specific portal validation rules, ICS2 filing modes, spot-product portal flows), agents drive the carrier portals directly and write the result back through Descartes' Broker & Forwarder Enterprise Systems API. The GLN's 200,000 connected parties cover most enterprise carriers natively; carrier-side variance handling fills the rest.
What about Descartes' Customs Compliance and Global Trade Intelligence modules?
Agents work with the standard Descartes forwarding workflow first (booking, SI, BL, documentation, tracking). Where the customer has Descartes Customs Compliance and AEI deployed for advance customs filings, agents read filing status as part of the documentation workflow. Denied-party screening through Global Trade Intelligence is typically embedded in the customer's compliance workflow; Expedion does not duplicate or replace this.
Will Expedion integration affect our Descartes pricing?
Descartes describes its pricing model as 'pay as you use' in company white-paper material, with messaging-layer fees that can scale with GLN traffic. Most agent-driven activity is reads and writes against existing Descartes records via the Broker & Forwarder Enterprise Systems API; impact on GLN messaging fees depends on whether agent activity generates additional GLN traffic. Specific fee schedules aren't published publicly. Confirm with the Descartes account team during onboarding.
Does Descartes support DCSA T&T v2.2 for tracking?
Descartes' tracking integration runs through GLN messaging for shipment status events. Whether the underlying pattern uses DCSA T&T v2.2 directly (for carriers that expose v2.2 APIs through GLN), INTTRA pass-through via GLN's 26 messaging-network interconnects, or an independent aggregator pattern is not specified in public-facing material. For compliance-sensitive forwarders requiring DCSA-conformance audit trails, Expedion agents can poll carrier DCSA APIs directly in parallel where conformance is verified (6 of 7 Tier 1 carriers).