A bakery website that takes the cake order.
Customers design their cake on your site, watch the price as they build it, pick a pickup time you can actually bake for, and pay the deposit. You get the order, the allergens and the schedule in one back office. Built on our modules, and the code is yours at handover.
They design it. You bake it.
No more back-and-forth over text about sizes, flavours and what "a little gold" means. The customer builds the exact order on your site, and it lands in your back office already specced.
- Cupcakes
- Single-tier cakes
- Multi-tier cakes
- Sheet cakes
- Decorated cookies
- Cake pops
See it before it's baked
A live drawing of the design with Build, Exploded and Finished views, a cut-away of the layers inside, and a "Play the build" button that assembles it step by step.
Price as they build
The quote updates with every choice. Your server re-prices every line at checkout, so the browser can never set its own price.
Every option, per tier
Sponge, filling, shape, texture, coating and colour tier by tier, plus toppers and messages drawn on the model exactly as they'll be written.
Allergens follow the choices
Pick the almond sponge and tree nuts join the list. Allergens show in the builder, the order, the emails and your calendar.
From "that one" to deposit paid.
Four steps, and the calendar only offers days your kitchen can actually make.
- 1
Design
Build one item or a whole cart: a tiered cake, two dozen cupcakes and a box of cookies in one order.
- 2
Date and time
Only open dates show. Lead times, daily capacity, closed days and blackout dates are checked, and a multi-tier cake gets the notice you set.
- 3
Review
The finished design is drawn again next to the price and allergens, so what they approve is what you bake.
- 4
Deposit
The deposit is paid through Stripe (you set the percentage) and the balance is due at pickup. The customer gets a private link to track their order.
One screen runs the kitchen.
Your staff sign in with Google. Everything a bakery owner juggles across notebooks, DMs and spreadsheets lives in one place.
Orders
Every order with its drawing, allergens, customer, deposit and history. Move a date, add a note, advance it from Confirmed to Baking to Ready to Picked up.
Schedule and calendar
A week view with capacity bars, synced to Google Calendar, plus a private calendar feed for any phone.
Capacity you control
Lead times, daily limits, open days, pickup windows and blackout dates, all edited in the back office. Two customers can't book the last slot at once.
Menu and prices
Change any price or switch any option off, like a flavour that's out of season, without calling a developer.
Inventory and recipes
Ingredient needs are worked out from open orders and your recipes, with a reorder list grouped by supplier and a cost per item.
Know which ad sold the cake
Built-in first-party analytics ties each order back to the search, ad or post that brought the customer.
Ask Claude
Connect Claude and ask what's due Saturday, check availability, take a phone order or mark a deposit paid, without opening the back office.
Found locally
Search-ready location pages, structured data and your Search Console and PageSpeed reports inside the back office.
The first bakery on it.
We built this for Kimmy's Bakery: the six product lines, the order flow, deposits, and the back office with its schedule, inventory and recipes.
It runs on the same production modules as the rest of our work (sign-in, analytics, SEO, locations, error reporting, the Claude connector), with the bakery pieces built on top. That's why a build like this costs a fraction of starting from zero.
Screenshots are from Kimmy's pre-launch site. Menu prices shown are samples.
Your site. Your orders. Your code.
No commission on your cakes
We don't take a cut of your orders. Card processing is between you and Stripe.
Built from modules
The common parts already exist and run in production, so you pay for what's specific to your bakery.
One team
The same people design it, build it, host it and support it.
The repository is yours
When the contract completes, the code, data and accounts transfer to you. Host it anywhere, hire anyone.
Bakery owners usually ask.
Can I change my menu and prices myself?
Yes. Every option has its own price and an on/off switch in the back office, so a seasonal flavour can disappear in October and come back in spring without a developer.
How does it stop me getting overbooked?
You set lead times, a daily capacity and your open days. The calendar only offers dates that fit, and the server checks again when the order is placed, so two customers can't take the last slot.
Do customers pay online?
The deposit is paid online through Stripe, at the percentage you choose, and the balance is due at pickup. Without Stripe, orders still come in and you collect the deposit yourself.
Does it do delivery?
Pickup windows are built in today. Delivery has its settings in place but stays switched off until we set it up for a bakery that needs it.
Does it work if I already have a website?
Yes. The builder and ordering can live on your current domain as a new site, or we rebuild the whole site around them. Either way the orders land in the same back office.
What do I own at the end?
The repository and everything in it: the code, your menu, your orders and your customer data, plus the hosting and accounts in your name.
Ready to grow?
Tell us about your roadmap, your stack, and the deadline that's making you nervous. We'll come back in 48 hours with a plan.