Multi-channel orders, multi-courier logistics, live tracking and COD & gateway reconciliation — every online sale posted to your real books.
Explore the Ecommerce moduleFrom auto spare parts to optical stores to cloud kitchens — find the configuration made for you.
Browse all industriesFBR, ZATCA, MyInvois & UAE e-invoicing — built into every invoice, not a bolt-on. Sell compliantly from day one.
Compliance hubBook a free 30-minute demo on your own kind of business — no slides, just the product.
Book a demoOne 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.
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.
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.
Any carrier with an API becomes another configured driver on the adapter — never a rewrite. Don’t see yours? It can be added.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.