Configuration
Configure the business rules before you invite vendors. Changing commission, zones or currency after orders exist is possible, but it makes reports harder to compare.
General
| Setting | What to check |
|---|---|
| Site name and URL | Exact HTTPS URL. A wrong URL breaks callbacks, emails and app links. |
| Timezone | Match the city you operate in; reports and order cut-offs depend on it. |
| Currency | Set before the first order. Changing it later does not convert historical orders. |
| Logo and colours | Use a square icon for the apps and a wide wordmark for the web storefront. |
| Support contact | A monitored email and phone/WhatsApp number. |
Orders and delivery
- Minimum basket — protects small orders from delivery costs.
- Preparation time — set a realistic default per vendor; it drives the customer ETA.
- Delivery zones — polygon or radius, each with its own fee and minimum. Test an address on each edge.
- Rider model — platform riders, vendor self-delivery, or pickup. Mixed models are supported per vendor.
- Cancellation and refund rules — decide who can cancel and at which stage.
Commission and settlements
Commission can usually be set globally, per vendor or per category, as a percentage or a per-order fee. Decide whether the delivery fee is retained by the platform or passed to the rider/vendor, and confirm the settlement report shows the same number your vendors expect.
Email, SMS and push
- Use SMTP or a transactional provider; test password reset and order confirmation.
- If SMS/OTP is enabled, test one local number and one international number.
- Push notifications require a Firebase project and the matching app configuration. Test on a real device, not only an emulator.
Apps and store links
Rebuild the Android app with your own package name and signing key. Publish under your own Play Console account. For iOS, use your own Apple developer account. Keep the customer, partner and rider builds on the same backend and the same API URL.
Performance and caching
After changing configuration, clear the application cache and any CDN cache. Serve images and static assets through a CDN where possible. Do not cache admin pages or authenticated API responses at the edge.