Platform · Core engine — shared

Eight apps. One engine underneath

Dispatch, payments, zones, and analytics are not four products bolted together. They are one system the delivery and mobility branches both sit on, which is why a food order and an airport transfer settle through the same ledger and appear in the same report.

Request Quote See the subsystems
01
Dispatch & routing
Auto-assignment, offer rings, batching, and multi-stop sequencing.
Both branches
02
Payments & payouts
Gateways, commission splits, partner payouts, and reconciliation.
One ledger
03
Zones & geofencing
Service areas, distance pricing, surge, and restricted zones.
Map-configured
04
Analytics
Operating reports, partner performance, exports, and audit trail.
One warehouse

Both Branches, The Same Foundation

A delivery order and a ride request enter the same assignment loop, draw on the same zone definitions, move money through the same payout rails, and land in the same warehouse. Running both verticals costs one integration, not two.

One backendOne ledgerOne zone mapOne reporting warehouseOne integration set
01 · Shared subsystem

Dispatch & Routing

The assignment loop both branches run on. It decides who takes a job, when they are offered it, and in what order they drive — with the operator able to override any of it.

Auto-assignment
Nearest eligible partner by distance, load, rating, and acceptance rate.
Offer rings
Sequential or broadcast offers with timeouts and widening radius on decline.
Prep-aware timing
Assignment timed against prep or wait so nobody idles at the pickup.
Batching
Compatible jobs grouped by proximity and time window, with a stop sequence.
Multi-stop routing
Optimised ordering across pickups and drops, recalculated on traffic.
Manual override
Operators reassign, force-assign, or unassign from the live map.
Delivery
Batching, prep-time offsets, and multi-drop sequencing
Mobility
Single-trip matching, destination filters, and airport queues
02 · Shared subsystem

Payments & Payouts

Money in from customers, money out to partners, and the commission split in between. One ledger covers both branches, so a marketplace with restaurants and captains settles from a single source.

Gateways
Cards, wallets, UPI, and regional processors, with cash handled in the same ledger.
Commission rules
Per-vendor, per-category, or per-zone rates, flat or percentage.
Multi-party split
Customer payment divided across platform, vendor, and partner automatically.
Payout schedules
Instant, daily, or weekly payouts with minimum thresholds and holds.
Refunds & adjustments
Partial or full refunds with reason codes that flow into reporting.
Reconciliation
Gateway settlements matched against internal ledger entries daily.
Delivery
Vendor commission, cash collection, and tip pass-through
Mobility
Fare splits, captain incentives, and corporate invoicing
03 · Shared subsystem

Zones & Geofencing

Geography is configuration. Service areas, delivery radii, surge boundaries, and airport pickup fences are drawn on a map in the console and take effect without a release.

Zone drawing
Polygon or radius zones drawn on the map, versioned and reversible.
Per-vendor fences
Each store or hub carries its own radius and delivery-time rules.
Distance pricing
Delivery fees and fares stepped by band, with minimums and caps.
Surge by zone
Automatic multipliers on demand-to-supply ratio, or manual overrides.
Restricted areas
No-service and no-pickup zones enforced at booking, not after.
Zone priority
Overlapping zones resolved by an explicit precedence order.
Delivery
Store radii, delivery-fee bands, and out-of-area blocking
Mobility
Airport fences, city limits, and surge boundaries
04 · Shared subsystem

Analytics

Every state change lands in one warehouse, so orders and trips can be read together. The console ships the operating reports; the export and API cover everything your analysts want to do themselves.

Operating reports
Volume, revenue, completion times, and cancellations by day or zone.
Partner performance
Acceptance, completion, ratings, and utilisation per rider or captain.
Vendor performance
Prep accuracy, rejection rate, and revenue contribution per store.
Cohorts & retention
Repeat rate and order frequency by acquisition period.
Exports
CSV downloads, scheduled email reports, and a read API for your warehouse.
Audit trail
Every state change timestamped and attributed, retained per your policy.
Delivery
Basket size, prep time, and vendor mix
Mobility
Utilisation, fare per km, and idle time

One State Machine, Two Vocabularies

Orders and trips are the same object with different labels. Every state change is timestamped, attributed, and replayable.

created
Order placed
Trip requested
Payment authorised or fare estimated, request enters the queue.
accepted
Restaurant accepts
Captain accepts
Prep time or pickup ETA committed; the customer's estimate updates.
assigned
Rider assigned
Captain matched
Dispatch picks a candidate and starts the offer ring.
in_transit
Picked up
Trip started
Live GPS begins, waiting time and tolls metered where applicable.
completed
Delivered
Dropped off
Proof of delivery or trip end; final fare or total locked.
settled
Payout queued
Payout queued
Commission split applied and the entry written to the ledger.

Run, Extend, Integrate

The engine is hosted and maintained by Aalpha, but it is not a closed box. Webhooks, a documented API, and a connector library let it sit inside the systems you already run.

HostingManaged by Aalpha on your chosen cloud and region
UpdatesSecurity patches and platform releases applied without losing your config
ConfigurationZones, pricing, commissions, and rules changed from the console
ExtensibilityWebhooks on every state change, plus a documented read and write API
Data ownershipYour data, exportable in full at any time
Integration surface
✓Payment gateways: cards, wallets, UPI, and regional processors
✓Maps and navigation providers, swappable per region
✓SMS, push, WhatsApp, and email messaging providers
✓Accounting and ERP export for settlements and invoices
✓POS and inventory connectors for vendor catalogues
✓Webhooks and REST API for anything not on the list
Connector library covers 24 integrations across payments, messaging, maps, and accounting.

Engine FAQ

How the shared layer is hosted, configured, and extended.

Still have questions? Talk to our team

Is the engine really shared, or two codebases with one brand? +

Shared. Delivery orders and mobility trips are the same underlying object with different labels and rule sets. That is why you can run both verticals on one backend, one ledger, and one set of reports.

Can we change dispatch logic ourselves? +

The parameters — radius, offer timeout, ring strategy, batching thresholds, acceptance weighting — are console settings you control. Replacing the algorithm itself is custom work, scoped separately.

Where does our data live? +

In a database instance dedicated to you, in the cloud region you choose. It is your data: exportable in full, at any time, in standard formats.

What happens during platform updates? +

Releases are applied by Aalpha on a regular cadence. Your configuration — zones, pricing, commissions, branding — is preserved across every update, and breaking changes are communicated ahead of the release.

Can we connect our own payment gateway or maps provider? +

Yes. The connector library covers 24 common providers, and anything outside it can be added against the same interface. Maps and messaging providers are swappable per region.

See the Engine Against Your Rules

Bring your zones, your commission structure, and your worst dispatch scenario. We'll configure it live and show you what the engine does with it.

Core engine · Quick facts
Subsystems Dispatch · Payments · Zones · Analytics
Serves Both branches, 8 apps
Extensibility Webhooks · REST API · 24 connectors
Hosting Managed, your cloud region
Hosting, patching, and platform updates are included in the managed plan.