Guide

Selling by plate, KG and deg: setting up a POS for a biryani or catering business

Units, prices, bookings and cash control for food businesses that do not sell by the plate alone.

DeviSofts Engineering Team Updated 2 November 2026 8 min read

A biryani or pakwan centre does not sell like a café. The same pot of biryani leaves the kitchen as plates, as half plates, by the KG, by the amount a customer wants to spend and as whole degs booked weeks ahead. A POS that only understands "one item, one price" pushes all of that onto the cashier's memory. Here is how to set one up so the system does the arithmetic instead.

Start with your units, not your menu

Before entering a single price, write down every way each dish is sold. For a typical biryani that might be:

UnitExampleWhere it is used
Plate (full / half)Single boti, double boti, half plateTables and parcels
KG0.5, 1, 1.5 or 2 KGCounter and parcels
KG by amount"Rs 500 worth"Counter
DegDeg sizes by the KG of riceBookings and catering
Per headCatering menusBookings and catering
Piece / eachRaita, salad, drinks, extra botiEverywhere

Each of these should be a variant of the same item, not a separate item. That keeps one dish in one place for reports and recipes, while each variant carries its own price.

KG by weight and KG by amount

Customers ask for weight ("one KG") or for money ("five hundred rupees of biryani"). The counter should handle both. Selling by amount simply divides by the KG price: at Rs 1,200 per KG, a Rs 500 order is about 0.42 KG. The bill should print both the weight and the amount, so the customer and the person packing the order see the same thing. Quick buttons for the common weights (0.5, 1, 1.5, 2 KG) save a lot of typing during a rush.

Extras and "without boti"

Extras change the price (extra boti, extra raita); notes do not (leg piece, chest piece, less spicy, pack separately). Keep them apart, and put limits on paid extras. "Without boti" is not a discount: it is a different, cheaper item (plain rice with aloo, for example). Set it up as a switch that changes the line to that item at its own price, so the kitchen and the stock both see what was really sold.

Screens for waiters who may not read

Many waiters in busy food businesses are fast and reliable but not comfortable reading menus on a phone. Design for them: pictures for categories and dishes, big numbers for tables and prices, colours for status (free, in the kitchen, bill asked) and taps instead of typing. A good test is to hand a phone to a new waiter with no training and watch the first order.

Deg and catering bookings

Bookings are where a notebook fails first. Record each one with the booking type (deg pickup, deg delivery, cooking the customer's own ingredients, catering, a niyaz or other occasion), date and time, venue, number of guests, items per deg or per head, services, notes, the advance and the balance.

  1. Inquiry and quotation. Price the items and services, and print or share a quotation.
  2. Confirmation with advance. Set a minimum advance percentage and take it against a receipt.
  3. Kitchen planning. A calendar shows degs per day and warns when a time slot is already at the kitchen's capacity.
  4. Cooking and delivery. The daily production sheet lists the degs to cook today and tomorrow, from bookings and pre-orders.
  5. Settlement. Take the balance, print the invoice and close the booking.
Servings per deg: set how many people each deg size serves at your portion size. The booking screen can then suggest the number of degs from the guest count, instead of the customer guessing.

Pots (bartan) go out; make sure they come back

When degs leave in your pots, give every pot a number and record it against the booking with a deposit and a due date. On return, release the deposit or charge for damage. A short list of "pots out and overdue" pays for itself within a season.

Khata without the notebook

Regular customers and offices buy on credit. Keep each customer by phone number, with a credit limit, every credit sale and payment, and the running balance. When the cashier picks "khata" as the payment method, the customer's ledger is updated at the same moment.

Cash, shifts and the day close

Open every shift with the cash in the drawer and close it with a count. Counting note by note (5,000, 1,000, 500 and so on) is faster and more accurate than a single total, and the shortage or excess should show while counting. Record expenses as they happen (gas, electricity, daily wages, vegetables) so the day-close report shows sales by unit type and payment method, expenses, and expected against counted cash. Sending that summary to the owner's phone every night keeps everyone honest.

Recipes, stock and real profit

Write one recipe per deg: a 10 KG chicken biryani deg needs so much rice, chicken, ghee, spices and gas. Plate and KG recipes can be derived from it. When a bill is paid, the POS deducts raw material; with purchase rates, it can show the real cost and profit of each item. Start simple, refine the quantities over a few weeks, and do a stock count with a manager's approval at month end.

Keep it working without internet

Rush hour and wedding season cannot wait for a slow connection. Run the POS on a PC in the shop, with the counter and waiters' phones on the shop's own network, and use the internet only for extras such as sending summaries or remote viewing. Add nightly backups with a copy off that PC.

Set-up checklist

  • Every dish entered once, with plate, half, KG, deg and piece variants.
  • KG quick buttons and KG-by-amount at the counter.
  • Paid extras with limits; free notes; "without boti" as its own item.
  • Picture-based waiter screens, tested on a new waiter.
  • Booking types, minimum advance, servings per deg and kitchen capacity per slot.
  • Numbered pots with deposits.
  • Khata customers by phone number with limits.
  • Shift float, note-by-note close and expense categories.
  • One recipe per deg; stock count at month end.
  • Runs offline on the shop network; nightly backup with an off-PC copy.

We built our biryani & catering POS around exactly this list, with a working pakwan and biryani centre. For a full-service restaurant with a kitchen display and recipe costing, see our restaurant POS.

Questions

Quick answers

How does selling by amount work for KG items?
The cashier types the amount the customer wants to spend and the POS works out the weight from the KG price. At Rs 1,200 per KG, a Rs 500 order is about 0.42 KG. The bill shows both the weight and the amount.
How many people does one deg serve?
It depends on the deg size and your portion size, so it should be a setting rather than a guess. Enter the servings for each deg size once, and the booking screen can suggest how many degs a booking needs from the number of guests.
Should a biryani shop POS work offline?
Yes. Rush hours and wedding-season bookings cannot wait for the internet. A POS that runs on a PC in the shop and serves the counter and waiters over the shop's own network keeps selling when the connection is down.
DeviBot
Usually replies in a few seconds
Hey there 👋 I'm DeviBot. What's your name?