Lowry Solutions

Cycle counting is supposed to protect accuracy.

But in a lot of operations, it creates its own disruption.

People stop what they are doing.
Locations get checked one by one.
Counts get written down or entered later.
Someone reconciles the numbers after inventory has already moved again.

By the time the count is finished, the operation has changed.

That is the part people forget.

A count is only useful if it reflects the business closely enough to support decisions.

RFID helps by making counts faster, more frequent, and less dependent on someone physically touching every item.

More tags can be read at once.
Locations can be checked with less interruption.
Reconciliation can happen closer to actual movement.

That does not mean process discipline goes away.

It means the process stops consuming so much operational time.

The question is not only:

“How accurate is our inventory?”

The better question is:

“How much work does it take to prove it?”

If the cost of checking accuracy is too high, teams will check less often.

And that is when small inventory errors become bigger operational problems.

Retail shrink gets treated like a loss problem.

Sometimes it is.

But some of the most expensive inventory problems do not look like theft at first.

They look like confidence.

The system says the item is available, so replenishment does not trigger. The online order gets accepted, because the record says the store has stock, store associate checks the shelf, then the backroom, then another location, because the system says the item should be there.

The customer does not care what the system says.

They only see that the product is not available.

That is the danger of phantom inventory.

It hides inside “available” stock.

RFID helps because item-level visibility makes it harder for bad records to sit unnoticed.

Instead of waiting for manual counts, stores can check inventory more often, compare system records against physical reality faster, and catch the gap before it turns into lost sales.

The real value is not just counting better.

It is catching the inventory lie before the shopper does.

Quick check:

How often does your system say an item is available, while the shelf, associate, or customer says it is not?

That is where inventory accuracy becomes a revenue problem.

RFID problems do not always start at the reader.

Sometimes they start much earlier.

At the label. A tag can be attached and still be wrong.

Wrong inlay for the product.
Wrong EPC.
Duplicate encoding.
Poor placement.
Bad print quality.

Then the team blames the reader.

Or the software.Or the warehouse process.

But the system was already carrying bad data before the item moved.

That is why source tagging matters.

It is not just a labeling task. It is the first data-quality step in the RFID workflow.

If the tag is wrong, every system after it has to work around that mistake.

The better question is not: “Did we tag the item?”

It is: “Can we trust the identity we just attached to it?”

That is the difference between RFID that reads and RFID that works.

Returnable containers are supposed to save money.

That is the whole point.

You buy the tote, bin, rack, pallet, or container once, then keep it moving through the supply chain.

But the economics change when the return loop is weak.

The product reaches the customer.
The shipment gets closed.
The invoice gets handled.

But the container is still sitting somewhere outside your control.

Maybe it is at a supplier.
Maybe it is sitting at a customer site.
Maybe it moved to another facility.
Maybe nobody knows because nobody owns that part of the loop.

That is where RFID helps.

Not by telling you that the container exists.

You already know it exists.

RFID helps by giving that returnable asset an identity and movement history, so the business can see where it went, how long it has been there, and which partner or site is holding it.

The better question is not:

“How many containers do we own?”

The better question is:

“How many containers are unavailable right now because we cannot see the return loop?”

That is usually where the shortage starts.

A hospital does not need to lose equipment for it to become a problem.

It only has to be unavailable when someone needs it.

Infusion pumps. Wheelchairs. Monitors. Mobile equipment.

If staff have to walk the floor, call another unit, or check a storage room manually, that time is already gone.

The issue is not always loss.

It is search time.

That is where RFID and RTLS matter.

Not because they make equipment “trackable” in theory.

Because they reduce the time between:

“We need it” and “Here it is.”

That gap matters in healthcare.

A handheld RFID reader is not a cheaper fixed portal.

It is a different workflow.

Fixed readers make sense when the read should happen automatically.

Dock doors.
Conveyors.
Entry points.
Movement zones.

Handheld readers make sense when the work is variable.

Audits.
Cycle counts.
Asset searches.
Exception handling.

The wrong question is: “Which RFID reader should we buy?”

The better question is: “Where does the business need the read to happen?”

That answer tells you whether the read should be automatic, manual, mobile, or built into a process checkpoint.

If you skip that step, you do not have a reader strategy.

You have hardware.

Retail RFID compliance breaks in the details.

Not in the idea.

A supplier can tag every item and still run into problems if the EPC is wrong, duplicated, poorly printed, or placed where it does not read well.

That is the part many teams underestimate.

The retailer mandate is not just asking for a tag.

It is asking for readable, standardized product identity at scale.

Before you ship, ask:

Can we verify the tag?
Can we trust the encoding?
Can we catch bad reads before the retailer does?

That is where the real readiness check happens.

RFID gives you visibility.

RFID + IoT gives you response.

That’s the real shift.

A tag read can tell you something moved.

But when RFID connects with sensors, gateways, and connected systems, it can also tell you:

Whether the condition changed
Whether an alert should trigger
Whether a workflow needs to start

That is where operations get faster.

Not because someone checks a dashboard sooner.

Because the system can surface the next action faster.

But connected systems come with a different responsibility.

If one part of the flow is weak, the issue doesn’t stay isolated.

A bad read, delayed alert, or broken integration can affect the next workflow.

So before expanding into RFID + IoT, check three things:

Can the system trust the data?
Can it trigger the right action?
Can your team see when something goes wrong?

That is the difference between connected tracking and connected control.

RFID improves traceability.

You can see:

Where something moved. When it moved. How it moved

That’s powerful.

But traceability only helps if the system behind it is reliable.

If there are gaps in reads, data flow, or system alignment, you don’t get better answers.

You get faster wrong ones.

Traceability depends on:
- Consistent reads
- System alignment
- Data integrity

Where RFID helps: It creates a full movement history that can reduce recall time, audit complexity, and manual investigation.

But the fix is not “track more.”

The fix is to test the trace.

Can every movement be followed end to end?
Does the data match across systems?
Can your team trust the record without rebuilding it manually?

Start there before the next audit, recall, or compliance review forces the issue.

RFID fixes one problem immediately.

Manual dependency.

No missed scans
No skipped steps
No “someone forgot”

That’s real value.

But then something else shows up.

Now you have continuous data instead of clean snapshots.

And unless that data is processed properly, it slows decisions instead of speeding them up.

Research shows RFID streams contain duplicates and incomplete reads that must be filtered before they become usable

So the real shift is this:

RFID doesn’t give you clarity by default

It gives you raw visibility

Clarity comes from how that data is handled

If you’re evaluating RFID:

Don’t just ask “What will we see?”

Ask “How will we decide from what we see?”

That’s where the system either works or breaks