Sell · free template

Cake Order Form

Custom bakery orders with flavours, tiers, inscription and collection date, priced automatically.

A ready-to-use e-commerce & payments form for online shops, makers and subscription brands: 15 questions, 3 pages, 5 conditional rules.

Questions
15
Pages
3
Layouts
classic · card
Conditional rules
5
Typical time
4 min
Preview it in the gallery

Searches this template answers

Also filed under

Live preview and test console

This is the real form. Answer it to test the 4 conditional rules — nothing is sent or stored.

Page 1 of 3Cake details

Order a custom cake

Include your country code.

Attach a file up to 10 MB.

Any file type up to 10.0 MB (larger files are rejected) · uploads are saved on the live form

Every question on this page is currently visible.

What happens after submit: nothing is stored in this preview. On your own copy, every response triggers an instant email notification and lands in your response dashboard, ready to export or forward.

Happy with it? Take a copy into your workspace — every question, rule and setting comes with it.

Who this template is for

Cake Order Form is built for online shops, makers and subscription brands who need to take an order, a deposit or a recurring payment without a checkout build.

  • Online shops, makers and subscription brands working in e-commerce & payments.
  • Teams who need to take an order, a deposit or a recurring payment without a checkout build without writing code or paying for a custom build.
  • Anyone replacing orders arriving as half-finished emails with no payment attached with one structured record per enquiry.
  • Respondents are shoppers and repeat customers — the form asks them 15 questions across 3 screens.
  • Mobile-heavy audiences, thanks to the one-question-per-screen card layout.

Why this form is useful

It removes the cost of orders arriving as half-finished emails with no payment attached and turns each submission into a record your team can act on immediately.

  • 8 questions are required, so submissions arrive complete instead of needing a follow-up email.
  • It collects a verified email address so replies and confirmations land.
  • It captures a phone number for urgent follow-up.
  • It accepts a document or photo upload as evidence.
  • It pins the request to a specific date.
  • Conditional logic hides 5 questions until they are relevant — shorter forms convert better than long ones.
  • Splitting the form across 3 pages keeps each screen short and shows respondents how much is left.
  • Every response is stored, searchable and exportable, so nothing depends on one person's inbox.

How to use this template

From copy to live form is a few minutes of work, and every step is reversible.

  1. 1Press “Use this template” — a fresh copy of Cake Order Form lands in your workspace, ready to edit.
  2. 2Rename or delete any question, and change what is required. Nothing here is fixed.
  3. 3Open Notifications and add the email addresses that should be alerted on each submission; add an auto-reply to the respondent if the form collects an email address.
  4. 4Check the upload limits on the file question so respondents can attach what you actually need.
  5. 5Publish it, then either share the link directly or paste the embed snippet into your site — the embedded form resizes to fit and loads no marketing or advertising trackers.
  6. 6Watch responses land in Submissions, where you can filter, label and export them to CSV or PDF.

Logic and conditions blueprint

Exactly how this form behaves as it is answered — 5 conditional rules ship with it.

  • Features advanced show logic: if “Does this order need to avoid any allergens?” is Yes, the form dynamically exposes “Allergy details”. Otherwise that question never appears.
  • Features conditional validation: if “Does this order need to avoid any allergens?” is Yes, “Allergy details” becomes mandatory before the form can be sent.
  • Features advanced show logic: if “Collection method” is Delivery, the form dynamically exposes “Delivery address”. Otherwise that question never appears.
  • Features advanced show logic: if “Collection method” is Delivery, the form dynamically exposes “Stairs or lift access at delivery venue?”. Otherwise that question never appears.
  • Features advanced show logic: if “Collection method” is Pickup, the form dynamically exposes “Preferred pickup time”. Otherwise that question never appears.
  • All 5 rules are editable in the Logic tab, and the built-in checker warns about rules that contradict each other.

About this template

Custom cake orders have more moving parts than a standard product sale — flavour, filling, tier count, inscription wording and an occasion date that can't slip. This form captures all of it in one pass instead of a back-and-forth thread of texts and photos. Choosing a cake size or tier count feeds a calculated price so the customer sees an estimate before they submit, which cuts down on quotes that don't match expectations later. Flavour and filling are separate dropdowns so a customer can genuinely mix and match rather than being boxed into preset combinations. An inscription field captures exact wording, spelling and punctuation, which matters far more on a cake than almost any other product. Because allergies are a real safety issue in a bakery, the form asks directly whether the order needs to avoid any allergens; answering yes makes a details field required so the kitchen has a written record rather than a verbal note that can get lost. The order branches on collection method too — pickup shows a store location and collection time, while delivery reveals an address and asks whether the venue has stairs or lift access, which affects how the cake needs to be boxed and transported.

What this form asks

Every question is editable — rename it, make it optional, or delete it entirely.

Page 1 — Cake details

  • Full namerequired
  • Email addressrequired
  • Phone number
  • Cake size / tiersrequired
  • Flavourrequired
  • Fillingrequired
  • Inscription wording
  • Reference photo or design inspiration

Page 2 — Dietary needs

  • Does this order need to avoid any allergens?required
  • Allergy details

Page 3 — Collection

  • Occasion / collection daterequired
  • Collection methodrequired
  • Preferred pickup time
  • Delivery address
  • Stairs or lift access at delivery venue?

15 questions in total.

How the form changes as it's filled in

This template ships with 5 conditional rules, grouped into 4 behaviours driven by 2 questions. Everything below is already set up — edit or delete any rule once the template is in your workspace.

Driven by “Does this order need to avoid any allergens?

  • Reveals questions

    If “Does this order need to avoid any allergens?” is Yes, the form reveals “Allergy details”.

  • Makes answers required

    If “Does this order need to avoid any allergens?” is Yes, “Allergy details” becomes required before the form can be submitted.

Driven by “Collection method

  • Reveals questions

    If “Collection method” is Delivery, the form reveals “Delivery address” and “Stairs or lift access at delivery venue?”.

  • Reveals questions

    If “Collection method” is Pickup, the form reveals “Preferred pickup time”.

Set it up step by step

  1. 1

    Set your real pricing behind each size option

    Match the calculated price to your actual per-tier cost so the estimate customers see is accurate.

  2. 2

    Flag allergy orders for a dedicated kitchen area

    Route any submission with allergy details to whoever manages cross-contamination controls before baking starts.

  3. 3

    Confirm the date isn't already booked

    Cross-check the occasion date against your order calendar before replying to confirm the order.

  4. 4

    Send a written confirmation with the inscription text

    Copy the inscription wording back to the customer to confirm spelling before you decorate.

Mistakes to avoid

  • Not confirming inscription spelling in writing, which leads to reprints on names and dates.
  • Treating the allergy question as optional, which risks a serious safety issue rather than just a preference.
  • Booking a collection date without checking kitchen capacity for that day first.

What it pairs with

Most teams don't run this form on its own. These are the forms and systems it sits next to.

What to do with the responses

Confirm the quoted price and collection date back to the customer in writing, and flag any allergy order to your kitchen lead before scheduling the bake.

Works in both layouts

These pages cover the same subject ground as the cake order form, matched on the words people actually search for.

Frequently asked questions

Can I use this for wedding cakes too?

Yes — add a consultation date field or link to a call before confirming, since wedding orders usually need a tasting first.

How far in advance should the collection date be set?

Most bakeries require at least 5–7 days' notice for custom cakes; add that as help text on the date field.

What happens if a customer needs to change the inscription after ordering?

Ask them to contact you directly rather than resubmit — the form is for new orders, not amendments.

Does the price update if they change the flavour?

The calculated total is driven by size and tier count; flavour and filling can carry a small surcharge if you price it that way.

Is the Cake Order Form template free to use?

Yes. You can preview and test Cake Order Form on this page without an account, and take a copy into your own HelloForms workspace on the free plan. There is nothing to install and no card required to publish it.

What does the Cake Order Form template ask for?

It asks 15 questions across 3 pages, 8 of which are required. Every question is listed in full further down this page, and each one can be renamed, reordered, made optional or deleted after you copy the template.

Can I edit the Cake Order Form form after copying it?

Yes — the copy is entirely yours. Change wording, add or remove questions, switch between the classic and card layouts, restyle it to match your brand, and set who gets notified on each submission.

How does the conditional logic in this e-commerce & payments form work?

5 conditional rules ship with the template: Features advanced show logic: if “Does this order need to avoid any allergens?” is Yes, the form dynamically exposes “Allergy details”. Otherwise that question never appears. Features conditional validation: if “Does this order need to avoid any allergens?” is Yes, “Allergy details” becomes mandatory before the form can be sent. Features advanced show logic: if “Collection method” is Delivery, the form dynamically exposes “Delivery address”. Otherwise that question never appears. All rules are editable in the Logic tab.

Where do responses to the Cake Order Form form go?

Submissions land in your workspace under Submissions, where you can search, filter, label and export them to CSV or PDF. You can also email a notification to your team on every submission and send the respondent an auto-reply.

Can I embed the Cake Order Form form on my own website?

Yes. Publish the form and paste the embed snippet into any page or share the direct link. The embedded form resizes to fit its container and loads no advertising or marketing trackers inside the iframe.

Can respondents upload files?

Yes. This template includes a file upload question, so respondents can attach documents or photos with their answers. You can adjust the accepted file types and size limits on that question.

More forms teams pair with the cake order form.

Related categories