A restaurant counter has three different transactions pretending to be one: a table that pays at the end, a takeaway that pays first, and a delivery order that someone else collects for.
Billing them identically is why most restaurant reports are useless.
Keep the three apart
- Dine-in - open the bill, add as they order, settle at the end.
- Takeaway - settle immediately.
- Delivery - settle against the aggregator or the customer, and record which.
Once they are separated, the reports start answering real questions: which channel is growing, which one carries the margin, and what the kitchen should be staffed for.
Beautiful GST invoices with your signature and stamp, quotations to credit notes, inventory, UPI collection and 30+ reports.
Start free See the demoBill by item, always
It is tempting to punch a total. Do not. Item-wise billing is the only way to get:
- A menu ranked by what actually sells.
- Wastage visible against sales.
- GST that stands up because it is derived from items.
- A real answer on which dish to remove.
How MizUp Finance handles it
MizUp Finance produces GST bills in seconds with the right tax treatment, holds items with rates and units, moves inventory as you bill, supports UPI collection on the bill, and provides over thirty reports including item-wise and daily sales.
Customers who share a number become records shared with MizUp CRM, so a Sunday offer through MizUp CLM goes to people who have actually eaten with you.
What it costs
Free plan available; paid plans from Rs 208 per month. See Finance pricing.
Where to start
Bill item-wise for two weeks and read the item report before changing anything on the menu. Explore MizUp Finance.
Where restaurants usually go wrong
- Punching a total instead of items. It is the single decision that makes every later report useless, and it is made a hundred times a day.
- Dine-in, takeaway and delivery billed identically. Three different margins and often different tax treatment, reported as one number.
- Payment at a counter rather than the table. A UPI QR on the bill removes a queue that costs you the last table turn of the evening.
- Wastage tracked separately, if at all. Wastage only means something against item-wise sales. Alone it is a number nobody acts on.
- Menu decisions by opinion. Everyone has a favourite dish. The item report has no favourites.
- No record of regulars. A restaurant with two hundred regulars and no way to reach them is leaving its most reliable revenue to chance.
A realistic first thirty days
| Week | Focus | What good looks like |
|---|---|---|
| Week 1 | Menu as items | Load the menu with rates and tax treatment. This is the foundation for everything else. |
| Week 2 | Item-wise billing | Every bill by item. Expect resistance for three days; it stops once the first report circulates. |
| Week 3 | Channel separation | Dine-in, takeaway and delivery tagged separately on every bill. |
| Week 4 | Read the report | Item-wise sales for the month. Remove nothing yet; just look at it. |
Wait a full month before changing the menu. Two weeks of data in a restaurant is weather, not climate.
The numbers worth watching
| Metric | Why it matters | How to read it |
|---|---|---|
| Item-wise sales | The only honest input to a menu decision | Weekly, ranked, for a month before acting. |
| Revenue by channel | Which part of the business is actually growing | Dine-in, takeaway and delivery kept apart. |
| Average bill value by channel | Where the margin is | Tracked monthly. |
| Table turns per evening | Whether payment friction is costing you | Compare before and after table-side UPI. |
| Repeat customers | The quiet foundation of a neighbourhood restaurant | Customers with two or more bills in sixty days. |
Menus improve by subtraction
The most common outcome of a month of item-wise data is not a new dish. It is the realisation that eleven items account for almost nothing, occupy kitchen attention, require ingredients that spoil, and exist because someone liked them two years ago.
Removing them is the highest-return decision most independent restaurants can make, and it is almost impossible to make without data because every item has an advocate.
The second common realisation concerns channels. Delivery volume often looks impressive and contributes far less margin than the same revenue from a table, once commission and packaging are counted. Separating them on the bill is what makes that visible.
Neither insight requires analytics software. It requires billing by item for one month and then reading the report.
How this fits with the rest of your stack
A restaurant has a counter, a kitchen and a staff roster, and the software conversation usually only covers the first.
On MizUp, Finance handles item-wise billing with the right GST treatment, stock movement, UPI collection at the table and item-wise reports. BMS runs shifts, attendance and payroll for kitchen and floor staff, which in a restaurant is the second-largest cost after food.
CLM can reach regulars on the official WhatsApp Business API against the customer record built from bills, which is a far better list than any table-tent sign-up sheet.
Getting staff to bill by item
The resistance to item-wise billing is real and it is not laziness. During a rush, punching a total takes four seconds and selecting six items takes twenty, and the person doing it is watching a queue form.
Three things make it work. Put the twenty fastest-moving items on the first screen so most bills need no searching. Let the kitchen order and the bill be the same action rather than two. And show the staff the first month's report, because people who see what their data produced start protecting its accuracy.
What does not work is enforcement. A manager checking bills creates resentment and a habit of punching totals when the manager is not looking, which is worse than no data because it is data that looks complete.
Restaurants that get this right usually did it by making the fast path the accurate path, not by insisting.
Related reading
- How to create an invoice
- GST invoice format under rule 46
- Profit margin versus markup
- Break-even point formula
Frequently asked questions
What does a restaurant need beyond a normal bill?
Separation between dine-in, takeaway and delivery, because the tax treatment and the margins differ, and you want to see them apart in reports.
Can it take UPI at the table?
Yes - a UPI QR on the bill means payment happens where the customer is sitting rather than at a counter queue.
How do you handle item-wise sales analysis?
Bill by item rather than by amount. It takes slightly longer at the counter and gives you the only report that improves a menu.
Does it handle GST correctly for restaurants?
Yes, with the applicable rate and the correct split on the invoice, and GST summaries from the same data.
Is it suitable for a small cafe?
Yes. The free plan covers basic invoicing; paid plans start at Rs 208 per month.
