In this guide 6 sections
Take every cake order on one form with flavour, weight, egg or eggless, message, design photo, slot and advance. Make that record visible at the counter and in the kitchen. Read it back to the customer before they leave. Then mark it baked, decorated and handed over, so nothing depends on a paper slip.
Decide what every order must carry
Most missed cakes trace back to a missing detail. The counter wrote the flavour but not the weight, or the message but not the spelling. Fix the list of fields first, before any tool.
Make every field compulsory. A blank slot or a missing photo should stop the order from being saved. Read the order back to the customer and send a copy to their phone.
- Flavour, weight and shape
- Egg or eggless
- Message, with spelling confirmed
- Design photo the customer approved
- Pickup or delivery slot and address
- Advance taken and balance due
One order book for every outlet and the kitchen
A bakery with two outlets often runs two order books. An order taken at one counter for pickup at the other is the one that gets lost. The design photo reaches a decorator who is off that day.
Keep a single order book that every outlet and the kitchen read. The kitchen sees what is due today and tomorrow. The counter can answer a caller asking about status without phoning the kitchen.
Advances, changes and cancellations
Record the advance on the order itself, with the payment mode. The balance due then shows at pickup. Nobody has to search a cash book.
Customers change flavours and messages. Write each change on the order with the date and who took it, and send the kitchen the revised version. Decide your cancellation rule in advance and tell it to the customer at booking. A rule told late starts an argument.
Feeding cake orders into tomorrow’s bake
Confirmed cake orders belong in the next day’s plan, alongside outlet indents and usual counter quantities. The head baker should see them on one list. Then fresh cream, chocolate and boards can be checked against the plan the evening before.
A late order after the plan is closed needs a clear rule. Either the kitchen accepts it with a later slot, or the counter declines it. Write the cut-off down.
Pickup, delivery and the closing check
Mark each order as baked, decorated and handed over. At closing, the counter reads tomorrow’s orders once more and checks every photo has reached the kitchen. This short check catches the most common miss.
Complaints belong on the order too. A pattern of complaints about one design or one flavour shows up only when they are recorded against the order. Read them monthly.
- Orders due tomorrow, with photos attached
- Advances recorded and balances due
- Changes sent to the kitchen
- Complaints logged against the order
Cake order card template
A one-page card with every compulsory field: flavour, weight, egg or eggless, message, photo reference, slot, advance and balance. Add tick boxes for baked, decorated and handed over. Use it on paper for a week to test the fields before moving to software.
Open a blank worksheet to printQuestions owners ask
Can delivery platform orders join the same order book automatically?
Not automatically. In GullySystem’s Bakery Management System, Swiggy and Zomato orders are entered at the counter like any other order, so the kitchen still works from one list.
Does the kitchen get a printed order ticket?
No. There is no kitchen order ticket printing in that system. Bakers work from the production plan and the cake list on screen.
How much advance should a bakery take?
That is your call, and it often varies with the design. Whatever you decide, record the amount on the order and show the balance at pickup.
Is a notebook enough for a single counter?
Often, yes. With one counter and a few custom cakes a week, a bound order book with carbon copies can work. Outlets and a central kitchen change the answer.