RFID in Europe: Plan a Deployment Country by Country - Yenra

Separate the three radio questions

On a small screen, scroll sideways to read all columns.

ETSI EN 302 208 V3.4.1 addresses UHF RFID equipment characteristics and measurement methods. Treat a named revision as a document to check against the equipment evidence and current applicable references; publication of a standard alone does not establish every national permission.

For EU equipment, the European Commission’s radio-equipment standards page and declaration-of-conformity guidance provide authoritative starting points. Identify the relevant national authority for each installation. Use CEPT Recommendation 70-03 and its implementation information as a regional cross-check, then confirm the controlling national conditions.

Control what is actually installed

Record the regional reader SKU, firmware, selected country profile, antenna model and gain, cable type/loss, power setting and mounting arrangement. Ask the supplier to explain how the complete radiated configuration meets the applicable limit and how unauthorized changes are prevented.

Use the regulator’s and manufacturer’s units exactly. Conducted transmitter power, effective radiated power and equivalent isotropically radiated power are different quantities. A value copied between fields with different definitions can invalidate the configuration. Have the responsible technical specialist verify the calculation and supporting component data.

Export the accepted configuration and identify who can alter it. After equipment relocation, replacement or firmware change, verify the destination settings before operation. A country name on a shipping label is not a configuration record.

Give each country an explicit release decision

A shared label can be tested across all intended routes, while readers remain configured for their own installation. Test the finished tagged product in representative packaging and orientation. Record misses, stray observations and recovery effort; a successful demonstration at one site does not characterize every site.

The release record should identify evidence dates, unresolved questions, the technical approver and the exact configuration tested. Keep a written reason for any difference from the common design.

Review linked records and responsibilities

Map what the system records beyond the tag: time, place, account, employee, customer or other associations. The European Data Protection Board’s guidance explains personal-data responsibilities, including information that can identify people indirectly. A numeric tag identifier may become personal data through its links.

Have the responsible privacy team assess applicable law, purpose, lawful basis, notices, access, retention and service-provider arrangements. Keep product inventory and people-related uses separately described. Record who can export observations and how deletion or retention rules reach downstream copies.

Maintain a country deployment packet

1. List the site, use case and country authority.
2. Save dated rule references, product declarations and exact configuration evidence.
3. Test the installed workflow with representative tagged items.
4. Resolve radio, data and operational questions with named owners.
5. Release the site against its documented configuration and retain the results.
6. Revisit after rule changes, hardware substitutions, firmware changes or relocation.

Use the linked official documents for current details; this planning record becomes useful when it shows both what was verified and which changes require another review.

Keep a working record

Download the editable rfid europe working record (plain text). Save a copy for each evaluation. It includes instructions, evidence fields and source links; record unresolved questions with their owner before signing off.