Nepal's restaurant industry has transformed dramatically over the past decade. From the dal bhat bhattis of Thamel serving budget trekkers to specialty coffee shops in Jhamsikhel, from family dhabas in Pokhara Lakeside to modern cloud kitchens in Kathmandu, the range of food businesses has never been wider — or more competitive.
What hasn't kept pace with this growth is business management. Many Nepal restaurant owners who are excellent cooks or hosts struggle with the operational side: tracking daily revenue, managing food costs, handling staff payroll, preventing cash leakage, and understanding which items are actually making them money. This guide covers the complete restaurant management cycle from opening to closing count — practically, for a real Nepal restaurant owner.
The Restaurant Business Is Fundamentally Different
Running a restaurant is operationally more complex than running a retail shop, for three specific reasons:
Perishable inventory: Unused food is waste. Unlike a hardware shop that can hold unsold stock indefinitely, a restaurant's unsold preparation is a daily loss. Food cost management is therefore more urgent and more dynamic than inventory management in retail.
Real-time demand: Customer flow varies dramatically by time of day and day of week. A restaurant that serves 100 covers on Saturday serves 15 on Tuesday. Staffing and preparation must anticipate demand that cannot be perfectly predicted.
High transaction volume, small amounts: A restaurant might process 80-150 individual transactions per day, each relatively small. Cash handling at this volume creates significant error and theft risk without proper systems.
The Daily Operation Cycle
Morning opening: Setting up for success
The first 30-60 minutes of your restaurant's day determine how smoothly everything that follows will go.
Cash float count: Count your opening cash float and record the amount. This is your baseline for the day's cash reconciliation. If your float is NPR 5,000 at opening and NPR 7,200 at closing with NPR 23,000 in recorded sales, NPR 21,200 should have been deposited or secured — a simple check that catches discrepancies daily rather than monthly.
Prep briefing: Before service begins, brief your kitchen on the day's menu, any items being offered as specials, and any items that are unavailable. Your front-of-house staff need this information so they never promise customers a dish that isn't available.
Stock check: Check key ingredients against your expected service volume. If you expect 50 momos orders and you have 30 portions prepped, either prep more or flag momo as limited quantity. Nothing damages a customer experience faster than "sorry, that's finished" — especially if it's finished before dinner service has ended.
Table and station setup: Ensure tables are clean and set, condiments are full, and each service station has what it needs. Customers notice when tables are dirty or napkins run out mid-service.
During service: The revenue engine
The service period is where your revenue is made and where most operational errors occur. The key discipline: every order and every payment goes through your POS. No exceptions.
Order recording: When a customer orders, it goes in the POS immediately — not "I'll put it in later." Later never happens, or happens inaccurately. The order record serves multiple purposes: it's the kitchen ticket, the basis for the bill, and your inventory deduction trigger.
Payment processing: When the bill is presented and payment is made, record the payment method in the POS — cash, eSewa, Khalti, FonePay, or khata. For split payments (part cash, part digital), both amounts must be recorded correctly. This matters for your end-of-day reconciliation: if you recorded a NPR 1,200 bill as full cash but the customer paid NPR 800 cash and NPR 400 via eSewa, your cash count will be NPR 400 short and you won't understand why.
Table management: For sit-down restaurants, know which table is occupied, for how long, and what they've ordered. A table that's been occupied for 2+ hours and hasn't ordered anything additional may be ready to leave — an unoccupied table costs you revenue every minute it's unavailable to new customers during peak hours.
Kitchen management during service
Order flow: In a busy restaurant, orders back up. A kitchen system — even just a clip on the wall for paper tickets — ensures orders are prepared in sequence and nothing is forgotten. For higher-volume restaurants, a small monitor or kitchen display is worth the investment.
Quality control: Outgoing dishes should be checked visually before reaching the customer — correct dish, correct portion, correct presentation. A dish returned from a customer because it's wrong wastes kitchen time, delays service at that table, and creates a negative experience that stays in the customer's memory.
Staff communication: Regular communication between front-of-house and kitchen about estimated wait times prevents the frustration of customers feeling ignored. "Around 10-15 minutes" is better than silence, even if it's the same actual wait.
End of day: The closing count
This is the most important financial process in a restaurant's day. Done correctly, it takes 20-30 minutes. Done incorrectly or skipped, discrepancies accumulate into large unexplained gaps by month-end.
POS closing report: Print or view your day's sales summary — total transactions, total revenue, and breakdown by payment method. This tells you: "Today, I should have NPR 18,400 in cash, NPR 7,200 in eSewa, and NPR 3,600 in Khalti."
Cash count: Count all cash in your till, subtract the opening float. The result should match the POS's reported cash sales. A NPR 0-100 discrepancy is rounding and acceptable. A larger discrepancy requires investigation before you close for the night.
Digital payment verification: Check your eSewa merchant app and Khalti merchant app for the day's receipts. They should match your POS records. If the POS shows NPR 7,200 in eSewa but your eSewa app shows NPR 6,900, you have a NPR 300 discrepancy to trace.
Cash deposit or secure storage: Never leave large amounts of cash in your restaurant overnight. Either deposit in the bank (if near closing time for deposit) or secure in a safe. Decide on a daily cash-up process and follow it consistently.
Food Cost Management: The Most Important Number
Nepal restaurants typically have food costs of 28-40% of revenue. If your food cost percentage is above 45%, you are losing money on the food itself — and all other costs come after that. Understanding and managing food cost is the most important financial discipline for any restaurant owner.
Calculating your food cost
Food cost percentage = (Cost of ingredients used ÷ Revenue from food) × 100
For a simple example: If your restaurant's dal bhat costs NPR 120 in ingredients and you sell it for NPR 350, the food cost percentage for that dish is 34%.
For the restaurant overall: if you spend NPR 1,50,000 on ingredients in a month and your food revenue is NPR 4,50,000, your food cost percentage is 33%. This is healthy.
Why food cost varies
- Waste: Ingredients prepped but not used (vegetable trimmings, over-preparation of perishables)
- Incorrect portioning: Staff serving larger portions than your recipe specifies
- Menu pricing errors: Some dishes priced below their actual ingredient cost
- Ingredient price increases not reflected in menu prices
Managing food cost
Standard recipes with specified portions are the foundation of food cost control. If your dal bhat recipe calls for 150g of dal, every portion should use 150g — not "a scoop" that varies between 130g and 180g depending on the cook's mood.
Monthly menu profitability analysis: for each item, calculate the food cost percentage. Items above 45% food cost need either a price increase or recipe adjustment. Items with high food cost and low sales volume are candidates for removal — they're tying up costly ingredients with minimal revenue contribution.
Staff Management in Nepal Restaurants
Restaurant staff management in Nepal involves the standard payroll obligations (SSF, TDS, Labour Act) plus the specific challenges of shift work, tip handling, and the high turnover common in the hospitality sector.
Shift scheduling
Match staffing levels to your actual demand pattern. If you're quiet on Tuesday mornings, you don't need the same staffing as Saturday evenings. Over-staffing quiet periods wastes payroll; under-staffing peak periods destroys customer experience and staff morale simultaneously.
Tip handling
If your restaurant receives tips (more common in tourist-facing restaurants in Thamel, Lakeside, etc.), establish a clear policy: all tips pooled and shared equally among service staff, or kept by the server who earned it. Document this in your staff agreements. Inconsistent tip handling is a major source of staff conflict.
Staff meals
Nepal's Labour Act provides for two meals per day for restaurant workers. This is a Labour Act entitlement, not an optional benefit. Factor staff meal costs into your food cost calculations — they are a real ingredient cost even if internal.
Digital Payments and Restaurant Billing
Nepal's restaurant customers increasingly prefer digital payments, especially in urban areas and among younger demographics. eSewa and Khalti QR codes at the counter are essential for urban restaurants. For high-end restaurants, consider table QR codes that allow customers to review the bill on their phone before paying — this reduces billing disputes significantly.
For catering and corporate orders, accept bank transfers via FonePay and issue proper VAT invoices. Corporate clients specifically require VAT invoices to claim expenses — if you can't provide them, you lose corporate business.
Frequently Asked Questions
Q: How do I handle a customer who claims they were overcharged?
A: With a POS, pull up their order immediately. Show them the itemised bill on screen. If there's a genuine error, correct it immediately and apologise sincerely. If the bill is correct, show them calmly — "here are the items, here are the prices." Having a digital record that you can show the customer in real-time is far better than debating from memory. Don't argue; show.
Q: My food costs are high but I'm not sure where the excess is going. How do I investigate?
A: Implement portion scales for one week on your highest-cost dishes. Weigh every portion going out. Compare actual portions to recipe specifications. In most restaurants where food cost creep is unexplained, over-portioning is the primary cause — staff serving generously without realising the cost impact. Seeing the actual weight often surprises the cook who thought they were being approximately right.
Q: How do I handle a day when sales are very different from expected — say, a festival day when we're overwhelmed?
A: Post-event, do a complete reconciliation before the following day. Festival days with high volume often result in recording errors — rushed transactions, split bills that weren't captured correctly. A next-day review of your POS data against your cash and digital payment receipts catches these while the day is still fresh in everyone's memory.
Q: Do I need accounting software specifically for restaurants, or does a general POS work?
A: For most Nepal restaurants under NPR 3 lakh monthly revenue with 1-2 service locations, a general POS handles daily needs. Restaurant-specific features (kitchen display systems, table management, recipe-level ingredient tracking) add value at higher volume and are worth considering once you're stable and growing. Don't over-invest in complexity before you need it.
Q: How do I manage a restaurant that is also doing home delivery?
A: Delivery adds operational complexity: order taking (phone/WhatsApp), packing, delivery management, and collection. Track delivery orders separately in your POS so you can see delivery vs. dine-in revenue. Consider adding delivery charges (NPR 50-100 for local area) to cover the cost. For food packaging, standardise so staff know exactly what to use for each item — reduces errors and waste.
Q: I suspect staff are giving free meals to friends. How do I address this?
A: Establish a clear policy: every item going out of the kitchen, including staff meals and any complimentary items, goes through the POS as a zero-value entry. This creates a record. When you review your daily POS report and see complimentary items, you can verify they were authorised. The existence of the system — even more than the enforcement — reduces the behaviour. Staff who know every item is tracked are less likely to help themselves.
Q: Should I use separate bank accounts for the restaurant business?
A: Absolutely. Mixing personal and business finances is one of the most common small business mistakes in Nepal. A separate business current account makes your income and expense tracking clean, makes reconciliation straightforward, and makes year-end accounting dramatically simpler. Opening a business current account requires your PAN and business registration — a one-time effort that pays back every month thereafter.
Restaurant management is hard work. The successful Nepal restaurant owners who've built loyal followings and sustainable businesses share a common trait: they treat the business side with the same care and attention they give the food. Great food gets customers in the door the first time. Great operations — fair prices, consistent service, clean accounts, reliable staff management — keeps them coming back. Both matter equally.