A wholesale sale gives you a customer, almost as a side effect: the invoice exists whether or not you think of it as a traceability record, and it names a business you can call. A farmers market box gives you no such thing. The person who buys six tomatoes and a dozen eggs pays cash, takes a canvas bag, and is gone. You cannot name them, and nothing about the transaction requires that you could.
It is tempting to conclude from this that direct-to-consumer sales sit outside traceability’s reach — that the whole discipline assumes a paper trail a market stand cannot produce. That conclusion is wrong, but understanding why requires separating two questions that get run together: who bought it, and what left the farm. You genuinely cannot always answer the first. You can always answer the second, and the second is most of what traceability actually asks for.
The obligation was never to name the customer
One up, one back — the standard behind most traceability expectations — asks a business to know its immediate supplier and its immediate customer for a lot. At a market stand, your immediate customer is, in a meaningful sense, the market itself, or the channel: a specific date, a specific location, a specific set of lots you brought that day. The individual buyer is one link further down a chain that the standard was never designed to name, because retail sale to an end consumer is the point at which formal traceability requirements generally stop — the same way a grocery store is not expected to know which named shopper bought a given apple.
This does not make the record optional. It changes what the record needs to say. Instead of “lot 0714 went to Riverside Restaurant, forty pounds, June 3,” the direct-sale version is “lot 0714 went to the Tuesday downtown market, June 3, along with lots 0710 and 0712.” That sentence is genuinely achievable, costs almost nothing to produce, and answers the question a recall actually asks: which lots reached the public, and through which channel and date.
It is worth stating plainly why this distinction is not a loophole. A recall exists to stop a specific problem from spreading further and to warn the people who might have it. Both goals are served by knowing which lots went where — you can stop selling the implicated lot immediately, and a public notice naming the market and the date reaches the population who might have bought it just as effectively as a phone call reaches a single named account. What a named-customer system buys you is a faster, quieter warning to one household. What lot-and-channel records buy you, at a fraction of the effort, is the ability to stop the problem and issue that warning at all.
Record the market day, not the customer
The practical unit of record for direct sales is the selling event, not the transaction. Before you load the truck, note which lots are going, in roughly what quantity. That single note — one line, written once per market day or once per CSA pack session — is the entire traceability record this channel requires of you, and it takes less time to write than a single wholesale invoice.
Where a CSA differs slightly from a market stand is that a box list often does exist — you likely know which households received a box in a given week, even without knowing which specific tomato went into which bag. That member list, kept alongside the lot or lots that filled the boxes that week, gets you further than a market stand ever can: a genuine, named forward trace, at the cost of one more line in a spreadsheet you are probably already keeping for billing.
The same logic extends to any channel with a recognizable intermediate structure — a farm-stand honor box, a restaurant that buys direct but resells to diners you will never meet, a food hub that aggregates several farms’ product into one delivery. In every case, find the layer at which a name genuinely exists — the CSA member, the restaurant account, the food hub’s delivery manifest — and keep your lot record joined to that layer. You are never obligated to see past the layer where names stop existing; you are only obligated to have kept the record up to that point.
Put the lot code where the customer can see it
There is one thing a direct-to-consumer sale can do that a wholesale invoice cannot: put the lot code or the harvest date directly in the customer’s hands, on a sign, a twist-tie, or a box insert. It costs nothing beyond printing, because the code already exists from harvest, and it converts an anonymous transaction into one where the buyer can call you back with something more specific than “I think it was two weeks ago.” That single detail is often the difference between a concern you can act on and one you cannot place at all.
It also protects you in the other direction. If a customer reports an issue and the date or code on their packaging does not match any lot you sold in that window, you have a fast, factual way to say so — rather than an argument about memory.
The gap is real, and it belongs to the channel, not to you
Be honest about what a market stand genuinely cannot do: reach a specific buyer directly, by name, the way a wholesale recall notice reaches a named account. That gap does not reflect a failure in your recordkeeping if your lot-and-date records are solid; it reflects a structural property of cash retail sale that public health authorities have already built a mechanism around — the public recall notice, aimed at the whole population that might have bought a lot rather than at named individuals. Your job is to make that notice as narrow and accurate as possible by knowing exactly which lots, dates, and markets are implicated, which is precisely what the one-line-per-market-day record above gives you.
Where this connects back to the rest of your operation is the same place every direct-sale question connects: the lot code has to have been assigned correctly at harvest in the first place, and it has to have stayed intact through any washing or packing that happened before the market. A market-day note is only as good as the lot code it references.
Where a simple record does the whole job
None of this requires a point-of-sale system or a customer database. A notebook line — date, market, lots loaded — kept alongside your harvest sheets is a complete traceability record for this channel. Where Farm40 adds anything is in keeping that market-day note joined to the same lot and harvest records your CSA or wholesale sales already use, so a mock recall does not require a separate process for the direct-sale channel. The limit is the same one that applies everywhere in the system: the join runs on the lot code you enter, so a market-day note with no lot code attached is a note, not a trace. For the wider picture of what a trace has to answer, see the traceability guide and the traceability hub.