Packages are configurable items that help your company classify inspections and apply the right quality expectations based on how the produce is packed or handled.
In Clarifresh, a package can represent a physical package type, such as a box, carton, clamshell, or pallet.
Packages are used together with produce and variety to give more flexibility when setting up inspections, standards, reports, and quality rules.
When to use Packages
Use Packages when the quality expectations or inspection setup may change based on the package or asset connected to the inspected produce.
For example, you may want to use Packages when:
- The same produce and variety can be packed in different package types.
- Different packages require different grade ranges or tolerance levels.
- The standard calculation depends on the package.
- You want to filter, group, or compare inspection results by package in reports.
Packages are a feature within a standard, allowing you to customize specific values of different packages.
Example
A company inspects strawberries.
The produce is Strawberry, and the variety is San Andreas.
The company may use different packages, such as:
- 250g clamshell
- 500g clamshell
- 1kg box
Each package may have different quality requirements. By assigning the correct package to the inspection, Clarifresh can apply the relevant standard logic and make the inspection data easier to analyze later.
How to manage Packages
To manage packages:
- Go to Settings.
- Open Produce Config.
- Select Packages.
- Add, edit, or manage the package values used by your company.
The package list should include the values that users need to select during inspection setup or inspection creation.
learn more in Creating packages, How to Rename or Delete a Package
How Packages are used in Clarifresh:
Process
To use packages in inspections, Package must be included in the relevant process settings:
- Go to Specs.
- Open the relevant Process.
- Go to process Settings
- Edit the process settings.
- Select the Include Package checkbox.
- Save your changes.
After selecting Include Package, the Package field is immediately added to the New Inspection screen preview, under the Variety field.
Once the process is updated, inspections created from this process will include the Package dropdown during inspection creation.
Standards
Packages can also be used inside a standard to customize grading values for different package types.
This is useful when the acceptable range for an attribute changes depending on the package, produce and variety. Instead of creating separate standards for each package, you can define package-specific grading rules within the same standard for different attributes.
For example, let’s look at the attribute Weight. The acceptable weight range may be very different for a carton and a bin. This allows the same attribute to be evaluated differently for each package while keeping the inspection process and standard setup flexible and accurate.
learn more in Advanced Package-Based Grading in Standards
QC Reports
When package information is part of the inspection, it can appear in the QC Report as part of the inspection details on the top toolbar after the variety.
Renaming the package to a custom alias
Not every company uses this field for physical packages.
If your company uses this field for a different asset, you can rename Package to a custom alias. For example, you may rename it to Brand, Customer, Market, or another term that better matches your workflow.
Learn more in Rename Package with a Custom Alias
Best practices
Keep package names clear and consistent so inspectors can select the correct value easily.
Use packages when they have a real impact on inspection setup, standard logic, reporting, or business analysis.
Avoid creating duplicate package names with small spelling differences, as this can make reports harder to analyze.
If your company does not use package-based logic, you do not need to include Packages in your process setup.