One rider fleet. Many clients. One dispatch layer holding it together.
Courier operations run into a specific problem every day - the same pool of riders is servicing several clients at once, each with their own SLA rules, tracking expectations and branded status pages. Iyerxpress runs that entire mixed operation as one live fleet, with per-client separation where it matters.
Shared riders. Separated everything else.
Your riders are a shared, mobile resource. Your clients are not - each expects their own rules, their own tracking, their own reporting. The engine keeps the pool shared and everything above it separated.
- Per-client SLA and window rules with independent thresholds
- Per-client tracking pages with client branding and domain
- Per-client notification templates, channels and cadence
- Per-client analytics and monthly SLA reports
A typical hour, three clients
Pharmacy - hard windows
Order 41 must land inside 25 minutes. Engine weights window heavily and prefers riders with cold-bag capacity.
Restaurant - ASAP
Order 78 goes to the closest rider available - no fixed window, but the customer expects fast.
Documents - batch
Two document runs bundled into one rider trip. Client C accepts a 60-min window in exchange for lower cost.
Same fleet
All three orders were served by riders in the same pool. The client-facing surfaces stayed separate.
Five things that stop being manual on day one.
Client-fair reallocation
Reassignments respect per-client priority so a low-priority order does not slip because a high-priority one arrived at the same time.
Different windows, one board
Hard-window pharmacy orders, ASAP food, and batched document runs all live on the same dispatch board without stepping on each other.
Client-templated status
Every client's customer receives status updates that read like the client's brand - not a courier company banner.
SLA reports on tap
End-of-month SLA reports per client run themselves. No dispatcher spending a weekend building CSVs.
Client onboarding
Adding a new client is a form, not an engineering project - SLA, branding, notification channels and pricing rules in one setup.
Access control
Fleet manager, dispatcher, and client-admin roles - a client only ever sees their own orders, riders on their runs, and their own metrics.
The riders shown are drawn from a shared pool. Client separation happens above the pool, not below it.
See the courier-company setup on your fleet
Book a working session. We will map your clients, your SLA tiers and your rider pool, and walk through the engine against a live shift.
Show us your fleet size. Watch the swarm move at your scale.
Type a rider count and a rough daily order volume. The view on the right rebuilds to that scale, with a sample reassignment playing every few seconds - the same kind of decision the delivery engine makes for a live fleet.
An illustrative view based on typical patterns - not a live read of your actual fleet. Numbers move with your inputs so you can see the shape of the problem the engine solves.