Kouzina OS is the system we built to run our own kitchens.
A live Control Tower, a Revenue Engine that catches what aggregators don't show you, and PayMatch — reconciliation down to the paisa.
They're losing it in small, silent leaks. A four-minute Swiggy outage at Whitefield. An item marked out-of-stock on Zomato when the kitchen actually had it. A Tuesday-night payout that's ₹17,264 short and nobody notices until the books close two months later.
POS systems weren't built to see these. Aggregator dashboards won't show you. Excel can't keep up. So the money quietly drips out of every outlet, every shift.
payout variance PayMatch surfaced for one brand in a six-week window
orders audited automatically — 73 unpaid, 37 cancelled, 9 flagged for variance
the largest single-UTR underpayment in that dataset — one Zomato bank cycle
finance teams burn each month on manual reconciliation — before PayMatch
Numbers shown are illustrative, based on patterns from Kouzina-operated kitchens and our early Lighthouse partners — not marketing benchmarks borrowed from a slide deck.
in payout variance surfaced per brand per 6-week reconciliation cycle
fewer hours spent on manual reconciliation each month
reaction time on aggregator downtime — managed Control Tower
of UTRs and orders audited automatically — by design, not by intent
Footnote. Upper-bound observations from Kouzina-operated kitchens and early Lighthouse Program partners, Apr–May 2026. Not customer testimonials. Your operational audit will quantify what's realistic for your specific operation.
Each module solves a problem we've watched cost us real money in our own kitchens. Take the whole stack, or start with the one that bleeds the most.
A real-time command center across every outlet on Swiggy & Zomato. We watch outages, OOS, prep delays and rating drops 24×7 — and react in under five minutes. The piece that keeps a 12-outlet brand from looking like an unattended kiosk.
Yesterday's revenue, the channel mix that produced it, the live operational state behind it — and an AI insight that names the two things to act on first. Summary, Analysis, Tracking and Planning live behind one tab, with per-location forecasts you can re-slice on the fly.
The reconciliation platform we use ourselves. Pulls every aggregator payout, joins it to bank credits, joins those to your underlying orders — and tells you where the money is short. Seven Pass/Fail audit lenses, one full ledger, Tally export in a click.
Demand forecasting per outlet, per daypart. Pre-prep matched to reality.
Inventory, indents, central kitchen flows, vendor recon — one ledger.
Deep Swiggy & Zomato integration. We ingest, you act.
One menu, many channels. Pricing, modifiers, availability in lockstep.
SOPs, micro-learning, audits — powered by Knowlys Learn.
SCM × Finance joined in real time. Margin by dish, hour, outlet.
Every order. Every payout. Every bank credit — matched, scored, flagged. The platform we use to close our own books in two days instead of fourteen.
PayMatch ships with two workbenches: Reconciliation (below) and the Revenue Workbench — same data graph, two jobs.
Pulls Swiggy & Zomato settlement files, direct-channel orders, and bank statements on a schedule. No spreadsheets.
Payout Summary · Order Variance · Unpaid · Cancelled · Special Charges · Negative · High-Value Underpaid — each with its own Pass/Fail threshold.
Multi-brand Platform view. Threshold-based Pass/Fail. Tally connector. One-click CSV export. Upload your bank statement; you're live.
Overview · KZ Foods · 24–30 Apr 2026. Seven Pass/Fail audit lenses at a glance — 99.9% of receivable matched, 0.2% mismatch surfaced.
| BANK UTR | FROM | TO | SOURCE | BRAND | ORDERS | OUR RECEIVABLE | PAID BY AGGREGATOR | CREDITED IN BANK | VARIANCE | VAR% | STATUS | BANK CREDIT COUNT |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 36982296 | 2026-04-30 | 2026-04-30 | ownly | KZ Foods | 1 | ₹112.35 | ₹112.35 | 112.35 | ₹0.00 | 0.00% | PASS | 1 |
| 41000100 | 2026-04-29 | 2026-04-29 | ownly | KZ Foods | 2 | ₹499.78 | ₹499.87 | 499.87 | ₹0.09 | 0.02% | PASS | 1 |
| CITIN26664326658 | 2026-04-27 | 2026-05-03 | zomato | KZ Foods | 247 | ₹79,121.63 | ₹78,864.18 | 78,415.65 | ₹-705.38 | -0.89% | PASS | 1 |
| AXISCN1332718521 | 2026-04-26 | 2026-04-30 | swiggy | KZ Foods | 134 | ₹52,761.79 | ₹52,765.45 | 52,765.56 | ₹3.77 | 0.01% | PASS | 1 |
| CITIN26660054827 | 2026-04-20 | 2026-04-26 | zomato | KZ Foods | 267 | ₹85,871.71 | ₹85,870.54 | 85,694.63 | ₹-176.85 | -0.21% | PASS | 1 |
| AXISCN1328249488 | 2026-04-19 | 2026-04-25 | swiggy | KZ Foods | 243 | ₹87,254.21 | ₹87,257.98 | 87,258.03 | ₹3.82 | 0.00% | PASS | 1 |
One UTR, one bank credit, hundreds of orders. PayMatch reconstructs the chain automatically — the 0.89% Zomato outlier shows up the moment the bank credit lands.
| ORDER ID | ORDER DATE | SOURCE | BRAND | ORDER STATUS | NET REVENUE | OUR RECEIVABLE | PAID BY AGGREGATOR | VARIANCE | VAR% | RECON STATUS |
|---|---|---|---|---|---|---|---|---|---|---|
| 8056562691 | 2026-04-29 | zomato | KZ Foods | DELIVERED | ₹236.10 | ₹163.94 | ₹0.00 | ₹-163.94 | -100.00% | FAIL |
| 8062912328 | 2026-04-30 | zomato | KZ Foods | DELIVERED | ₹426.38 | ₹295.90 | ₹295.47 | ₹-0.43 | -0.15% | PASS |
| 8062719027 | 2026-04-30 | zomato | KZ Foods | DELIVERED | ₹300.19 | ₹208.46 | ₹208.17 | ₹-0.29 | -0.14% | PASS |
| 8065080746 | 2026-04-30 | zomato | KZ Foods | DELIVERED | ₹852.75 | ₹591.82 | ₹590.96 | ₹-0.86 | -0.15% | PASS |
| 236538335340967 | 2026-04-30 | swiggy | KZ Foods | DELIVERED | ₹855.75 | ₹585.02 | ₹585.07 | ₹0.05 | 0.01% | PASS |
| 8067576868 | 2026-04-30 | zomato | KZ Foods | DELIVERED | ₹233.09 | ₹161.75 | ₹161.55 | ₹-0.20 | -0.15% | PASS |
| 236536187753818 | 2026-04-30 | swiggy | KZ Foods | DELIVERED | ₹262.43 | ₹175.85 | ₹175.85 | ₹0.00 | 0.00% | PASS |
| 8063313798 | 2026-04-30 | zomato | KZ Foods | DELIVERED | ₹619.89 | ₹430.22 | ₹429.60 | ₹-0.62 | -0.15% | PASS |
| 236529548224455 | 2026-04-30 | swiggy | KZ Foods | DELIVERED | ₹541.54 | ₹368.24 | ₹368.26 | ₹0.02 | 0.01% | PASS |
Every order. Every aggregator. Every variance — to the paisa. The single ₹163 FAIL row at top is the only mismatch across 538 orders this period.
The second workbench inside PayMatch. Yesterday's revenue, the channel mix behind it, the live operational state, an AI insight that names the next move — and a forecast that re-runs the moment you change a variable.
Each session opens with a short, plain-English read on yesterday's revenue — and three to four ranked actions with revenue or order-impact estimates. Tap Track to start measuring whether the action worked.
Avg prep, items OOS, stores online, full Swiggy / Zomato funnels — on the same canvas as the revenue card. The "why" sits next to the "what".
Next 7 / 30 / 90 days. Baseline, optimistic or aggressive. Per-location ad-spend, discount %, hours and rating are editable — projected revenue updates in place. Built on documented elasticities, not a black box.
Yesterday's revenue was ₹31,142, up 12.3% from the previous period. The most important thing to act on next is to review and adjust your pricing strategy to increase average order value, as it currently stands at ₹486.
Written by AI from your own numbers. Summary figures are real data; action impacts are AI estimates, not exact.
Summary · Yesterday · KZ Foods · One screen, every channel. AI-flagged actions sit next to the live operational state that produced the number.
Yesterday's revenue was ₹31,142, up 12.3% from the previous period. Review and adjust your pricing strategy — AOV is at ₹486.
Analysis · Build any cut, save the view, drop opportunities straight into Tracking. Every metric is sourced from the same audit-graded data as PayMatch Reconciliation.
Planning · Per-location ad-spend, discount %, hours and rating are editable. ΔRev updates in place. Built on documented elasticities, not a black box.
We move fast — but we don't promise "minutes." A 5–10 outlet brand is live on PayMatch in week one and fully on the Control Tower inside a month.
We plug into your aggregator and bank data and produce a single number: the rupees you leaked last month. Sourced from PayMatch (the under-payouts) and the Control Tower (downtime & OOS impact). No deck, no commitment.
Menu mapping, Swiggy/Zomato deep API integration, Tally connector, POS sync. Our team handles the aggregator paperwork. PayMatch goes live in week one with bank statement uploads while the deeper integration finishes.
Control Tower running 24×7 with sub-5-minute reaction SLA. PayMatch reconciling daily with Pass/Fail thresholds. A weekly Recovered-Revenue report lands in the CFO's inbox. You start asking different questions.
From a single high-volume cloud kitchen to a 50-outlet QSR network. Our sweet spot is 5–20 outlet chains — the platform flexes up and down from there.
5–20 outlets · 2+ cities
multi-brand · virtual outlets
50+ outlets · COCO + franchise
We built this for ourselves first.
Now you can use it too.
Three components. Skin in the game from day one, aligned to outcomes from day thirty. We quote after the audit — pricing flexes by outlet count, order volume and module mix.
Covers data integration, menu mapping, PayMatch & Tally setup, and team onboarding. Ensures both sides have skin in the game.
SaaS access to PayMatch, Planning & SCM. Tiered by outlet count or order volume — pick the modules you actually need.
For Control Tower & Revenue Engine. Fixed base plus a small share of Recovered Revenue — money that would have leaked out.
No public price list. We quote after the free operational audit — once we both know the actual leak size.
Stress-test the Control Tower across Kouzina's own kitchens as if they were external clients. PayMatch + Tally connector as the MVP door-opener for Indian restaurant owners.
Onboard five high-profile regional chains at early-adopter pricing in exchange for case studies on revenue lift, reconciliation hours saved, and prep-time reduction.
Full Kitchen ERP with real-time True Unit Economics. Global expansion into UAE and SE Asia — markets that mirror India's aggregator-heavy landscape.
Honest answers — not the rehearsed sales kind. If your question isn't here, just email chanakya.r@kftpl.com.
Five days. Your aggregator data plugged into PayMatch and the Control Tower. One number at the end: what you lost last month, in rupees.