Acceptance criteria
The target is to keep physical and system stock aligned across stores and warehouses.
- Physical-system stock match
- Lossless receiving and dispatch
- ERP data flow without gaps
Retail RFID
RFID retail store management system
RfidSpace connects product EPC, barcode, size, color, store, warehouse, POS, reader and ERP events in one operational model for retail chains.
Operational overview
From EPC reads to retail decisions
The retail workflow starts before the item reaches the shelf. Purchase or transfer documents, carton reads, handheld counts, e-commerce picking lists, POS transactions, fitting-room movement, gates and integration jobs are reconciled under the same platform.
Retail operation scope
Document-based receiving
Incoming products can be accepted with or without a document, then compared with expected purchase or transfer lines.
- Purchase receiving
- Unplanned receiving
- Expected-read difference
Warehouse-store shipment
Store shipments can be document-based, partial and grouped for the same destination store.
- Partial shipment
- Grouped dispatch
- Carton and item validation
Store returns
Returns from store to warehouse are read by RFID and entered back into the receiving flow with user, time and reason context.
- Return receiving
- Reason tracking
- Stock correction
Full and partial counts
Teams can run full-store counts, partial location counts and product-group counts, then transfer count results to ERP.
- Full count
- Partial count
- Product group count
Product search and alterations
Handheld workflows help staff locate products and record alteration processes as traceable store operations.
- Item finder
- Size/color lookup
- Alteration record
E-commerce picking
Online order picking lists can be entered or received, then validated with RFID reads before packing.
- Order picking list
- Expected-read validation
- Packing control
RFID tag import and printing
Pre-encoded tag lists can be imported from CSV, while new labels can be printed and encoded from selected templates.
- CSV EPC import
- Template-based printing
- Print and encode log
End-to-end retail flow
1. Product and EPC are matched
ERP product data is linked with barcode, EPC, size, color, season and variant information.
2. Receiving is validated
Incoming items are read by handheld, tunnel or desktop station and compared with the document when available.
3. Store operations run
Transfer, item finder, fitting-room insights, alteration records, sales and returns are handled in controlled workflows.
4. Reports close the loop
Counts, stock differences, door/tunnel reads, sales and integration logs are reported and reconciled with ERP.
Management and audit reports
Counting reports
- Full count
- Partial count
- Product group count
- ERP count export
Store reports
- Current store stock
- Fitting-room movement
- Door transition
- Tunnel read report
Sales reports
- POS sale
- POS return
- Top five sellers
- Total sales
Technical reports
- User operations
- Integration errors
- Service runtime
- Device health
Traceability reports
- EPC movement history
- Document movement report
- User audit trail
- Label print history
ERP, POS and device integration
Master data
Product code, description, season, barcode, color code, color description, size and variant data are received from ERP/POS services.
- Product card
- Barcode
- Color-size-variant
Stock and warehouse data
Store, warehouse and current stock information is used for comparison before counting and transfer reconciliation.
- Store code
- Warehouse code
- Current stock
Document exchange
Receiving, shipment and transfer documents are exchanged through API with document code, source, destination, barcode and quantity fields.
- Receiving document
- Transfer document
- Reference document
POS communication
Checkout scenarios can use controlled Windows app integration or serial/keyboard-emulation transfer depending on POS constraints.
- Sale
- Return
- Serial or keyboard mode
Device governance
Handhelds, fitting-room readers, printers, desktop stations, gates and tunnel readers are tracked by version and health status.
- Version control
- Auto update
- Heartbeat status
Integration logging
Integration jobs write operational logs for errors, duration and transferred document status.
- Error log
- Runtime
- Transfer status
RFID master data
RfidSpace can keep RFID-side master data for EPC, barcode, product, user, device and location parameters while synchronizing with ERP.
- EPC master
- User and device parameters
- Location definitions
Device API communication
Handhelds, fixed readers and desktop stations communicate with the platform through TCP/IP and web API services.
- TCP/IP devices
- Web API
- Online/offline sync
Frequently asked questions
Can the system work with both document-based and non-document receiving?
Yes. RfidSpace can separate document-based receiving, unplanned receiving and later ERP reconciliation according to the project rules.
How are POS constraints handled?
Depending on checkout limitations, the sale/return signal can be exchanged through API, Windows app, serial port or keyboard-emulation scenarios.
Can device health be monitored?
Handhelds, readers, printers and tunnel/gate stations can be followed with communication time, version and status information.
Can e-commerce orders be picked by RFID?
Yes. Picking lists can be created manually or received through integration, and the prepared package can be validated by RFID before dispatch.