Garment Lifecycle
One garment. One identity. Complete history.
Every garment in the system gets a unique identifier at intake. From that moment, every wash, inspection, repair, reproof, and condemnation is recorded against that identity. Nothing is estimated, reconstructed, or assumed.
The garment card
What operators see on scan.
One scan surfaces everything the operator needs. No searching, no cross-referencing, no guessing.
Garment UID
VX-002041
Product type
Structural Jacket — EN 469:2020
Wearer
FF Sarah Mitchell — Blue Watch
Wash count
142 of 200 max
Status
Clean Stock — ready for issue
Next action
Inspection due at wash 145
The lifecycle
11 steps. Every transition logged.
From goods-in to condemnation. Every zone. Every transition permanently recorded.
Intake
Z01Garment scanned at goods-in. UID assigned. Lifecycle begins.
Sort
Z02Operator scans each garment. System routes: wash, quarantine, or condemn.
Wash
Z05Batch created. Temperature and chemicals recorded per ISO 15797.
Dry
Z06Post-dry scan. System routes to inspection, reproof, or clean stock.
Inspection
Z07Guided checklist. Hard-fail items trigger auto-condemnation.
Hard-fail → CONDEMNED · R-003 · No override
Clean Stock
Z10Inspected and compliant. Available for issue or buffer stock.
Pick
Z10Pick list generated. Scanner validates: right client, right wearer, right size.
Dispatch
Z11Cage loaded. Route assigned. Driver app notified.
Delivery
Z12Electronic POD: signature, GPS, timestamp. Portal updated.
In Service
Z13Garment with wearer. Protection Engine monitors coverage.
Collection
Z14Soiled garment collected. Consignment created. Cycle repeats.
Cycle repeats. Every transition logged.
Scan interface
One scan. One instruction. Complete context.
The operator scans a garment and sees exactly what to do with it right now. The system evaluates wash count, inspection schedule, wearer entitlement, and workflow state before presenting a single instruction.
A new operator and a ten-year veteran produce the same routing decision. Neither makes the decision — the system does.
The scan interface — one instruction per garment
Try the interactive demo below
Waiting for a garment
Present the tag to the reader. The terminal returns the state and the station it routes to — nothing else.
No garment on the reader · queue holds 5 items
Demonstration only. Five canned garments from a real Goods In queue.
Identification
Barcode at every station. RFID-ready when you are.
Handheld Scanner
Code 128 barcode scanning at sort bench, inspection, and dispatch. One scan returns the garment card, current instruction, and routing decision.
Scan → garment card → one instruction
RFID-Ready Architecture
The garment identity model supports RFID tag IDs alongside barcodes. When your operation adds UHF tunnel scanning, the system accepts RFID reads with no data model changes.
Future-ready · no migration required
Event log
Append-only. No updates. No deletes.
Every scan, wash, inspection, condemnation, and reproof writes an immutable lifecycle event. Temperature, programme, checklist items, measurements, inspector credentials — all recorded at the moment they happen.
Immutability is enforced at the database level. Not application-level protection — a constraint that cannot be bypassed by any user, administrator, or developer. The record cannot be changed after it is written.
A QR code on the garment label links to the garment's compliance history — wash count, last inspection, and lifecycle timeline. No login required for auditors.
Representative view
See the real system in a demo.
FAQ
Common questions
How many statuses does a garment move through in Vorrex?
Every garment carries a unique identifier and moves through a defined lifecycle — from first issue through every wash, inspection, and repair, to eventual condemnation. 22 statuses cover the full lifecycle with no gaps.
How does Vorrex identify garments on the plant floor?
Vorrex Terminal scans barcode or RFID tags at every station. Handheld scanning is standard today, with an RFID-ready architecture for future tunnel scanning without re-platforming.
Can the garment event log be edited or deleted?
No. The event log is insert-only, enforced by a database constraint rather than application code, so no bug, mistake, or future developer can erase a garment’s compliance history.
See the full lifecycle in action.
45 minutes. We'll trace a garment from intake through wash, inspection, and dispatch — on real data.