5 RFID Implementation Mistakes to Avoid

Why RFID Implementations Fail in Indonesia

UHF RFID technology has proven itself in thousands of warehouses and factories worldwide. Yet in Indonesia, many companies that have invested in RFID end up frustrated because the system doesn't deliver the expected results.

The problem is almost never the technology itself. RFID fails not because of poor equipment, but because of avoidable planning and implementation mistakes.

Across RFID projects in Indonesia, the same mistakes appear again and again. This article summarizes the 5 most common mistakes and, more importantly, how to avoid them.

Mistake #1: Choosing the Wrong RFID Tags

This is the most expensive and most common mistake. Many companies buy the cheapest generic RFID tags without considering the actual environmental conditions in their warehouse or factory.

Why This Is a Major Problem

UHF RFID operates between 860 and 960 MHz (920 to 923 MHz in Indonesia). These signals are highly sensitive to certain materials:

Generic tags that work perfectly in open air can fail completely when attached to metal drums, liquid bottles, or damp wooden pallets.

The Solution: A Site Survey Before Buying Tags

Before deciding on a tag type, conduct an RF site survey that includes:

1. Identifying all materials to be tagged (metal, liquid, plastic, wood, etc.)
2. Measuring RF conditions in the warehouse (interference from machines, building structure)
3. Testing at least 3 different tag types on real product samples
4. Recording read rates at various distances and orientations

The right tags for Indonesian conditions:

• On-metal tags for equipment and metal assets (machinery, racks)
• UHF tags designed for liquids for F&B, pharma, and cold storage products
• Laundry tags for hotel and hospital linen (heat resistant up to 150°C)
• Hard reusable tags for pallets and containers that get washed
• Wet inlays / paper labels for standard cardboard and packaging

Impact of this mistake: Replacing thousands of tags that are already attached means repeating the entire tagging effort and disrupting operations all over again.

Mistake #2: Underestimating Reader Placement

"Just put readers anywhere; they'll read all the tags." This is a very dangerous assumption.

Common Problems

Dead zones: Areas of the warehouse that aren't covered because the reader signal doesn't reach them. Tags pass through but aren't recorded, and inventory data becomes inaccurate.

Ghost reads: A reader picks up tags outside its intended zone, so products on shelf A are "read" by the reader in zone B. Inventory reports become chaotic.

Multipath interference: In warehouses with tall metal racks, RFID signals bounce in all directions, creating inconsistent readings.

Overloading: One reader trying to read hundreds of tags at once in a dense area leads to a high collision rate and many missed tags.

How to Avoid It: Proper RF Planning

Step 1: Heat mapping. Map the warehouse with an RF coverage simulation. Tools such as the Zebra and Impinj RFID planning guides, or specialized software, can visualize each reader's coverage area.

Step 2: Choke point design. Focus readers on "choke points", the locations that ALL items MUST pass through: warehouse entry and exit doors, loading dock doors, and conveyor checkpoints. Don't try to cover the entire warehouse floor with readers.

Step 3: Antenna orientation. Aim reader antennas correctly. Linear and circular polarization provide different coverage for different tag orientations.

Step 4: Physical testing. Before permanent installation, conduct a walk test with a portable reader: walk around the area while reading sample tags. Identify dead zones and reposition readers before mounting them permanently.

The number and placement of antennas, along with the read-rate target, should be determined through a site survey and tests with sample items.

Mistake #3: Not Training the Staff Who Will Use the System

Many companies assume: "RFID is automatic, so staff don't need training." This is fundamentally wrong.

What Happens Without Adequate Training

• Operators store items in the wrong positions: Items block each other and read rates drop sharply
• Staff don't know how to handle "tag not found": Items are assumed lost when the tag is actually damaged or badly positioned
• Managers can't read system reports: RFID data exists but isn't used for decisions
• Old SOPs keep running in parallel: Staff continue manual entry because "it's more reliable," creating duplicate data
• Readers aren't restarted after errors: The system freezes, and operators keep working without realizing data isn't being saved

An Effective Training Program

Ideally, RFID training is delivered at 3 levels:

Level 1: Daily Operators (2 to 3 hours)

• Correct scanning technique with a handheld reader
• What to do if a tag can't be read
• How to confirm actions in the mobile app
• Signs that a reader has a problem

Level 2: Supervisors and Team Leads (4 to 6 hours)

• How to read the real time dashboard
• Interpreting inventory reports
• How to conduct RFID stock audits
• Escalation procedures for system anomalies

Level 3: IT/Admin (1 day)

• Basic system configuration
• How to add and remove asset tags
• Data backup and export
• Support contacts and escalation

Mandatory: A parallel run of 7 to 14 days, with RFID and the old system running side by side. This builds staff confidence that the new system is accurate before the old one is shut down.

Mistake #4: Not Defining Clear Use Cases Before Implementation

"We want to implement RFID for inventory." That is not a use case; it's a wish.

Without a specific definition of what you want to achieve, RFID implementations often end with a system that "runs but doesn't deliver real value."

Signs of Unclear Use Cases

• Success KPIs were never defined before starting
• No business processes changed after RFID was installed
• RFID reports exist, but no one reads them regularly
• "Our RFID is 80% accurate," but there was no clear target, so 80% is considered "good enough"
• The implementation finished, but the results were never measured

A Framework for Defining the Right Use Case

Before starting implementation, answer these 5 questions:

1. What specific business process do you want to improve?

Bad example: "We want to know where all our items are"

Good example: "We want to shorten the cycle count from 3 days to 4 hours at most"

2. What are the measurable success metrics?

Bad example: "More accurate inventory"

Good example: "Read rate > 99%, inventory accuracy > 99.5%, audit time < 4 hours"

3. Who will use RFID data daily, and for what decisions?

Warehouse manager: which items expire this week?

Purchasing: when should we reorder, based on real time stock?

4. What needs to change in existing SOPs?

List the specific SOP changes that will take effect once RFID is active.

5. What is the current baseline?

Measure the current state without RFID: how long do audits take? What's the error rate? How often do stockouts occur?

Without a baseline, there's no way to measure real improvement.

Mistake #5: Choosing a Vendor Based on Lowest Price Alone

"Vendor A is cheaper than Vendor B, so we'll choose Vendor A."

This logic is very dangerous for RFID implementation, because the biggest costs aren't in the initial hardware; they're in failures, rework, and long term support.

What's Often Missing from Cheap Proposals

Hidden Costs of the Lowest Bid

Items that are often overlooked:

• Rework if reader placement is wrong: extra labor plus operational downtime
• Tag replacement if tags don't suit the conditions: thousands of tags removed and reapplied
• Data gaps during system downtime: every day of downtime in a 200-SKU warehouse means inaccurate inventory and wrong decisions
• Unplanned custom integration: Built from scratch after the contract is already signed
• Internal time spent troubleshooting the system: 100+ hours of IT manager and supervisor time

Together, these hidden costs can easily exceed the initial price difference.

RFID Vendor Evaluation Checklist

Use this list when selecting a vendor:

✅ Does the vendor conduct an RF site survey before proposing a solution? ✅ Is there a pilot project of 2 to 4 weeks before full rollout? ✅ Does the vendor have client references in the same industry? ✅ Is there a written SLA for support response time? ✅ Does the software have a clear update roadmap? ✅ Has ERP integration actually been done before (not just promised)? ✅ Is there a structured onsite training program?

How Katalyst Avoids These 5 Mistakes

At Katalyst, every implementation follows a 4-phase methodology designed to prevent all five mistakes above:

Phase 1: Discovery & RF Survey (Week 1) A site visit is mandatory. We map the warehouse or factory, identify all materials, take RF measurements, and test at least 3 tag types in real conditions before making any recommendations.

Phase 2: Pilot Installation (Week 2) We install the system in a limited area (one zone or one shift), measure actual read rates, fine-tune reader positions if needed, and validate the data against real business processes.

Phase 3: Training & Parallel Run (Week 3) Staged training for operators, supervisors, and IT, followed by a parallel run of 7 to 14 days with RFID and the old system side by side until the team is confident.

Phase 4: Full Rollout & Hypercare (Week 4 Onward) Full go-live with onsite support during the first weeks, and agreed response times for support after that.

Conclusion

RFID is not "plug and play" technology. Investing in proper planning (a site survey, the right tags, planned reader placement, staff training, and an experienced vendor) is the difference between an RFID system that delivers real results and one that never lives up to expectations.

5 mistakes you must avoid:

1. ❌ Buying cheap generic tags without a site survey
2. ❌ Installing readers at random without RF planning
3. ❌ Neglecting staff training
4. ❌ Starting without clear use cases and KPIs
5. ❌ Choosing a vendor on lowest price alone

Want to make sure your RFID implementation succeeds from the start? Free consultation with the Katalyst team →

Discuss Your RFID Project → | See Our Industry Workflows → | RFID Vendor Selection Guide →