Revera

Problem

The brand takes in used clothing, then labels, washes, repairs and resells it. That is not one step, it is a pipeline, and every single garment goes through it individually. Tracking that on a shared spreadsheet falls apart fast: a piece gets washed but not logged, a repair is finished but nobody knows, an item is "somewhere" between stages. They needed to know, for any garment at any moment, exactly where it was.

What I built

• A unique QR per garment. Each incoming piece gets its own code, so from intake onward it is a tracked individual item, not an anonymous unit in a pile.
• Stage tracking through the pipeline. Scanning a garment moves it through its states (received, washed, repaired, sent, resold), so its status is always current and set by the person actually handling it, not typed in later.
• A data model that treats the process as data. Because each garment and each stage change is a record, the brand can answer where any piece is, how long each stage takes, and where things pile up, without chasing anyone.
• Scoping and schema first. I scoped the operation and designed the data model before building, so the pipeline in the app matched the pipeline on the floor.

Results

The point of this one is that the process itself became the data. A garment is not "in the shop somewhere", it is at a known stage with a known history, reachable by scanning the tag on it. That is the same instinct I bring everywhere: model the real-world process accurately and the reporting, the bottleneck-spotting and the accountability come for free.