A farm selling into a few different channels can end up facing three different kinds of audit in the same year: one commissioned by a specific buyer, one run by an accredited third-party certifier against a published standard, and possibly a government inspection with legal force behind it. They can feel like the same exercise wearing different badges, and in some ways they are — but the reader on the other side of the table, and what they can do with the result, differ enough to matter.
What they are not is three separate recordkeeping systems. Underneath all three is the same set of records — water, training, sanitation, harvest, traceability — being read by different audiences for different reasons, which is the whole premise behind preparing for a food safety audit: build the records once, well, and let whichever reader shows up read them.
Each scheme sets its own requirement. Which audits a farm must undergo, what each one covers, and how a result is scored is set by the buyer, the certifying body, or the regulator running it, not by this page. This page describes the shape of the differences between audit types, not a substitute for any one of them.
A buyer audit answers to one customer
A buyer audit exists because a specific customer wants assurance before continuing to purchase from a farm, and it is conducted against a standard that buyer chose — sometimes their own, sometimes a recognized third-party scheme they require as a condition of the relationship. The result of a buyer audit is, first and foremost, a decision that buyer makes about continuing to do business. It may not transfer to any other customer at all, which means a farm selling to several buyers with their own audit programs can face a version of the same review multiple times a year, each time for an audience that only cares about its own result.
The relationship also shapes the tone of the review in a way worth naming. A buyer’s auditor, or an auditor hired on the buyer’s behalf, is ultimately reporting to a customer who has a commercial stake in the answer — sometimes that means more familiarity with the operation from prior seasons, and sometimes it means more specific, relationship-driven requirements layered on top of a generic standard. Either way, the audit is happening inside a commercial relationship, not outside one.
A third-party certification answers to whoever accepts the scheme
A third-party certification is different in structure: an accredited certifying body — independent of any single buyer — audits the farm against a published standard and issues a certificate. The value of that certificate is that it is, in principle, portable: any buyer who recognizes that particular scheme can accept the result without running their own audit. This is the main reason farms pursue third-party certification at all — one audit, potentially satisfying several buyers, rather than a separate audit for each.
The word “potentially” matters. Not every buyer recognizes every scheme, and some buyers layer their own additional requirements on top of a certification they otherwise accept. A third-party certificate reduces the number of audits a farm faces; it does not always eliminate the need for a buyer-specific review as well.
Because the certifying body is independent of any single buyer, the audit itself tends to be a more standardized, checklist-driven exercise than a buyer audit shaped by one customer’s particular concerns. That standardization is the whole point — it is what makes the result legible to a buyer who was not in the room for the audit at all.
Government programs carry a different kind of consequence
A government food safety inspection or audit sits apart from both of the above, because its authority comes from regulation rather than from a commercial relationship. It can run independently of whatever buyer or certification audits a farm also undergoes, and its findings can carry legal consequences that a buyer’s decision not to continue purchasing does not. Whether and how often a government program applies to a given operation is a question for the regulator with jurisdiction over it, not something this page — or any buyer or certifier — can answer on the regulator’s behalf.
Different readers, but the same underlying documents
What makes all three manageable together is that they mostly draw on the same pool of records. A buyer auditor, a third-party certifier, and a government inspector are all, in one form or another, going to ask about water testing, worker training, sanitation, and traceability, because those categories map to the same handful of ways food actually becomes unsafe, regardless of who is asking. The specific checklist, the scoring rubric, and the acceptable ranges differ by scheme — but the underlying discipline of keeping a complete, contemporaneous record serves all of them at once.
This is the practical argument for building one solid recordkeeping habit rather than a separate system per buyer. A farm that keeps a genuinely complete water testing record, done right, does not need a different version of that record for each audience — it needs the same record, available whenever any of them asks.
The power to walk away sits in different hands each time
The practical difference that matters most day to day is not the paperwork; it is who can walk away. A buyer audit's consequence is usually commercial and immediate — this customer stops buying. A failed third-party certification can cost access to every buyer who requires that scheme at once, which is a wider door to lose. A government finding can carry consequences neither of the other two can reach. None of that changes what belongs in the underlying record; it changes how much is riding on getting it right, and for whom.
This is worth internalizing before the first audit of any kind arrives, because it changes how a farm should read a poor result. A weak finding from one buyer’s audit is a signal about that relationship. A weak finding in a third-party certification is a signal about every relationship that depends on it. Treating the two as equally contained is a common and expensive misjudgment — the same underlying gap can have a very different reach depending on which door it walks through.
Farm40 exports the same underlying records — input applications, water and sanitation entries, harvest and traceability data — in the form most reviewers ask for, regardless of which of the three is knocking. The limit stays constant across all of them: an export formats what was entered. It cannot tell a buyer, a certifier, or a regulator anything the farm did not first write down, and it has no view into which scheme a given buyer will ultimately accept.