Skip to main content
GullySystem

Planning what the sweet kitchen cooks each day

Each morning the head cook needs to know the number of trays of each sweet to make. The plan reads past sales, the order book and the festival calendar, and sets the day’s cooking. As batches finish, the cook records the real yield, so tomorrow’s plan starts from facts.

Trays, batches and yields in the cook’s plan

Each sweet gets a line and a number. Behind that number sit the tray size, the batch size and the expected yield. The cook adds what actually came out of the pan. The gap between the two is the next lesson.

Trays to cook per sweet

Each sweet shows the number of trays to cook today. The figure starts from past sales and is raised for orders due and festival dates. Final say sits with the kitchen. Changes are kept with the plan.

Demand drivers behind each figure

A figure carries its reasons, which are sales of that sweet, orders in the book and a festival marker. Why a sweet is up or down is visible. Holiday weeks stand out in the history.

Batch marked done

When a batch comes off the stove, the cook marks it done and enters the tray count. The batch gets a date. Shelf life starts from that date. It then moves to the case or the cold room.

Real yield against expected

Real yield of each batch is recorded next to the expected quantity from the recipe. A short batch shows at once. Repeated short batches point to a recipe or a pan to check. Missing raw material is traced.

A cook’s morning from plan to last batch

The kitchen starts before the shop opens. Milk is on the stove while the counter is still being cleaned. It has to be ready before the first pan, because a wrong number shows only when a case is empty or full.

The manager opens the plan

Each morning the manager opens the plan with yesterday’s sales, orders due today and tomorrow, and the festival calendar beside it. A quick scan shows which sweets need extra trays. The kitchen joins. Both agree the numbers.

Raw materials drawn for a batch

Before a batch starts, the store issues milk, sugar, ghee and nuts against its recipe. Any extra draw is noted with a reason. The clerk and the cook both see the quantities. Nothing leaves the store unrecorded.

Pans, trays and timing

Which batch goes first is the cook’s decision. Sweets for the earliest pickup and the festival orders come off the stove before the shop opens. Fast sellers are cooked in smaller rounds through the day. Still, it is only a guide.

End of day yield check

After the last batch, the cook reads the yield figures. Any sweet that came out short is noted. One left unsold in the case is noted too. Both feed tomorrow’s numbers. Adjusting is quick with figures in front of the cook.

Who cooks, who plans and who reads the totals

One plan is shared between the kitchen and the shop floor. The cook acts on trays, the manager on orders, the buyer on raw materials and the owner on waste. Each opens the same plan for a different decision. Roles differ. The page is shared.

For the head cook and kitchen

The head cook opens the day’s plan, sees which batches to cook first and records what came out of the pan. The screen speaks in trays. Money does not clutter it. Batch order is the cook’s call.

For the manager owning the plan

The manager reads the orders due and compares them with the trays proposed. A date with a heavy order book goes to the owner for a decision. Speaking to the family is also the manager’s job. That call is short.

For store staff issuing material

Store staff issue raw material against the recipe for each batch. A draw above the recipe is recorded with a reason. At close, usage is read against the recipe. Gaps show where stock went. The buyer reads the same report.

For the owner reading waste

The owner reads trays cooked against trays sold, with discards logged by reason. Overcooking the same sweet again and again is easy to spot. Cutting it is the owner’s decision. A festival rise can be judged the same way.

Production numbers to agree before cooking by plan

A plan works only if the kitchen trusts it. The owner and the head cook decide how it is built before it replaces habit. Those choices set how far the cook can overrule it. Settle them early.

How far back sales history reaches

Decide the stretch of past sales the plan reads for each sweet. A short stretch follows recent trade closely. A long one smooths the ups and downs. Festival sweets need a look at the same season last year.

Cook’s right to overrule the figures

The head cook knows what the data does not, such as a power cut or a wet day. Decide whether the cook may change a number freely or must note a reason. Either way the change is kept.

Buffer trays for walk-in demand

Orders are known but walk-in sales are not. Decide the number of extra trays to cook above the order book. Too little runs a case dry. Too much feeds the discard log. Balance is chosen sweet by sweet.

Which sweets the plan leaves alone

A few sweets are made to the cook’s judgement, such as a special of the day. Decide which sweets sit outside the plan. Say how their batches are still recorded. They must reach the case with a made-on date.

From plan to stove, store and case

It sits between sales and stores. It reads sales and orders, asks the store for material and gives each finished batch a date. Whatever it plans for, the store and the counter read the same numbers. A change to the order book changes the plan the same day.

  • Counter weighing and billing supplies past sales
  • Festival and wedding advance orders supply the order book
  • Raw material stock and purchases receives the shopping list
  • Shelf life, expiry and wastage stamps each finished batch
  • Branches and central kitchen receive trays against dispatch lists

Limits of the production plan

Numbers come from sales, orders and dates. It does not know a power cut or a cook who is off sick. Treat it as a guide. Recipes and food safety practice are set by the shop, not by the plan. A shop that makes one or two sweets in the same quantity every day may manage with a whiteboard.

FAQ

Frequently asked questions

What does the plan use to set trays?

It reads past sales of each sweet, the orders due in the book and the festival dates you enter. Each figure can be changed on sight. The result is a starting point. Nothing is forced on the kitchen.

Can the cook record less than the planned yield?

Yes, the cook records the real yield, whatever it was. The recipe gives the expected quantity. The difference is kept against that batch. Gaps are read sweet by sweet. A pattern of short pans is worth a visit.

What if a festival order arrives late?

The order enters the book at once. Its trays join the plan. The new total is read before the next batch. Whether the kitchen can add it is for the manager to decide. Capacity is not unlimited.

Does the plan buy the raw materials?

It does not buy anything. It shows the quantity of milk, khoya, sugar and ghee the trays will use. A purchase order can be raised from that total. A person still reviews and sends it.

How are festival days treated in the plan?

You enter the festival dates your kitchen plans around. Those days are marked in the plan. Trays for seasonal sweets are raised on them. A rise is judged against past sales. The festival range gets its own rows.

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