Sweet items, recipes and rates for the mithai counter
Every sweet the shop sells sits here as one entry. It holds the rate per kilo or piece, the tray size, the shelf life and a recipe of raw materials. The till reads the rate. The cook reads the recipe. Whoever owns the shop reads a cost per kilo that moves when milk, sugar or ghee is bought at a new price.
Fields behind every sweet on the rate board
A sweet entry carries the rate per kilo or piece, the tray size, the shelf life and a recipe of raw materials. The till needs the first, the cook needs the last, and the owner needs both to know what a kilo of barfi really costs. Nothing else is typed twice.
A week of ghee prices and sweet rates
Ghee costs more on delivery day, and the old price still hangs on the case board. Margin is the first thing lost. A sweet entry that moves with the purchase keeps that margin visible. The same record is read at the store, the stove and the counter.
Who reads the rate and who reads the recipe
The rate and the recipe are read by different people. Each role opens the part of the entry it works from. Cost and margin matter to the owner. The cook needs quantities, and the counter needs the price.
Settling rates and recipes before the first bill
The sweet list is easy to type and hard to correct once the counter relies on it. A few choices made on day one decide how clean the cost figures stay. Settle them with the head cook.
How sweet entries feed billing, cooking and buying
The sweet list is the source the rest of the product reads from. Billing takes the rate, the kitchen plan takes the tray size, and purchasing takes the recipe quantities. A corrected entry shows the correction on every screen that reads it. Nothing is copied by hand.
- Counter weighing and billing takes the rate per kilo
- Kitchen production plan reads tray size and yield
- Raw material stock and purchases receives the recipe quantities
- Gift boxes and assortments list pieces from this item list
- Shelf life, expiry and wastage reads each sweet’s limit
Limits of the rate and recipe list
The list holds your rates and your recipes. It does not decide them. Food safety practice, the wording on legal labels and the tax treatment of a sweet stay with the owner and an adviser. The cost per kilo is only as good as the recipe quantities the kitchen gives it. A shop with a handful of sweets and one rate board may find a laminated price sheet enough.
Frequently asked questions
How are sweets sold by the piece entered?
Each piece sweet is entered with a rate per piece and the number of pieces in a tray. Billing then goes by count instead of weight. Its cost still follows the recipe. Laddu and gulab jamun are common examples.
What happens to the cost when ghee gets dearer?
Enter the new purchase price for ghee. The cost per kilo of every sweet whose recipe uses ghee moves with it. Your selling rate does not change by itself, so the owner decides whether to raise it.
Can we keep festival sweets apart from everyday ones?
Yes, the festival range is added to the same list as the daily sweets, with its own rates and recipes. Grouping is agreed with your team at set-up. Past festival bills stay as they were printed.
Does it record the weight lost in cooking?
In the kitchen plan, the cook records the real yield of each batch. The expected quantity comes from the recipe. Comparing the two shows where weight is lost. What loss is acceptable is the shop’s own call.
Can the cost per kilo include packing material?
Packing material is a raw material like any other. Put it in a recipe if every kilo of that sweet uses it. Leave it out and charge it at the counter if only some do. Set this with your adviser.
How this feature fits the system.
Sweet Shop Management Software: the parts that work with this feature, the trades that use it and the ways to put it in place.
Counter weighing and billing
Weight, rate, packing and tax meet on one bill, printed at the counter in a festival queue.
Point of Sale BillingFestival and wedding advance orders
Bulk orders keep their date, advance and balance, and the kitchen sees what is due each day.
Order ManagementKitchen production plan
Trays to cook are set from sales history, the order book and festival dates.
Production PlanningTell us what you need.
Tell us what your team does today, where work gets stuck and what you want to change.
What happens after you share your requirements
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- Review the scope and commercial terms before deciding whether to proceed.
Start with your requirements
Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.
Share your requirements