AI system for automatic sorting and grading of food products

Manual control on the line cannot keep up with conveyor speed: defects pass further, and batches are sorted unevenly. We develop and implement turnkey machine vision systems that sort and distribute products into classes automatically, without stopping the line. Grading accuracy increases, and the share of manual operations at the control point is reduced severalfold.
Frequently Asked Questions

Automated Product Sorting: Where Manual Control Breaks Down

The throughput of a packaging line usually hits a limit not at the machines but at the inspection station.

The conveyor and packaging unit maintain a steady pace, while sorters can physically inspect only part of the flow — the rest passes on a residual basis or accumulates in a buffer.

The higher the speed, the less time remains to decide on each fruit, and the more actual and declared line throughput diverge.

Manual quality control on a line relies on attention, and attention is inconsistent. By mid-shift reaction time increases; by the end of a shift, operators miss defects they would have removed immediately at the start of the day: small dents, uneven color, lesions under the skin.

The human factor in sorting manifests not as a gross error but as a slow drift of the threshold — the "acceptable" criterion imperceptibly shifts, and across a batch it is visible only in the summary.

The second effect is divergence between shifts and between people. One rejects by color more strictly, another misses a spot, a third looks only at size and ignores shape.

For the warehouse and shipping, this turns into an unstable reject share of raw material and misgrading within the batch: part of the good product goes to waste, part of the defective product enters commercial packaging and comes back as a complaint.

The losses are visible in two places — in rejection fluctuation from shift to shift and in downtime when the flow is stopped for re-inspection.

Automated product sorting removes this exact limitation: evaluation uses the same thresholds across the entire flow speed, without fatigue, rotation, or shifts. Below we break down what such a system consists of and what it changes in line operation.

What Machine Vision Delivers on the Quality Control Line

A person on the belt maintains pace only up to a certain threshold: by the end of a shift, attention drops, and the same batch receives different ratings in the morning and in the evening.

For the line, this results in returns, disputes with the supplier, and misgrading that is discovered at the recipient.

Which Metrics to Use to Measure the Result

You should look not at a single number but at a set. Grading accuracy — the share of objects assigned to the correct category, and we calculate it separately for borderline classes where an error is most costly.

Repeatability of quality assessment — the discrepancy of verdicts on a repeated run of the same frame: it shows whether the system can be trusted without manual recheck.

  • Reduction of batch returns — share of claims closed before shipment, not after.
  • Line throughput — how many objects per minute pass without loss of accuracy.
  • Batch quality stability — spread of assessment within a batch and between shifts.

Why Accuracy Holds Over the Long Run

The model is configured on data from a specific line, not an abstract sample: variety, lighting, belt speed, and typical defects are set at the start.

We use industrial-grade optics and illumination — Basler and analogues, otherwise drift in light and focus eats repeatability before accuracy.

Then the monitoring loop works: we compare labeling with the reference sample, catch class bias, and retrain the model on disputed frames. We keep the discrepancy with manual recheck as a separate metric — if it grows, we learn about it, not the batch recipient.

Sorting and Grading Modes: Comparison of Approaches

The sorting mode determines what the line considers a defect: only visible signs or also hidden product properties. This affects equipment composition and how often the operator must intervene manually.

Appearance-Based Assessment

Cameras and computer vision evaluate color, size, shape, and surface damage. This is the fast path: the conveyor line runs without stops for recalibration. The weak point is hidden defects: the product looks flawless but is overripe or damaged inside.

Internal Quality Assessment

Internal characteristics are added to external ones: density, ripeness, dry matter content, cavities. More accurate for batch quality, but sensitive to skin thickness and size variation — reconfiguration is required for each variety.

In practice, the choice comes down to four options — from appearance-only assessment to a manual station and a hybrid mode that combines both approaches.

Option When It Fits Limitations
Appearance-based sorting Mass batches, defect visible externally Does not detect hidden damage
Internal quality sorting Ripeness, density, hidden defects important Sensitive to skin thickness and size variation
Hybrid mode Need external and internal control at once More expensive to configure, subsystem synchronization required
Manual inspection station Non-standard batches and disputed cases Depends on operator, lower repeatability

How We Implement the System on an Existing Line

A line can rarely be stopped for long, so implementation proceeds in stages and is combined with shifts, and each stage ends with a verifiable result.

  1. Line audit. Site layout, flow speed, drop points, response of existing automation to external commands.
  2. Installation layout. Module location, illumination contour, integration with the conveyor, and removal of rejects from the flow.
  3. Installation and image output. Cameras, lighting, regions of interest for each product type, validation on real batches.
  4. Rejection threshold tuning. Defect boundary, acceptable false-positive rate, behavior on borderline fruit.
  5. Model training. Samples from different sizes, seasons, and suppliers, not only demonstration ones.
  6. System acceptance. Run of reference batches with manual recheck and a protocol for missed defects.
  7. Operator training. Switching recipes for a new product, actions during feed failure, rollback to manual mode.

Unit Survey and Installation Layout

The system fits into the existing flow without rebuilding the area. We look at where the flow narrows, how the product behaves on turns, and whether there is enough space for reject removal. The result is an installation layout: module coordinates, illumination, signal pickup points.

Rejection Threshold Tuning

The threshold is a compromise: a stricter boundary means more good product in rejects; a softer one means some defects reach the consumer. We select values together with the technologist on your batches. Borderline cases are described separately: product with damage at the stem goes for a repeat pass.

Documentation, Diagrams, and Procedures: What the Customer Retains

The system is delivered not only as a working line and a trained model. If the customer only gets access to the control panel, any operator or contractor replacement turns into reconstructing the logic from indirect signs. Therefore we assemble the documentation set as part of delivery, not as an accompanying appendix.

Operating Set

  • Design documentation: line composition, camera installation points, product and reject flow diagram.
  • Layout diagrams: module positioning relative to the shop floor area, service zones, rejected product removal routes.
  • Operator instructions: shift start, reference calibration, switching to another product, actions during stoppage.
  • Maintenance procedure: optics cleaning frequency, lighting and reference sample checks, replacement of consumables.
  • Event log: logging levels, export format, retention period, retrospective incident analysis.
  • Model datasheet: what data it was trained on, for which product classes accuracy is confirmed, and where the applicability limits are.

Procedures for Non-Standard Situations

  • Accuracy drop: check against the control set, monitor lighting conditions, retrain or roll back the version.
  • Camera or conveyor section failure: switch to manual mode without stopping the entire line.
  • Procedure for rolling the model back to the previous version while preserving current sorting settings.
  • Escalation: what data and in what form to send to our engineers for analysis and what response time to expect.

Case Study: Improved Grading Accuracy on a Customer Line

The customer's line is assembled on Marel equipment: a conveyor with several pickup points, with operators between them who visually distributed the flow into categories.

We started with area labeling: timed shifts, digitized several thousand product units, and calculated where exactly the assessments of two operators diverged on the same object.

Situation Before Implementation

Agreement of assessments between shifts held at 71-74%: different operators assigned the same batch to different categories. Each shift began with setting thresholds "by eye", and the first forty minutes the flow ran with elevated rejection.

The share of product sent to reject reached 9% of volume, and part of the good raw material fell into the lowest category simply because the operator did not have time to return to the belt.

What Changed in Shift Work

The model evaluates features for each object directly in the flow and passes disputed cases to the operator — their share is 6-8%.

Grading accuracy increased to 94-96% and stopped depending on who is on the line: thresholds are fixed in the configuration, not in the setup technician's head, so a new shift arrives at the same decisions as the previous one.

Rejection decreased from 9% to 3%, shift handover takes 10-15 minutes instead of over an hour, and unplanned line stops for reconfiguration almost disappeared.

Over six months of observation, the metrics did not degrade: accuracy remains in the same corridor, and the share of disputed cases does not grow.

We separately checked behavior on raw material change and on batches after sanitary washing of the line — no above-normal discrepancies appeared.

What to Do If Old Inspection Systems Are Already on the Line

At an operating production facility, the question is not "replace or not replace" but where to draw the boundary between line mechanics and analytics.

Old inspection systems reliably output a "good/reject" signal and maintain conveyor speed — the new system adds defect recognition, category sorting, and per-fruit tracking.

Compatibility with the conveyor is resolved at the signal pickup point: if an object passage sensor is already installed, its readings become a trigger for the camera, and the line continues operating without stopping.

Hence three real scenarios — upgrade, phased transition, and full replacement of the inspection section.

Option When It Fits Limitations
Upgrade of existing system Mechanics and rejection are functional, only recognition is missing Ceiling on number of classes and feed speed, some defects outside logic
Phased implementation by zones Line runs multiple shifts, downtime unacceptable Coordinated logic required at interface of old and new sections
Full replacement of inspection section Mechanical wear, frequent false positives, new sorting scheme needed Longer ramp-up to operating mode, operator retraining

In practice, phased implementation more often wins: the new loop is installed on one zone or shift, compared with the current rejection, and only then expanded. This way the false-positive rate and manual re-sorting volume decrease without the risk of stopping the line.

The old logic remains a backup loop — rollback takes one reconfiguration, not restarting the line. Modernization of an existing line gives an effect faster; full replacement is more sustainable on worn mechanics.

The choice depends on the conveyor condition and requirements for the number of sorting classes, and we calculate it based on measurements of your line, not general recommendations.

Technical Concerns Before Launch

Engineering objections are better addressed before commissioning, not during the first shift on the line. Below are four questions that most often come up during approval: behavior during failure, batch change, model update, and acceptable deviations.

What happens if the model makes a mistake?

Every decision has a confidence threshold. Until it is reached, product does not go to reject but is sent for a repeat pass or manual sorting. Disputed cases are written to the event log — it shows on which classes the share of refusals grows.

How does the system behave during equipment failure?

Failure of the camera, lighting, or master controller does not stop the conveyor. The line switches to basic mode and passes product by mechanics, while disputed units are diverted to the manual section. An event with a timestamp enters the log, so the shift understands the cause immediately.

Will production have to be stopped to update the model?

No. The new version first runs in shadow mode on the live flow, and its decisions are compared with the current one on a labeled sample. Only after that is it enabled on the fly, and the previous version remains available for rollback. Line stoppage for version replacement is not required.

Is retraining needed when changing batch?

A change of color, variety, or supplier is usually covered by calibration on a short labeled set from that batch — full retraining is not needed. It is required when product geometry or class composition changes.

Acceptable deviations and calibration frequency are fixed in the procedure, and degradation is tracked by metrics in advance.

Let's Discuss the Task and Come Back with an Estimate and Plan

The estimate for such a system is not calculated "by price per camera" — it depends on the number of quality classes, conveyor speed, and how strictly the solution must keep up with the flow.

Therefore the first step is a short snapshot of your line: we compare it with typical sorting modes and return a range for accuracy and equipment load.

What we need from you to come back with an estimate and plan:

  • line description: what is sorted, flow speed, and how many manual positions currently cover this work;
  • list of quality and reject classes with priority — what is critical not to miss, and where deviation is acceptable;
  • video or photos of the flow from the actual area, including difficult cases: glare, sticking, wet product, stuck-together items;
  • how rejection is arranged today: where the signal goes, who and how executes it, whether there is an operator decision log;
  • access and constraints: possibility to install cameras and lighting above the conveyor, window for line stoppage, sanitary zone requirements.

In response we send not a general proposal but a working package: equipment layout diagram, list of classes with expected accuracy for each, implementation plan starting with a pilot on one line, and support procedure after launch.

The pilot occupies one line, runs in parallel with the operator, and does not affect output — its metrics show the actual share of missed defects and false positives before scaling to the entire area.

Describe the task in free form — according to the points above or as convenient. We will come back with an estimate, pilot scheme, and implementation plan.

AI Development Areas

Latest works

  • Development of a web application for FEEDME
    Development of a web application for FEEDME
    1393
  • Development of an online store for the company FURNORO
    Development of an online store for the company FURNORO
    1368
  • B2B Advance company logo design
    B2B Advance company logo design
    815
  • Development of a web application for Enviok
    Development of a web application for Enviok
    1139
  • AIDER company logo development
    AIDER company logo development
    1057
  • CRM development for Chasseurs
    CRM development for Chasseurs
    1152