08Why Ordinal

Not another route planner.
Decision intelligence.

Routing answers how to serve the orders you already accepted. Ordinal helps decide which delivery promises should enter the network at all.

01
Customer preference

Logistics decisions should account for when customers actually want their orders, not only how to move them efficiently.

02
Network-aware decisions

A delivery promise is evaluated against the wider network before it is offered.

03
Operational feasibility

Recommendations account for real constraints: capacity, shifts, service time and existing commitments.

04
Incremental impact

Ordinal evaluates what adding or changing a commitment does to the network.

05
Works alongside existing operations

A decision intelligence layer, not a forced replacement for your logistics stack.

06
Saudi-first

Built around the realities of Saudi delivery operations: growing volumes, dense urban networks and rising customer expectations.

09 / Maturity

Production infrastructure.
Pilot-stage deployment.

Ordinal is built for controlled pilot deployments. We are now working with operators on network analysis and pilot opportunities.

Persistent network state

Delivery commitments and network state persist across analyses and operational decisions.

Background analysis

Network analyses run independently in the background and remain available when complete.

Isolated environments

Customer operational environments are logically isolated from one another.

Operated infrastructure

A secured production API with monitoring, backup and recovery mechanisms in place.

06 / Customer experience

A delivery window should be a promise.

Some delivery models provide almost no timing control to the recipient. Others ask customers to select a delivery window but struggle to consistently fulfil those preferences once the route is built. Ordinal's architecture is designed to make the promise operationally informed before it is offered.

Without Ordinal

"We'll contact you when the driver is nearby."

↓
Network tries to accommodate it later.

With Ordinal

"Choose from delivery options that already fit the network."

↓
Selection becomes a commitment.
↓
Network is optimised around it.

Choice that the network
can actually support.

07Counterfactual validation

Does Ordinal actually cause the improvement?

Each simulated customer has an underlying uninfluenced delivery choice. In Control, the customer selects that choice. In Ordinal, the customer either follows the recommendation or makes the same uninfluenced choice they would have made in Control.

At 0% influence, Control and Ordinal should converge. As influence increases, a genuine mechanism should strengthen the network effect.

RECOMMENDATION INFLUENCE / MEAN DISTANCE EFFECTDevelopment simulation · synthetic demand
  • 0%0%
  • 20%11.1%
  • 40%15.1%
  • 60%23.3%
  • 80%39.6%
  • 100%52.0%

These results demonstrate the behaviour of the current model under controlled synthetic conditions. They are not claims of expected savings in live commercial operations.

09Where Ordinal sits

A decision layer between commerce and fulfilment.

Ordinal is designed to complement an operator's existing logistics stack rather than replace it.

Its primary role is upstream of routing: helping determine which delivery promises should enter the network in the first place.

DECISION LAYER / POSITIONUpstream of routing
Ecommerce / OMS / order source
↓
New order
↓
Ordinal
  • Read network
  • Evaluate options
  • Recommend
  • Capture commitment
↓
Delivery commitment
↓
TMS / routing / dispatch
↓
Fulfilment
Free network analysis

Request a free network analysis.

Give Ordinal a representative historical delivery set. See what changes when delivery demand becomes a decision variable.

Analyse Your Network →

Historical data only. No checkout integration required for the initial analysis.