Li-Ning / Apparel retail
RFID inventory across Li-Ning's 6,000+ stores
Customer deployment reference / SEUIC (Dongji) hardware platform
Li-Ning paired AUTOID UTouch RFID handhelds with apparel tags to digitize receiving, stock counts, item locating, replenishment and cross-store transfers.
Customer context
What had to work on the ground
Barcode-based stocktaking took hours, item locating was slow and delayed updates made replenishment less precise across more than 6,000 stores.
Documented solution
The hardware and operating pattern used
The reference combines RFID tags, group reading, item-finding algorithms, ERP/POS/WMS integration and Wi-Fi plus 4G connectivity with offline caching.
Hardware platform usedSEUIC AUTOID UTouch RFID handheld
Operating flow
How this workflow operates
These are the work events that connect the device to the customer process. They are the useful starting point for an equivalent RuggedLayer solution scope.
01 / Receive tagged goods
Read incoming apparel tags as goods enter the store workflow.
Creates an inventory event before goods reach the sales floor.
02 / Count stock in groups
Use RFID group reading for periodic inventory counts.
Replaces item-by-item barcode counting with a faster store-count process.
03 / Locate an item
Use the RFID handheld to find a specific tagged item.
Supports replenishment and customer-service work when the item is not at its expected location.
04 / Synchronize transfers
Update replenishment and cross-store transfer activity through the connected workflow.
Keeps POS, ERP or WMS inventory decisions tied to the store-side capture event.
Documented deployment outcomes
What the original deployment achieved
These figures belong to the documented customer deployment. RuggedLayer validates the equivalent workflow, configuration and acceptance criteria before delivering a new project.
Inventory counting
10x faster; several hours reduced to under 30 minutes.
Item locating
5x faster.
Inventory accuracy
More than 99%.
Group reading
Up to 950 tags per second in the documented configuration.
RuggedLayer implementation blueprint
How we would deliver this solution for a comparable operation.
The customer result above is the documented reference. The scope below is RuggedLayer's delivery design for a new project: we define the workflow and device layer, review the integration boundary, configure and validate the solution, then hand over a controlled rollout. UROVO and SEUIC (Dongji) supply the authorized hardware platforms.
Primary users
Store associates, inventory leads, replenishment teams and retail application support.
Capture method
UHF EPC reads for bulk counts and item finding, with barcode fallback for item and location confirmation.
Systems in scope
RFID store application, POS, ERP, WMS, inventory adjustment service, user identity and device management.
Operating constraints
Dense garment racks, neighboring read zones, changing tag orientation, customer-facing ergonomics and intermittent store connectivity.
System architecture and ownership
Four layers from frontline action to system of record.
RuggedLayer owns the agreed solution and device-delivery scope. Customer and software owners retain the production business rules, credentials and authoritative enterprise data unless those responsibilities are explicitly added to the project.
Store workflow application
Role-based flows cover receiving, shelf work, item lookup, counting, replenishment, transfers or mobile checkout without exposing unnecessary back-office functions.
Delivery boundaryRuggedLayer translates store tasks into device and validation requirements; the retailer or ISV owns price, promotion, payment and inventory rules.
Store device layer
Shared handhelds or mobile POS units combine the required barcode, RFID, payment and camera functions with practical holsters, charging and handoff controls.
Delivery boundaryRuggedLayer selects and configures the hardware platform, accessories, capture settings and managed application profile.
Store connectivity
Store Wi-Fi or cellular service synchronizes transactions, inventory events and device status, with queued work for short network interruptions.
Delivery boundaryRuggedLayer proves roaming, reconnect and application recovery on the device; store network remediation is separately scoped.
Retail systems
POS, ERP, WMS, inventory, customer and device-management systems retain the authoritative product, stock, transaction and policy records.
Delivery boundaryRuggedLayer validates the agreed integration points and handover package while the retailer controls production data and commercial logic.
Exceptions and acceptance
Design the failure paths before the happy path goes live.
A useful deployment specification defines what happens when capture, data, connectivity or business rules fail, and it gives the pilot a measurable release gate.
Exception handling
- 01
A tag is read from the neighboring zone or through a wall.
Keep it outside the proposed adjustment, require zone review and tune power or operator motion before repeating the session.
- 02
An EPC is unknown, duplicated or mapped to the wrong SKU.
Quarantine the observation for master-data review and use the approved barcode fallback without silently rewriting the EPC mapping.
- 03
The store loses connectivity during a count.
Retain the session and read set locally, prevent duplicate submission and require a visible reconciliation after reconnect.
Pilot acceptance criteria
Read accuracy
Representative racks meet the agreed expected-tag detection rate while adjacent-zone leakage remains below the approved threshold.
Count productivity
A complete pilot zone is counted, reviewed and submitted within the target time by trained store staff.
System reconciliation
Missing, unexpected, duplicate and replacement tags follow the approved inventory adjustment workflow.
Usability
Associates complete the defined count and item-find sessions within the weight, battery and training limits.
RuggedLayer rollout plan
Move from samples to a supportable operating fleet.
Each phase produces a reviewable project output. Volume deployment starts only after the workflow owner, application owner and RuggedLayer agree that the acceptance criteria have passed.
01 / Discover
A store-task map covering user roles, item and tag types, payment boundary, stock rules, device sharing and support ownership.
02 / Store validation
Configured samples tested on real shelves, racks, labels, applications, peripherals, Wi-Fi and daily charging routines.
03 / Pilot stores
A small representative store group with baseline timings, exception logs, associate feedback and a documented go/no-go review.
04 / Wave deployment
A repeatable store kit, enrollment profile, installation checklist, training package, replacement pool and support route.
Candidate configurations
Devices to include in the first evaluation
The hardware used in the customer reference is shown above. These are additional starting points from the related solution guide; RuggedLayer confirms the exact SKU, region, accessories and application compatibility during validation.
UROVO / Rugged handheld computer
DT50
General-purpose handheld with a replaceable-battery option for mixed store work.View product details
UROVO / Enterprise mobile computer
DT66
Modern full-touch platform for app-first retail workflows.View product details
SEUIC (Dongji) / Touch mobile terminals
CRUISE2
Full-touch mobile terminal option for inventory and store applications.View product detailsRuggedLayer application validation
Adapt this reference to your application and environment.
Share the users, labels or tags, software, country, working conditions and expected volume.