U.S. vs European UHF RFID Frequencies

What the two labels mean

The U.S. band relevant here is 902–928 MHz under FCC section 15.247. The European technical reference ETSI EN 302 208 covers 865–868 MHz and a separate 915–921 MHz band. Its scope specifies up to 2 W ERP for the lower band and up to 4 W ERP for the upper band, subject to its channel conditions. Those headline intervals are not an instruction to transmit anywhere inside them.

In a buying conversation, FCC and ETSI often act as convenient labels for alternative tag designs. Treat the label as the beginning of a specification. Ask the supplier to state the actual frequency interval for the finished model and the surface used for its performance test. A regional name copied from an IC's broad operating range cannot substitute for that information.

The practical question is whether the tag, reader, antenna, and local channel plan work together at the intended site. Start with the site, then identify the reader's permitted configuration, then shortlist tags. Reversing that sequence can leave you with a tag that looks attractive on a catalogue page but has no relevant evidence for the installation.

Compare the decisions, not just the band names

Compare the decisions, not just the band names

Decision	U.S. installation	European installation
Radio authority	FCC rules and the reader's authorization	Applicable national rules and equipment conformity
Familiar catalogue label	FCC	ETSI for the lower-band variant
Evidence to request	Finished-tag band and U.S. setup results	Finished-tag band and local setup results
Reader setting	Authorized country profile and antenna configuration	Authorized country profile and permitted channels
Export check	Review each destination separately	Review each destination separately

Use this comparison to organize a request for samples. It is not a list of interchangeable approvals. In particular, selecting a European country in a reader interface should be part of a documented commissioning process. Record the selected country, firmware, antenna model, cable, power setting, and channel behavior so another technician can reproduce the setup.

For a mobile deployment, build a country list before buying hardware. A reader that stays in one plant presents a different configuration problem from equipment moved between customer sites. Give the integrator the travel pattern and ask how approved profiles will be controlled. Do not assume the most recent setting remains suitable when the equipment crosses a border.

Keep power measurement bases intact

FCC section 15.247 distinguishes conducted transmitter power, antenna gain, and hopping conditions. For its 902–928 MHz hopping provision, the permitted conducted level depends on the number of hopping channels; higher antenna gain also changes the allowed conducted level. Keep those conditions attached to any quoted limit. The rule should be read with the approved reader documentation.

ERP and EIRP express radiated power using different antenna references. A reader setting shown in dBm, an antenna gain shown in dBi, and a legal limit expressed in ERP are not interchangeable entries in a spreadsheet. Ask the system supplier to show the calculation with its measurement basis and cable losses, and retain that calculation with the installation record.

For tag comparison, use the same lawful reader configuration for all candidates. If one sample is tested at a different setting, the result no longer isolates the tag choice. Record the setting rather than describing it as full power. That description is ambiguous across readers, firmware versions, antenna gains, and countries.

European upper-band availability needs a local check

An ETSI standard is a technical reference, while permission to operate comes from the relevant jurisdiction. An upper-band-compatible tag therefore does not by itself establish that the proposed upper-band installation is permitted at a particular address. Ask for the national rule and the exact approved reader profile before treating it as an option.

The United Kingdom illustrates why the distinction matters. Ofcom's April 2026 IR 2030 lists separate lower-band RFID entries and an upper-band entry covering specified channels within 916.1–918.9 MHz. It does not present the entire ETSI upper-band scope as one unrestricted transmit interval. Preserve the channel, bandwidth, power basis, and operating conditions in the installation specification.

When reviewing an old project document, check its date before reusing its country assumptions. Keep a dated copy or link to the applicable rule in the commissioning package. If the integrator cannot identify the rule behind a proposed profile, resolve that gap before approving the reader configuration or ordering a production tag batch.

Separate protocol compatibility from regional suitability

GS1 Gen2 Release 3.0.1 defines a passive UHF RFID air interface with a stated 860–930 MHz scope. That protocol scope is not a worldwide transmit allocation. Older chip documents can refer to an earlier Gen2 version; retain their version rather than silently treating it as the current release.

Your acceptance checklist should have separate lines for protocol support, tag frequency coverage, reader authorization, and mounted performance. This avoids an approval discussion turning into a debate about the chip logo. It also makes substitution review easier: a proposed replacement can satisfy one line while still needing evidence for another.

For laundry assets, request samples attached using the intended sewing, pocket, or bonding method. For metal assets, use the actual substrate and mounting method. Compare candidates in the same read zone with representative asset movement. Define a useful read event before testing, such as a correctly identified item passing through the agreed process checkpoint.

A buying and commissioning checklist

• Identify every destination country and whether readers move between sites.
• Obtain the reader's approval documents and intended country profile.
• Ask for the finished tag's band, exact model, chip option, and mounting assumptions.
• Retain power calculations with the stated ERP, EIRP, or conducted basis.
• Test representative attached samples under the permitted local configuration.
• Record successful reads, missed assets, unwanted reads, and the repeatable test setup.
• Recheck substitutions and firmware changes before introducing them into production.

Include those requirements in the sample request so suppliers can propose a suitable variant. The tag finder can narrow the catalogue, but final selection should follow the deployment evidence. Compare textile laundry tags or FR4 on-metal tags according to the asset and attachment, then request samples for the actual region.

When this does not apply

This comparison does not cover HF, NFC, LF, active tags, or radio installations outside the passive UHF RFID use case. It also does not establish approval for a country omitted from the examples. Specialized locations and deployment conditions need their own assessment, even when the frequency overlaps a familiar catalogue band.

If your problem is inconsistent reads within an already approved installation, review read-range troubleshooting and a repeatable sample test. If equipment will operate internationally, use the dated country frequency reference to organize further checks. Neither task can be completed by changing the tag's regional label alone.