Describe your berries, prices, and pickup plan. Makeform turns the details into a strawberry order form for customer selections, quantities, contact details, fulfillment, and payment status.
Send orders to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, adjust it, or send it into the Makeform builder. The example structure is not a live AI result.
Audience
Local customers reserving berries before market day
Format
Product order form with pickup windows
Prompt size
249 chars
Example form structure
Product order form with pickup windows
Customer name, mobile number, and email
Choose a variety and package size
How many packages would you like?
Select a Saturday pickup window
Payment method and order notes
Suggested routing tags
New orders
Payment due
Ready for pickup
Keep package size and quantity separate so orders are easy to total.
Step 1
Offer
varieties, packages, prices, and dates
Step 2
Order
customer, quantity, seller, and pickup choice
Step 3
Prepare
totals grouped for picking and packing
Step 4
Distribute
payment checked and order handed over
Why use an order form
Texts and handwritten sheets separate package, payment, and pickup details. A structured strawberry order form records them consistently.
Name quarts, flats, or fundraiser bundles with prices, then collect a numeric quantity for totaling and packing.
Show location-specific windows or reveal an address only for delivery, keeping unrelated questions out of the order.
Keep buyer, seller, quantity, fulfillment, and payment fields together from packing through handoff.
Built for berry season
Choose a flow, then replace its products, prices, dates, sellers, and locations.
Reserve packages and sort orders by variety, size, quantity, and pickup window.
Credit a student, classroom, player, or team while keeping buyer and distribution details together.
Offer location-specific slots and request an address only for delivery.
Combine arrival slots, container quantities, pre-picked add-ons, and a farm notice.
Order workflow
Start with packing and distribution details, then edit the generated structure before sharing it.
Provide the seller, varieties, packages, prices, and available fulfillment methods.
Add current products, required quantities, seller attribution, pickup windows, and conditional delivery fields.
Share a link or QR code and route responses to the coordinator's connected workflow.
Group spreadsheet quantities by product and location, then flag payment statuses needing attention.
Form vs messages vs paper
Preserve package, quantity, buyer, seller, payment, and fulfillment details without reinterpreting each order.
Field guide
Capture the decisions that affect picking, packing, payment, and handoff.
Buyer details
Collect contact details for changes or missed pickup. Keep the buyer separate from the fundraiser seller.
Berry options
Separate variety from package size when both affect packing, and display each matching price.
Quantity & totals
Use required number fields, with a separate quantity for every package buyers can combine.
Fulfillment
List actual pickup windows and reveal address details only for delivery orders.
Payment tracking
Record payment method and status separately so coordinators can reconcile orders consistently.
Confirmation & changes
Repeat the pickup details and provide one route for corrections before packing begins.
Related tools
Use broader produce, pre-order, fundraising, or payment forms for a larger campaign.
Sell strawberries alongside vegetables, herbs, eggs, and other farm products in one produce catalog.
Open toolStart with a general product reservation flow when the offer extends beyond one berry crop.
Open toolOrganize fruit-sale buyer details, seller attribution, product quantities, and distribution choices.
Open toolCreate a broader campaign form for supporters, donations, and fundraising activity beyond berry orders.
Open toolCollect payment-focused details when checkout is the central task rather than product selection.
Open toolBuild a card-payment-specific form for workflows that require separate payment collection details.
Open toolFAQ
Practical answers for farms, schools, teams, and community groups planning berry pre-orders.
Include buyer contact details, variety, package, quantity, price, total, payment status, and fulfillment. Fundraisers should also capture the student, classroom, member, or team credited. Keep core order details in structured fields.
Name each package with its price and pair it with a required whole-number quantity. If buyers can combine packages, use one quantity field per item for cleaner totals.
Yes. Add a seller dropdown or fields for student, classroom, grade, team, or member. Keep these separate from buyer details. Consistent seller choices simplify grouping and distribution.
Yes. A pickup choice can show location and time windows, while delivery reveals address instructions. Remove unavailable windows as the distribution schedule changes.
State the deadline and availability. Use inventory or choice capacity when supported; otherwise monitor response totals and close or update sold-out options. Explain your substitution process when weather changes the harvest.
Record the accepted method, expected amount, and payment status. Test any connected online payment flow before sharing. For seller-collected cash or checks, use consistent received and pending statuses.
Yes. Makeform provides unlimited free forms and responses for generating, editing, publishing, and collecting orders. The paid tier removes the Makeform badge.
Send structured product, quantity, seller, location, window, and payment fields to your spreadsheet. Group products for packing, then sort customers by location and window for handoff.
Get berry pre-orders out of messages and notebooks.
