Skip to content
TThe Consulting Crew

Blogs · Case Study

Case study: one kitchen to three outlets — the build behind a Jaipur restaurant

By Ashish Kumar Sharma · Published 17 Aug 2026

A C-Scheme success story wanted to become a chain. Between it and outlet three stood GST's no-credit regime, two aggregator platforms, four licences and a costing model that lived in the owner's head.

A composite case drawn from real engagements with Jaipur food-service clients; names, figures and identifying details changed.

The first outlet was the classic Jaipur story: a family recipe, a good C-Scheme location, queues by month six. Revenue was around ₹1.6 crore a year, a third of it through Swiggy and Zomato. The owners wanted two more outlets in eighteen months. The business underneath, though, was still a one-kitchen operation: single GST registration handled casually, purchases largely in cash from Johri Bazaar-side mandis, staff paid without structure, and profit measured by what was left in the account.

The GST reality of restaurants

Restaurant service is taxed at 5% without input tax credit — a regime that quietly reshapes expansion economics. The fit-out of a new outlet — kitchen equipment, furniture, interiors — carries GST you cannot claim, so every capex quote was re-read at its gross number, and the project budget rebuilt on landed cost. The same logic changed vendor choices: with no credit at stake, the negotiation is purely on price and reliability, but with purchases formalised so the income-tax side of the books holds.

The aggregator leg had its own trap. For orders through food-delivery platforms, section 9(5) makes the platform liable to pay the GST on restaurant service — but the restaurant still reports those supplies in its returns in the ECO-specific disclosures. The books had been treating platform settlements as “whatever hits the bank,” which meant commissions, ads, and TCS were all buried in one line. We rebuilt the platform reconciliation monthly: gross orders, platform commission and ad spend (both carrying GST the restaurant also cannot credit), TCS trail, and settlement to bank — tied to the returns.

The licence stack, per outlet

RequirementThe practical point
FSSAIEach outlet licensed for its own premises — at this turnover a state licence, renewed on time, displayed as required
GST registrationNew outlets added as additional places of business the day fit-out starts
Shops & EstablishmentsRajasthan registration per establishment, staff hours documented
Fire & local NOCsSequenced before interiors, not after — retrofits are expensive
PF and ESIHeadcount across outlets counts together — the chain crossed both thresholds, registrations done before the department noticed first

Payroll went from cash-and-goodwill to structured: appointment letters aligned to the Labour Codes, wage records, PF/ESI filings monthly. Food businesses live on staff continuity; formalisation, done with pay structured properly, became a retention tool rather than a cost.

The per-outlet MIS

The decision instrument for expansion was a one-page monthly MIS per outlet: revenue split dine-in versus delivery, food cost percentage against a target band, platform commission as a percentage of delivery sales, staff cost, rent, and outlet-level breakeven. Within a quarter it produced the chain's first honest facts — the flagship's food cost was two points above target (portioning, fixed with a gram-level recipe sheet), and delivery orders below a ticket size were losing money after commission (fixed with delivery-only pricing and combos). Those two fixes funded a meaningful part of outlet two's fit-out.

What eighteen months produced

  • Three outlets running, each with its own licence file and its own P&L.
  • Platform reconciliations current, returns matching the books every month.
  • Outlet three sited using the MIS — the glamorous location lost to the one whose numbers worked at realistic volumes.
  • A franchise enquiry answered with a data room instead of a shrug: licence stack, per-outlet economics, standard recipes and SOPs.

Lessons that generalise

  • No-ITC businesses budget gross. Wherever credit is blocked — restaurants and several composition cases — capex and vendor maths must use the GST-inclusive number.
  • Platforms are a second set of books. If a marketplace or aggregator sits between you and the customer, reconcile their statements monthly or fly blind.
  • Thresholds aggregate. PF, ESI and several registrations count the entity, not the outlet. Expansion plans need a compliance calendar of their own.
  • Expand on unit economics, not on the brand's mood. A per-outlet MIS is the cheapest expansion insurance there is.

How we can help

We run this build for food businesses regularly: FSSAI licensing, GST with aggregator reconciliation, payroll setup and the per-outlet MIS. If you are one good outlet dreaming of three, the right time to build the boring layer is before the second lease is signed.

The numbers that made these decisions: our 12-number business health check →

This case study is illustrative general information, not advice. Rates, thresholds and licence requirements change; confirm current rules for your business before acting.

Let's get your compliance off your plate.

Tell us what you are dealing with. A short reply from someone who does this every day — no pitch, no obligation.

  • Reply within one working hour on WhatsApp
  • Fixed monthly fee, agreed before any work starts
  • No lock-in — month to month, 15 days’ notice

Request a callback

Two fields and you are done. We reply on WhatsApp within one working hour, Mon–Fri 10:00–19:00 and Sat 10:00–14:00 IST.

or message us on WhatsApp instead →
The Consulting Crew

A Strategy That Drives Results