Coupons by zone, restaurant, and first order
Separate coupon rules for neighbourhoods you are trying to win, for partner restaurants, and for new customers.
A white-label food delivery platform designed for entering a new city with aggressive offers while keeping margin visible. The described scope covers Android customer, restaurant, and rider apps, a web storefront, and an admin console; an iOS release is scoped and quoted on its own.

A Keeta-style platform is a food delivery marketplace where promotions are the growth engine. Instead of one global discount, the operator runs offers by delivery zone, by restaurant, and for first orders, and decides who funds each one.
The practical difference from a generic delivery app is accounting. When a discount is applied, the order record notes whether the platform or the restaurant paid for it, and commission is calculated on the basket before discounts, so a promotion-heavy launch does not quietly erase your take rate.
Planned scope for the standard build. Every item is reviewed in scoping and can be adjusted, dropped, or extended.
Separate coupon rules for neighbourhoods you are trying to win, for partner restaurants, and for new customers.
Each discount line is tagged as platform-funded or restaurant-funded, which keeps settlement disputes short.
Commission is computed on the pre-discount basket, so promotions do not reduce the platform share by default.
Basket-value rules for free delivery and cashback credited to the customer wallet for the next order.
Restaurants opt in to platform campaigns from their app, and campaign participation is visible to the admin.
Operators switch peak delivery fees on per zone during demand spikes rather than raising prices city-wide.
Restaurants can request promoted placements that the admin approves before they go live.
Reference configuration. Included modules and custom changes are confirmed in your scope.
Role panels are configured to your operating model during scoping.
Orders food and uses offers.
Accepts orders and joins campaigns.
Picks up and delivers.
Runs zones, money, and offers.
Confirm included modules, third-party accounts, source-code licensing and support terms in the written scope. Third-party software, APIs and model licenses retain their own terms.
The Android apps are published under your account.
A gateway approved for your country, onboarded before testing.
Mapping, geocoding, and OTP providers billed to you.
Server or cloud account where the backend and web storefront run.
The first delivery zones, commission rates, and opening promotions.
The described build covers Android apps for all three app roles. If you need iPhone apps or App Store publishing, that work is scoped and quoted separately before it starts.
New promotion mechanics, such as spend-tier coupons or loyalty points, are custom work. We define the rule, the funding logic, and the reporting it needs in writing before quoting.
Have a question about your next step? Tell us what you have in mind.
Not in the described scope. The customer, restaurant, and rider apps are Android builds. An iOS version is planned as a separate, quoted piece of work.
See the workflows that matter to your business in a guided product walkthrough.
Book a live demo call and we will walk through the exact flows you care about.
Book a live demoTell us your city, zones, and the offers you want to run, and we will send a written scope covering the Android build and any iOS work.