Every certified organic operation faces the same annual moment: an inspector at your table, pointing at a product you sold months ago and asking to see the paper trail behind it. The National Organic Program regulations (7 CFR 205.103) require records that fully disclose all activities, are sufficient to demonstrate compliance, and are kept for not less than 5 years — and your certifier will test those records live, not just read them. Here is what the annual inspection actually walks through, and how a lot-level batch ledger answers most of it before the inspector asks.
What 7 CFR 205.103 actually requires
The regulation is short but demanding. Certified operations must maintain records that fully disclose all activities of the operation, are adapted to the particular business, and are sufficient to demonstrate compliance with the organic regulations — and those records must be kept for not less than 5 years. They must also be made available to the certifier and the accredited certifying agent during the annual inspection.
“Adapted to the particular business” means there is no mandated format — a spreadsheet is technically acceptable. But “sufficient to demonstrate compliance” is tested in real time during the inspection, and a records system that takes an hour to answer a lot-level question tends to generate follow-up questions of its own.
What the annual inspection walks through
After the facility walkthrough, the inspection becomes a records exam. Inspectors typically want to see the full chain for the products you handle:
- Supplier organic certificates for every organic input you purchased
- Receiving records — what arrived, from whom, in what quantity, on what date
- Production or handling records if you repack, combine, or transform product
- Sales and shipping records tying finished product to customers
- Inventory adjustments — shrink, damage, and corrections, with reasons
Then come the two live tests inspectors commonly run: the traceback and the mass balance. These are where a filing cabinet full of individually fine documents can still fail as a system.
Anatomy of a traceback exercise
The inspector picks a product you actually sold — often from an invoice or order they choose, not one you offer — and asks you to trace it backwards to its source: which lot fulfilled that order, when that lot was received, which supplier it came from, and whether that supplier held a valid organic certificate covering the product at the time. A clean traceback runs from a single sold unit all the way to a certificate in minutes.
The common failure point is the order-to-lot link. Most sellers can show what they bought and what they sold; far fewer can show which specific lot filled a specific order. If your fulfillment system deducts stock without recording the lot, the traceback stalls at exactly the step the inspector cares about. Running a mock recall exercise before inspection season is the cheapest way to find that gap yourself.
Anatomy of a mass-balance exercise
The mass balance is the traceback’s mirror image: instead of one order, the inspector takes a period and compares organic product in versus organic product out. If you received 500 kg of an organic ingredient, your sales, current inventory, waste, and documented adjustments for that ingredient should reconcile to roughly 500 kg. Selling more organic product than you bought is the classic signature of fraud, which is exactly why certifiers run the exercise.
UNEXPLAINED GAPS READ AS FINDINGS
A mass balance that does not reconcile is not automatically treated as fraud — but an unexplained difference becomes a noncompliance you must answer. A correction entry with a recorded reason (“12 units damaged in receiving, disposed 14 March”) turns the same gap into a documented, closed event.
The records a batch ledger answers automatically
Both exercises are queries against the same underlying data: lot-level movements. A per-lot batch ledger — every receipt, every order deduction, every correction, every transfer — produces the answers as a side effect of normal fulfillment:
| Inspector asks | Record that answers it | Batch ledger entry |
|---|---|---|
| Which lot filled this order, and where did it come from? | Order-to-lot link plus receiving record | Per-order deduction with the order reference, tied to a receipt showing supplier, date, and quantity |
| Why does inventory not match purchases? | Adjustment log | Correction entries, each with a recorded reason |
| Did product move between locations? | Transfer record | Transfer entries between locations, per lot |
| Show me everything that happened to this lot | Complete lot history | The full ledger for the lot, from receipt to final deduction |
If your records live in tabs and email threads, reconstructing this table for one lot is an afternoon. If they live in an audit-ready batch tracking system, it is already on screen when the inspector sits down.
Inspection-ready lot records as a side effect of shipping orders
TraceLot keeps a per-lot ledger automatically as you fulfill through Veeqo or Shopify — receipts with supplier and quantity, order deductions with order references, corrections with reasons, and transfers — so tracebacks and mass balances are lookups, not projects.
See how audit-ready records workAttach the certificates to the lot, not the filing cabinet
A traceback ends at a document: the supplier’s organic certificate, and often a certificate of analysis for the ingredient. Storing those in a shared drive means matching filenames to lots under time pressure. Attaching the certificate directly to the lot it covers — with a custom batch field carrying the COA number — means the document surfaces the moment the lot does. One lot, one screen, everything the inspector asked for.
Why certifiers tightened traceability
If your last few inspections felt more traceability-heavy than they used to, that is deliberate. High-profile organic fraud cases pushed the USDA to strengthen enforcement and oversight of organic supply chains under the Strengthening Organic Enforcement effort, and certifiers have responded by probing traceability harder — more tracebacks, more mass balances, more supply-chain questions. The specifics vary by certifier and operation, so check current guidance from your certifier and the USDA; the direction of travel, though, is clear. For food and beverage sellers, the same lot records increasingly serve organic, retailer, and recall requirements at once.
Frequently asked questions
How long must certified organic operations keep records?
Under 7 CFR 205.103, records must be maintained for not less than 5 years, must fully disclose all activities of the operation, and must be sufficient to demonstrate compliance with the organic regulations.
What is a mass-balance audit in an organic inspection?
A mass-balance exercise compares organic product purchased against organic product sold plus inventory, waste, and documented adjustments over a period. If more organic product went out than came in, the records cannot demonstrate compliance — which is why inspectors commonly run the check.
What is a traceback exercise during an organic inspection?
The inspector selects a product the operation sold and asks it to be traced backwards through lot records to the receiving record and the supplier, including the supplier’s organic certificate. The critical link is knowing which specific lot fulfilled which specific order.
Does using batch tracking software make my operation organic compliant?
No software makes an operation compliant — certification decisions rest with your certifier, and compliance is achieved by your people and processes. What a batch ledger does is keep the lot-level records that let you demonstrate compliance quickly during tracebacks and mass balances.
Never ship expired stock again.
TraceLot adds batch tracking, FEFO allocation, and audit-ready records to Veeqo and Shopify. First month free.