MICROBAKERY BUSINESS · A practical production control
A customer order is not a loaf of bread. Between the message that says “two sourdoughs, please” and the bag handed over at pickup, that order passes through mixing, dividing, shaping, proving, baking, cooling and packing. If those stages live in separate messages, notebooks and your memory, mistakes become harder to spot as production grows.
When I ran Healthy Nasti Kitchen, I learned that increasing demand did not automatically increase what I could produce. My small-oven setup could bake only a limited number of loaves per hour. That was a real capacity constraint. But there is a second problem worth solving before buying equipment: knowing exactly what each batch is supposed to deliver.
A one-page batch sheet is a simple way to connect confirmed orders to finished loaves. The workflow below is a suggested system for small bakers; I am not claiming it is an exact copy of a historical Healthy Nasti Kitchen document.
Start with confirmed orders, not your best guess
Build the production plan from orders that have passed your stated cutoff. Keep enquiries, unconfirmed orders and “I might want one” messages out of the committed total. If you choose to bake extras for a market or walk-in sales, put them on a separate line so you can see the difference between committed demand and speculative stock.
My earlier article on why I required 48 hours’ notice explains the customer-facing side. The batch sheet handles what happens after the order is accepted.
Give every bake one clear identity
Put the production date and a simple batch reference at the top, such as a date followed by a letter for the mix. The reference should help you connect your own ingredient, production and dispatch information; it is not a substitute for any labelling or food-safety obligations that apply to your business.
Keep different formulas and important allergen differences visible. A plain country sourdough and a seeded loaf may share an oven, but they should not disappear into a single anonymous count. If you change ingredients or suppliers, record that separately rather than relying on yesterday’s formula.
The six columns that make a batch sheet useful
| Stage | What to record | Why it matters |
|---|---|---|
| Orders | Confirmed loaves by product and collection or delivery route | Defines the actual commitment |
| Mix | Formula or batch reference, ingredient lots where relevant, total dough prepared | Connects inputs to production |
| Divide and shape | Number of pieces and target piece weight | Catches a shortfall before proving |
| Prove and bake | Basket or tray allocation, bake sequence and actual oven output | Shows the capacity bottleneck |
| Cool and pack | Saleable loaves packed, rejects and packaging checks | Prevents assuming everything baked is ready to sell |
| Dispatch | Customer or route, quantity handed over and any outstanding orders | Closes the loop |
This can be a printed sheet, a spreadsheet or a notebook page. The format matters less than one person being able to reconcile the numbers without searching through messages.
Do the reconciliation before the oven is switched on
Suppose your confirmed orders require 24 loaves. If you deliberately decide to make two additional loaves for sale, your planned total becomes 26. Those are illustrative numbers, not figures from my bakery. Write both lines down: 24 committed and two optional. If only 25 pieces are shaped, you know there is a one-piece gap before the bake begins. If 26 are baked but one is damaged, you know the packed total is 25—not 26.
The basic check is: planned pieces = committed orders + deliberately planned extras. Later, reconcile shaped pieces, acceptable baked loaves, packed loaves and handed-over loaves. Explain every difference. A rejected loaf, staff meal, sample or damaged item should be visible, not silently removed from the count.
Schedule backwards from the customer handover
A pickup time is not a bake-finish time. Bread needs an appropriate cooling period before packaging, and the cooling space itself can become a constraint. Read why cooling is a microbakery bottleneck before setting a collection window too close to your final oven load.
Work backwards from the time the bread must be ready: allow for packing, cooling, oven batches, loading, final proving and earlier fermentation. Use timings established from your own formula, oven and conditions; do not copy a universal schedule from someone else’s kitchen. If your oven is the slowest stage, buying more baskets will not automatically move the dispatch time forward. I covered that equipment lesson in choosing the right bread oven.
Separate production control from food-safety compliance
A batch sheet is useful operationally, but it does not by itself prove compliance with Australian food law. Food Standards Australia New Zealand advises food businesses to maintain traceability of ingredients, packaging, products and recipients where relevant; food manufacturers and wholesale suppliers also have specific recall-system obligations. The rules for labelling and records depend on what you make and how you sell it. Read FSANZ’s traceability guidance and confirm the requirements for your own activity with your local council or regulator.
Do not use a generic production sheet as your only allergen control. Maintain accurate ingredient and allergen information, identify any recipe changes, and prevent cross-contact through the procedures appropriate to your business. The FSANZ food-safety standards overview is a starting point, not a replacement for tailored advice.
Make the last check someone else can understand
Before collection or dispatch, compare the packed quantities with the confirmed order list. Check the product, customer, quantity and any required label or allergen information. Mark the order as handed over only when it actually leaves. If something is short, contact the customer with a clear solution before they arrive.
After the bake, keep a short note of what caused friction: late order changes, dough that was not ready, baskets occupying fridge space, oven queues, slow cooling or a missing delivery label. You do not need a complicated dashboard. You need evidence that helps you remove the next real bottleneck.
The lesson from a small bakery
A microbakery does not become more professional because its paperwork becomes longer. It becomes more reliable when the promises made to customers match what the bakery can produce, pack and deliver. Start with one page, use it for a few production days, and keep only the fields that help you make or verify a decision.
For the logistics after baking, see the hidden cost of microbakery delivery. For more practical articles on bread and small-bakery operations, join the SA Bakery Supplies Baking Journal.
Leave a Reply