Why packaging qualification comes before installation

Build an evidence-based acceptance list for the containers your project wants to collect.

Hands comparing real bottle and can samples for a return-system review

Build an evidence-based acceptance list for the containers your project wants to collect.

Collect representative samples

Gather containers in the condition visitors are likely to bring them: intact, crushed, wet, unlabelled or partially filled. Record material, shape, dimensions and barcode or visual features. Include items that should be rejected.

Keep recognition and intake separate

A camera or barcode reader may identify a package while the intake cannot safely accept it. Verify the physical path, user message, rejection behavior and material destination together. Do not use a brand logo as a substitute for an approved list.

Control changes

Give the accepted list a version and a responsible owner. When packaging changes, repeat the relevant tests and update equipment rules, signage, software and operator instructions as a coordinated change.

Record a decision that can survive a change

For each sample, keep a unique ID, material, physical condition, test setup, recognition result, mechanical result, reason for rejection and approval owner. When a label or package shape changes, create a new version of the decision. Do not silently overwrite a former pass. The public-facing accepted list should be generated from approved results, with uncertain items excluded until reviewed.

Test the edge of the rule

If a clean, intact sample passes, try the same format in the condition a visitor will actually bring it: damp, slightly crushed, rotated or with an imperfect label. Add a similar-looking format that must be excluded. Watch not only the recognition decision but also the physical path and the visitor message. A system that rejects the right item with a confusing instruction can still create extra work for site staff.

Separate a test failure from a policy decision. A package may be technically readable yet excluded because the collector cannot take it, or it may be in the programme but require a different intake configuration. Record that distinction in the qualification table. It helps the programme owner explain a rejection without asking engineers to solve a downstream policy problem.

Plan for the next package revision

Packaging can change while the programme stays live. Agree who will notice a new label or shape, obtain samples, approve a rule update and tell operators what changed. A date and version on the accepted list are more useful than a static poster that no one owns. If the change affects a reward or deposit, test the event and ledger as well as the physical intake before publishing the new rule.

Use the qualification worksheet and send representative samples with their intended downstream route when you request an assessment. The stream selection guide helps separate PET, cans and glass before testing.

Related stories

Turn your site brief into a configuration

Share the location, container stream, operating team and systems already in place.