Key Takeaways
1. Outlet spend moved from cash to company-funded UPI wallets. Every kitchen, dark store and delivery hub now runs its day-to-day expenses through a CashBook UPI wallet instead of physical petty cash, so company money leaves the business only as a recorded UPI payment.
2. Fuel, utilities and local suppliers are paid the same way, now fully tracked. Delivery-fleet fuel, LPG, electricity, water, ingredient top-ups and maintenance vendors, much of it paid to individuals on personal UPI, are logged automatically the instant money moves.
3. Control runs before the money moves, not just after. Just-in-time funding and per-wallet limits set a hard ceiling on every outlet, while instant approval alerts and a live policy flag anything unusual the moment it happens.
4. Bills and categories are captured at the point of payment. Instant receipt capture and a clean spend taxonomy give finance audit-ready, GST-friendly records without anyone chasing paper at month end.
5. The model scales with new locations. Opening a dark store simply means issuing a wallet, activated in under an hour through video KYC, so expense control grows with the network instead of slowing it down.
About Company
Swish (Munchmart Technologies Private Limited) is a fast-scaling, Bengaluru-based quick food-delivery and cloud kitchen operator. Its platform manages the full flow from food preparation through to doorstep delivery, competing in India's ten-minute food delivery race. Behind that speed sits a distributed operation: a network of cloud kitchens, dark stores and hyperlocal delivery hubs, plus a delivery fleet, all spending money every hour to keep orders moving.
That scale is exactly what makes outlet expense management hard. A quick commerce operator does not have one office where everyone spends and files bills at the end of the day. It has dozens of kitchens and hubs across a city, each generating a steady stream of small, time-sensitive payments: a rider's fuel at midnight, an LPG refill before the dinner rush, an emergency ingredient run, a housekeeping or maintenance vendor. Individually these are tiny amounts. Across a multi-outlet network they add up to thousands of transactions a month, and traditionally most of them moved as cash. Managing this distributed petty cash across a fast-growing network is what brought Swish to CashBook.
Why outlet expenses are the hidden challenge in quick commerce growth
India's quick commerce and ten-minute food delivery boom is one of the fastest-moving parts of the economy. The country crossed 6,000 operational dark stores in 2026, with thousands more opening, and cloud kitchens and delivery-first brands are multiplying alongside them. Every new dark store or kitchen adds throughput, but it also adds a new node of daily spending that the finance team back at head office has to somehow see and control.
Almost all of that spending happens over UPI. India now has more than 65 million merchants accepting UPI, and person-to-merchant payments make up the majority of transaction volume. For a quick commerce operator that is both an opportunity and a problem. Frontline teams can pay virtually any vendor instantly, from petrol pumps to gas agencies to vegetable suppliers, but when they pay from personal accounts or a cash box, the company loses sight of where its money actually went. The question for a multi-outlet operator is not whether to use UPI; it is how to make UPI spending company-funded, controlled and audit-ready across every dark store, kitchen and hub. This is the gap Swish set out to close, and the story below shows how a fast-scaling quick commerce operator went from cash-driven outlet operations to a fully digital, controlled expense system using CashBook UPI wallets, and why the same approach works for almost any quick commerce, cloud kitchen or dark store brand.
Challenges
What expense challenges do multi-outlet quick commerce operators face?
Before CashBook, expenses at a quick commerce operation are managed the way most fast-growing networks do it: with cash floats and after-the-fact reimbursement. Head office pushes money to outlets or to managers, frontline staff spend it on whatever the hub needs that day, and the paperwork catches up later, if at all. For a single location this is workable. Across a network of dozens of dark stores, cloud kitchens and delivery hubs, it quietly becomes one of the biggest operational and financial risks in the business.
The first problem is the nature of quick commerce spending itself. Outlet expenses are high in frequency and low in value, punctuated by large, lumpy fuel fills. A busy hub makes dozens of small payments a month, and across the network that becomes thousands of transactions. The single largest category for a delivery-heavy operator is fuel, which can run close to half of on-ground spend, followed by kitchen and dark-store utilities such as electricity, LPG and water, then ingredient top-ups, labour, repairs, housekeeping and last-mile logistics. A large share of these payments go to individuals rather than to organised merchants with clean invoices, and petrol pumps rarely take corporate cards without a fuel surcharge, so the operator keeps getting pushed back toward cash.
Frontline staff paid fuel, utilities and suppliers from personal cash or UPI, then waited days for reimbursement.
Payments to individual vendors and petrol pumps left almost no usable digital trail, and card fuel payments carried a surcharge.
Paper bills for fuel, repairs and supplies went missing before they reached finance.
Cash floats sat idle across dozens of outlets with no real-time view of balances, and no hard limit on how much could be spent.
Month-end reconciliation meant rebuilding each outlet's spend from memory and scattered receipts, with no clean per-kitchen cost view.
That creates the second problem: visibility. When a hub manager pays a fuel pump or a supplier from a personal account or a cash float, there is no clean digital record tied to the company. Finance cannot see, in real time, what a given kitchen has spent or on what. Paper bills fade, get lost or never reach head office, so by month-end the team is reconstructing each outlet's spend from memory, WhatsApp messages and whatever receipts survived. The third problem is control and timing. Floats sitting in dozens of outlets mean company money is scattered with no view of how much is left or whether it was used as intended, and because a meaningful share of spend happens during late-night dinner-service and delivery hours, the money moves precisely when oversight is weakest. Petty cash abuse, in particular, is not caught by looking at last month's ledger; it is prevented, or not, at the moment of payment.
Solutions
How CashBook solved Swish's multi-outlet expense problem
Swish moved its outlet spending onto CashBook UPI wallets. CashBook is an NPCI-certified, RBI-regulated, UPI-native expense management platform built around company-funded UPI wallets. The idea is simple but powerful: instead of giving outlets cash, the company gives each kitchen, dark store and hub a wallet loaded with company money. Teams pay vendors by UPI exactly as they always did, but now the money is the company's, the control is the company's, and every payment is recorded the instant it happens.
A master account is loaded centrally, and finance distributes funds into individual outlet and hub wallets. Because the money is pushed from the centre, there is no need for staff to front their own cash and no loose float sitting in a drawer. Every vendor the operation already paid, the petrol pump, the gas agency, the vegetable supplier, the housekeeping and pest-control staff, already accepted UPI, so CashBook slotted into existing relationships without changing a single one, and because payments ride UPI rather than corporate cards, Swish sidesteps the fuel surcharge that erodes every card-based fuel fill on its single largest spend category.
The part that matters most for a network of this size is that control runs before the money moves, not just after. CashBook gives Swish three hard, before-the-fact guardrails. First, wallets are funded just-in-time rather than holding idle floats, so the wallet balance itself is a ceiling: a hub can never spend more than finance deliberately loaded, and if a phone is lost the exposure is capped at whatever is left in that one wallet. Second, finance sets daily, weekly and beneficiary-level spend limits that auto-reset, so a kitchen can cover its running costs but no one can quietly overspend or route money to an unapproved payee. Third, every payment is captured against a clean operations taxonomy, fuel, utilities, LPG, water, labour, purchases, so spend is structured at the point of payment rather than guessed at later. On top of those preventive limits, CashBook layers real-time oversight: the moment a payment happens, the app prompts for a receipt photo and fires an instant alert to the assigned manager to approve or reject it, and a live approval policy routes spend into review. Hard limits stop the wrong payment before it happens; instant alerts and approvals catch anything unusual the second it does.
Company-funded UPI wallets for every outlet, loaded centrally and funded just-in-time, so no one spends personal money, no cash sits idle, and each wallet balance is a built-in spending ceiling.
Pre-set limits and category control, daily, weekly and beneficiary caps that auto-reset, plus a clean spend taxonomy, so the wrong payment is prevented before it happens rather than spotted afterward.
Instant approval alerts and a live policy engine, every payment pings the assigned manager to approve or reject and routes into review, so anomalies surface in seconds, not at month end.
Universal UPI acceptance with zero fuel surcharge, teams scan and pay any merchant or individual, from petrol pumps to gas agencies to ingredient vendors, and skip the card surcharge on fuel.
Bills at the point of payment and a real-time dashboard, a receipt photo is captured with every payment and tagged by outlet and category, giving finance GST-ready records and live per-location spend that sync in one click to Zoho Books and Tally.
Picture it at a Swish dark store on a busy Friday night. The wallet has been topped up just-in-time for the weekend with a daily cap, so total exposure is fixed before a single payment is made. At 11 p.m. a rider needs fuel; the manager scans the petrol pump's QR and pays over UPI in seconds, no card, no surcharge, no cash. The payment appears live on the finance dashboard, tagged to “fuel,” with a receipt attached and an approval alert already sent. Funding stays deliberate rather than reactive, and onboarding is just as fast: opening a new dark store does not mean waiting on bank paperwork, because a CashBook wallet is issued and activated in under an hour through simple video KYC, with only basic identity and business details needed. Since each wallet maps to a kitchen or hub cost-centre rather than to an individual, Swish scales by adding wallets as it adds locations, not by processing a stack of employee paperwork each time.
Impact
What changed after Swish moved to CashBook?
Within months of rolling out, the way money moves through Swish's outlets looked completely different, and it scaled hard along the way, growing from a handful of pilot wallets to a multi-outlet deployment spanning dozens of kitchen and hub cost-centres. The shift from cash to company-funded UPI wallets did not just digitise payments; it changed what the finance team could see and control. Thousands of small outlet payments that used to disappear into cash and lost receipts now arrive as structured, categorised, bill-backed records in real time. The change was not gradual either: once an outlet switched to a wallet, its spending became visible from the first transaction, so the benefit landed the moment each store came online.
The most visible change is transparency. Every outlet transaction is now captured with the payee, amount, time, category and location, including the large share of payments that go to individual vendors and petrol pumps. The biggest blind spot in quick commerce expense management, payments to people rather than to organised merchants, became fully auditable. Control improved as much as speed: with hard wallet ceilings, enforced bill capture and policy-based approvals, the gaps where petty cash leakage usually hides simply close up, and the large majority of spend is now reviewed with over 95% of it carrying a digital bill. Cash exposure dropped at the same time, because funds are pushed just in time instead of parked as floats, and month-end reconciliation stopped being a reconstruction project, becoming a quick review of records already tagged by outlet and category.
Every outlet transaction is now digitally recorded, with payee, amount, time, category and location captured automatically.
Previously invisible payments to individuals and fuel pumps became fully auditable, with over 95% of spend carrying a bill.
Out-of-pocket spending and reimbursement claims were removed for frontline staff, who now pay directly from company wallets.
Idle cash float across outlets dropped sharply, and each wallet balance now acts as a hard, pre-set spending ceiling.
Month-end reconciliation became a review, not a reconstruction, with audit-ready, GST-friendly, per-location records on demand.
What the savings can look like (illustrative)
Every operation is different, so the figures below are a ballpark illustration for a mid-size operator running dozens of outlets, not Swish's actual results, but the levers are easy to size for any quick commerce or food delivery business. Fuel over UPI removes the card surcharge (typically about 0.5 to 1%) on what is often 30 to 45% of on-ground spend, tens of thousands of rupees a month for a fuel-heavy fleet. Just-in-time funding and hard ceilings commonly cut petty-cash leakage by a double-digit percentage. Bills captured at payment and one-click accounting sync can close books up to 10x faster, turning days of reconciliation into minutes. Because wallet costs are a small fraction of the fuel-surcharge saving alone, the programme typically pays for itself within the first month or two. Re-run these with your own fuel spend, outlet count and float sizes for a real estimate.
The deepest change is structural. Finance moved from reconstructing the past to reviewing the present, and the same wallet infrastructure that runs today's outlets will absorb the next wave of dark stores and kitchens without adding administrative overhead. For an operator still expanding across a city, that is the difference between expense control that fights growth and expense control that enables it.
Industry Application
Which businesses around quick commerce benefit most from CashBook?
Swish's challenges are not specific to one brand or even to food delivery. Any business that operates more than a handful of locations, a field or delivery fleet, or frontline teams who need to pay small amounts fast runs into the same pattern: high-frequency, low-value spending, much of it paid to individuals, happening far from the finance team. CashBook is built for exactly this kind of distributed, on-the-ground spending, which makes it a strong fit across the wider quick commerce, food delivery and multi-outlet retail ecosystem.
Quick commerce and dark store operators. Run utilities, stocking, maintenance and last-mile spend across every hyperlocal fulfilment hub through capped, bill-backed UPI wallets with outlet-level visibility
Cloud kitchens and delivery-first brands. Give each kitchen a wallet for ingredients, LPG, packaging and small repairs without handing out cash or waiting on reimbursements.
Food delivery and hyperlocal logistics. Channel delivery-fleet fuel and on-ground costs through UPI wallets, tracked per rider and per hub, with no card fuel surcharge.
Multi-outlet retail and D2C fulfilment. Control per-branch petty cash and micro-warehouse spend from one dashboard while letting each location pay vendors instantly.
QSR chains and restaurant groups. Manage multi-outlet restaurant spend on repair, supplies and utilities with central caps, approvals and audit-ready records.
The pattern Swish proved applies to any multi-outlet operator: if your spending happens at the edge, your control should too. To see how the same wallet model works in other distributed businesses, look at how Roastery Coffee runs multi-outlet cafe spend, how HopCharge manages field and fleet payments, how WOW! Momo runs multi outlet QSR spends both on the same company-funded UPI wallet structure.
Frequently asked questions
How do quick commerce and cloud kitchen operators manage petty cash across multiple dark stores?
Most start with cash floats and after-the-fact reimbursement, where head office pushes money to outlets and reconciles later. This breaks down at scale because spending is high-frequency and largely paid to individuals. CashBook replaces it with company-funded UPI wallets that carry hard balances and limits, enforce bill capture and route approvals by policy. See our guide to the best petty cash management software for how the options compare.
Can UPI wallets be used for delivery-fleet fuel and kitchen expenses like LPG and ingredients?
Yes. Petrol pumps, gas agencies, vegetable and ingredient suppliers, and maintenance and housekeeping vendors almost all accept UPI, so CashBook wallets pay them directly without changing any vendor relationship, and paying fuel over UPI avoids the card surcharge. Here are 10 benefits of using UPI for petty cash management that apply directly to quick commerce operations.
How does CashBook give finance real-time, per-location expense visibility across dark stores and hubs?
Each wallet is tagged by outlet, so every payment lands in the ledger instantly with its category and bill. Finance sees spending across all kitchens, dark stores and delivery hubs from one dashboard in real time, instead of reconstructing each location's spend from receipts at month end, and approved records sync in one click to Zoho Books and Tally.
Conclusion
Swish is building a fast quick commerce and cloud kitchen network by opening locations quickly across the city. CashBook extends that same discipline to the money that keeps each outlet running: the rider's fuel at midnight, the LPG refill before the dinner rush, the ingredient top-up from a nearby vendor. Spending that used to move as untracked cash and surface weeks later now flows instantly through capped, bill-backed UPI wallets and lives in one real-time ledger across every hub the brand operates.
For any multi-outlet quick commerce, food delivery or dark store operator, the lesson is simple. You do not have to choose between letting outlets move fast and keeping finance in control. Company-funded UPI wallets give you both: instant spending power at the outlet and complete visibility at head office, with hard limits and audit-ready records by default.
Book a demo to see how the same multi-outlet expense management setup used by Swish can work for your quick commerce operation, cloud kitchens or delivery network, or write to us at team@cashbook.in.
