Key points
- A declaration is a supplier's assertion, not an independent verification.
- Specificity matters: reference the lot, the standard and the scope.
- High-risk claims should be supported by audit or testing.
Common declaration types
GMO or non-GMO status, allergen presence, absence of processed animal protein, absence of specified additives, radiation or treatment statements, and sustainability or certification scheme claims.
Making a declaration usable
It should reference the product and lot, state the standard or definition applied, describe the basis of the claim, and be signed by an authorised person with a date. Undated blanket declarations are of little value.
Verification for high-risk claims
Where a declaration protects a regulatory or contractual position, support it with scheme certification, audit evidence or periodic testing rather than relying on the statement alone.
What to verify
- Declaration referencing product, lot and applicable standard
- Signed by an authorised person with a date
- Supporting evidence available for high-risk claims
Risks to manage
- Regulatory exposure from an unsupported declaration
- Certification claim not covering the specific product supplied
- Blanket declarations issued once and never renewed
Common mistakes
- Accepting a declaration in place of testing for a critical parameter
- Not checking whether a scheme certificate covers the traded product
- Failing to renew declarations after a process change
Frequently asked questions
Do declarations carry legal weight?
They can support a due-diligence position, but they do not transfer regulatory responsibility from the operator placing the feed on the market.
How often should declarations be renewed?
On a defined cycle and on any change of process, formulation, origin or certification status.
Related reading
Need this applied to a specific purchase?
Send your requirement and we will structure the specification, supplier shortlist and verification plan around it.
Start a sourcing request