The Elo Cloud family
EloERP Cloud
Start Free Trial
The compliance differentiator

FBR, ZATCA, MyInvois & UAE e-invoicing — built into every invoice, not a bolt-on. Sell compliantly from day one.

Compliance hub
Ecommerce › Courier & logistics

Book any courier, allocate by rules, track to the doorstep

One dispatch desk that speaks to every carrier through a single generic adapter — add a new courier by configuration, route each parcel by rules, ingest status three ways, and work failed deliveries from a dedicated NDR desk. Every booking and every RTO posts straight to your real double-entry ledger.

Multi-courier integration

One adapter, every carrier — new couriers added by configuration, not code

Each courier is a driver behind one generic adapter contract. Onboarding a new carrier is a configuration exercise — credentials, endpoints and field mapping — so your dispatch desk never depends on a code release to add capacity.

  • A generic adapter pattern that normalises booking, tracking and cancellation across carriers
  • API credentials are tested against the carrier before they are ever saved
  • Per-courier origin city and pickup office configuration for accurate rating and labels
  • Per-courier ledger account mapping, so each carrier’s charges land in the right book
  • Carrier labels stream server-side — credentials never reach the browser
courier connections
Leopard Connected
TCS Connected
Trax Testing key
Add carrier — paste credentials, run a live test, map the ledger account, save. No deploy.
Carrier network

Connect the couriers you already use

From national names to specialist COD networks, EloERP books, labels and tracks across 30+ integrated carriers — each a configured driver on the same generic adapter, so adding one never waits on a code release.

30+Integrated couriers
1Generic adapter
0Lines of code to add one
Leopards
TCS
M&P
Trax
DigiDokan
Daewoo Express
PostEx
BlueEx
Dex
DHL
FedEx
Couriers Next
Active Courier
RS Courier
Run Courier
XPS Worldwide Express
ZM Express
Zoom COD
One Day Courier
Nexus Global
Swift Post
Central Logistics
Shaheen Delivery
Bouraq COD
TSC Courier
Shark Logistics
ShipKartEx
Run Right Global
Fast & Quick
Safarx

Any carrier with an API becomes another configured driver on the adapter — never a rewrite. Don’t see yours? It can be added.

Allocation rules engine

Every parcel routed to the right courier, automatically

Stop hand-picking a carrier per order. Author allocation rules once and the engine chooses the courier for each shipment — then prove it against real history before you switch it on.

Match on the dimensions that matter

Route by destination city, payment type (COD or prepaid), parcel weight, order value and service type — layer conditions to describe exactly which courier handles which parcel.

Percentage-based split across couriers

Spread volume across two or more carriers by weight — send 60% to one and 40% to another — to balance load, hedge capacity, or benchmark carriers head-to-head on the same lanes.

Fallback courier chains

When the preferred carrier can’t service a city or its booking fails, the engine walks an ordered fallback chain so a parcel is never stranded without a carrier.

Scorecard-based routing

Route by measured performance — delivery success, RTO rate and speed per lane — with a minimum-sample requirement so a carrier is only judged once there’s enough data to trust the score.

Dry-run simulation before you commit

Replay a rule set over recent orders and see exactly which courier each would have picked — catch gaps and surprises before a single live parcel is affected.

Manual override, always available

Rules are the default, not a cage. Any operator can override the allocated carrier on a single order, and every override is recorded on the parcel’s audit trail.

status chokepoint
Webhook
Real-time
carrier push
Polling
Scheduled
pull job
Manual
On demand
bulk refresh
1Booked 2Picked up 3In transit 4Delivered
Status ingestion

Three ways in, one chokepoint out

Carriers report differently, so EloERP ingests status three ways and funnels all of them through a single chokepoint that normalises, de-duplicates and posts — your reports and the customer see one consistent truth.

  • Webhook — carriers that support it push updates in real time
  • Polling — a scheduled pull keeps carriers without webhooks current
  • Manual — refresh a single parcel or a whole batch on demand
  • 13 canonical shipment statuses in a central catalog, so every carrier maps to one vocabulary
  • Idempotent event de-duplication — the same update, arriving twice, posts once
Failed delivery (NDR) desk

A dedicated desk for every parcel that didn’t make it

Failed deliveries are where COD margin leaks. The NDR desk gathers every non-delivery in one queue, with the carrier’s reason, your operator’s notes, and the action to take next.

Reason codes with operator remarks

Each failed attempt carries the carrier’s reason code — customer unavailable, refused, wrong address — alongside free-text remarks your team adds, so nothing is lost between the courier and the next call.

Four decisive actions

Resolve each NDR one way: re-attempt delivery, hold for the customer, return to origin, or cancel outright. The chosen action drives the parcel’s next state and the matching ledger movement.

Full delivery-attempt history

Every attempt is logged per parcel — when it was tried, why it failed, and what was decided — so a second or third attempt is always made with the full picture, not a blank slate.

An open-NDR count that follows you

A sidebar badge shows the live count of open NDRs across the operation, so failed deliveries never quietly pile up out of sight — the queue is always one glance away.

Dispatch & serviceability

Scan parcels out, receive returns back, and know every city upfront

Barcode dispatch scanning

Scan-and-ship confirms outbound parcels at handover, and scan-and-receive re-inducts inbound RTO parcels back into stock. Every scan is audited with a timestamp and the operator who made it, and feeds directly into the RTO re-induction pipeline so returned stock is never lost.

City serviceability & mapping

A centrally-managed city catalog is mapped to each courier’s own city names, aliases and all. A fallback chain resolves the destination from shipping to billing to customer city, and any city that still can’t be matched is flagged right on the order desk before booking.

Outbound, inbound and serviceability all write to the same ledger the rest of EloERP runs on — an RTO re-induction reverses the original movement, so your stock and your books stay in step without a manual journal.

Explore the suite

Courier & logistics connects to the whole ecommerce module

← Back to the Ecommerce overview

One dispatch desk

Every courier, every parcel, on your real books

Book across any carrier, route by rules, track to the doorstep, and work failed deliveries in one place — with every booking and RTO posted to your ledger. Start free for 14 days.

Start 14-Day Free Trial Book a demo
Schedule a demo