Aramex

Engagement summary

IndustryLSP B2C — global express and freight
RegionGCC / global
Engagement typeAgent marketplace — multiple agents across CX, settlements, control tower, freight quotation
StatusActive

The business problem

Aramex operates global express, freight, and logistics across dozens of markets. Two areas consumed disproportionate manual effort:

  1. Freight quotation. Inbound RFQs arrive by email in varied formats. Quoting requires checking rates across Incoterms (EXW through DDP), applying margins, and responding within SLA — all manually.
  2. Operational CX and settlements. The standard logistics pain points: WISMO, dispute resolution, POD validation, vendor settlement reconciliation — all requiring human agents stitching context from multiple systems.

The solution: Agent marketplace

Aramex is deploying a multi-agent approach across four domains:

AgentWhat it does
Atlas (Control Tower)Operational visibility and anomaly detection across shipments
Vera (Disputes)Dispute intake, evidence gathering, resolution recommendation with HITL
Nexa (Settlements)POD validation, invoice reconciliation, automated vendor payouts
Clara (CX)Inbound customer query resolution across channels
Freight Quotation AgentEnd-to-end RFQ handling — intake, rate lookup, margin assembly, quote generation

Freight Quotation Agent (deep dive)

The Freight Quotation Agent is a standout use case specific to Aramex. It handles:

  1. RFQ intake — parses inbound email with shipment details
  2. Data extraction — pulls origin, destination, commodity, weight, dimensions, Incoterm
  3. Rate lookup — queries rate databases for applicable tariffs
  4. Margin assembly — applies customer-specific and route-specific margins
  5. Quote generation — produces a formatted quotation ready for customer response

Covers all 11 Incoterms (EXW, FCA, FAS, FOB, CFR, CIF, CPT, CIP, DAP, DPU, DDP), each with different cost component structures.

Why CS folks should study this

  1. The “agent marketplace” model. Aramex isn’t buying one agent — they’re buying a platform of agents. This is the end-state for large enterprise customers: multiple specialized agents, one orchestration layer.
  2. Freight quotation as a use case. High-volume, rules-heavy, email-native — a pattern that applies to any freight forwarder or 3PL. See RFQ + Freight AI.
  3. Multi-domain deployment. CX + settlements + control tower + freight automation in one engagement. Good example of how to expand scope within an account.

Materials

Changelog

  • 26 May 2026: Full content from Drive decks. Agent marketplace model, freight quotation deep-dive added.