RFID Inventory Systems

Last updated: November 8, 2026

RFID inventory systems use radio-frequency tags and readers to identify and count items without line of sight. A UHF RFID reader can read hundreds of tags per second from several metres away, so a stock count that takes a team days with barcode scanners can be done in hours or, with fixed infrastructure, continuously. 360 Soft, an Istanbul-based software company, designs and integrates RFID solutions end to end: tag and reader selection, gates and portals, handheld apps, drone, tower and robot-based counting, middleware and integration with your WMS and ERP.

This guide explains how UHF RFID works in inventory management, which hardware options fit which processes, how integration with SAP and other systems is done, the regulatory points (including the EU 865–868 MHz band), implementation steps and timelines, KPIs, cost drivers and the questions to ask a supplier.

Who uses RFID inventory systems

• Warehouses and 3PL operators that need accurate stock positions, faster goods receipt and dispatch verification.
• Fashion, footwear and retail chains that want item-level stock accuracy across stores to support omnichannel fulfilment.
• Manufacturers tracking work in progress, returnable transport items, tools and spare parts.
• Hospitals, laboratories and pharmacies managing high-value consumables, instruments and equipment.
• Enterprises and public bodies tracking IT equipment, furniture and other fixed assets, and laundry, rental and events businesses with reusable items.

Problems RFID solves

The typical starting point is inventory that does not match the system. Periodic counts tie up staff and often require closing the warehouse or store. Shrinkage and misplaced items are discovered weeks later. Goods receipts are checked by sampling because scanning every barcode is too slow, so supplier errors flow into stock. Online orders are accepted for items that cannot be found on the shelf. RFID changes the economics of counting: when reading an item is nearly free, you can verify every carton at the dock door and count the whole store or warehouse far more often.

How UHF RFID works

A passive UHF tag contains a chip and an antenna, but no battery. The reader emits radio energy through one or more antennas; the tag uses that energy to send back its identifier, usually an EPC (Electronic Product Code) encoded according to GS1 standards, such as an SGTIN that combines the product GTIN with a serial number. Most inventory deployments use the EPC Gen2 air interface (ISO/IEC 18000-63). Read range depends on tag design, reader power, antennas and the environment, typically from a few centimetres up to around ten metres or more for fixed readers.

Technology	Frequency	Typical use
LF RFID	125–134 kHz	Access control, animal identification, short range
HF / NFC	13.56 MHz	Library items, tickets, smartphone interaction, short range
UHF RFID (passive)	865–868 MHz in the EU; 902–928 MHz in the US; other bands in other regions	Inventory, logistics, retail, asset tracking, long range and bulk reading
Active RFID / BLE	Various	Real-time location of high-value assets, people or vehicles; battery-powered

Frequency regulation: in the EU and Turkey, UHF RFID readers operate in the 865–868 MHz band under rules based on the ETSI EN 302 208 standard, and some countries also allow an upper band around 915–921 MHz. The US uses 902–928 MHz, and Gulf countries have their own allocations. Readers must be configured for the country of operation, and global tags are designed to work across these bands. We check the applicable rules for each site during design.

Hardware options for inventory counting

Option	How it works	Best for	Considerations
Handheld readers	Staff walk the aisles with a handheld UHF reader or a sled attached to a smartphone	Cycle counts, store counts, searching for a specific item	Low infrastructure cost; depends on staff walking routes
Gates and portals	Fixed readers and antennas at dock doors, store entrances or between zones	Goods receipt, dispatch verification, movement between areas	Antenna tuning and shielding to avoid stray reads from nearby stock
Tunnels and conveyors	Enclosed readers on a conveyor read every tag in a carton	Inbound carton verification, e-commerce packing, returns	Throughput and carton content must be tested
Fixed overhead readers and towers	Ceiling- or mast-mounted readers cover a zone continuously	Near real-time stock visibility in stores and fixed storage areas	Higher hardware and cabling cost; careful coverage design
Drone-based counting	A drone carrying a lightweight reader flies along high-bay racks	Tall racking and large warehouses where manual counting needs lifts	Flight safety rules, battery time, indoor navigation; usually done outside peak hours
Robot-based counting	An autonomous mobile robot with readers drives a planned route	Stores and warehouses with regular, unattended night counts	Floor layout, obstacles and robot navigation need to be validated
Smart shelves and cabinets	Antennas in shelves or cabinets detect items placed or removed	High-value items, medical consumables, tools	Cost per location; good for controlled stock

Most projects combine options: for example tunnels at receiving, gates at dispatch, handhelds for store counts and a drone or robot for periodic high-bay counts. We are hardware-neutral and specify readers, antennas and tags from established manufacturers to fit the process, or work with hardware you already own.

Tags and encoding

• Paper and synthetic labels for cartons, boxes and retail items, often printed and encoded on RFID-enabled label printers.
• Hang tags and sewn-in care labels for apparel.
• On-metal and rugged tags for IT equipment, tools, containers and returnable transport items.
• Tamper-evident and special-purpose tags for high-value goods, sterilisation or laundry cycles.
• Encoding standards: GS1 EPC schemes such as SGTIN for products, SSCC for logistic units and GRAI or GIAI for returnable and fixed assets, so that tags remain readable across partners in the supply chain.

Software, middleware and WMS/ERP integration

Hardware produces raw reads; value comes from turning them into business events. The software layer typically includes:

• Device management and middleware that configures readers, filters duplicate and stray reads, and converts reads into events such as received, moved, counted or shipped.
• Mobile apps for handheld counting, item search with a proximity indicator, and tag commissioning.
• Inventory and reconciliation services that compare counted EPCs with expected stock and flag missing, extra or misplaced items.
• Integration with WMS and ERP such as SAP (including SAP EWM and S/4HANA), Microsoft Dynamics, Oracle or local ERP products, via APIs, IDocs, message queues or file interfaces.
• Dashboards and alerts for stock accuracy, unexpected movements and dock door exceptions.
• Deployment on premises, in the cloud or hybrid, with edge processing at sites where network connectivity is limited.

For SAP-centric landscapes, our SAP consulting team works alongside the RFID engineers.

Implementation process and typical timelines

Phase	Scope	Typical duration
1. Process analysis	Current flows, stock data, pain points, target KPIs	1–3 weeks
2. Site survey and tag tests	RF environment, materials, tag candidates, read tests on real products	2–4 weeks
3. Solution design	Hardware layout, encoding scheme, software architecture, integration design	2–4 weeks
4. Pilot	One warehouse zone, store or process; measure read rates and accuracy	6–12 weeks
5. Rollout	Phased installation, tagging at source or in-house, training	Depends on the number of sites
6. Operate and optimise	Support, tuning, new use cases	Ongoing

The pilot is where read rates, accuracy and process changes are measured on your own products. We recommend deciding on rollout only after pilot results are reviewed.

KPIs and SLAs

KPI	What it shows
Inventory accuracy	Match between counted and system stock at item or SKU level
Read rate	Share of tagged items read in a count or pass, measured in the pilot
Count duration and frequency	Labour and time needed per count, and how often you can count
Receiving and dispatch errors	Discrepancies caught at the dock door before they enter stock
Out-of-stock and unfindable items	Impact on sales and order fulfilment
System availability and incident response	Agreed in the support SLA for middleware and integrations

Delivery models

• Turnkey project: design, hardware specification, software, integration and rollout delivered as a project.
• Software and integration only: you or your hardware supplier provide the devices; we deliver middleware, apps and WMS/ERP integration.
• Dedicated team or staff augmentation: RFID, mobile and integration developers join your team; see staff augmentation in Turkey and hire a software development team.
• Managed service: monitoring, support and on-site field service coordination after go-live, as part of our IT outsourcing services.

Engineering work is done remotely from Istanbul, with on-site work for surveys, installation and go-live; hybrid setups are standard for multi-site rollouts.

What drives the cost

Factor	Effect
Number of sites, doors and zones	Determines how many readers, antennas and installations are needed
Counting method	Handhelds are lowest in infrastructure cost; fixed, drone and robot options cost more but reduce labour
Tag type and volume	Simple labels cost far less than on-metal or rugged tags; tagging at source shifts cost to suppliers
Integration complexity	Number of systems, data quality and change processes in your WMS or ERP
Environment	Metal, liquids, dense stock and cold storage need more testing and specialised tags
Support level	Business hours vs 24/7, remote vs on-site field service

Commercial models: fixed price for defined phases such as the pilot, person-month team rates for ongoing development, hourly rates for consulting and changes, and outcome-based elements for managed services tied to agreed SLAs. Hardware and tags are quoted separately, at the prices of the chosen manufacturers or suppliers.

RFID vs barcode, and who should build it

Criterion	Barcode	UHF RFID
Line of sight	Required, one item at a time	Not required, many items at once
Item-level serialisation	Possible, but slow to scan	Standard with EPC serial numbers
Count speed	Limited by manual scanning	Much faster; continuous with fixed readers
Cost per label	Very low	Higher, depends on tag type
Infrastructure	Scanners	Readers, antennas, middleware, integration

Criterion	In-house team	Freelancers	360 Soft
RF and hardware know-how	Usually must be built	Rare and fragmented	Combined RFID, mobile and integration engineering
Integration with WMS/ERP	Good system knowledge, limited capacity	Varies	Dedicated integration engineers, SAP experience
Continuity	Depends on retention	Weak	Contractual support and documentation
Scaling for rollout	Slow	Limited	Teams scaled to the rollout plan

Risks and mitigation

Risk	Mitigation
Low read rates on metal or liquid products	Tag tests on real products, on-metal tags, antenna placement and orientation
Stray reads from neighbouring areas	Antenna tuning, power settings, shielding, software filtering and direction detection
Tags not applied consistently	Clear tagging procedures, encoding checks, supplier tagging agreements
Integration does not match processes	Process-led design, pilot with real users, staged rollout
Non-compliant radio settings	Readers configured for the country of operation; site-specific regulatory checks

Contract, security and data protection

We work under a B2B agreement with a mutual NDA; software and work product developed for you are assigned to your company. Inventory data is usually not personal data, but RFID systems can become personal data processing when tags are linked to employees, patients or customers. In those cases we sign a GDPR data processing agreement (DPA), use the EU Standard Contractual Clauses (SCCs) for any transfers from the EU/EEA to Turkey, comply with Turkey’s KVKK, and design for data minimisation, for example by not storing personal identifiers on tags. Reader networks are segmented from office networks and devices are managed with secure configurations.

Checklist for choosing an RFID partner

• Will the partner test tags on your actual products and environment before committing?
• Is the design hardware-neutral, or tied to one manufacturer?
• Which WMS and ERP integrations has the team built, and how are interfaces documented?
• How are stray reads, duplicates and direction handled in the software?
• Is there a measured pilot with agreed success criteria?
• Who supports the system after go-live, and with what SLA?
• Who owns the software and the data?

Explore our other solutions or learn more about 360 Soft.

Frequently asked questions

What is an RFID inventory system?

It is a combination of RFID tags, readers and software that identifies and counts items by radio without line of sight, and updates stock records in your WMS or ERP.

Which RFID frequency is used for inventory?

Passive UHF RFID is the standard for inventory and logistics. In the EU and Turkey readers operate in the 865–868 MHz band; the US uses 902–928 MHz, and other regions have their own allocations.

How accurate is RFID inventory counting?

Accuracy depends on products, tags, hardware and processes. We measure read rates and inventory accuracy on your own products during the pilot before any rollout decision.

Does RFID work on metal and liquids?

Yes, with the right tags and antenna placement. Metal and liquids affect radio signals, so we use on-metal tags and test on real items during the site survey.

Can drones or robots count inventory with RFID?

Yes. Drones carrying RFID readers can count high-bay racking, and autonomous robots can run regular counts in stores or warehouses. Their suitability depends on layout, safety rules and operating hours, which we assess in the design phase.

What is the difference between RFID gates and handheld readers?

Gates are fixed readers at doors or between zones that record movements automatically. Handheld readers are carried by staff for counts and item searches. Many projects use both.

Can RFID integrate with SAP or our existing WMS?

Yes. We integrate with SAP, including SAP EWM and S/4HANA, Microsoft Dynamics, Oracle and other WMS or ERP systems through APIs, IDocs, message queues or file interfaces.

Do we need to replace our barcodes?

No. Most organisations keep barcodes and add RFID. GS1 standards allow the same product identity in both barcode and EPC form.

How long does an RFID project take?

Typically a few weeks for analysis and tag tests, six to twelve weeks for a pilot, and a phased rollout whose duration depends on the number of sites.

Do you supply the hardware?

We are hardware-neutral. We specify readers, antennas and tags from established manufacturers and can work with suppliers you choose or hardware you already own.

Is RFID data personal data under GDPR?

Inventory data usually is not. It becomes personal data when tags are linked to people, such as employees or patients. In that case we apply GDPR and KVKK safeguards, including a DPA and data minimisation.

What does an RFID inventory system cost?

It depends on the number of sites and doors, the counting method, tag types and integrations. We provide a written estimate after process analysis and tag tests.

This page in other languages: Türkçe · Deutsch · العربية

Talk to us about RFID inventory

Tell us about your sites, products and current systems, and we will propose a pilot scope and a written estimate. Use our contact page, call +90 850 335 10 87 or email info@360-soft.com. 360 Soft, Nidakule Ataşehir, Istanbul.