Integrations
Works with your existing scanners, printers, and infrastructure.
Any USB or Bluetooth barcode scanner. Any Zebra thermal printer. Your own servers or ours. No proprietary hardware, no vendor lock-in, no per-request fees for route planning. Your data in a standard database you can query and export at any time.
Scanning
Barcode scanning. RFID-ready architecture.
Barcode Scanning
Code 128 barcode scanning at every station. One scan returns the garment card, current instruction, and routing decision. Any USB/Bluetooth scanner.
Scan → garment card → one instruction
RFID-Ready
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
Printing
14 label templates. Auto-print on lifecycle transitions.
14 label templates covering garment labels, bin labels, sling tags, dispatch notes, and inspection certificates — works with Zebra thermal printers and standard printers.
Labels print automatically on lifecycle transitions — intake, inspection pass, dispatch. No manual trigger required. Just scan the garment, and the right label appears.
Routing
Self-hosted routing engine. No Google Maps dependency.
Route planning powered by a self-hosted routing engine that runs alongside the application. Real driving times rendered on maps — not straight-line estimates.
No Google Maps dependency. No per-request fees. No usage caps. The routing engine runs on your infrastructure — updated on your schedule, under your control.
SMS
Urgent PPE alerts only. Not marketing.
SMS alerts sent only when a wearer has zero compliant PPE and is on shift — a genuine safety concern, not a notification preference.
SMS goes to the responsible H&S officer, not the wearer. The message contains the wearer name, station, and which garment types are missing. One message per coverage gap.
Storage
Standard cloud storage. Any provider.
All documents, photographs, and certificates stored in standard object storage. AWS, Azure, Backblaze, or any compatible provider — your choice.
Swap providers without touching the application. No migrations, no downtime.
Import / Export
CSV in. PDF and PostgreSQL backup tooling out.
CSV Import
Upload a CSV, map columns to fields, preview the data, then import. Existing garment records from spreadsheets brought into the system without manual re-entry.
PDF Export
Compliance packs, inspection certificates, and operational reports exported as PDF. Generated on demand from live data — not cached snapshots.
Full Database Backup
Standard database backup tooling — take a complete snapshot of every record at any time. No proprietary format. No vendor negotiation required.
QR verification
Scan the label. See the complete compliance history. No login.
Every garment label carries a QR code linking to a public verification URL. Auditors scan the code and see the garment's wash life, inspection history, and a condensed lifecycle timeline. No login required. No app to install.
Notification Rules
Notification Rules
Configure which events trigger notifications and which channels deliver them. Compliance breaches go to SMS. SLA warnings go to the Command Centre. Client portal actions go to the account manager's inbox. Every notification is logged in the audit trail.
Data access
Your data in a standard database. No lock-in.
Vorrex does not ship a public API in this release. Your data does not need one to leave: it lives in a standard PostgreSQL database on your own server, so your team can query it, back it up and export it with standard tooling at any time. A partner API is on the roadmap and will be built against a named client need, not ahead of one.
- ●Standard PostgreSQL — query, back up and export with the tools your DBA already uses
- ●CSV import for garments, wearers and clients; PDF export for packs, certificates and invoices
- ●Plant-to-hosted sync is outbound-only HTTPS with mutual key auth — no inbound firewall holes
- ●No proprietary formats and no data extraction fees — if you leave, you take everything
FAQ
Common questions
What barcode and RFID hardware does Vorrex support?
Vorrex Terminal accepts input from any USB or Bluetooth barcode scanner that emulates a keyboard. RFID reader support is architecture-ready — the hardware abstraction layer supports RFID alongside barcode without changes to business logic. Specific RFID reader models are validated on request.
Can Vorrex export data to Xero or other accounting systems?
Yes. The Export Centre in Vorrex Manager produces Xero-compatible CSV files from billing run data. The export maps to configurable nominal codes. Other accounting systems can be supported by adjusting the column mapping in the export configuration.
Does Vorrex have a public API?
No. Vorrex 2.0 has no public or partner API. Data leaves the system through standard PostgreSQL export tooling and CSV, not a live API surface — so there is no integration endpoint for a third party to depend on or for an attacker to target.
What label printers does Vorrex support?
Vorrex generates Zebra ZPL label output for garment barcodes, bin labels, and cage manifests. ESC/POS receipt output is also supported for docket printing. Printers are claimed using a 3-second exclusive access pattern to prevent simultaneous print jobs from multiple terminals.
Related reading
See it on your data, or start with the checklist.
Either path works. Pick whichever fits where you are today.