Development Agency
Contact Sign in Get a project quote

Service

Bakery ordering software development

For bakery owners, cake makers and patisseries who take orders for a future day and need the order book, the configurator, the deposit and the production schedule to agree with each other, rather than a shop plugin that sells cakes like T-shirts.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A bakery sells things that have to be made on a particular day for a particular time, by a kitchen that can only make so many.

  • Most bakery websites ignore this.
  • A shop plugin takes an order for a three-tier celebration cake on Thursday for collection Saturday, with no idea that the decorator is already full and that a tiered cake needs four days.
  • Custom cake enquiries arrive as a direct message with a photo and the words "something like this"; the baker replies with questions about size, flavours, finish and the message, a price is agreed in the thread, and the deposit is a bank transfer that may or may not arrive.
  • On Saturday morning two cakes are collected by the wrong people and one was never written in the book.

Where it gets harder

Production is planned on a wall calendar.

  • Standing wholesale orders for the café round the corner are remembered, until the week they are not.
  • A sold-out day is still taking orders online because nobody turned the shop off.
  • Allergen information is a laminated sheet behind the counter that does not match the website.
  • Customers ring to ask whether their cake is ready, the counter has to ask the kitchen, and the kitchen has to find the ticket.
  • The owner cannot see how many custom cakes are due on the Saturday before Mother's Day until it is too late to say no, and has no record of which flavours and sizes actually sell.

Scope of the service

What the build covers

A custom bakery build normally covers:

  • A product catalogue Where each product carries a lead time and a production category
  • A custom cake configurator that walks the customer through size Tiers, flavours, filling, finish, message and a reference image, and ends in either a fixed price or a quote request depending on how far the request strays from the standard
  • Daily production capacity per category With blackout dates so the website stops selling when the kitchen is full
  • Collection or delivery date and slot selection within the lead time
  • Order status from confirmed through in production to ready With the customer told at each step
  • Deposits for custom work with the balance due at collection
  • Allergen declarations shown against each product exactly as the bakery records them
  • Wholesale standing orders That generate the production list each week without anyone remembering

How discovery works

Discovery works through a production week with you: what is baked daily and what is made to order, how many celebration cakes the decorator can finish in a day, which products need two or four days, when the shop stops taking orders for a Saturday, how deposits are taken for custom work and what happens if the customer does not collect, how wholesale customers order today and when the round goes out. Each answer becomes a named workflow stage in the scope document.

  1. Configure
  2. Quote or price
  3. Deposit
  4. Production schedule
  5. Ready
  6. Collected

Deliberately out of scope

  • Ingredient stock and purchasing, recipe costing beyond the price you set, the till itself and payroll

When the scope grows

Scoping scenario

A bakery with a shop, a production unit and a wholesale round of thirty cafés wants one system where the shop sells from the daily bake, custom cakes are configured and quoted online, wholesale customers adjust next week\'s standing order themselves by a Thursday cut-off, and the production unit prints one bake list on Sunday night that covers all three. That is a materially different build from a home-based cake maker who.

That needs

  • A configurator
  • A deposit
  • The scope document says which one is being built

Deliverables

What you receive

  • Discovery notes from a walk-through of a production week, from order book to collection
  • A written scope document naming each stage from configuration to collection, with what is out of scope
  • Design of the configurator, the order book, the production calendar and the bake list, on a phone for customers and a tablet in the kitchen
  • The build, deployed to your hosting or ours
  • Migration of the product list, open orders and standing orders from your current shop or book, where relevant
  • Training for the owner, bakers and counter staff, with a one-page guide for capacity and blackout dates
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access, contacts, your current product list, order book, wall calendar and any shop plugin in use.

    Project stage: Onboarding

  2. Planning

    Discovery with the owner, the head baker and whoever answers cake enquiries; the scope document and milestone plan are agreed.

    Project stage: Planning

  3. Design

    Clickable designs of the configurator, the order book and the production calendar, reviewed with the decorator who will live in them.

    Project stage: Design

  4. Development

    Built in stages: catalogue, lead times and capacity first, then the configurator and deposits, then status, standing orders and the bake list.

    Project stage: Development

  5. Client review

    The bakery runs a fortnight of real orders through the system alongside the book and tells us where capacity, lead times or the configurator are wrong.

    Project stage: Client review

  6. Revisions

    Capacity rules, configurator options and bake list layout are adjusted from the review and re-checked against the scope.

    Project stage: Revisions

  7. Ready for launch

    Products and open orders loaded, standing orders set, payment and ready notifications tested, checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    The bakery takes and plans orders on the new system; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Card payment providers for deposits, balances and standard product orders
  • SMS and email providers for order confirmations and ready-for-collection notices
  • Accounting software for wholesale invoicing and deposit reconciliation
  • Label printers for order tickets and allergen labels in the kitchen
  • Delivery and courier services for cakes sent rather than collected
  • Till systems where counter sales and collections meet

How we would approach it

Worked example

Concept demo

A patisserie with a decorator who could only do five a day

The situation

A patisserie with one decorator wanted to keep taking celebration cake orders online without ever selling a Saturday it could not deliver.

Why it is a custom build

This needs a custom build rather than a shop plugin because the scarce resource is decorator hours on a specific day, not stock on a shelf, and every date the website offers has to be a date the kitchen has agreed to.

The scope we would propose

  • Celebration cakes belong to a production category with a daily capacity of five finished cakes, which the owner can raise when a second decorator is in
  • The configurator counts a tiered cake as two units of that capacity
  • The collection date picker shows only days with capacity inside the lead time and hides the week before Mother\'s Day once it is full
  • A request that picks a non-standard finish or an uploaded reference goes to a quote queue rather than a price
  • The deposit is taken at acceptance with the balance at collection

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Standard products, custom cakes or both, and how far the configurator goes
  • How production capacity is counted per day and per category
  • Quote queue for non-standard requests alongside fixed-price configurations
  • Deposits for custom work and the payment provider involved
  • Delivery or courier dispatch in addition to collection
  • Wholesale standing orders, customer self-service and invoicing
  • Allergen declarations and label printing in the kitchen
  • Migration of open orders and the product list
  • Hosting choice: your own hosting or ours

Start from a package

Custom cake ordering package

A cake configurator with sizes, tiers, flavours, finish and message, lead times per product, daily production capacity with blackout dates, deposits for custom work, order status and wholesale standing orders for bakeries and cake makers.

Custom build
View the package

FAQ

Frequently asked questions

Would the package do, or do we need a custom build?

A bakery or cake maker with a standard product list, a configurator and a daily capacity is usually covered by the custom cake ordering package through configuration. A custom build is the honest answer when a wholesale round, a separate production unit or several shops have to plan from one bake list. Discovery is where we tell you which.

Can the website stop taking orders when we are full?

Yes. Each production category has a daily capacity and blackout dates, and the collection date picker only offers days with room inside the product's lead time. The owner can lower capacity or black out a day from a phone and the website follows straight away.

How do you deal with "something like this" photo requests?

The configurator covers the standard choices and prices them; anything beyond, including an uploaded reference image, goes into a quote queue where the baker replies with a price and the customer accepts and pays the deposit online. The thread, the image and the agreed version stay on the order.

How is allergen information shown?

The bakery records allergen declarations against each product and the website displays exactly what has been recorded, with a prompt to ask in the shop. The system publishes your own records; keeping them accurate remains the bakery's responsibility and no compliance claim is made by the software.

Who owns the system afterwards?

You do. Source code and your data, including order history and standing orders, are handed over at delivery; hosting and maintenance are optional and separately agreed.

Get a project quote for bakery and custom cake orders software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences