Master doc: for the merged lifecycle + KSA/NSW stack + readiness scorecard, open BLUEDXP-MASTER-READINESS.html (this file is still the detailed 13-stage journey view).
Hosted URL: the main workspace is /; this map (with the Motion live lab below) is at /customer-journey — open that path on your deployment if you landed on the enterprise console and do not see this page.

Customer journey × platform capabilities

End-to-end map for BlueDXP: what your customers touch from first visit through planning, quotes, marketplace, AI, and operations feedback. Click any journey stage or use filters. Status reflects what this repository ships today, not a future roadmap deck.

Ecosystem & merged lifecycle

Interactive ecosystem graph, P1–P9 process rail, KSA context, and path-level readiness live in the master artifact (separate from this 13-stage view).

③ Product & ops — graph + orbit ② Process map — P1–P9 ④ Acquisition → success (compact) ⑥ Readiness scorecard ⑤ KSA / NSW stack

Crosswalk — 13 customer stages ↔ P1–P9 logistics spine

Stages describe who touches the product; P-phases describe how freight moves. Hover a badge for the full phase name.

Customer stage P-phases Typical ops emphasis Deep dive

KSA / NSW / ports — authority surfaces

Official entry points for customs, tax authority NSW materials, transport regulator, and ports. Repo surfaces context in workspace alerts — not live filing APIs unless you wire them.

FASAH (trade window) fasah.sa — trade home (EN)
ZATCA — NSW / customs journey zatca.gov.sa — customs journey
TGA (land transport) tga.gov.sa
MAWANI (ports) mawani.gov.sa
Daleel — logistics news (not port slots) news.daleel.gov.sa/logistics
In-repo registry (staff) /official-data-sources When hosted; same seed JSON as data/seeds/

Path-level readiness (summary)

This journey map tracks capability status per stage. For file paths, FASAH/Wasl gaps, dispatch/ePOD, use the scorecard chapter.

Live end-user & WhatsApp pilot

Same-deployment shortcuts for UAT: testers use the workspace; operators verify RFIs in Admin; the Hazalyze WA gateway must forward to the webhook URL below with the same secret as HAZALYZE_WEBHOOK_SECRET.

Hazalyze gateway — direct links (keys & signup)

One-page runbook in repo: GO_LIVE.md. Platform code lives in this repo; gateway accounts/keys live on the Hazalyze site above.

Operator runbook: GO_LIVE.md. On the hosted site, staff can also open Settings → Live integrations and click Refresh status to copy the webhook URL and checklist.

Motion intelligence — live try (corridor + ports + trip memory)

This calls POST /api/motion-intelligence?action=evaluate on the same origin as this page. Enable Remember this trip to store journeyState in your browser and send it back as priorJourneyState on the next evaluation — you will see anchor_entered / anchor_exited and role changes, the same contract dispatch or a TMS can use. Staff Geofence hub (same engine, operator narrative): /motion-geofence. 

Ready. Serve this page from your deployment or local dev server so /api/motion-intelligence exists (file:// cannot call the API).

Select a journey stage

Mapped to workspace, APIs, and operator tasks

Cross-cutting gaps

from README & END_USER_READINESS

Quick matrix — journey stage × surface

Stage Primary UI / URL Key routes API / backend Coverage