Checklist for fruit quality control software
Whether for BRC, HACCP, GlobalGAP, CanGAP, EuroGAP, Farm Safe, ISO or other standards, fruit quality control for fresh produce can be a complex management scenario. Use this handy checklist to learn about available features in fruit quality control software for the fresh produce industry. Essentially, you should be able to integrate parts of your qualiy management system into your Quality Control program to make compliance easier, consistent, and enforced.
Checkout FarmSoft’s free fresh produce traceability software.
Fruit Quality Control Software Checklist:
Flexible quality control configuration
The ability to configure flexible quality control programs and criteria is essential for successful quality control management. Ensure your chosen fruit quality control software includes the ability to define quality programs for customers, internal purposes, and specific standards. A good fruit quality control software solution is essential to maintain traceability and customer satisfaction. It is important to be sure your chosen fruit quality control software has the ability to define:
- Quality Programs: Ability to define unlimited quality programs, each program should include optional employees whom will be automatically emailed a copy of any failed quality control program, version, features, finish class, fail class, pass alert employees, and user defined fields for any additional information you may require, and the subject of the Program
- Subjects: When a quality test is performed, it is performed on a “subject”. This means you need to be able to define a subject and the fields that the user must record when performing a test on this subject. Fields they will need to record should likely come from other parts of the business (these should be look-up fields to ensure no mistakes are made), like Batch Number, Supplier, Inventory Number, Equipment Number, Crop / Patch Name, Pallet Number, Farmer Name, Employee, Warehouse, Task Number, and any user defined free text fields that may additionally need to be recorded.
- Quality Criteria Categories: A quality program may have many quality categories. Common categories include example such as “Major”, “Minor”, “Physiological”, “Appearance”. Details such as category name, description, and the number of criteria test fails required to make entire test fail, must be recorded.
- Criteria: This is by far the most detailed of the quality control elements. Ensure you can record the criteria name, description, fail message (to be shown to user if test fails), fail class (the class of the inventory will be reset if test fails), one or more images to help the user visually comprehend this test, documents/pdf’s/Docx etc in case this is a complex test and the user needs to be trained or look up details, failure behaviour, maximum value & minimum value. See example figure below.
- Hold Reasons: Sometimes fruit and vegetables must be ‘put on hold’ or separated from other inventory until management can make a decision about the fruits destiny. Giving users multiple “hold reasons” will allow them to rapidly categorize fruit and vegetables, and a good quality control software should immediately alert management.