Getting started
When a spreadsheet stops working for bakery orders, and how to switch
Signs a bakery order spreadsheet has stopped working, a column layout to use until you switch, and the order to move customers, orders, pantry and expenses across.
the ibakepro team ·
A spreadsheet works for cake orders until about the point where two people touch it or a week holds more orders than you can remember. The usual tipping point is the first double-booked Saturday or the first balance you find out was never paid. When that happens, move your customers and open orders into order software first, keep the old sheet as a read-only archive, and build your products and recipes once rather than importing them.
The signs the sheet has stopped working
Most bakers switch after one of these, not before:
- A double-booked date. The sheet holds orders, not capacity. Nothing in it stops a third wedding cake landing on a Saturday you can only do two on.
- A balance nobody chased. The deposit column says paid, the balance column is blank, and the event was last week. A sheet records payments; it does not remind anyone.
- Prices built from last year's costs. Your costing tab used butter at last spring's price. Every quote since has been built on it, and the sheet gives no sign that anything moved.
- Allergens retyped on every order. The recipe changed in March; the allergen note on the order template did not.
- Orders arriving in four places. Instagram, email, a web form and a phone call, all copied into the sheet by hand, some of them twice.
- A second person. The moment someone else edits the sheet, you start finding rows changed with no record of who changed them or when.
If two or more of these happen every week, the sheet is costing you more than a switch would.
A cake order sheet layout to use until you switch
If you are not ready to move yet, set the sheet up so the move is easy later. One row per order line (not one row per order), with the order number repeated on every line of the same order:
| Column | Example | Why it matters |
|---|---|---|
| order_number | 1042 | Groups lines into one order |
| order_date | 2026-09-14 | When the order was taken |
| event_date | 2026-10-18 | The date that drives everything else |
| fulfilment | delivery | Pickup or delivery |
| customer_first_name | Priya | |
| customer_last_name | Shah | |
| customer_email | priya@example.com | The one field that reliably identifies a customer |
| customer_phone | 0400 000 000 | |
| item | 2-tier fondant cake | One line per item |
| quantity | 1 | |
| unit_price | 340.00 | In dollars or pounds, not cents |
| allergens_notes | no nuts, guest is coeliac | Copied from the customer, in their words |
| deposit_paid | 170.00 | |
| deposit_date | 2026-09-14 | |
| balance_due_date | 2026-10-08 | Set from the event date, not the order date |
| balance_paid | Blank until it lands | |
| delivery_address | 12 Harbour St | |
| notes | topper ordered in |
Three rules keep it clean: one date format in every date column (YYYY-MM-DD avoids the day-month mix-up), one email per customer and no merged cells.
What to move, and in what order
The order that works is pantry, customers, open orders, expenses, then build your products.
- Pantry items. Ingredients and packaging, with what you paid and the pack size. Everything else is costed from these.
- Customers. Name, email and phone at minimum. This is the list your marketing and repeat orders run from.
- Open orders first, history second. Everything with an event date in the future needs to be in the new system before you stop using the sheet. Past orders are worth bringing in for the customer history, but they can follow a week later.
- Expenses. The last twelve months, so your profit figures start with a real baseline.
- Products, built by hand. A product made from recipes, components and packaging is something you set up once in the product builder, not a row you import. It is usually an afternoon for a core menu, and it is the step that makes every future price come from real costs.
Run both for one week. New orders go in the new system only; the sheet stays open read-only for lookups. After a week you will have stopped opening it.
How long it takes
For a typical home or small bakery, a weekend: an evening tidying the sheet, an evening importing, a day building the core products. The tidying is where the time goes, and the causes are predictable: two date formats in one column, one row per order instead of one per line, customers with no email and totals that disagree with their own lines because a delivery fee went missing. Fix those in the spreadsheet with find-and-replace before you import, not row by row afterwards.
Moving into ibakepro
ibakepro, used by bakeries of every size moving off spreadsheets, from home cake makers to sourdough, cookie and wholesale bakeries, imports orders, customers, expenses and pantry items from CSV, matches your column names for you, shows every problem row grouped by cause before anything is saved, and leaves automated messages off for imported records unless you switch them on, so nobody gets a payment reminder for a cake they ate in March. Once the pantry is in and the products are built, the cake pricing calculator is the arithmetic every price is then built on. For moving from other software rather than a sheet, see how to switch bakery software.