Skip to main content
GullySystem

Central kitchen and branch outlets for sweets

One kitchen cooks and several counters sell. Trays are sent from the central kitchen to each outlet against a list, and each branch receives them against a count. Stock, sales and waste can be read for one branch or for all, so the owner sees one picture of the chain.

Dispatch lists, receipts and branch balances

A dispatch is a list of trays leaving the kitchen for one outlet on one day. The branch’s receipt is the same list, counted at the door. Where the two meet, any difference is the story. Each carries a date.

Branch request for trays

A branch manager asks for trays by sweet and quantity for the next day. The request sits on a list the kitchen can read, not on a phone call. Its plan decides how much can be met.

Dispatch list and van load

Each outlet gets a dispatch list from the kitchen, with the sweets, tray counts and batch dates. Counting out follows the list before loading on the van. The list travels with the trays. Nobody phones to check the load.

Receipt against the count

The branch counts what arrived and confirms it against the list. A short or damaged tray is entered with a reason. Selling starts after confirming. Any difference is seen in the kitchen at once. Both sides read one figure.

Branch stock, sales and waste

Figures are kept per outlet. Stock, sales and discards can be read for one branch or for all. A busy branch low on stock stands out beside a quiet one with trays going stale. Comparison is simple.

From the kitchen van to the evening count

Trays leave the central kitchen before the counters open. A late van or a short count changes what a branch can sell all day. The record has to travel with the trays, from the van to the evening count. Timing decides the day.

Branch managers request trays

At closing time a branch manager enters tomorrow’s request for each sweet. The request reflects what is left in the case and the orders due at that outlet. Every request is read together. Nothing is lost to a missed call.

The kitchen balances demand

The kitchen manager lays the requests beside the plan. One branch asks for more kaju barfi than the day’s cooking allows. The manager trims that request and favours the busier outlet. The decision is recorded. Branches see the reason.

Van loading and the late delivery

The van is loaded outlet by outlet. When it runs late, the branch sees the dispatch as on the way and not yet received. No branch sells a batch it has not counted. Its status reads the same in the kitchen.

Evening count at the outlet

At close, the branch counts what is left and logs what was discarded. Sales for the day are read against what was received. The owner reads that branch’s picture first, then the chain’s. A gap is traced to one counter.

Kitchen, outlet and owner views of the chain

A chain of outlets means several people watching the same trays from different places. Dispatch goes from the kitchen, receipt happens at the branch and comparison is the owner’s. Outlets read their own figures. The owner reads them all.

For branch managers at each outlet

Branch managers request trays, confirm each delivery, count what is left at close and see their own sales and waste. The screen is that outlet’s alone. Nobody reads another branch’s stock to do the job.

For the kitchen manager dispatching

The kitchen manager sees every request, the plan’s output and the dispatch lists being built. Each tray is ticked off against the list. Short batches are spotted before the van leaves. Phone calls shrink to exceptions.

For the owner comparing outlets

For one branch or for all, the owner reads stock, sales and waste. Heavy waste and weak sales at one branch are easy to spot. So is one that sells out early and under-orders. Both need a different fix.

For the head cook feeding the chain

The head cook cooks for several counters at once. The plan shows total trays by sweet, split by outlet. A cook who knows where each tray is going packs it in the right order for the van. Loading order follows the route.

Dispatch, receipt and branch choices before launch

A chain stays honest only if the kitchen and the outlets agree how a tray changes hands. These choices are about people before they are about software. Settle them with branch managers in the room.

Branch counts versus kitchen counts

Say a branch counts fewer trays than the kitchen sent. Who is right? Decide which figure stands and who looks into the gap, the kitchen manager or the branch manager. Set a cut-off for challenges so a count does not hang open.

Overnight stock a branch may hold

Some chains send each branch just enough for the day. Others keep a buffer at the outlet. Decide how much stock a branch holds overnight. Say whether leftovers go back to the kitchen. Sweets with a short shelf life need the tighter rule.

Which outlet sees the chain’s totals

Outlets see their own figures and the owner sees all. Decide whether branch managers may also read the chain’s totals. Some owners share totals to spark friendly rivalry. Others keep each outlet’s numbers private to that outlet.

Who covers a failed dispatch

A van breaks down or a batch is spoiled. Decide who tells the branch and who decides to cook again. Settle how the loss is booked. Waste in transit gets its own reason in the log.

How the central kitchen feeds every outlet

Branches sit at the end of a chain that starts in the kitchen plan. Each tray carries its batch date and its count from the pan to the outlet case. Sales at the outlet flow back to the plan. The whole chain is visible at once.

  • Kitchen production plan splits trays by outlet
  • Shelf life, expiry and wastage keeps batch dates on arrival
  • Counter weighing and billing reduces branch stock on each sale
  • Festival and wedding advance orders name the pickup outlet
  • Sweet items, recipes and rates give branches one rate list

Limits of central kitchen and branch stock

The system records dispatches, counts and sales. It does not drive the van, count a tray for the branch or decide what each outlet deserves. Lateness of the van is a logistics matter for the shop. Rent, staffing and local rules for each outlet stay with the owner and the adviser. A single shop with its own kitchen has no use for dispatch lists.

FAQ

Frequently asked questions

How does a branch confirm trays it received?

The branch counts the trays against the dispatch list and confirms each line. Short or damaged trays are entered with a reason. Confirmed stock alone joins the branch balance. Selling starts from a true figure.

Can the owner see one branch or all together?

Yes, stock, sales and waste can be read for one branch or for all. Each outlet sees its own figures. The view is the owner’s choice. Comparison needs no spreadsheet. A weak branch shows against a strong one.

What if a branch needs trays during the day?

Staff at the outlet enter a fresh request, and the kitchen sees it beside the plan. Whether the kitchen can spare more is a call for the kitchen manager. A top-up is a separate dispatch. Counting works the same way.

How are late or damaged deliveries recorded?

A late van keeps the dispatch in transit until the branch counts it. A damaged tray is entered with a reason at receipt. Both are visible in the kitchen. The cause of a gap is known without a phone call.

Do branches share one rate list?

All outlets read the same sweet entries and rates. A change to a rate per kilo is made once. It then applies at every counter. Needing a different rate at one branch is a set-up discussion. Raise it early.

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