How does quality control work?
Rotion's quality control module covers inspections, damage photos, repair tracking, and wash cycles, so asset condition is part of the same record as location.
Last updated: 29 September 2026
Rotion treats asset condition as part of the asset record. The quality control module covers inspections, damage documentation with photos, repair tracking, and wash cycles, all written to the same digital packaging passport that tracks location and handovers. An asset's fitness for reuse is a recorded fact, not a guess.
How are issues reported from the floor?
Anyone scanning an asset can report an issue at the point of scan: damage, a labeling problem, or anything that makes the asset unfit for circulation. Reports carry photos, captured in guided steps so the documentation is usable, and each flag is tracked until it is resolved rather than disappearing into a message thread.
Because reporting rides on the normal scan flow, it costs the operator seconds. A damaged crate spotted at a washing station becomes a documented, assignable issue in the same motion that records the wash.
What does an inspection look like?
Quality control inspections in Rotion follow configurable templates: pass or fail checks, numeric thresholds, and visual assessments, matched to the asset type. A returnable transport item (RTI), a garment, and a keg need different checks, and each fleet defines its own.
| Inspection element | What it captures |
|---|---|
| Pass/fail checks | Binary condition gates an asset must clear to circulate |
| Numeric thresholds | Measured values checked against limits |
| Visual assessment | Photo-documented condition judgments |
| Damage grading | Severity classification that drives the follow-up action |
How are repairs and washes tracked?
Repairs move through recorded statuses, from flagged to in repair to repaired, including rewash loops when cleaning has to be redone, and costlier repairs can require approval before work starts. Wash cycles increment per-asset counters, so every asset carries its wash and wear history.
Those counters connect condition to economics: an asset's cycle count is what reuse reporting and break-even analysis read from, and repair history explains why a fleet segment underperforms before anyone has to go looking.
Why does condition tracking belong in the tracking system?
Because a reuse loop is only as large as its fit-for-use fleet. Assets stuck in repair are invisible in systems that only track location, and condition data kept in a separate tool drifts from operational reality. In Rotion, one record answers where an asset is, who has it, and whether it can go around again.
See condition tracking live
How does deposit management work?
In Rotion, a deposit is charged on the issue scan and released on the return scan, and every venue and return point keeps a balance that updates itself.
How do roles and partners work?
Rotion is built for multi-party loops: producers, fleet owners, carriers, service partners, and retailers each work with role-based access and permissions.