Merchant app for restaurants and vendors
The merchant app is the restaurant's control room: accept orders, update preparation, manage the menu, pause the store and see the day's earnings without calling the platform owner.
What the merchant app does
- Incoming order queue with accept, reject and preparation states
- Menu, category, item, variant and add-on management
- Store open/closed, busy mode and temporary pause
- Order history, cancelled orders and refund visibility
- Daily and weekly earnings, commission and payout view
- Push alerts for new orders and status changes
Why a native app matters for vendors
Restaurant staff cannot sit in front of a browser all day. A phone app with a loud order alert is the difference between accepting an order in 30 seconds and losing it. The app also lets the owner update the menu from the shop floor instead of asking the platform admin.
Android and iOS
Android and iOS are separate $49 builds. Both connect to the same Foodomaa backend and merchant API. You own the Google Play and Apple developer accounts, package names and signing keys. The licence covers one production build per platform.
What you need
- An existing Foodomaa installation with the merchant API reachable over HTTPS
- Vendor accounts configured in the admin panel
- Your own app-store accounts and signing credentials
- A test restaurant with a real menu and delivery zone
If you are launching a new platform, use the $299 package so the customer, merchant and rider apps share one tested backend.
Questions
Is the merchant app included in the $299 package?
Yes. The package includes Android and iOS builds for customer, merchant and rider apps.
Can a vendor use one app for several outlets?
The merchant app is built around the vendor account. If you need multi-outlet switching, confirm the workflow in the demo and include it in your build scope.
Does it work without the rider app?
Yes. A vendor can use self-delivery or the web merchant panel. The rider app is a separate client.
Can I white-label it for a client?
One licence covers one production installation. Client-branded builds and multiple brands need a separate written agreement.