Skip to main content
GullySystem

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.

Rate per kilo or piece

Loose sweets such as kaju barfi and soan papdi carry a rate per kilo. Counted sweets such as laddu carry a rate per piece. The entry says which one applies. Nobody weighs a piece item.

Tray size and yield

A tray is the unit the kitchen cooks and the case holds. The entry records the number of kilos or pieces in one tray. Dispatch, cooking and shelf life all count in trays. One size is fixed here.

Shelf life of each sweet

Milk sweets spoil sooner than dry ones, so each entry carries its own shelf life. Each batch date is measured against it. The case then shows what is fresh and what is near its limit.

Recipe of raw materials

The recipe lists milk, khoya, sugar, ghee, nuts and packing material with the quantity for one batch. Cost per kilo is worked out from it. When a purchase price changes, the cost of every sweet using that material moves too.

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.

The ghee delivery arrives

The clerk enters the new ghee price. Every sweet whose recipe uses ghee shows a new cost per kilo straight away. The owner opens the list and sees which rates now sit too close to cost.

The owner revises the board

Kaju barfi gets a higher rate per kilo while jalebi stays exactly where it was yesterday. The new rate applies at once. Billing follows it, and nobody keys a price from memory at the till.

The cook starts a festival sweet

The head cook wants a new sweet in the case before the festival season. The manager adds the item, enters the tray size and shelf life, and writes the recipe from the cook’s quantities. Billing can then begin.

The evening cost check

At close the owner sets the rate on each sweet beside its cost per kilo. Any sweet priced below cost is easy to spot. Sometimes the answer is a new rate. Sometimes it is a cheaper recipe.

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.

For the owner setting margins

The owner and shop manager read cost per kilo beside the rate for every sweet on the list. Dearer sugar thins the margin. From there they decide which rates to lift before the next festival.

For counter staff at the case

Counter staff see the item name, the rate per kilo or piece and whether it is sold by weight. The recipe is not their concern. Nobody has to recall a rate from memory. Festival items sit in the same list as everyday sweets.

For the head cook in the kitchen

The head cook opens the recipe for the sweet being cooked and reads the quantity of each raw material for one batch. Tray size tells the cook the number of trays a batch fills. Selling price is not the cook’s concern.

For store and buying staff

Store staff read the recipes to see which raw materials a sweet draws and in what quantity. When a purchase price is entered, the cost per kilo of every sweet using it changes. Buying staff watch that change.

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.

Recipe quantity per batch or per kilo

Cooks speak in batches. Costs are read per kilo. Decide whether each recipe is written for one full batch or for one kilo of finished sweet. The tray size and the yield must then agree with it.

Festival range beside everyday sweets

Seasonal sweets can sit in the same list as the daily range or in a separate group. Decide which one suits the counter. A separate group keeps the counter screen short in a quiet month. Mixed lists mean fewer places to look.

Who signs off a new rate per kilo

A wrong rate costs money on every sale. Name who may revise a rate per kilo and whether the manager must approve it. Say whether a festival rate is set in advance or on the day.

How a sweet is retired from the list

Some sweets are made only for one season. Decide what happens to an entry once the season ends. It can stay for next year, be hidden from the counter, or be removed. Past bills must still show it.

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.

FAQ

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.

Where it fits

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 Billing

Festival and wedding advance orders

Bulk orders keep their date, advance and balance, and the kitchen sees what is due each day.

Order Management

Kitchen production plan

Trays to cook are set from sales history, the order book and festival dates.

Production Planning
Talk to us

Tell 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

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. 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