Skip to content
Formward
Log inStart free

Order forms · 7 fields

Bakery order form template

For bakeries and home bakers who take custom orders. The customer chooses an item, a quantity and a pickup date and describes flavours or decoration, and you answer with a price and a yes.

Get the code

Bakery order

Live demo: try the fields. Submitting sends nothing.

Why these fields

  • Name

    text · required

    Required. The name the order is collected under.

  • Email

    email · required

    Required. Your confirmation with price and pickup time goes here.

  • Phone

    tel · optional

    Optional, but ask for it: on the pickup day a call is quicker than an email when something has changed.

  • Item

    select · optional

    Cake is preselected in the generated HTML. Rename the options to your own range and add an empty first option so that nobody orders a cake by accident.

  • Quantity

    number · required

    Required number. Add min="1", and say in the label whether it counts pieces, boxes or portions.

  • Pickup date

    date · required

    Required date. Give it a min attribute that respects your lead time; without one, customers can pick tomorrow or last week.

  • Special requests

    textarea · optional

    Optional, yet most cake orders depend on it: flavour, filling, text on the cake, colours. Ask about allergies here and answer honestly about what your kitchen can guarantee.

When to use it

Use it for celebration cakes and pre-orders, where you need notice and a conversation about details. Counter sales and same-day orders do not need a form.

State your lead time next to the form, for example orders at least five days ahead. The date input cannot know your notice period unless you give it a min value.

Privacy and GDPR

  • An allergy note is health information. Use it for the order and do not keep it afterwards.
  • Take payment or a deposit by payment link or at pickup. The form should never ask for card details.

Choose your stack. Copy your form.

Replace the example endpoint with your Formward endpoint, then adapt the fields to your needs.

<form action="https://forms.formward.eu/f/your-form-id" method="POST">
  <label for="name">Name</label>
  <input type="text" name="name" id="name" required />
  <label for="email">Email</label>
  <input type="email" name="email" id="email" required />
  <label for="phone">Phone</label>
  <input type="tel" name="phone" id="phone" />
  <label for="item">Item</label>
  <select name="item" id="item">
    <option value="Cake">Cake</option>
    <option value="Cupcakes">Cupcakes</option>
    <option value="Cookies">Cookies</option>
    <option value="Bread">Bread</option>
    <option value="Pastries">Pastries</option>
  </select>
  <label for="quantity">Quantity</label>
  <input type="number" name="quantity" id="quantity" required />
  <label for="pickup_date">Pickup date</label>
  <input type="date" name="pickup_date" id="pickup_date" required />
  <label for="notes">Special requests</label>
  <textarea name="notes" id="notes"></textarea>
  <input type="text" name="_gotcha" tabindex="-1" autocomplete="off" style="position:absolute;left:-9999px" aria-hidden="true" />
  <button type="submit">Send</button>
</form>

Accessible by default, and how to keep it that way

  • Every field in the code has a visible label tied to it with for and id, so screen readers announce what to enter and a click on the label focuses the field.
  • Required fields carry the required attribute, so the browser explains a missing answer before anything is sent. Say “required” in words as well; an asterisk or a colour alone is easy to miss.
  • The spam trap field (_gotcha) is hidden from screen readers with aria-hidden and skipped by the Tab key, so people never meet it.
  • In the JavaScript versions, show the confirmation or error in an element with role="status" so the result is announced, and keep the entered answers when sending fails.

Changed the fields? Paste your version into the HTML form tester to see exactly what it sends, or run it through the GDPR form checker.

How the code talks to Formward

Each form you create gets its own endpoint in the form https://forms.formward.eu/f/your-form-id. The HTML version posts to it directly and the browser is redirected to a thank-you page, so it works without JavaScript.

The Next.js version below sends the same fields with fetch and an Accept: application/json header. Formward then answers with { ok: true, id }, or an error body with 402 when the account is over its allowance and its Over limit folder is full, and 429 when the rate limit kicks in. See responses and status codes.

Next.js client component

"use client";

import { useState } from "react";

export function BakeryOrderForm() {
  const [sent, setSent] = useState(false);
  const [error, setError] = useState("");

  async function onSubmit(e: React.FormEvent<HTMLFormElement>) {
    e.preventDefault();
    const form = e.currentTarget;
    setError("");
    try {
      const res = await fetch("https://forms.formward.eu/f/your-form-id", {
        method: "POST",
        headers: { Accept: "application/json" },
        body: new FormData(form),
      });
      if (res.ok) {
        setSent(true);
        form.reset();
        return;
      }
    } catch {
      // Network failure: fall through to the same message.
    }
    // The answers stay in the form so the visitor can try again.
    setError("Sending failed. Please try again.");
  }

  if (sent) return <p role="status">Thanks! Your message has been sent.</p>;

  return (
    <form onSubmit={onSubmit}>
      <label htmlFor="name">Name</label>
      <input type="text" name="name" id="name" required />
      <label htmlFor="email">Email</label>
      <input type="email" name="email" id="email" required />
      <label htmlFor="phone">Phone</label>
      <input type="tel" name="phone" id="phone" />
      <label htmlFor="item">Item</label>
      <select name="item" id="item">
        <option value="Cake">Cake</option>
        <option value="Cupcakes">Cupcakes</option>
        <option value="Cookies">Cookies</option>
        <option value="Bread">Bread</option>
        <option value="Pastries">Pastries</option>
      </select>
      <label htmlFor="quantity">Quantity</label>
      <input type="number" name="quantity" id="quantity" required />
      <label htmlFor="pickup_date">Pickup date</label>
      <input type="date" name="pickup_date" id="pickup_date" required />
      <label htmlFor="notes">Special requests</label>
      <textarea name="notes" id="notes" />
      <input
        type="text"
        name="_gotcha"
        tabIndex={-1}
        autoComplete="off"
        style={{ position: "absolute", left: "-9999px" }}
        aria-hidden="true"
      />
      <button type="submit">Send</button>
      <p role="status">{error}</p>
    </form>
  );
}

Spam protection

  • The generated code already includes the hidden _gotcha honeypot. Leave it in: a bot that fills it gets a normal success response, the submission is filed as spam and no email is sent.
  • Every form has a per-IP rate limit, and you can restrict it to your own domains with the allowed-origins list in the form settings.
  • Cloudflare Turnstile is optional and works on every plan, including Free. Turn it on in the form settings, add the widget to your markup and Formward checks the token server-side.
  • The form settings can also reject disposable email addresses, which is worth turning on when a fake address would waste your time.

What happens after submit

  • Each bakery order is emailed to your notification address and kept in the dashboard on every plan.
  • From Personal, an automatic reply can say that the order is confirmed only when you have replied with a price.
  • From Personal, a CSV sorted by pickup date doubles as the week's baking list.

Questions

Can customers upload a picture of the cake they want?
A file field for reference pictures needs Professional or above. On other plans, ask them to paste a link to the picture in the special requests, or to reply to your confirmation with it.
How do I stop orders for dates I am closed or fully booked?
The form cannot check your calendar. Set min and max on the date input for the period you accept, list closed days beside the form, and decline by email when a day is full.

Customize before publishing

  • Remove fields you do not need and mark only essential answers as required.
  • Replace placeholder wording with terms your audience already understands.
  • Add your privacy notice, retention details and expected response time.
  • Test keyboard focus, validation errors and the confirmation state on mobile.

Use this template

Create a free account and the form is set up from this template. Copy your endpoint and replace https://forms.formward.eu/f/your-form-id in the code above.

Use this template →