Every garment. Every wash. Every time.
Proof that holds up.
The garment management system built for fire service PPE laundries. Every scan enforces compliance. Every decision is recorded. Every firefighter walks onto shift with kit that meets the standard.
The problem
Spreadsheets don't enforce compliance. Clipboards don't catch coverage gaps. Manual systems don't scale.
Compliance that exists on paper, not in practice
ISO 23616 requires proof that every garment was washed, inspected, and maintained to standard. A spreadsheet can record it. It can't enforce it. It can't stop a condemned jacket being reissued. It can't auto-condemn at wash 200.
Coverage gaps that nobody sees until a shift starts
A firefighter's structural jacket fails inspection at 3pm. Their shift starts at 6am. Who checks? Who orders the replacement? Who confirms it arrived? In a manual system, the answer is: whoever remembers.
An audit trail that depends on people doing the right thing
If your compliance record can be edited, deleted, or forgotten, it isn't a compliance record. It's a hope. ISO 23616 auditors want evidence, not intent.
How it works
Three steps. Full traceability.
Garment In
Scanned, identified, routed to first station.
Tracked & Compliant
Washed, inspected, repaired, protected — every step recorded.
Garment Out
Picked, packed, delivered compliant.
The product
Seven screens that carry the operation.
The approved Vorrex 2 interface designs — the scan a gloved operator hits four hundred times a shift, the contamination hard stop, the batch charged into a dryer, the rail the next person pulls from, the invoice that traces to events, the answer your client needs, and the proof captured at the tailgate.
Vorrex Terminal
Goods In · garment scan
The verdict, then the destination.
One scan returns the state and the station it routes to. The plant link is down in this shot — the scan still commits on the terminal and reconciles when the link returns.
See the garment journey→Vorrex Terminal
Quarantine · declared contamination
Declared contamination, and nobody opens the bag.
ISO 23616:2024 requires contaminated kit to leave the incident sealed, travel with a contamination notice, and have every cleaning decision recorded against the garment. Vorrex enforces that at the machine: the sealed bag is verified and logged before anything enters a wash — and where the standard permits no cleaning path at all, the system doesn’t offer one.
How the 14 compliance rules work→Vorrex Terminal
Dryer charge · batch open
Batch where the evidence allows it. Item-level everywhere else.
The operator scans the dryer, then each trolley into it — no garment is re-scanned at this hop, because every item was scanned individually at sort and the batch inherits that proven membership. Batch-level scanning over loads, item-level scanning everywhere money or compliance depends on the answer. A load due reproof is refused here, with the machine that takes it named.
How wash and dry are evidenced→Vorrex Terminal
Put-away · clean stock
The system tells the next person exactly which rail to pull from.
Put-away is system-directed: the verdict names the rail and the position at across-the-aisle size — HANG → RAIL R-07 pos 12 — and a confirming scan of the rail label completes the movement. Stock is grouped by client, then by delivery order, so the rail section is tomorrow’s consignment. Scan the wrong rail and the movement is refused with R-07 named; the location is never inferred from where the garment was put.
How clean stock is located→Vorrex Manager
Billing · invoice record
Every line traces to an event.
Each invoice line derives from the lifecycle events recorded on the plant floor, priced from the effective-dated rate card line beneath it. Approve it and the document is numbered and frozen; a correction is a credit note, never an edit.
How billing works→Vorrex Portal
Client dashboard
Am I compliant right now?
Your fire service client gets the answer in one sentence and one number, gaps ranked worst-first, and the compliance pack sitting beside it as the thing they hand to an auditor.
What clients see→Vorrex Go
Stop detail · cage swap
Proof captured at the tailgate.
Signature, photo and a GPS fix with its accuracy, each stamped with device time. No signal at the station: the button says the stop queues, and it queues.
How delivery proof works→The product suite
Seven surfaces. One system.
One interface per role — plant floor, back office, clients, firefighters, drivers.
Vorrex Server
The engine that enforces every compliance rule, catches every coverage gap, and keeps a record that holds up in court. Runs on your plant server, on your terms.
Runs silently. Nobody sees it. Everything depends on it.
45 minutes. Your garment types. No slides.
We walk through the real system with your products, your compliance rules, your contract structure. Pick a time that works.
What to expect
- Live walkthrough with your garment types and standards
- Compliance engine demo — see 14 rules enforced on real data
- Protection engine — watch a coverage gap get caught and resolved
- Client portal — what your fire brigade clients would see
- Pricing discussion — transparent, no pressure