Most traceability advice is about the product you grow — the field it came from, the lot code it carries, the customer it ships to. That is the forward half of the picture. The backward half starts before any of that: with the seed, the amendment, the crop protection product, or the day-old chicks that arrived on your farm from somewhere else. You did not grow those. You received them, and the moment you did, you became responsible for knowing something about where they came from.
This is the least glamorous corner of traceability, and it is also the one most likely to be skipped, because it feels like paperwork about someone else’s business rather than your own. It is not. One up, one back means exactly what it says: your one-back is every supplier you bought from, and the obligation to know them is yours, not theirs.
What counts as adequate supplier verification varies by input, buyer, and certifier. A seed purchase, an organic amendment, and a crop protection product each carry different documentation expectations, and your certifier or buyer sets the bar, not this page. What follows describes the practice of keeping a record — for the standard itself, read your certification body’s requirements.
You are responsible for what came onto your farm
It is easy to think of traceability as something you owe forward — to your buyer, to the regulator chasing a complaint about your product. Half of it runs the other way. If an input you used turns out to be the source of a problem — contaminated seed, an amendment that was not what its label claimed — the trace runs back through you to whoever sold it to you, and the first question asked is simple: what do you know about that supplier?
A farm with no answer to that question has not done anything illegal by most standards, but it has left itself with no way to separate its own practice from a problem that originated upstream. A supplier record is not a favor to your certifier. It is the thing that lets you say, credibly, that a contamination event traces to a specific shipment from a specific supplier rather than to something you did.
This matters even for inputs that never touch a customer directly. A pallet of packaging film or a batch of clamshells is not something you sell, but it is something that touched product you did sell, and a supplier problem with either can implicate your farm just as surely as a problem with seed or feed. The habit of asking “where did this come from, and what do I have on file about it” is worth applying to anything that arrives on the farm and touches what you ship, not only to inputs applied to a field.
The record is short, and it is about the shipment, not the relationship
A supplier approval record does not need to evaluate a supplier as a business. It needs to establish, for what you actually bought: who sold it, what it was, when you received it, and what basis you have for trusting it — a certificate of analysis, a seed tag, an organic certificate, or in the plainest case, simply an invoice that includes a lot or batch number. The lot number is the piece that matters most and is easiest to lose, because it is often printed small on a bag or a tag that gets thrown away once the contents are used.
Keep that lot number even after the packaging is gone. It is the single fact that lets a recall notice from your supplier — one you have not received yet, for a product you already used — resolve to your farm specifically, rather than requiring you to guess whether the notice applies to you.
A practical habit costs almost nothing: before discarding a seed tag, a feed bag, or an amendment container, transcribe the lot number onto whatever record you already keep for that purchase — a receipts folder, a spreadsheet row, a photo taken on a phone. The transcription takes seconds. Recreating a lost lot number after the packaging is in a burn pile takes a phone call you may not be able to make, to a supplier who may not remember either.
An informal supplier is still a supplier
The instinct to skip this discipline is strongest with small or informal sources — a neighbor’s saved seed, a feed mix bought off a handshake, a local hatchery with no formal paperwork. The instinct is understandable and the conclusion is wrong. The obligation is not proportional to how formal the transaction felt; it is proportional to whether the product entered your operation and could plausibly carry a problem forward. A record for an informal purchase can be equally informal — a note of who, what, and when, in your own hand — but it still has to exist.
Where documentation genuinely is not available, write that down too. “Bought from Neighbor X, no certificate offered, asked and was told none exists” is a real record of a real limit. It is worth more than silence, because it shows the question was asked, even though the answer was thin.
Supplier records and your own lot codes share a boundary
The place a supplier record actually earns its keep is at the join between what you received and what you grew. An input applied to a planting — logged as part of your input application records — should reference the same lot or batch number that appears on the supplier record for that product. Without that shared reference, the two records are each individually true and jointly useless: you know you bought seed from a supplier, and you know you planted seed on a date, but nothing connects the two well enough to answer “which shipment of seed is in this field” when a supplier recall arrives.
This is the same discipline that makes forward traceability work, run in the opposite direction. A lot code is only useful if it is carried forward to the sale; a supplier’s batch number is only useful if it is carried forward onto the planting record it was used on.
Where a linked record turns a recall notice into a lookup
If a supplier issues a recall on a product lot, the question you need to answer fast is which of your plantings, if any, used that lot. Farm40 records input applications with an active ingredient, a rate, and a lot number as first-class fields tied to the planting they were applied to, so a supplier lot number can be searched against your own application history directly, rather than requiring you to reread every input record from memory. The limit is the same one that runs through the whole system: it can only search what was entered, so an application logged without its lot number is invisible to that search, no differently than if it had never been recorded. For how this backward half connects to the rest of the discipline, see the traceability guide.