Integration plan
The run-up to the 17 September pilot, the sprint plan for the two months after it, and the federal arc beyond. Go-live is configuration more than construction: the engine already runs.
Where the programme stands
Pilot
- The ADEED portal on the live TruKKer engine
- Accounts and data in the UAE-resident tenancy
- 2-3 public-sector anchor clients, their current carriers invited
- Waybill v0: an ADEED-issued ID under every movement
- Transparent bidding, live tracking, PODs, invoice views
Federal MVP
- National Carrier & Driver Registry at scale
- e-Bayan issuance engine and the operating-card pathway
- Migration of the existing carrier base into the registry
- First regulator views, webhook channel, ERP self-serve
- Invoicing and collections writes, once commercial terms settle
Mandate readiness and scale
- Regulator and inspection console
- Smart gates: 24 gates, trusted-operator fast lanes
- Emirate interop with Asateel, RTA and SRTA
- UAE e-invoicing regime, mandatory Jan 2027
- GCC interoperability: Saudi Bayan and Fasah, Hafeet corridor
The two months after go-live
Four two-week sprints. Scope is drawn from the P1 asks and from what the live pilot surfaces.
Fix what the first live loads surface. Tracking and exception handling tightened, cancel and amend (GAP-09), daily reconciliation running clean, joint standup with TruKKer through week one.
Invoice acceptance and disputes (GAP-12), payment and settlement read-back (GAP-13), carrier settlement visibility including MoXey status.
Carrier self-serve onboarding beyond the anchor group, user provisioning (GAP-17), carrier bidding inside ADEED (GAP-21), rate-card reads (GAP-22).
Webhook channel to replace polling (GAP-05), full document taxonomy (GAP-10), bulk carrier-migration prep (GAP-18), first regulator preview for Phase 1.
Journey by phase
| Journey | Phase 0, pilot | Phase 1, federal MVP | Phase 2, mandate |
|---|---|---|---|
| J1 Shipper onboarding | Anchor clients | UAE Pass, self-serve | - |
| J2 Registry onboarding | Current carriers in 72h | 70k base migration | AEO and Emiratisation tiers |
| J3 Demand capture | Portal, Copilot, assisted | ERP self-serve | Third-party platforms |
| J4 Pricing and bidding | Transparent board | Award API automation | Published service levels |
| J5 Booking and e-Bayan | Waybill v0 | e-Bayan engine | Smart-gate enforcement |
| J6 Tracking and exceptions | Milestone-grade, polled | Event-grade, webhooks | Border and gov events |
| J7 Delivery and POD | POD in 6h, vault | Full doc taxonomy | - |
| J8 Invoicing and collections | Reads, acceptance UX | Write activation | UAE e-invoicing |
| J9 Regulator and gates | - | First regulator views | Inspection console, GCC |
| J10 Control tower | Full pilot KPI board | Radar-integrated | National scale-out |
Architecture
Every call between the platforms passes through the ADEED Integration Gateway, one seam to secure, log and monitor. Clients never touch TruKKer directly. ADEED holds the governance data, TruKKer runs execution.
How the sync runs
Data custody
Copy on receipt: documents generated in TruKKer are copied into ADEED's UAE-resident storage the moment they are retrieved.
| Artifact | Master | Mirror |
|---|---|---|
| Account, organisation, roles | ADEED | TruKKer client record |
| Registry entry and quality score | ADEED | TruKKer onboarding stack |
| RFQ, price and bid audit trail | ADEED | TruKKer inquiry and loadboard |
| Bid (execution) | TruKKer | ADEED audit mirror |
| Order, trip, telemetry | TruKKer | ADEED shipment and milestones |
| Waybill (e-Bayan) | ADEED, the issuing authority | Waybill ID on the TruKKer order |
| POD and movement documents | TruKKer originates | Binary copy on receipt to UAE storage |
| Invoice and payment allocation | TruKKer finance, pending the agreements | ADEED finance mirror for SOA |
System flows
How one load moves through the platform, left to right. The top lane is what the customer experiences on ADEED. The bottom lane is TruKKer running the freight. Every arrow crossing the gateway band is data moving between the two.
Journey map
Ten journeys, step by step. Follow the colours: blue steps happen on the client side, dark steps belong to the carrier and TruKKer, green is the system working in the background. Tags under each step are the APIs that power it.
Who the portal serves
8
Eight roles across the whole arc, but only four designed surfaces at go-live: the shipper portal with role-gated tabs, the carrier onboarding wizard, the ops console and the programme KPI page. The tag on each card says when that role gets its screens.
API readiness
What is live today, what is waiting on field-level contracts, and what ADEED builds. The red segment is what is missing: those asks sit in the For TruKKer tab.
For the TruKKer team
What the integration needs from your side, ready to table. All of it already runs inside the TruKKer platform; the missing piece is the API contracts, and thirteen of them block the pilot.
The thirteen pilot blockers
The pilot cannot go live without these. To hold 17 September, the contracts need agreement at scope lock and a live sandbox in the first week of September. Select a card for the detail and the suggested contract shape.
Also to table, non-functional: a sandbox before scope lock; sign-off on the shared identifier (ADEED org ID as the externalShipperMasterId join key); rate limits and SLOs compatible with polling cadences; idempotency keys on all writes; the data-processing agreement with UAE residency attestations; webhook HMAC signing; and versioning with agreed deprecation windows.