KSA freight market
$65Bannual ICT/IT spend
A compliance-led AI wedge into KSA freight forwarding — built for SABER, ZATCA Phase 2, and FASAH. Arabic-native, AI-first, integrated with the regulators that the global TMS vendors don't prioritize.
Six pressures we hear from compliance managers, CFOs, and ops directors at mid-market forwarders. Compliance is forced; everything else is contested.
Every regulated import requires a Shipment Certificate of Conformity. Non-compliance triggers re-export at the forwarder's cost. The risk is catastrophic and the workflow is manual.
Real-time Fatoora e-invoicing becomes mandatory June 2026 for forwarders above the SAR 375K threshold. Penalty is SAR 50K per violation. Most freight billing systems aren't ready.
The Tabadul single-window is becoming the customs norm. API access is bilateral and limited; without an integrator, mid-market forwarders are locked out of the modern flow.
Manual rate-card matching means 3-7% of carrier billing is overcharged. Without automated audit, the leakage is found by spot checks — most of it isn't found at all.
Mid-market forwarders quote in hours via WhatsApp and email. Sales reps cannot win volume against carriers' digital portals. Quote autopilot — not "RPA" — is the lift.
Operations teams work in Arabic; the global TMS stack ships English-only. Compliance reports for SASO, ZATCA, and customs require Arabic-native generation, not afterthought translation.
Six disciplines, sector-tuned for the freight forwarder operating model and the regulatory wedge that defines it.
Canonical shipment, document, and rate model — the substrate for SABER, ZATCA, FASAH, and carrier audit. Built once, reused across every product.
Bilingual conversational agents handling rate requests, quote follow-ups, and customer service — wired to the carrier rate APIs and the customs flow.
OCR + field extraction for invoices, BOLs, packing lists, and SCoC documents in mixed Arabic/English. Auto-extract, classify, and route.
PDPL-aligned deployment in STC Cloud or AWS Bahrain. Long-running customs and carrier round-trips orchestrated on Temporal.
SCoC, customs, and carrier-rate data is sensitive. Managed detection, NCA-aligned controls, and incident response tuned for trade flows.
A unified operating picture — shipments, exceptions, compliance status, and carrier performance — for the ops director, not the dashboard vendor.
Compliance-first wedge, CFO suite, ops layer, and a thin AI-native TMS — all sharing one canonical shipment data model.
Automated Shipment Certificate of Conformity workflow with regulated-product detection, CAB orchestration, and FASAH hand-off.
Real-time Fatoora e-invoicing for freight forwarders — Wave 24 ready, freight-native invoice lines, carrier line-item compliance.
OCR-driven extraction and rate-card matching across carrier invoices — surfacing overcharges in days, not quarterly spot-checks.
Bilingual quote agent that ingests RFQs from email and WhatsApp, queries carrier rate APIs, and returns priced proposals in minutes.
HS classification with ZATCA rulings RAG and GCC tariff schedule — preferential FTA logic and duty optimization for every shipment.
An agent layer over the shipment lifecycle — exceptions, ETAs, customer comms, and Arabic-native operator support.
Bilingual operations UX collapsing compliance, audit, quoting, and customs into a single shipment-centric console.
Thin AI-native transport management system that emerges from the modules — with CargoWise migration tooling for forwarders graduating up.
Regulators, certification bodies, sovereign infrastructure, and the carrier-and-broker partners we integrate with across the trade flow.
Compliance is forced buying with deadlines. SABER non-compliance triggers re-export at the forwarder's cost; ZATCA Phase 2 carries SAR 50K/violation penalties. The wedge into a forwarder's stack is a problem they cannot ignore — TMS replacement is a contested decision, compliance is a forced one.
Not on day one. We integrate alongside the existing TMS, owning the compliance and audit layer. As the canonical data model populates, the TMS kernel emerges as a thin AI-native option for forwarders who want to graduate off legacy platforms — including with migration tooling.
In-Kingdom by default. STC Cloud or AWS Bahrain (me-south-1) under PDPL and SDAIA controls. SCoC documents, customs filings, and carrier-rate data never leave the region.
Multi-modal vision pipelines tuned to mixed Arabic/English freight documentation, with PaddleOCR fallback for Arabic-heavy stamps and seals. Output flows into the canonical Document and ChargeLine entities.
Fixed-scope consulting setup followed by managed-service operation. CAB partnerships, ZATCA certification path, and FASAH onboarding handled as part of the engagement.
Mid-market KSA-HQ freight forwarders with multi-modal exposure (air + ocean + land). Names disclosed under MNDA at the working-session stage.
Sixty-minute working session with our Logistics lead and a compliance engineer. Bring your SABER backlog, the ZATCA gap, or the carrier invoice headache. We'll come back with a one-page roadmap you can take to the CFO.