Produce Box Order Form Template
Farm-box signups with size, frequency, swap-outs, and pickup point. The harvest decides the contents; your members decide the rest.
Get a box of whatever's best on the farm this week. You choose the size and where to collect, and the season chooses the vegetables. Settle up monthly with the farm.
What's in the box this week, plus pickup reminders.
Up to two items, and we'll sub in more of something else.
A produce box program lives or dies on a single trade: members give up choosing what they eat, and in exchange the farm gives them the best of what the ground produced that week. The order form honors both sides. It captures the choices members need (size, rhythm, location) while protecting the farm's right to let the season write the menu.
Box size options carry feeds-how-many language and prices, because "Solo versus Family" answers the real question, will this rot in my crisper, better than bushel weights ever could. Weekly-versus-biweekly exists because the biweekly option converts the hesitant household that loves the idea but fears the volume; farms that skip it lose those members by August. Swap-outs cap at two items in the description, because a full preference list would break pack-line efficiency, while "never beets" costs nothing and prevents quiet quitting. The pickup point dropdown carries days and hours in the labels, doubling as the schedule. Add-ons (eggs, honey, flowers, bread) are where farm margins live, and putting them at signup normalizes them from day one.
Item-level box building stays out; that's a grocery store, and the pack line can't run twelve custom manifests. Home delivery stays out too, since routes are a second business and the pickup-point model keeps the farm farming. Payment fields stay out as well: farm shares settle monthly, in the high-trust rhythm small agriculture runs on.
CSA farms filling seasonal memberships use it. So do market gardeners adding a box program to smooth cash flow, food hubs aggregating several farms into one pickup network, and flower farms running bouquet-subscription variants of the same model.
Rename pickup points with their real hours, and update add-ons as the season changes: eggs sell out, flowers arrive in June. Cap total responses at your pack-line capacity so membership sells out without overbooking the pack line. The weekly harvest email keeps members engaged, and a CSV export builds the pack list and the per-pickup-point manifests each week. When the season ends, close the form with a "join the spring list" message pointing to your waitlist form.
Every-other-week members split your season into an A-week and a B-week, and when signups land unevenly the harvest swings between overrun and underrun Fridays. Assign each new biweekly member to whichever week is lighter, since the frequency column plus signup order makes the split obvious in the export, and tell them their week in the first harvest email. A balanced calendar lets the field get picked at a steady rate all season, the whole point of selling a rhythm rather than an inventory.
The ending says totals settle monthly by invoice or at the stand. Members are paying for a relationship with a farm, and the money should feel that way too.
Frequently asked questions
How do members pay for their boxes?
Monthly, by invoice or at the stand; box prices are in the size labels so totals are predictable. The form manages membership and pack lists, not transactions.
Can members choose exactly what goes in the box?
The harvest decides, which is the CSA model working as intended. The swap-outs field handles real dislikes (up to two items) without breaking the pack line.
How do I build weekly pack lists per pickup point?
Export the CSV and filter by the pickup-point column: box sizes and add-ons per location are your manifests, and swap-outs flag the boxes that need a substitution.
What happens when the season fills up?
Set a response cap at your capacity, and the form closes itself with your message. Point latecomers at a waitlist form so next season starts with a queue.