Food Order Form Template
A takeout ordering form for kitchens without an app — mains, sides, pickup time, and a mobile number to text when the bag is ready.
Order ahead and skip the line. We'll text you when it's ready — pay at the counter when you collect.
Ordering apps take a cut of every sale and bury small kitchens in tablet chaos. This form is the counter-service alternative: customers order from a link or a QR code on the door, the kitchen sees a clean ticket, and payment happens where it always has — at the register, with no commission skimmed off the top.
Why these fields. The mobile number is the operational heart of the form. Takeout runs on the "it's ready" text, so the label promises exactly that, and customers type their number more carefully when they know what it's for. Mains and extras are separate multi-select blocks with prices in the labels — separating them mirrors how people actually decide (protein first, temptation second) and keeps the extras list from crowding the money question. The mains block requires at least one choice and caps at six, which covers family orders without letting a typo turn into a forty-burger ticket. Pickup time is a time block with the 20-minute kitchen reality stated in the description, heading off the 12:00 order for a 12:05 pickup. The instructions field is where "no onions" lives — free text, because modifier grids are where ordering apps go to become unusable.
What we left out. Quantity-per-item inputs. For counter food, selecting an item twice is rare enough that a note in instructions ("two burgers") covers it, and the simpler form finishes faster — speed is the entire pitch of order-ahead. We also left out delivery: this is a pickup form, and pretending otherwise means building a dispatch operation into a lunch rush.
Who uses this. Food trucks that post the link on the window, cafes running lunch pre-orders for the office crowd, pop-up kitchens doing weekend menus, and church or school kitchens taking plate orders for fundraiser Fridays.
Make it yours. Rewrite the menu options weekly — edits go live the instant you save, which makes this form double as a specials board. Turn on email notifications or, better for a busy kitchen, add a webhook that posts each order into a kitchen Slack channel or prints via your ticket tool. During service, keep the responses view open on a tablet: it is the order queue, newest on top. When the kitchen hits capacity, close the form from Settings with a message like "Sold out — back at 5pm," which reads as success, not failure.
On payment. The ending says pay at pickup, and that is the feature: no processor fees, no refund workflow when someone no-shows, and the register you already trust does what it is good at.
Frequently asked questions
How does the kitchen see orders as they come in?
Keep the responses view open — new orders appear at the top with every item and note. For busier services, a webhook can push each order straight into Slack or your ticketing tool in real time.
Do customers pay online when they order?
No. The form fires the ticket; payment happens at the counter on pickup. That keeps 100% of the sale with the kitchen and avoids refund headaches for no-shows.
Can I update the menu day to day?
Yes — edit the option labels and prices anytime and the live form updates immediately. Many kitchens rewrite the mains list each morning as a specials board.
What happens when we sell out mid-service?
Close the form in Settings with a custom message ("Sold out — back tomorrow"). You can also cap total responses so the form closes itself after a set number of orders.