Why configuration, not features, decides dispatch quality
Almost every delivery management platform today claims "automated dispatching." The differences live almost entirely in the config layer. Two platforms with identical feature lists can produce radically different outcomes depending on which rules they expose, how much weight they give each constraint, and how gracefully they handle exceptions.
At Sendme by Lilwa, we treat the dispatch engine as a configurable decision system, not a black box. The eight configurations below are the ones our enterprise deployments always start with.
Configuration, not features, is what separates a dispatch engine that scales from one that collapses under peak load. The eight layers below are the enterprise minimum.
Assignment rules — who gets the order?
The most basic config is also the most consequential. Assignment rules define the prioritisation hierarchy the engine uses to select a rider. Real operations need more than one rule. A mature config supports:
- Priority riders — specific in-house riders you want on premium accounts.
- Zone locks — riders who only operate inside a named area.
- Vehicle class — motorcycle vs van vs bicycle, matched to parcel type.
- Skill tags — medical-handling, fragile-handling, or cash-on-delivery authorised.
- Fallback sequence — in-house first, 3PL second, gig third — or the reverse.
Routing logic — what path does the rider take?
Routing is where dispatch becomes either a cost centre or a cost-saver. A configurable routing engine lets you trade between:
- Shortest distance — fuel optimisation for high-volume days.
- Shortest time — customer SLA wins, especially for food and medicine.
- Multi-stop clustering — combining 2–4 nearby deliveries into a single leg where the merchant permits it.
- Time-window optimisation — routing on customer-committed windows rather than immediate urgency.
If your platform can only route "fastest path," it will fail the moment a merchant introduces a customer time window.
Capacity constraints — what can each rider carry?
Without capacity constraints, dispatch assigns a 25kg water order to a motorcycle with a 15kg limit. The result is a failed delivery, a refund, and a frustrated customer. Every enterprise-grade dispatch config needs:
- Weight and volume ceilings per vehicle class.
- Temperature and cold-chain flags for food and medical.
- Fragility classes that restrict assignment to tagged riders.
- Cash-limit ceilings for riders handling cash-on-delivery.
SLA enforcement — which orders are urgent?
SLA enforcement is where Sendme's dispatch engine earns its keep. Instead of treating every order as equally urgent, the platform accepts a per-order SLA — for example, "delivered within 45 minutes" — and prioritises accordingly. SLA enforcement interacts directly with assignment:
- High-priority orders can skip the fallback sequence and jump straight to a premium rider.
- At-risk orders appear in the merchant dashboard before they breach, giving humans time to intervene.
- Repeated breaches trigger analytics and, in some enterprise configs, automatic refund recovery from third-party partners.
See our main article on dispatch, scheduling, and tracking for the wider SLA model.
Exception handling — what happens when things go wrong?
The most underrated configuration in any delivery management software is exception handling. Real deliveries fail for a hundred reasons: customer unavailable, address incorrect, rider breakdown, weather, cash dispute. A configurable platform lets you define the fallback for each class:
- Customer unavailable — attempt contact up to N times, then return-to-origin or hold at a hub.
- Rider breakdown — auto-reassign to the next-nearest available rider, preserving the SLA clock.
- Address problem — escalate to the merchant before dispatching, avoiding a wasted trip.
- Cash-on-delivery dispute — route to human approval rather than auto-cancelling.
Exception handling is the config most platforms ship shallowest and the one that decides the day your rider breaks down at 6pm on a Friday. Specify it before you sign.
Hybrid fleet configuration — in-house, 3PL, and gig
Modern operations almost never run a single fleet model. They run owned riders, third-party 3PL partners, and gig capacity side by side. A dispatch engine must let you express the priority order explicitly, and let you shift it by order class. For example: in-house for high-value goods, gig for peak-hour overflow, 3PL for out-of-zone deliveries. Read more in our hybrid fleet management guide.
Driver feedback loop — rating-aware dispatch
Dispatch is not only about physics. It is also about reputation. A mature platform lets you weight the assignment hierarchy by driver rating, so consistently high-rated riders are rewarded with more work — and consistently poor riders are nudged out of premium zones.
Integration configuration — webhooks, APIs, and events
The final config layer is technical. Automated dispatching is only as useful as its ability to receive orders and emit events. Sendme exposes:
- REST API — create orders programmatically from any system.
- Webhooks — push events on assignment, pickup, in-transit, delivered, and failed.
- Shopify and WooCommerce plugins — checkout-time delivery rate calls and one-click install.
Full details at the SendMe API Gateway.
The automated dispatching config checklist
| Config | Why it matters | Common failure without it |
|---|---|---|
| Assignment rules | Controls who gets which order | Premium orders go to untrained riders |
| Routing logic | Controls cost vs SLA trade-off | Missed time windows |
| Capacity constraints | Prevents oversized assignments | Failed deliveries, refunds |
| SLA enforcement | Prioritises urgent orders | High-value customers lost |
| Exception handling | Defines fallback behaviour | Silent failures, no audit trail |
| Hybrid fleet config | Blends in-house, 3PL, and gig | Coverage gaps at peak |
| Driver feedback loop | Rewards quality riders | Ratings drift down over time |
| Integration config | Connects to your existing systems | Manual re-entry errors |
Frequently asked questions
What is automated dispatching in delivery software?
Automated dispatching is the rule-based, algorithm-driven assignment of delivery orders to drivers. It replaces manual dispatch by evaluating driver availability, proximity, capacity, and customer SLA.
Which configurations matter most in automated dispatching?
The five highest-impact configs are: assignment rules, routing logic, capacity constraints, SLA enforcement, and exception handling. Hybrid fleet configs, driver feedback loops, and integration settings follow close behind.
Can automated dispatching handle hybrid fleets?
Yes. Sendme by Lilwa's dispatch engine can prioritise in-house riders, 3PL partners, or gig capacity depending on the config you set, and can shift priority order by order class.