Cake Order Form Checklist: What Every Cake Shop Should Capture
Learn what to include in a cake order form, from customer details and cake design to allergens, deposits, collection dates, payments and order confirmation.
Taking an order for a bespoke cake can look deceptively simple.
A customer walks into your shop or sends you a message saying they need a chocolate birthday cake for Saturday. They show you a picture from Instagram, tell you roughly how many people it needs to serve and ask how much it will cost.
Then the details start changing.
The customer decides they want vanilla instead of chocolate. Their daughter prefers lavender rather than pink. They send another photograph showing a completely different decoration. A week later, they call the shop and change the collection time. Somewhere in the original WhatsApp conversation, they also mentioned that one of the guests has a nut allergy.
By the time your decorator begins making the cake, the final specification could be spread across WhatsApp, Instagram, a handwritten order book, a payment receipt and the memory of whichever employee originally spoke to the customer.
That is where mistakes happen.
A good cake order form gives your bakery one reliable record of what has actually been ordered. It should tell your team who the customer is, what cake they want, when it is needed, what design has been agreed, whether there are important allergen requirements and how much has been paid.
For a growing cake shop, that order record can become much more than a piece of paperwork. It can form the foundation of your production planning, payments, customer communication and future repeat business.
Why a cake order needs more information than a normal retail sale
If someone walks into a bakery and buys a croissant, the transaction might take less than a minute. The customer chooses the product, pays and leaves.
A bespoke cake can have a customer journey lasting several weeks.
The initial enquiry might happen in August for a cake required in September. During that period, the bakery could have multiple conversations with the customer, collect a deposit, order a personalised topper, receive reference photographs, change the design and eventually collect the remaining payment.
That makes a bespoke cake closer to a small project than a simple retail transaction. The order form therefore needs to become the central record of that project.
Instead of employees asking, “Which pink cake was this?” or “Did this customer pay the deposit?”, the information should already be attached to the order.
The objective isn't to make ordering bureaucratic. In fact, the opposite is true. A properly structured order process should make life easier for both the customer and the bakery.
Start with accurate customer information
Every cake order should begin with the person placing it.
At minimum, that usually means recording the customer's name and an appropriate contact method, such as their mobile number or email address. If the cake is being delivered, you will naturally need the relevant delivery information as well.
It sounds basic, but small errors here can create surprisingly large problems. One incorrect digit in a telephone number could prevent a collection notification from reaching the customer. An incorrectly typed email address could mean the customer never receives their order confirmation.
It is also useful to give each cake order its own reference number. When you're processing ten orders a month, referring to “Sarah's blue cake” might seem sufficient. When the bakery processes hundreds of orders, a reference such as TLZ-1048 is far easier to use when discussing payments, changes, collections or complaints.
The date the order was placed is worth keeping too. Over time, that information can help you understand how far in advance customers typically book different types of cakes.
You should, however, resist the temptation to collect customer information simply because it might become useful one day. UK data-protection principles require personal information to be adequate, relevant and limited to what is necessary for the purpose for which it is being processed.
A better cake-order system therefore collects information with a reason behind it.
Record the occasion, not only the collection date
One of the most valuable pieces of information in a cake business is often overlooked: what is the cake actually for?
Consider a customer collecting a cake on 17 September. If your system records only the collection date, you know when your kitchen needs to have the cake ready. But perhaps the cake is for their daughter's birthday on 18 September.
Those are two different dates with two different purposes.
The collection date is operational information.
The birthday is customer relationship information.
Recording the occasion also gives your team useful context. A birthday cake, anniversary cake, graduation cake and corporate event cake may require different wording, presentation and communication.
It can also become valuable later.
If the customer has an appropriate relationship with your bakery and your marketing permissions allow it, remembering that the same birthday is approaching next year creates an opportunity for a genuinely useful reminder rather than a random promotional email.
That is why a good cake order form should ideally distinguish between the order date, collection date and occasion date rather than treating them as the same thing.
Describe the cake in enough detail that another decorator could make it
One of the best tests of a cake order form is simple:
Could another member of your team make the correct cake using only the information recorded on the order?
If the answer is no, the order probably isn't detailed enough.
The form should clearly capture the cake's size, shape, number of tiers where relevant, approximate servings, sponge flavour, filling and finish.
For example, instead of writing:
Chocolate birthday cake.
a good order record might say:
8-inch round chocolate sponge with chocolate ganache filling, finished with white buttercream.
That small difference removes a lot of ambiguity.
It is also useful to standardise common choices wherever possible. If your team types “Chocolate”, “Choc”, “Chocolate Cake” and “Choc Sponge” into different orders, your reporting later becomes unnecessarily messy.
Defined options for your regular sizes, flavours and fillings make both order taking and business analysis easier.
You can still include a free-text area for unusual requests, but your standard products should ideally use standard terminology.
Design details deserve their own section
The design is usually where bespoke cake orders become complicated.
Customers may describe colours differently. They may send several photographs. They may want the piping from one cake, the colours from another and the topper from a third.
Simply attaching three Pinterest screenshots and writing “similar to these” isn't enough.
Your order should explain what has actually been agreed.
For example:
White buttercream finish with lavender piping around the top and base, small gold balls, three butterfly decorations and a personalised gold acrylic topper.
That written description becomes extremely useful if there is later disagreement about what the customer requested.
Reference images are still valuable, but they should support the specification rather than replace it. If a customer sends several images, you might note that one is for the overall layout, another is only for the colour and a third demonstrates the topper style.
This also helps manage expectations. Handmade cakes are not mass-manufactured products and will naturally contain some variation. A reference photograph should therefore normally be treated as inspiration for the agreed design rather than an automatic promise to reproduce another baker's work exactly.
Always confirm personalised wording
A spelling error on a cake can turn an otherwise perfect order into a disappointed customer.
Names are particularly risky because employees may assume they know how a name is spelled.
Sophia could be Sofia.
Mohammed could be Muhammad.
Isabelle could be Isabel.
The safest process is simply to record exactly what the customer wants written on the cake and ask them to confirm it.
Instead of the baker interpreting a handwritten note that says “Happy Birthday Sophia 10”, the agreed wording could be clearly recorded as: Happy 10th Birthday Sophia.
The same applies to ages, dates and anniversary numbers. Don't make production staff infer information that the customer could confirm during the ordering process.
Treat allergen information as critical order information
Allergen information should never disappear inside a general notes box.
If a customer tells you that someone eating the cake has an allergy or food intolerance, that information needs to be clearly identifiable and properly handled through your bakery's allergen-management procedures.
The Food Standards Agency's current best-practice guidance recommends making written allergen information easily available and supporting it with a conversation. It also recommends having processes that ensure a customer's allergen requirements are accurately recorded, shared in writing with the person preparing the food and understood.
That is particularly relevant to bespoke cake shops.
Imagine a customer mentions a nut allergy during the initial consultation, but the decorator working on the cake three weeks later never sees that original WhatsApp conversation. The problem isn't simply that someone forgot something. The business process itself has failed.
A good cake-order workflow should therefore make allergy or intolerance information prominent.
It should also distinguish between an allergy requirement and a general dietary preference. Someone requesting a vegan cake, for example, should not automatically be told that the product is suitable for someone with a milk allergy.
Your cake order form doesn't replace your allergen matrix, staff training or food-safety procedures. Instead, it should connect the customer's requirement to those procedures.
Capture collection and delivery details clearly
Cake collections are another area where vague information creates unnecessary problems.
“Saturday afternoon” might mean 12pm to one employee and 4pm to the customer.
It is much better to agree a specific collection time or clearly defined collection window.
The order should therefore record the date and agreed collection time separately.
If you offer delivery, the order needs additional information. The delivery address and postcode should be confirmed, together with the recipient's details and any instructions needed to complete the handover.
For a house delivery, that may be straightforward.
For a wedding venue, hotel or restaurant, it can become more complicated. Your driver might need a loading entrance, venue contact, parking information or a particular room where the cake should be delivered.
Collecting this information before the delivery day can prevent a lot of last-minute phone calls.
Make the financial side of the order impossible to misunderstand
A good cake order form should make it immediately obvious how much the cake costs and how much the customer still owes.
For example, suppose the base cake is £95, a personalised topper costs £10 and delivery is £15. The total order is therefore £120. If the customer has paid a £40 deposit, the order should clearly show an £80 outstanding balance and the date that balance is due.
Your team shouldn't need to search through a card machine, bank account and WhatsApp thread to find out whether the cake has been paid for.
Clear statuses such as Deposit Paid, Part Paid and Paid in Full can make collection much easier, particularly on busy Saturdays when several customers may arrive at once. The same record can capture how payment was made, whether that was by card, payment link, bank transfer, cash or another method.
This becomes even more important as the bakery grows because payment information starts to influence production planning. A business may decide, for example, that a bespoke order should not move into a particular production stage until the required deposit has been received.
Record changes instead of silently replacing the original order
Customers changing their mind is normal.
What matters is how the change is managed.
Imagine a customer originally chooses pink and later changes the cake to lavender. If someone simply deletes “pink” and replaces it with “lavender”, the bakery loses the history of what happened.
That might not matter most of the time. But if a disagreement arises, knowing when the change was requested and what was ultimately approved can be valuable. A better approach is to record important changes against the order.
For example:
5 September: Customer changed primary colour from pink to lavender. Updated design approved by customer.
For highly bespoke cakes, it can also make sense to establish a sensible deadline for significant design changes. Once decorations have been ordered or production has begun, alterations may create additional work or cost.
The important thing is for your process and customer terms to explain this clearly rather than surprising the customer later.
Give the customer a clear point of approval
When the specification is complete, the customer should have an opportunity to check it. This doesn't need to involve printing a four-page contract in the cake shop. A digital confirmation can work just as effectively.
The customer might receive a summary showing the agreed cake size, flavour, filling, design, wording, collection date and total price, followed by a clear Confirm Order action.
That creates a useful moment in the customer journey Before confirmation, you're discussing possibilities. After confirmation, you have an agreed order specification. It also protects the customer because they have the opportunity to spot errors before production begins.
Make your terms clear, especially around deposits and cancellation
Bespoke cake businesses often take advance payments because they are reserving production capacity and may purchase materials specifically for an order.
That doesn't mean any deposit policy automatically becomes fair simply because it is written into your terms.
Current UK government guidance explains that consumer contract terms can be unfair where they allow businesses to keep prepayments automatically or impose disproportionate cancellation charges. Where a customer cancels, amounts retained should take account of the business's genuine losses rather than operate simply as a punishment.
This is why your order process should clearly explain what the deposit is for, when the balance is due and what happens if an order is cancelled or significantly changed.
Avoid hiding important terms in tiny text or expecting customers to discover them after paying. Good order management isn't only about protecting the bakery. It should make the transaction clearer for both sides.
Your internal team needs information too
Not everything on a cake order is customer-facing. Once an order reaches the kitchen, your team may need production notes. Perhaps the personalised topper is arriving on Thursday. Maybe the customer will bring a decorative toy into the shop before collection. A particular baker is responsible for the sponge while another decorator is creating the fondant figures.
This operational information should ideally sit with the order rather than being communicated through separate group chats. As the cake progresses, an order status can also make workloads easier to understand. A new enquiry might become Confirmed, then Ready for Production, followed by Baking, Decorating, Ready for Collection and eventually Completed.
In a busy bakery, being able to see where each order currently sits can give the owner a much clearer view of production than physically searching through paper slips.
The order shouldn't end when the customer collects the cake
Traditional cake-order systems tend to treat collection as the end.
The cake leaves the shop.
The receipt is filed.
The next customer arrives.
But from a customer relationship perspective, collection is potentially just the beginning.
You now know that this customer has trusted your bakery with an important occasion. You know what they ordered, when the occasion happened and whether they had a good experience. A thoughtful post-order journey could include a thank-you message and, where appropriate, a request for a review.
The order history can also make future service considerably better. If the customer returns next year and says, “Can we have something similar to the cake we ordered last September?”, your team shouldn't need to ask them to find the old photograph again.
You should ideally be able to see it. This is how an order-management system starts becoming a customer-relationship system.
Related Rise guide: How to Increase Repeat Cake Orders.
Why paper order forms become difficult as a bakery grows
Paper has worked in cake shops for decades. For a small operation, it can still work perfectly well but the challenge appears when order volume increases.
Paper can't easily tell you how many chocolate cakes were sold last quarter. It can't instantly show which customers still owe balances. It can't automatically find everyone collecting cakes tomorrow. It can't remind a previous customer that an important occasion is approaching again.
Information also gets duplicated when the customer's name might be written into the order book, typed into the card-payment system, added to a spreadsheet and later entered into an email platform.
Every manual transfer creates another opportunity for an error. Moving to a digital system isn't valuable simply because digital sounds more modern.
The real benefit is creating one reliable source of order information.
What should a digital cake order system actually do?
A useful digital system shouldn't simply recreate a paper form on a screen. It should connect the different stages of the customer journey.
When a customer places an order, their details should connect to the cake specification. The cake specification should connect to the deposit and balance. The payment should connect to the production status. The completed order should become part of the customer's history.
That means your bakery isn't repeatedly recreating the same customer every time they buy something.
You begin building a relationship. Imagine a customer returns and your team can see that last year they ordered an 8-inch chocolate cake with strawberry filling for their daughter's birthday.
Instead of saying:
“Can you send all the information again?”
you could say:
“Last year you had our 8-inch chocolate and strawberry cake. Would you like the same size and flavour with a different design this year?”
That feels like a business that knows its customers.
How Tolloz approaches cake order management
Most generic point-of-sale systems are built around simple retail transactions.
Select product.
Take payment.
Print receipt.
Move to the next customer.
Cake shops often need something different.
A bespoke cake order may involve customer information, an occasion, several flavours, design references, personalised wording, allergens, a collection date, a deposit, an outstanding balance and several conversations before the finished product ever reaches the customer.
Tolloz is being built specifically around this bakery workflow.
The aim is to connect the customer's record with the actual cake order, reference images, collection or delivery information, payments, order progress and future customer history.
Instead of relying on a separate paper order book, payment terminal, WhatsApp conversation, spreadsheet and customer database, the goal is to give bakeries a clearer operating system for managing the whole journey.
Because the most useful cake order record shouldn't only answer:
What cake are we making?
It should also answer:
Who is it for? What exactly did they agree to? When is it needed? Has it been paid for? What needs to happen next?
And once the cake has been collected:
How can we provide an even better experience next time?
Cake order form checklist
Although the order itself should feel simple to the customer, behind the scenes your bakery should make sure it captures the essential information. A practical checklist would include:
Customer name and reliable contact details
Unique order number and order date
Occasion and occasion date where relevant
Collection or delivery date and time
Cake size, shape, tiers and approximate servings
Sponge flavour, filling and finish
Agreed colours, theme and design description
Reference images and what each image represents
Exact personalised wording and age where applicable
Toppers, flowers, figures and other decorations
Allergy, intolerance and relevant dietary information
Delivery address and instructions where required
Itemised price, deposit, outstanding balance and payment status
Important order changes and customer approval
Production notes and assigned staff
Order status through baking, decorating and collection
Final payment and handover confirmation
Appropriate post-order follow-up
The checklist should support the customer conversation rather than dominate it. The customer should feel like they're ordering a cake, not applying for a mortgage.
One order. One clear record.
Customers don't see most of the work that goes into producing their cake.
They shouldn’t. It should be simple: they say what they want, you confirm, they pay, and on the agreed day the right cake is ready. Behind that simple experience, however, your bakery needs a reliable process.
A good cake order form creates that process. It reduces ambiguity, helps protect important customer information, gives decorators clearer instructions, improves payment visibility and makes collection easier.
Most importantly, it creates one clear version of what the bakery and customer have agreed.
As your cake business grows, that single order record can then become something even more valuable: part of an organised history of your customers, their occasions and their relationship with your bakery.
Rise by Tolloz provides practical advice to help bakery and cake shop owners run better organised, more profitable businesses. And Tolloz is being built to make the entire cake-order journey easier to manage from the first customer enquiry through to payment, collection and the next order.
Frequently asked questions about cake order forms
What should be included in a cake order form?
A cake order form should capture enough information for another member of your team to understand and fulfil the order correctly. This normally includes the customer, cake specification, design, wording, allergen requirements, collection or delivery details, price, payment status and final order approval.
Should I include reference photos?
Yes. Reference photographs are particularly useful for bespoke cakes, but don't rely on the image alone. Record which aspects of the photograph the customer wants and write a clear description of the final agreed design.
Should allergy information be included on the order?
Yes. Any allergy or intolerance requirement communicated by the customer should be accurately recorded and appropriately passed to the person preparing the food as part of your wider allergen-management procedure. Current FSA best-practice guidance specifically recommends having processes to record allergen requirements and share them in writing with the person preparing the food.
Should customers approve the final cake specification?
For bespoke orders, giving customers a clear opportunity to confirm the final size, flavour, design, wording, collection details and price can reduce misunderstandings. The confirmation can be physical or digital depending on how your bakery operates.
Should the cake order form contain marketing consent?
Your operational order information and direct-marketing processes should be considered separately. Only collect personal information that is relevant to your stated purposes, and make sure any marketing activity follows applicable privacy and electronic-marketing requirements.
Is a digital cake order system better than paper?
Paper can work for smaller bakeries. Digital order management becomes increasingly useful as order volumes, customer records, payments, employees and locations grow because information is easier to search, update, share and analyse.
Start your Tolloz free trial and build your bakery on better systems from day one.
This article provides general business information and does not constitute legal, food-safety or data-protection advice. Requirements depend on your individual business circumstances and may change. Check current Food Standards Agency, Information Commissioner's Office and GOV.UK guidance and seek professional advice where appropriate.