Customer App & Ordering Website
Browse, order, pay, and watch the rider approach — on iOS, Android, and a responsive web storefront that shares the same catalogue and checkout.
Sign-up & addresses
Catalogue & search
Checkout
Live tracking
Re-order & ratings
In-app support
Delivery Driver App
Everything a rider needs between going online and getting paid: offers with the payout visible up front, navigation to both stops, proof of delivery, and an earnings ledger that matches their payout.
Onboarding
Shifts & zones
Offers
Navigation
Proof of delivery
Earnings
Restaurant Panel
A counter tablet for the order queue and a browser panel for the back office, both on the same account. Prep times set here feed straight into the customer's ETA and the rider's arrival time.
Staff roles
Order queue
Catalogue
Prep time
Reporting
Settlements
Admin Console
The operator's surface: a live map of every order and rider, an exception queue for what needs a human, and the configuration that governs pricing, zones, commissions, and payouts.
Live dispatch map
Exception queue
Vendors & riders
Analytics
Configuration
Finance
One Order, Across All Four
The apps are separate surfaces on one state machine. A single order moves through them without anyone re-keying it.
Order placed
Accepted with a prep time
Rider assigned
Picked up and delivered
Settled and logged
Your Brand on the Store Listing
Apps are published under your Apple and Google developer accounts, with your name, icon, screenshots, and support contact. Customers never see DeliveryStack, and you keep the listings if the engagement ends.
Are these real apps or a wrapped web view? +
Native builds for iOS and Android, submitted to both stores as standard apps. The ordering website is a separate responsive surface sharing the same catalogue, checkout, and account system.
How much of the app can we change? +
Branding, copy, notification templates, catalogue structure, pricing, and zones are all configuration you control from the admin console. Layout changes and new screens are custom development, scoped separately.
Do we need our own Apple and Google accounts? +
Yes, and that is deliberate. We set them up in your name if you do not have them, then publish under your ownership so the listings, reviews, and install base belong to you.
Can we launch with fewer than four apps? +
Most operators start with the customer app, driver app, and admin console, and add the restaurant panel when they onboard third-party vendors. The engine does not change either way.
Who handles store updates and OS releases? +
Aalpha. Platform releases, security patches, and compatibility updates for new iOS and Android versions are applied on a regular cadence, with your configuration preserved across updates.
Walk the Four Apps With Us
We'll open the real builds against your menu, your zones, and your commission rules, then show the same order move through all four surfaces.