Built for your kind of kitchen
Every platform, one queue.
Many brands out of one kitchen, every aggregator landing in the same line, and settlements that reconcile themselves.
What this shape of kitchen needs.
Many brands, one kitchen
Each brand keeps its own menu, its own prices and its own bill numbering, while the kitchen sees one stream of work — because that is what the kitchen actually is.
Every platform in one line
Zomato and Swiggy orders arrive by webhook, priced and tagged, into the same queue as your own storefront. Nobody watches four tablets.
The kitchen sees one board
Tickets group by station and age in colour, so the pass knows what is late without anyone shouting. Section 9(5) orders are tagged, not taxed.
Settlements that reconcile themselves
Import the platform statement and every payout matches to the orders behind it, to the paisa — commission, taxes and deductions each in their own column.
Wired into what you already run.
The names below are live integrations, not logos on a wall.
- Zomato
- Swiggy
- UPI
- Razorpay
- Cashfree
The modules this leans on.
FAQ
How many brands can one kitchen run?
As many as you have menus for. Brands are children of the kitchen, so they share stock and staff while keeping separate menus, prices and bill series.
Do aggregator orders get taxed twice?
No. Section 9(5) makes the aggregator the GST-liable party on the orders it collects, so those are recorded and tagged but never taxed on your invoice. That is the law, and it is how the engine is built.
Can I see which brand is actually making money?
Yes. Sales, item mix and margin break down per brand as well as per kitchen, so a brand that only looks busy shows up as one that only looks busy.
Other shapes of kitchen.
One kitchen, every channel.
Free for your first 6 months. Every module included, nothing to switch on later.