How to Manage Farm Operations, Inventory, and Sales

A small farm is six sales channels and three production cycles running at once. CSA subscribers expect their box on Wednesday. The farmers market opens at 7 a.m. Saturday. The farm stand has to be stocked Friday afternoon. The chef at the bistro downtown texts at 11 p.m. asking what you'll have Tuesday. Meanwhile the layers need feed, the Roma tomatoes need to go in this week or they won't ripen before frost, and the H-2A worker who showed up in March goes home in November.

The farm that wins is the one whose tomatoes show up at 7 a.m. Saturday at the market AND on a chef's plate Tuesday — same harvest, different invoice, no double-counting. Most farm software solves one slice of that. QuickBooks for the books. Square for the market. Mailchimp for the CSA newsletter. A spreadsheet for the planting schedule. A second spreadsheet for the chef invoices. By August, the spreadsheets disagree with each other and you're running the farm from memory.

This guide walks through the five operational stacks a diversified small farm needs — crop and livestock, CSA, farmers market, restaurant and wholesale, and labor and compliance — and how to run all of them on one platform instead of six.

Production planning is the spine. Everything downstream — what you can sell, what you can promise the chef, what goes in the CSA box — comes from what's actually in the ground or in the barn.

What to track per crop: variety, planting date, days-to-maturity, expected harvest window, yield estimate, square footage or row count, succession number. The yield estimate is what tells you whether you have 40 lbs of tomatoes or 400 lbs hitting the same week. That's the difference between a $200 farmers market and a chef relationship.

What to track per livestock group: breed, ear-tag or band ID, birth date, weight gain, vaccination dates, breeding cycle position, expected slaughter or laying-end date. Pasture-raised eggs need flock-age tracking because dozen-per-bird drops after week 70. Beef cattle need finish-weight projections so you can pre-sell quarters six months out.

Crop rotation is the rule that ties planning to soil health: brassicas don't follow brassicas, nightshades don't follow nightshades, legumes go where heavy feeders just left. A field map with the last three seasons of plantings prevents the rotation mistakes that show up as disease pressure two years later.

A farm CRM with custom record types holds all of this — plantings, livestock groups, field plots, harvest logs — in one place, with the harvest log feeding the inventory that the CSA, market, and chef invoices all draw from.

CSA is recurring revenue with a logistics problem. The members paid in March. You owe them a box every week from May through October. Miss one week and the email thread starts.

What the system needs to do: bill subscriptions on the schedule the member signed up for (full season, half season, monthly installments, weekly), generate the weekly box manifest based on what actually got harvested, route the box to the right pickup site (farm stand, three drop-offs around town, home delivery for the premium tier), handle vacation holds without losing the member's place in the queue, and surface a member portal where they can update their card, swap a vacation week, or pause for a month.

The weekly box content is where most CSAs leak quality. The harvest comes in Tuesday afternoon. Someone has to decide what's in this week's box, write it on a card that goes in every box, and post it to the member newsletter. If that decision happens in a group text and a Google Doc, the card and the newsletter and the box content stop matching by week 4.

Doing this on one platform means: subscription billing pulls from the same customer record as the CSA member portal. The weekly harvest log generates the box manifest. The newsletter pulls from the manifest. One source of truth, one button, three outputs.

Saturday morning is the most operational hour of the week. Tent up by 6:30. Tables loaded, signs out, scale calibrated, change box opened, first customer at 7:00. By 1 p.m. you need to know what sold, what's left, and what you can promise the chef who walked the market and asked about peppers.

What the market POS needs: mobile checkout (phone or tablet, cellular fallback because rural market wifi is a fiction), weighed pricing for produce sold by the pound, unit pricing for bunches and pints, EBT/SNAP support if you take it, and a tip option for the high-touch customer base. The cart should accept cash, card, EBT, and farm-store credit on the same transaction without requiring a different app.

Market-day inventory tracking is the part that gets ignored. You loaded the truck with 60 lbs of tomatoes, 40 lbs of cucumbers, 30 dozen eggs, and 12 quarts of blueberries. By 1 p.m. the system should tell you you sold 52 lbs of tomatoes, 38 lbs of cucumbers, 28 dozen eggs, and 9 quarts of blueberries — and what's left goes back to the farm for the CSA box, the farm stand, or the chef.

That ending inventory is what unlocks the rest of the week. The chef text at 11 p.m. asking about peppers gets answered from real numbers, not a guess.

Chef accounts are the highest-margin channel and the one that requires the most professionalism. The chef is buying because your tomatoes taste better than the Sysco truck's. They will leave if you become a flake.

What the chef relationship needs: a weekly availability list (sent Sunday night, what you'll have for the Tuesday and Friday deliveries), a clean way to take the order (email reply, text, portal — chef's choice), a delivery route that gets to four restaurants between 8 and 11 a.m. without the produce sitting in a hot van, an invoice that lands in the chef's inbox the same day with line items they can hand to their bookkeeper, and net-15 payment terms tracked so you know who's late.

The weekly invoice cycle is where small farms get burned. You delivered eight times in October. By November you've forgotten which delivery had the substitution, and the chef's bookkeeper is asking why two invoices show different prices for the same lettuce. A wholesale account record that ties every invoice back to the underlying delivery and the underlying harvest log is the only durable answer.

Delivery routes also matter more than they look. A four-stop route at 8 a.m. is one truck-hour. Two two-stop routes is two truck-hours. Routing software that batches deliveries by zone and time window saves a working morning per week.

Family farms become real businesses the day they hire someone. Seasonal labor is when the paperwork gets serious.

H-2A (the agricultural guest worker program) is the most regulated piece. Every H-2A worker requires a job order filed with the State Workforce Agency, housing inspections, transportation, the adverse effect wage rate, and weekly pay records that the Department of Labor can request at any time. Mess up the housing inspection and you can lose the program for a year.

Seasonal payroll is its own problem. You might have two full-time year-round workers, four H-2A workers from April to November, and a dozen weekend market helpers from May to October. Some are W-2, some are 1099, some are paid in farm credit and a meal. The platform that runs the books has to handle all of those without a spreadsheet on the side.

USDA Organic certification, if you carry it, requires a season's worth of records: every input applied to every field, every seed source, every harvest, every wash-pack step. The annual inspection wants to see the records, not hear about them. OSHA records on injuries, training, and PPE are required for any farm with 11+ employees. Both certifications die in a clipboard binder and live in a digital record system.

A single platform that ties workers to time entries, time entries to payroll, payroll to tax filings, and field activity to compliance logs is the version of farm software that survives an audit.