Recognition is not acceptance: designing the reward boundary
A proposed event model that keeps UI feedback separate from the physical event and the reward ledger.
Reviewed Read morePlan a controlled comparison when artwork, label placement or print finish changes, and keep barcode recognition separate from physical acceptance.
A label revision needs a comparison against the approved package, not a single successful scan. Identify exactly what changed, test representative physical samples and retain a decision for the new version. A readable code alone does not prove that the complete return journey works.
SDR Portugal’s guidance for packaging producers discusses barcode contrast and placement on a suitably smooth area. These are scheme-specific requirements; confirm the current specification for your market. Do not assume that conformity with a print layout proves RECYNEX equipment acceptance or participation in a national deposit system.
Record the old and new artwork references, package identifier, label material and changed finish. If the identifier stays the same while the packaging changes, preserve both versions in the sample record so that a later failure can be traced to the actual package.
| Comparison | Evidence to retain |
|---|---|
| Previous approved label versus new label | Physical samples and artwork versions |
| Different permitted label orientations | Read result and observed retry behaviour |
| Representative wet or imperfect returned labels | Condition, result and exception message |
| Similar excluded packaging | Evidence that it remains excluded |
Use the same approved configuration for paired comparisons. If you change reader rules and artwork simultaneously, record both changes and avoid attributing the result to the label alone. Follow the actual programme’s condition requirements rather than inventing a universal tolerance for damaged packaging.
Observe identification, acceptance or rejection, user feedback and the recorded event. A recognized sample that cannot safely pass through the approved intake is not a successful end-to-end result. Check that a rejected sample does not create a completed return record.
Retain the rule version, equipment reference, sample condition, result and reviewer. If an issue is unresolved, keep the new package outside the approved scope until the responsible owner decides how to proceed. Deployment should include the accepted-list change, staff instructions and any revised participant signage.
Can a screen image replace a physical sample? It may help an artwork discussion but cannot validate the mechanical journey or a real printed label.
Does passing one orientation establish acceptance? No. Agree the intended use conditions and document results across the sample matrix before approval.
Review the Vision scope and the equipment family with the actual samples.
A proposed event model that keeps UI feedback separate from the physical event and the reward ledger.
Reviewed Read moreSeparate container eligibility, barcode readability and machine availability when an apparently intact bottle is rejected at a return point.
Reviewed Read moreDesign a clear route for containers outside a campus return programme, while keeping local recycling instructions separate from machine acceptance.
Reviewed Read moreTell us what you need to return and where. We can help define the remaining details.
May we use Google Analytics to understand which pages help visitors? Your choice does not affect enquiries. You can change it at any time using Analytics preferences. Privacy notice