SYSTEM ARCHITECTURE
Know what happened. Then act on it.
Follow a container from packaging recognition to physical acceptance and a verified return event. See where equipment, software and reward decisions separate.
ONE RETURN, FOUR DECISIONS
A reliable event starts at the equipment.
Qualify
Establish which packaging belongs in the project, using real samples and an explicit exception list.
Recognise
Assess each presented item against the approved rules and make uncertainty visible.
Accept
Confirm that the physical process completed before recording a successful return.
Reconcile
Give the event a unique identifier and protect downstream systems from duplicates and retries.
The contract behind connected operations.
Equipment state
Device identity, software version and operating status make an event traceable.
Event vocabulary
Accepted, rejected, full, service and collection events need unambiguous meanings.
Handover evidence
Collection records and downstream receipts remain distinct from equipment acceptance.
Recognition is only one step
A camera or scanner may classify a container, but that alone does not prove it entered the system. RECYNEX treats packaging qualification, recognition, physical acceptance and downstream acknowledgement as separate parts of the design. The exact sensors, mechanical sequence and software behavior depend on the selected equipment configuration.
Give every event a clear owner
A connected project defines a versioned event format, device and site identifiers, event time, delivery retries, duplicate handling and an accountable destination. If a loyalty or incentive program is involved, it decides eligibility only after the verified acceptance event reaches the authorized server-side system.
Design for exceptions
A useful integration also explains rejection, offline periods, full storage, collection, maintenance and service recovery. The integration checklist provides a starting point for discussing those responsibilities.
Turn your site brief into a configuration
Share the location, container stream, operating team and systems already in place.