SOFTWARE PLATFORM
Packaging intelligence, grounded in samples.
Build a tested acceptance list for bottles, cans or specialist packaging before configuring return equipment. Define unknown items, exclusions and verification steps.
FROM SAMPLE TO RULE
Put the accepted packaging list on firm ground.
The useful output is a project-specific decision that equipment, software and operators can all follow.
Capture representative samples
Record material, shape, labels, barcode condition and relevant handling constraints.
Review uncertain items
Make exceptions visible to a person instead of turning a weak match into a promise.
Version the decision
Retest changes against equipment behavior and participant instructions before rollout.
QUALIFICATION PATH
Four decisions before a rule goes live.
Collect
Build a sample set that reflects the real return stream.
Observe
Test recognition and physical handling as separate steps.
Decide
Approve inclusions, exclusions and exception ownership.
Release
Publish one versioned list to the machine and the user journey.
Vision connects packaging samples, capture conditions, recognition rules and human review. It gives procurement and operations teams a versioned acceptance scope before a visitor reaches the equipment.
Sample intake
Record container material, form, label, barcode condition and representative photos. Decide which physical machine path each accepted item uses.
Recognition review
Evaluate barcode and visual signals against controlled samples. Keep unknown items in a review queue; recognition alone does not confirm physical acceptance.
Change control
Version recognition rules and packaging lists. Re-test a change with the equipment, user instructions and operator process before rollout.
Prepare a sample review
Choose representative accepted items, close lookalikes that must be rejected and real-condition examples such as damaged labels or residual liquid. Give each a sample ID and intended downstream route. The review can then compare classification with physical machine behavior instead of treating a model score as a pass. Bring the selected equipment configuration and any existing product database so version ownership is clear.
Turn your site brief into a configuration
Share the location, container stream, operating team and systems already in place.