How NorthStar Kitchens runs 3 cloud-kitchen brands from one tablet

NorthStar Kitchens is a multi-brand cloud kitchen operator founded in 2023 by Rahul Singh, a former QSR franchisee who decided the math made more sense on delivery-only. Two kitchen units — one in Gurugram Sector 49, one in Noida Sector 18 — running three virtual brands on the food delivery aggregators:

• Biryani Sutra — premium dum biryani, lunch + dinner
• The Momo Lab — pan-Asian momos and bowls, all day
• BowlCraft — healthy salad + grain bowls, lunch hour

Three brands, three menus, three target customers, three sets of recipes — all running out of one 800 sq ft kitchen with one chef team. On paper, beautiful unit economics. In practice, in early 2024 it was operational chaos.

NorthStar's pre-OutletPilot setup was three tablets in the kitchen window — one per aggregator account (Zomato Biryani Sutra, Swiggy Biryani Sutra, Swiggy Momo Lab, Zomato BowlCraft… ten total tabs across two kitchens). Every order came in on its own tablet. The kitchen team manually translated it to a paper KOT slip and routed to the appropriate station.

Rahul tracked sales in a Google Sheet. Once a day, his manager downloaded CSVs from Zomato Partner, Swiggy Captain, and a small direct-website channel — and pasted them into a master sheet. By Tuesday morning he had Monday's numbers. By that point Monday's mistakes were two days old.

The kitchen had its own problem: brand-mix invisibility. The chef team had no idea which brand was driving which volume in real time. If BowlCraft suddenly spiked at 1 PM, they didn't know — they just saw "lots of orders" and started losing tickets. Average kitchen ticket time was crossing 28 minutes during peak — for delivery orders that should be out in 15.

Most Indian POS were built for dine-in first, with cloud-kitchen mode as an afterthought. Rahul had spent a month trialing Petpooja and a few others. What killed each of them for him was the same thing: "brand" was a tag, not a first-class entity.

OutletPilot treats virtual brands the way a real cloud-kitchen operator thinks about them. Each brand has:

• Its own menu (with shared underlying recipes when applicable)
• Its own channel mapping (Zomato Biryani Sutra ID, Swiggy Biryani Sutra ID, etc.)
• Its own loyalty wallet (a Biryani Sutra customer doesn't see BowlCraft points)
• Its own P&L report — revenue, COGS, gross margin per brand
• Its own commission accounting (Zomato Pro 27%, Swiggy basic 22%, direct 0%)

Critically, the kitchen view didn't fragment. One KDS screen with colored station-routing showed all orders across all three brands in a single queue, prioritized by promise time. The chef team saw a unified prep board; the customer dashboards stayed separate.

NorthStar's rollout was actually one of the simpler ones because Rahul had no legacy data to migrate. He used the Setup Wizard on a Sunday afternoon — created the company, two outlets (one per kitchen), three brand entities under each outlet. The OutletPilot team helped him map aggregator accounts on Monday.

By Wednesday his team was live. Inventory took another 10 days because Rahul wanted to digitize the recipes properly — a discipline he hadn't enforced before. He resisted the temptation to skip "the boring part."

Stack as of Feb 2025:

• 1 POS tablet per kitchen (replaced 3 aggregator tablets each)
• 1 PilotKDS screen per kitchen, station-routed: Tandoor / Wok / Cold Bowls
• 1 receipt printer per kitchen (for delivery rider handoff slips)
• 3 brand workspaces visible to Rahul on the admin web
• Direct-website orders coming into a fourth channel: "Direct"

1. Kitchen ticket time fell from 28 min to 17 min during peak. The unified KDS queue plus station routing meant chefs stopped wasting cycles re-reading KOT slips. The "promise time visible to chef" feature alone shaved 4 minutes per ticket.

2. Aggregator reconciliation went from 4 hours/day to 30 minutes/week.The channel-mix report automatically reconciled aggregator-reported orders against OutletPilot's recorded orders. Rahul's manager went from filling Excel to actually managing the kitchen.

3. The "money-losing brand" got identified. BowlCraft, which Rahul believed was his best margin brand, was actually his worst once Zomato's 27% commission and the higher-priced fresh greens cost were attributed correctly to the brand. Biryani Sutra at 35% commission still made more contribution margin per order because its food cost was lower. Rahul cut BowlCraft's portion size by 12% and adjusted MRP — moved BowlCraft from −3% net margin to +9% in two months.

4. Customer wallet started compounding. Each brand has its own wallet, but a customer who orders biryani regularly now sees their balance grow. Re-order rate on Biryani Sutra direct-website moved from 18% to 41% in the same 6 months — primarily driven by wallet credit + WhatsApp birthday nudges.

Three OutletPilot capabilities mattered more than the rest for a cloud-kitchen use case:

Offline-first sync. NorthStar's Gurugram kitchen had patchy Jio coverage in the basement. POS would have been a non-starter without offline queueing. OutletPilot keeps the POS and KDS local-state-of-truth and syncs to cloud on reconnect. The chef team has literally never noticed a 'network issue' since rollout.

Per-brand channel mapping. Each aggregator account ID is mapped to a specific brand. When Zomato sends an order for "BowlCraft", OutletPilot knows it's BowlCraft revenue with Zomato commission attribution. Rahul's P&L slices cleanly.

Recipe-driven food cost. Same as Tandoor's story but more critical for a cloud kitchen where you can't see customer reactions. NorthStar's biryani recipe says 175g rice per portion. Variance dashboard flags any drift beyond 7%. Without that, drift compounds silently until the quarter-end finance review.

NorthStar Kitchens is opening a third kitchen in South Delhi (Saket) in Q1 2026. The rollout playbook is now a 5-day exercise: kitchen lease day → device unboxing day 2 → aggregator mapping day 3 → 2-day soft launch → live. No more 30-day onboarding pain.

Rahul's longer-term play is to franchise the "NorthStar OS" — the combined brand portfolio + OutletPilot setup — to single-kitchen operators in tier-2 cities. He's not building the software himself; he's standing on OutletPilot. "It would have taken me three years to build half of what they ship by default," he said. "And I'd have built it worse."