Cookie Order Form Template
A by-the-dozen cookie ordering form for home bakers: flavors, dozens, need-by date, and wrapping, all settled when the box changes hands.
Fresh-baked cookies by the dozen. Tell us flavors and when you need them. We confirm every order by email, and you pay on pickup or delivery.
Your name, or the lucky recipient if it's a gift.
Home cookie businesses run on batches, and a batch has hard edges: an oven holds so many trays, a Saturday holds so many bakes. The order form's real job is fitting demand inside those edges without a single back-and-forth text thread. Every field here maps to a production constraint, which is why a form this short can run a whole cottage bakery weekend.
Every field is a constraint. The flavor multi-select caps at three per order, an oven-scheduling limit rather than a style choice, and the description says so, which makes the cap feel like freshness instead of refusal. Dozens (1–20) is the unit the kitchen thinks in, and selling by the dozen keeps unit pricing simple when you confirm the total by email. The need-by date carries the 48-hour bake-to-order minimum in its description, filtering out tonight's emergency requests before they reach your inbox. The wrapped question looks small but changes both labor and use case: individually wrapped means wedding favors, bake sales, and teacher gifts, worth knowing before you quote. "Who's this batch for?" doubles as gift detection, since a recipient name that differs from the email tells you to skip the price slip in the box.
Drop cookies only. Decorated custom cookies stay out. Royal-icing work with logos and color matching is design labor for a custom order form with references and a consultation, not drop cookie flow. Delivery scheduling stays out too: most cottage bakers do porch pickup, and adding courier logic to a $40 order helps no one.
Who fills the weekend. Cottage-license bakers taking weekend orders through a bio link, parents running seasonal cookie side businesses, and school clubs pre-selling dozens for fundraisers where the tally must be exact before flour is bought. Holiday and bake-sale weeks lean on it hardest, when a dozen small orders would otherwise scatter across texts and sticky notes.
Season it, then hand it off. Swap flavors seasonally; pumpkin snickerdoodle in October sells itself, and the option edit doubles as your announcement. Cap each weekend by closing after a set number of responses, sized to your oven. Turn on notifications so orders ping your phone, and use the CSV to sum dozens per flavor before shopping for butter. If wrapped orders outgrow the rest, give favors their own form with quantity tiers. The ending promises a confirmation email with the price, and payment at pickup. For cottage-food sellers that keeps things simple, and many local rules favor direct exchange; confirming the total in person is where repeat customers get made.
Frequently asked questions
How is the price set if the form takes no payment?
You confirm the total in your reply email: dozens × your per-dozen rate, plus wrapping if you charge for it. Payment happens at handoff, cash or however you like.
Can I limit orders to what my oven can handle?
Set a response cap in Settings sized to your weekend capacity. The form closes itself with your message when the batch is full.
How do I know how much of each flavor to bake?
Export the CSV and tally the flavor column against dozens; five minutes with a spreadsheet turns the weekend's orders into a shopping and bake list.
Do buyers get a confirmation automatically?
They see your custom ending screen immediately, and you reply personally by email to confirm flavors, total, and pickup, which is what the email field exists for.