RFID business case: 7 critical questions for retailers

A customer is ready to buy an item that the stock file says is available, but when a colleague goes to find it, it isn’t there. Does that sound familiar?

That’s because a gap between the record and reality starts a chain of retail challenges:

• products sit in the back room instead of reaching the shop floor;
• online orders get accepted and then cancelled;
• hours are spent counting stock;
• and extra inventory is bought as insurance against uncertainty.

RFID can help close that gap by improving item-level visibility. But proving that a tag can be read is not the same as proving the investment will pay back.
Your RFID business case must set out:

• what will change;
• how the value will be measured,
• and who will make the change stick.

Here, we bring together lessons from an analysis of 25 major retail case studies and detailed research with 10 RFID users.

We also draw on a recent case study charting River Island’s ten-year RFID journey, including how greater confidence in its stock changed the way the retailer buys inventory.

Together, the evidence points to seven questions that every retailer should answer before approving, expanding or revisiting an RFID programme.

Want to compare your plans with retailers already using RFID? Register for the upcoming RFID in Retail Innovation Summit in Madrid.

What should an RFID business case prove?

The purpose of an RFID business case is so much more than proving the technology can read a tag.

It’s about demonstrating that improved product visibility will create enough operational or commercial value to justify the investment and the organisational change.

That means connecting four things:

1. A clearly defined business problem;
2. A process change made possible by better item-level data;
3. A measurable improvement in a retail outcome;
4. The full cost and capability required to sustain that improvement.

The link between them must be explicit.

If inaccurate stock records are causing replenishment failures, for example, RFID may make inventory records more accurate.

But the value appears only when those improved records trigger better replenishment and make products available for customers to buy.

The same discipline applies to omnichannel fulfilment.

More accurate stock data can cut uncertainty about whether an item is available, but any benefit depends on how that data is used in ordering, picking, cancellation and customer-service processes.

An RFID business case therefore needs a chain of evidence from the original problem to the operational response and then to a financial or customer outcome.

1. Which retail problem are you solving?

A strong RFID business case starts with a problem statement, not a preferred technology.

Our research found that retailers invested for several connected reasons:

• to improve inventory visibility and accuracy;
• to grow sales;
• to optimise stock holding;
• to reduce markdowns;
• to improve productivity;
• and to support omnichannel retail.

Our later 25-retailer analysis found a similar pattern, with RFID linked to corporate priorities rather than presented simply as an operational tool.

Those priorities can sound broad. But your first job is to turn them into a problem that can be observed and measured, for example:

• The stock file says an item is available, but colleagues cannot find it.
• Products are in the back room but not replenished to the sales floor.
• Online orders are accepted and then cancelled because store stock is missing.
• Counts take too long to complete frequently enough to support decisions.
• The business carries extra buffer stock because it doesn’t trust its records.
• Markdowns are increased because products are discovered too late in the season.
• Teams cannot distinguish physical loss from process or data errors.

Each problem implies a different RFID business case.

It may also require different data, readers, integration and process changes.

Trying to solve all of them at once can make a trial expensive, slow and difficult to interpret.

A useful starting question is: What decision or action will colleagues take differently when they receive more accurate item-level information?

If there is no clear answer, the business case is not ready.

2. Where will the value come from?

An RFID business case can draw value from several areas, but they should not all be treated as guaranteed.

Retailers need to select the value pools relevant to their own categories, margins, operating model and starting performance.

Better inventory accuracy

Inventory accuracy is the foundation for many other benefits.

RFID allows colleagues to identify many tagged items quickly and without scanning each barcode individually.

When counts become faster and more frequent, the business has more opportunities to correct its records.

In our detailed study of 10 companies, participating retailers typically reported improvements from around 65–75% inventory accuracy to 93–99%.

These were company-reported figures and were not independently verified, so they should be treated as evidence of what may be possible rather than a forecast for every retailer.

The commercial question is what improved accuracy unlocks.

A percentage improvement has limited value by itself.

The RFID business case should connect it to replenishment, availability, order acceptance, stock holding or another business outcome.

Higher sales and better availability

Nine of the 10 companies in our study used sales as a measure of RFID’s impact.

Seven shared figures, reporting sales improvements between 1.5% and 5.5%, although their methods and retail contexts differed.

The mechanism is straightforward: a more accurate stock record helps colleagues identify products that should be replenished and helps systems recognise when an item is out of stock.

Customers then have a better chance of finding and buying the product they want.

That does not mean an RFID system creates sales automatically.

The benefit depends on staff acting on replenishment prompts, supply being available and the product having customer demand.

A sound RFID business case should separate the enabling data from the actions that convert it into revenue.

Faster counts and better use of staff time

Our 25-retailer analysis found that faster counting was one of the most consistent execution benefits.

Handheld RFID readers can make it practical to count stock more often, while fixed readers or portals can automate selected movements.

Time saved is not automatically cash saved. The business must decide whether it expects to:

• reduce paid hours;
• avoid third-party audit costs;
• or redirect colleagues towards replenishment, customer service and selling.

These are different benefits and should be valued differently.

Only one company in our earlier 10-retailer study explicitly measured staff-cost savings, reporting a figure equivalent to around 4% of store staffing costs.

That single result should not be generalised, but it illustrates why the deployment plan needs to state what colleagues will do with the time released.

Lower stock holding and fewer markdowns

Retailers often carry buffer stock because they do not fully trust their inventory records.

More reliable visibility can give the business confidence to reduce that buffer, releasing working capital and lowering storage, handling and damage costs.

Five of the six companies that shared stock-holding data in our study reported reductions between 2% and 13%.

Most participants also regarded fewer markdowns as an important benefit, although they did not provide figures that could be published.

River Island offers a striking recent example.

The retailer reports that it now buys 30 to 40% less inventory than before implementing RFID because it has greater confidence in what stock exists and where it is located.

This purchasing figure is not directly comparable with the stock-holding reductions above, but it shows how better visibility can reduce precautionary overbuying.

These benefits need careful timing, as stock can be reduced only after the new process has proved reliable.

And cutting it too early could weaken availability and undermine confidence in the programme.

More reliable omnichannel fulfilment

For a customer, inventory accuracy becomes visible when an order is accepted, found, picked and made ready as promised.

RFID can support buy online, pick up in store and ship-from-store services by giving the ordering system a more trustworthy view of store inventory.

The relevant measures may include cancellation rates, pick success, time to locate an item, substitutions, split shipments and fulfilment promises met.

These operational measures can then be connected to customer satisfaction, cost and retained sales.

This is one reason the RFID business case often extends beyond store operations.

E-commerce, supply chain, finance, technology and customer teams may all own part of the value.

Loss insight and product authenticity

RFID can help retailers understand the status and movement of individual tagged products.

That may provide better evidence about process failures, fraudulent returns, unpurchased items leaving a store or counterfeit goods.

However, our research found that relatively few retailers treated loss reduction as a primary RFID measure.

Only two of the 10 companies actively measured stock loss as a KPI, and just one shared a figure.

Tags may be removed, exit reads may be incomplete and more frequent stock data does not always reveal why an item disappeared.

Loss prevention can form part of an RFID business case, but the claim should match the proposed design and evidence.

Better visibility is not the same as guaranteed theft prevention.

3. What operating model will deliver the value?

Across the 25-retailer analysis, a common execution pattern emerged:

• tags applied at source, frequent counts using handheld readers;
• selected fixed readers at distribution or store transition points;
• and software connected to core inventory and order systems.

The pattern matters because each component supports the next:

• Source tagging helps ensure products arrive with usable, correctly encoded tags.
• Readers and counting routines capture the presence or movement of tagged items.
• Software associates each Electronic Product Code (EPC) with the correct product and status.
• Integration passes reliable information to inventory, replenishment, point-of-sale and order-management processes.
• Store routines turn the data into action.

GS1’s EPC/RFID standards provide the common data and technical foundations that allow unique identifiers to be encoded and read consistently.

But standards alone do not define a retailer’s operating model.

An RFID business case should specify:

• where tags will be applied;
• which products and locations are in scope;
• how often information will be captured;
• which system holds the trusted record;
• and what colleagues do when systems disagree.

A scalable RFID business case should also price the whole model. Tags and readers are only part of the cost.

Retailers may need supplier onboarding, testing, software, integration, devices, support, training, process redesign, data management and ongoing quality control.

Starting simply is usually an advantage. Our 10-company study found handheld readers were the most common capture technology.

Nine of the 10 companies considered source tagging at manufacture the only feasible route to scale.

This does not mean every retailer needs the same design; it shows the value of choosing an operating model that is practical before adding more complex use cases.

4. How will you measure the RFID business case?

Measurement should be designed before the trial begins.

Otherwise, teams may prove that RFID can count products without showing whether the count improved the business.

The RFID business case needs a practical measurement framework that separates four levels:

This structure prevents a high read rate from being mistaken for a return on investment.

Read rate is important, but it is a system-health measure. The financial value comes from better decisions and actions.

Any trial also needs a credible comparison. Depending on the use case, that might mean:

• matched test and control stores;
• a pre-agreed baseline period;
• category-level comparisons;
• or phased implementation.

Seasonal effects, promotions, store changes and other interventions should be recorded rather than ignored.

An RFID business case should state:

• the baseline period and data source;
• the stores, categories and processes in scope;
• the calculation behind each claimed benefit;
• which costs are one-off and which recur;
• who owns each measure;
• how long benefits must be sustained;
• which assumptions remain untested.

The result does not need to be a single grand ROI figure.

A decision-ready RFID business case can show a range, with a conservative scenario, an expected scenario and the conditions required for a stronger return.

5. Which assumptions could weaken it?

Every RFID business case contains assumptions. The risk comes when they remain invisible.

Common assumptions include:

• 100% tag coverage;
• consistent tag quality;
• reliable reads across every product and fixture;
• perfect mapping between tags and products;
• timely system integration;
• regular store counts;
• and immediate colleague action.

Real deployments are less tidy:

• Products containing metal or liquid may behave differently.
• Tags can be damaged, removed, duplicated or incorrectly encoded.
• Interfaces can fail.
• Stock can move without the expected transaction.
• Filters, timing and system scope can create apparently contradictory figures.

Our article on nine real-world RFID implementation challenges shows why a surprising stock number is a signal to investigate, not proof of a single technical failure or a theft event.

A resilient RFID business case should therefore include sensitivity tests.

• What happens if tag coverage reaches 95% rather than 100%?
• If stores complete only four counts out of five?
• If integration is delayed?
• If only part of the released staff time turns into a measurable benefit?

This does not weaken the proposal, it makes it more credible and shows leaders which conditions need active management.

6. Who will own RFID after deployment?

RFID crosses organisational boundaries.

• Store operations may own counting and replenishment.
• Supply-chain teams may own source tagging and inbound processes.
• Technology teams may own integrations.
• Finance may validate benefits.
• Loss prevention may use selected data.
• E-commerce teams may depend on the stock record.

Without clear ownership, each function can assume another team is maintaining the system, improving the process or protecting the value.

Our 2026 research on RFID retail deployment examined 27 retailers operating 45,500 stores across 12 countries.

Among retailers scaling RFID or already at scale, four in five viewed it as a core organisational capability. For organisations at an earlier stage, only 17% did.

That association does not prove that mindset alone causes success. It does suggest that mature programmes are less likely to treat RFID as a finite technology installation.

An RFID business case should therefore name:

• one accountable executive sponsor;
• one leader responsible for the overall programme;
• process owners in each affected function;
• the team responsible for data quality and system health;
• the governance route for new use cases;
• the budget and capacity required after launch.

Ownership is part of the investment, not an administrative detail to be resolved later.

7. How can the business case grow beyond the store?

The first RFID business case is often deliberately narrow.

Frequent store counts and better replenishment offer a relatively clear route from improved visibility to measurable value.

Once that foundation is reliable, retailers can test additional uses.

The 25-retailer analysis identified activity around distribution-centre movements, self-checkout, fitting rooms, product authenticity and circularity.

Current industry discussions extend further into supply-chain visibility, automated readers, consumer devices, digital product information and the use of AI to interpret large volumes of RFID data.

Expansion should not be justified by novelty.

Each new RFID business case needs its own problem statement, process, measures and costs.

It should also reuse existing tags, data and infrastructure where that creates genuine incremental value.

The same questions are shaping the next phase of retail RFID:

• expanding beyond apparel;
• extending RFID through the supply chain;
• improving tags and readers;
• making better use of RFID data;
• and building the organisational capability needed to sustain progress.

For retailers with an established programme, the question is no longer simply “Does RFID work?”

It is “Where can the next unit of investment create the most useful return?”

RFID business case checklist for retailers

Use this RFID business case checklist before approving a trial or expansion. The proposal should answer each of these questions:

• Is the business problem specific, material and measurable?
• Is there a reliable baseline for current performance?
• Does the proposal explain how RFID data changes a process or decision?
• Are benefits separated into inventory, sales, labour, stock, fulfilment and loss measures?
• Are the relevant costs included beyond tags and readers?
• Are tag coverage, read performance, integration and colleague adoption treated as assumptions to test?
• Is there a named owner for the programme and each operational outcome?
• Does the trial design allow a credible comparison?
• Are reported benefits presented as a range rather than a guarantee?
• Is there a clear decision gate for scaling, adapting or stopping?

If several answers are unclear, the RFID business case needs more work before the technology is blamed or celebrated.

Frequently asked questions about the RFID business case

What should an RFID business case include?

An RFID business case should define:

• the retail problem;
• the process change enabled by better item-level data;
• the expected operational and financial benefits;
• the full implementation and running costs;
• the trial method, the measures of success;
• the principal risks and the people responsible for delivery.

How does RFID improve inventory accuracy?

RFID enables many tagged products to be identified quickly without scanning each barcode individually.

This makes frequent counts more practical.

Accuracy improves when retailers use those counts to:

• investigate discrepancies;
• correct records;
• and maintain disciplined tagging, movement and replenishment processes.

Which KPIs should retailers use for RFID?

Relevant KPIs may include:

• inventory accuracy;
• count time;
• tag coverage;
• read rate;
• on-shelf availability;
• replenishment completion;
• sales;
• stock holding;
• markdowns;
• order cancellations;
• pick success;
• labour cost;
• and stock loss.

The right set depends on the problem the programme is designed to solve.

Does RFID reduce retail loss?

RFID can improve item-level visibility and help investigate process errors, fraudulent returns or unpurchased products leaving a store.

It does not automatically prevent theft, and removable tags or incomplete reads can limit its security value.

Loss claims should be measured against the retailer’s actual design and data.

Where should a retailer begin with RFID?

Begin with a clearly defined business problem and a measured baseline.

1. Test the technology and operating process on a manageable group of products and locations
2. Agree the measures and decision rules in advance.
3. And involve the teams that will need to act on the data.

Build an RFID business case that can grow

The strongest business cases are built with evidence, challenged by operational experience and improved over time.

Start with a measurable problem, prove the operating model and establish who will own the capability.

Once those foundations are reliable, further use cases can be assessed on their own merits.