Feed mill buyer guide
Feed mill automation and traceability: specify evidence, not labels
Describe the actions and records you need instead of asking for a “fully automatic” mill. Specify which ingredients, batches, transfers and dispatches must be traceable, how exceptions are handled, and how records can be retrieved. Automation features alone do not establish accuracy, feed safety or regulatory compliance.
Explore free tools
Define the records a batch must leave behind
Map ingredient receipt and lot identity to storage, dosing, recipe revision, production batch and finished-product dispatch. Identify where blending or rework changes the relationship between incoming and outgoing lots. Your quality team should decide the required record detail and retention period for the relevant business and jurisdiction.
Ask suppliers to demonstrate retrieval with an agreed example. A screen displaying a batch number is not enough if the team cannot reconstruct material movements, corrections and operator actions. Check whether exported records preserve timestamps, units, identifiers and the meaning of status fields.
- Lot-to-batch and batch-to-dispatch relationships
- Recipe versions, rework and corrections
- Record retrieval and usable exports
Specify control behavior and exceptions
Document how weighing verification, ingredient availability, interlocks, alarms and manual overrides should work. State who can change a recipe or release a held batch and what evidence the system records. Accuracy needs a defined measurement and acceptance procedure, not an unsupported percentage in sales copy.
Discuss power loss, sensor failure, interrupted batches and loss of network access. Ask how production resumes and how incomplete records are flagged. Interfaces between scales, machines, the control system and business software need named responsibilities and test cases.
- Roles, overrides and audit trail
- Failure and recovery behavior
- Interface responsibility and acceptance tests
Compare lifetime support and data access
Request the licence model, recurring charges, update policy, backup and restore process, remote-access controls and support coverage. Clarify who owns configuration files and who can export records when changing service providers. Avoid assuming that every proprietary platform includes perpetual access or local support.
Test restoration of a representative backup and verify that operators can find records without the original salesperson. Quantify potential labour or loss changes only with your own measured baseline and labelled scenarios. Automation is a means of controlling a process, not a guaranteed return or certification.
- Licence and support boundaries in writing
- Controlled remote access and backup ownership
- Demonstrated restore and operator handover
Free tools for your assumptions
Enter your own figures and retain the assumptions with the result. These tools do not validate engineering, optimize a complete feed formulation or guarantee costs, output or returns.
References and professional review
The FAO/IFIF manual provides general feed-production and feed-safety context; it is not a project design or certificate. ICC explains Incoterms responsibilities; the selected rule does not replace a full installation and acceptance contract. Confirm applicable requirements with qualified local advisers.