Site survey
Order flow, trolley types, volumes and handover points.
Receiving and dispatch are often the best starting points. We add read points where they actually improve linen flow and order verification.
Order flow, trolley types, volumes and handover points.
Your textiles, tags, metal cages and realistic loading.
Read performance, operator time and customer batch verification.
Training, operating procedures and records integration.
We configure antennas, travel direction, shielding and sensitivity for the actual location. Densely packed metal cages may need controlled passage, a reading cabin or multiple read positions.
The pilot also tests wet textiles and nearby trolleys. The goal is to capture the correct batch without including items from a neighbouring order.
Results depend on configuration. We determine accuracy and the required operating procedure through pilot measurements.
Linen keeps moving. The records keep pace.
UHF RFID readers, suitable antennas, read zones and clear terminals. An optional handheld reader supports stocktakes and investigation of differences.
Textile identities, customers, receiving, wash batches, dispatch and exceptions. Role-based permissions and traceable history.
Import existing records and design data exchange with your ERP. APIs, exports and any customer portal are scoped as part of the project.
No. A pilot can cover one customer, textile type or part of the circulation. RFID visibility covers tagged items; untagged items follow an agreed alternative procedure.
Often yes, but reading depends on cage construction, loading, moisture and tag position. We validate a sample first, then adjust antennas, shielding or the passage procedure.
Textiles are assigned to a wash batch. Only its confirmed completion creates a wash-cycle event. An operator or available integration confirms it; repeated RFID reads must not increase the wash count.
Sew-in or heat-seal tags designed for industrial laundries are used. Selection depends on temperature, chemicals, pressure and attachment. The chosen type’s datasheet and tests on your textiles establish its limits and lifetime.
The system shows the difference from the expected order. The operator repeats or supplements the read, or records an explained exception. Dispatch procedures are designed to keep the discrepancy visible.
Local buffering, terminal availability and subsequent synchronisation are part of the design. We specify and test outage behaviour before go-live.
We first review your ERP capabilities and agree data flows — customers, orders, receipts, deliveries or billing inputs. Integration is priced according to the actual interface and scope.
Together, we will identify where better records can save the most work.