Platform

Four Apps, One Core, already built

Customer app, rider app, vendor panel, and admin dashboard — all running on one order, dispatch, and payments engine. This page is what actually ships, screen by screen.

Request Quote Explore the apps

How the Platform Is Put Together

Four client surfaces, one shared core, and a configuration layer that holds your business rules. Verticals change the configuration, not the engine.

Layer 01 · Client surfaces
Customer app
iOS · Android · Web
Driver app
iOS · Android
Store app
Tablet · Web panel
Admin dashboard
Web
Layer 02 · Shared core
Order engine
States, refunds, audit trail
Dispatch engine
Assignment, batching, routing
Payments
Multi-party splits and payouts
Identity & roles
Auth and permissions
Layer 03 · Configuration
Zones & pricing
Per city and per vertical
Commission rules
Per vendor or group
Dispatch parameters
Radius, batching, surge
Branding
Logo, palette, domain
Layer 04 · Integrations
Payment gatewaysPayout railsMaps & routingSMS & pushWhatsAppPOS / KDSBI & data exportWebhooks

The Four Apps

Each group gets the screens it needs, not a shared generic UI stretched across all four.

Account & auth

Email, phone OTP, and social login with profile and address book management.

Browsing & search

Category discovery, smart filters, and ranking that respects delivery radius and availability.

Ordering & checkout

Saved cards, wallets, cash on delivery, promo codes, and scheduled orders.

Live tracking

Order state plus rider GPS from pickup to doorstep, with ETA recalculated en route.

Post-delivery

Ratings, tipping, and one-tap re-order to drive repeat purchase.

Support

In-app chat, issue reporting, and refund requests routed into your ops queue.

The Dispatch Engine

The part everyone underestimates. Assignment reasons about distance, capacity, prep time, and batching — and your ops team can always override it.

Assignment

Nearest-available matching weighted by current load, vehicle type, and rider rating, with a configurable search radius that widens if nobody accepts.

Batching

Stack compatible orders by zone, value, and maximum detour — or switch batching off entirely for premium single-drop service.

Prep-time awareness

For food and any prepared-goods vertical, assignment is timed against the vendor's prep estimate so handover happens as the order is packed.

Manual override

Ops can assign, reassign, or hold any order from the live map. Every override is logged with the operator and reason.

Configuration, Not Code

Everything in this list is editable from the admin dashboard without a development ticket. That’s the line between configuration and custom work — and it’s where most of the day-to-day lives.

Delivery zones
Polygon zones per city with their own fees and rider pools.
Pricing logic
Base fare, distance and time bands, minimum order, and surge windows.
Commission rules
Per vendor or vendor group, with separate pickup and delivery rates.
Payout schedules
Daily, weekly, or instant payouts for riders and vendors.
Promotions
Discount codes, first-order offers, and vendor-funded campaigns.
Proof of delivery
Photo, signature, or OTP, set per city or order value.
Notification templates
SMS, push, and email copy per market and per order state.
Refund policy
Reason codes with rules for who absorbs the cost.
Roles & permissions
What ops, finance, and support can each see and do.

Security, Compliance & Reliability

Payment data is encrypted in transit and at rest, access is role-based across all four surfaces, and every order, refund, and payout action is logged for audit.

Payments

Encrypted and tokenized

Payment data is encrypted in transit and at rest, with tokenized handling aligned to PCI-DSS requirements.

Access

Role-based across four surfaces

Customer, rider, vendor, and admin permissions are separately scoped, with per-user roles inside the admin dashboard.

Audit

Every action logged

Orders, refunds, payouts, and dispatch overrides are logged with operator and timestamp for audit.

Reliability

99.95% uptime SLA

Horizontal scaling on order throughput, queued dispatch and notification paths, and automatic failover.

Data handling is configured per region — GDPR-aligned for EU/UK deployments, with local data residency options where required.

Platform FAQ

Technical questions about how the platform runs and what you can change.

Still have questions? Contact our support team

What actually runs on your infrastructure versus ours? +

On Starter and Growth the whole platform is hosted and managed by Aalpha — application, database, and media storage. Enterprise engagements can deploy into your own cloud account where compliance or procurement requires it. Either way, the apps are published under your developer accounts and the domain is yours.

Can we change dispatch logic ourselves? +

The parameters, yes: assignment radius, batching limits, maximum detour, surge windows, and priority rules are all editable from the admin dashboard. The underlying algorithm is platform code, and changing how it reasons is custom development work — which is deliberate, since that logic is the part already tested at volume.

Is there an API? +

Yes. Orders, riders, vendors, and webhooks for order state changes are exposed so you can connect internal tools, a data warehouse, or a partner's system. API access and rate limits are set per tier.

How do updates reach our deployment? +

Platform releases are applied by Aalpha on a regular cadence, with security patches applied out of band when needed. Your configuration and branding are preserved across updates — that separation is why the core stays upgradable while your rules stay yours.

What happens to our data if we leave? +

Your data is yours. On exit we provide a full export of orders, customers, vendors, riders, and financial records in a structured format, and the deployment is decommissioned on an agreed timeline.

How does the platform behave at peak? +

Infrastructure scales horizontally on order throughput, and the dispatch and notification paths are queued so a demand spike degrades gracefully rather than dropping orders. Uptime is covered by a 99.95% SLA with automatic failover.

See the Platform on a Call

We'll walk the four apps and the admin dashboard against your business rules, not a canned demo script.

1

Schedule a Discovery Call

Discuss your business model, target market, and specific vertical requirements with our experts.

2

Review Proposal & Pricing

A scoped quote based on city count, order volume, and any custom requirements.

3

Launch Your Platform

Our team handles the deployment while you focus on onboarding your first partners and customers.

Platform · Quick Facts
Apps included Customer · Driver · Store · Admin
Time to launch 2-4 Weeks
Uptime SLA 99.95%
Hosting Managed or self-host
Single-city, single-vertical launches start at$10K–$20K