There is a specific way order forms go wrong. Somebody copies a template built for a purchase-order department, ends up asking a customer for a billing address and a PO reference to buy two dozen cookies, and then wonders why only a third of the people who opened the form finished it.
A small business order form has one job: capture enough to fulfil the order, and nothing else. Here is the list that does it, in the order it should appear on the page.
The nine fields that earn their place
1. The items themselves, with prices
This is the form. Everything else is logistics. Each item needs a name a customer would recognise, a unit price, and a quantity control.
Name items the way they get said out loud, and put the yield in the name: "Family lasagna tray · feeds 4", "Cinnamon rolls · 6-pack", "Club tee · Navy · L". The single most common cause of a wrong order is a customer who thought "tray" meant something different from what you meant. The name is where you fix that, not the notes field.
If you sell variants — sizes, colours, flavours — you have two options. List each combination as its own line, which gives you a breakdown you can hand straight to a printer or supplier. Or use one line plus a dropdown, which is tidier on screen but leaves you counting variants by hand afterwards. For anything you have to order in from a supplier, use separate lines.
2. Quantity, with a limit
A quantity stepper per item, capped at what you can actually produce. The cap is what makes the form safe to leave running while you sleep. Without one, you are checking your phone at midnight to see whether you have oversold.
3. Full name, required
Not "first name" and "last name" as two fields — one field, required. Handover day is a name-by-name exercise and a box labelled "Sarah" is a box you will hand to the wrong Sarah.
4. Phone number, required
The most useful field on the form after the items. When a batch runs twenty minutes late, one round of texts prevents a lobby full of people. Ask for a mobile, and validate that it looks like a number so you do not discover a typo at the moment you need it.
5. Email address
Two reasons: it is how a confirmation reaches them, and it is the beginning of a customer list you own rather than rent from a social platform. Optional if you already have their phone number, but ask.
6. Pickup or delivery
A single-choice question, not a free-text one. If you deliver, this is the field that decides whether the next question appears — and it is worth stating your delivery radius and fee right in the option label: "Delivery (within 5 miles · $6)". People self-select correctly when the constraint is visible.
7. Date and time slot
Use a dropdown of slots you have chosen, not a free date picker and not an open text box. Two things happen when you offer slots: collections spread out across the day instead of piling into one hour, and you stop receiving orders for the Tuesday you are closed.
For a delivery address, one long-text field beats five address fields on a phone. You are not validating it against a postal database; you are giving a human directions.
8. Notes, allergies, or special instructions
One long-text field. If you sell food, make it required and label it "Allergies (write 'none' if none)" — a required field is how allergy information ends up in writing, attached to the order, instead of in a comment someone half-remembers.
9. How did you hear about us?
Optional, a dropdown, and the only field on this list that is for you rather than the customer. Four or five options — Instagram, a friend, walked past, market stall, other. Three months of answers will tell you which channel to stop spending time on.
Showing prices and totals
Show the unit price beside every item, and a running total that updates as quantities change. This is not a nicety. It does three measurable jobs:
- It qualifies people before they order. Someone who finds out the price at the end and abandons has cost you nothing; someone who finds out at pickup has cost you an awkward conversation and probably the sale.
- It ends arithmetic disputes. A total the customer watched change as they chose is a total they accept. A total you calculate afterwards is a total they check.
- It raises order value. When adding a second loaf visibly costs $8, people add the second loaf. When the cost is invisible, they do not risk it.
This is the one thing generic form builders genuinely cannot do. Google Forms and Microsoft Forms have no concept of a price, so a total means exporting to a spreadsheet and writing a formula afterwards — see the Google Forms walkthrough for exactly how that ends up looking. If your form is priced, that is the feature to shop for.
Delivery fees, minimums, and tax
State them as plain text on the form, near the total, in the language a customer uses: "Delivery $6 within 5 miles. $40 minimum for delivery. Prices include tax." Do not try to compute tax on an order form for a business that collects at pickup — your point of sale does that, and duplicating it just creates two numbers that can disagree.
Deposits: when to ask, how much
The rule is simple. Take a deposit when a cancellation leaves you holding something you cannot resell.
| Order type | Deposit | Why |
|---|---|---|
| Weekly menu drop, pickup | None | Unclaimed items sell at the counter. Chasing deposits costs more than the occasional no-show. |
| Custom cake or decorated set | 50% at booking | Personalised work is worthless to anyone else, and the date is blocked out either way. |
| Catering over ~$300 | 25–50%, balance on the day | You buy ingredients against the headcount. A deposit is what makes the headcount real. |
| Printed merchandise | Full payment up front | The print run is committed before anyone collects. Nobody else wants a shirt with your club's name on it. |
| Wholesale to trade accounts | None — invoice on terms | Shops pay on 14 or 30 day terms. Asking for a deposit signals you are new. |
Whatever you choose, write the cancellation terms in one sentence on the form itself: "Deposits are non-refundable within 72 hours of pickup." A sentence the customer agreed to at ordering time is worth more than any policy page.
Pickup details: the part that saves your Saturday
Everything above concerns getting the order. This part concerns getting through the day it is collected.
- Put the address and the slot on the confirmation, not only on the form. People find the confirmation email at the moment they are getting in the car.
- Slot in fifteen or thirty minute bands and cap how many orders fit in each. Ten pickups between 10:00 and 10:15 is not a slot, it is a queue with a name.
- Give each order a reference number. Short, visible on the confirmation, searchable by you. It is the answer to "I definitely ordered two."
- Send one reminder the day before with the slot, the address, and the total. It measurably reduces no-shows, and it lets people correct a mistake while you can still act on it.
- Mark orders fulfilled as they leave. At the end of the day, what is left unticked is your call list — not a memory exercise.
What to leave off
Business name, unless you sell to businesses. Billing address, unless you ship. Job title, ever. A CAPTCHA, unless you are actually getting spam. "Terms and conditions" as a separate required checkbox on a $30 order — put the one sentence that matters on the page instead.
And leave off the second page. Every form builder will offer you sections and multi-step flows; on a phone, on a $40 order, a single scrollable page finishes more often than a wizard does.
A worked example
A caterer taking Friday pre-orders, in full: six menu items with per-head prices and caps; quantity steppers; full name (required); mobile (required); email; pickup or delivery single-choice with the radius in the label; a pickup-window dropdown with four slots; a required dietary-requirements long-text field; and an optional "how did you hear about us". Nine questions. Under ninety seconds on a phone. Every piece of information the kitchen needs, captured once, in writing, before anybody starts prepping.
That is the whole art of it. The hard part was never the form — it is being disciplined enough to keep it short.
