How to Choose an Embedded RFID Reader Module: OEM Integration Checklist

The right RFID reader module is the one that reads your exact credentials, fits your host’s interface and power budget, and still performs inside your final enclosure. Start from the credential list, work outward to interface, antenna and firmware, and plan certification of the finished device before you freeze the design. That order avoids the most expensive redesigns.

The checklist and RFQ template at the end turn these decisions into a request a supplier can quote against.

Start with the credentials you must read

Credentials fix the frequency and protocol, and nothing else in the design can compensate for a module that does not support them. List every credential that must work in the field, including legacy cards, key fobs, wristbands, phones and tags.

Band	Carrier frequency	Air-interface standards	Typical credentials	Read distance class
LF	125 kHz (134.2 kHz for animal ID)	Proprietary EM4100 family; ISO 11784/11785 for animal ID	EM4100/TK4100, T5577, EM4305, HID Prox®-compatible, FDX-B ear tags	Centimeters
HF	13.56 MHz	ISO/IEC 14443 A/B, ISO/IEC 15693, NFC Forum tag types	MIFARE® Classic, DESFire®, NTAG®, ICODE®, NFC phones	Centimeters (≤ 10 cm for 14443)
UHF	860–960 MHz (regional sub-band)	ISO/IEC 18000-63 (EPC Gen2)	RAIN RFID labels, on-metal tags, windshield tags	Up to several meters

Then work through the details that trip up integrations:

• UID or data? Many modules only return the UID. If you need to read or write memory, authenticate MIFARE sectors, read DESFire applications or parse NDEF messages, confirm the command set supports each operation.
• LF modulation. A 125 kHz module that reads EM4100 does not automatically read HID Prox-compatible cards. EM4100 uses amplitude modulation with Manchester encoding, while HID Prox uses FSK, so the demodulator must support both. FDX-B animal tags run at 134.2 kHz and need a module built for that frequency.
• HF protocol coverage. Some 13.56 MHz front-ends support only ISO/IEC 14443 Type A. Multi-protocol NFC front-ends add Type B, ISO/IEC 15693 and FeliCa® (NFC-F). If phones must work, the module has to handle ISO/IEC 14443-4 (ISO-DEP) exchanges, not just MIFARE Classic reads.
• UID format. ISO/IEC 14443-3 UIDs can be 4, 7 or 10 bytes long. Confirm how the module outputs them (byte order, hex or decimal, fixed or variable length), because a mismatch with an existing database means cards “don’t work” even though they read.

Our 125 kHz reader modules and 13.56 MHz NFC modules cover single-band designs. For a mixed card population, multi-technology modules read LF and HF credentials from one board.

For UHF, the module must also be configured for the destination market: 902–928 MHz under FCC rules, 865–868 MHz under ETSI rules, and other sub-bands elsewhere. Check our UHF frequency by country guide before you fix a SKU, and browse UHF reader modules for embedded EPC Gen2 options.

Interface and power budget

Pick the interface from where the module sits relative to the host, not from habit.

Interface	Signal levels	Typical cable reach	Good fit	Watch-outs
TTL UART	3.3 V or 5 V logic	Same board or short harness	MCU-hosted devices	Match logic levels; agree baud rate and framing
RS232	Bipolar, ±3 to ±15 V	~15 m (50 ft)	Legacy industrial hosts	Never wire directly to TTL pins
RS485	Differential	~1,200 m (4,000 ft) at lower data rates	Module remote from the host	Termination, biasing, half-duplex turnaround
USB 2.0	5 V bus power	5 m (16 ft)	PCs, kiosks	Choose HID keyboard, virtual COM or PC/SC (CCID)
Wiegand	5 V, active-low pulses (typical)	~150 m (500 ft)	Feeding an access controller	One-way; host cannot send commands

Also decide how reads reach the host. In auto-read mode the module pushes a card number whenever a credential enters the field; in command-response mode the host polls. Check how the module handles duplicate-read suppression, card-removed events and several cards in the field at once (anticollision).

For power, ask for three currents separately: idle, RF field on, and sleep, plus any inrush at power-up. Field-on current dominates HF and LF budgets. Battery devices such as smart locks benefit from front-ends with low-power card detection, which wakes the full field only when something approaches the antenna.

UHF is a different scale. Many modules can transmit up to about +30 dBm (1 W) conducted, and regional rules then cap radiated power (for example 4 W EIRP in the FCC band and 2 W ERP in the ETSI 865–868 MHz band). Because the power amplifier is far from 100 % efficient, the module draws considerably more than 1 W from the supply while transmitting. Size the regulator and bulk capacitance for transmit bursts, or the module may brown out and reset mid-inventory.

Supply noise matters as much as capacity. LF and HF receivers detect small amplitude changes on the carrier, so switching-regulator ripple near 125 kHz or 13.56 MHz, or their harmonics, can cut read range. Feed the RF section from a linear regulator or an LC filter, and keep switchers away from the antenna.

Antenna: on-board vs external, and metal enclosures

Each band uses a different antenna, and each reacts differently to its surroundings:

• LF: a wire-wound coil, air-core or on ferrite, resonated at 125 kHz with a capacitor.
• HF: a PCB or wire loop with a matching network tuned to 13.56 MHz. External antenna boards connect over a short cable and must be matched to the module’s output, often 50 Ω.
• UHF: an on-board ceramic patch, or an external antenna on 50 Ω coax. Every dB of cable and connector loss comes straight off the link budget, so keep runs short and use low-loss cable.

Metal is the most common cause of disappointing range. Near an LF or HF antenna, metal carries eddy currents that oppose the reader field and detune the resonant circuit. Batteries, PCB ground planes and display backplanes count as metal. Mitigations include a non-metallic window in the enclosure, ferrite sheet between antenna and metal, more spacing, and retuning the matching network with the antenna in its final position. For UHF, metal reflects and blocks the field, so the antenna must see the tag through plastic or glass, not steel.

Two readers mounted close together can also interfere with each other. Keep antennas apart, or choose modules that support synchronized or time-shared operation. Where many UHF readers share a site, look for dense reader mode support.

Firmware, command sets and secure key storage (SAM)

Ask for the full protocol document, not just a demo application. A usable command set defines frame format, checksum, error codes and timeouts, and ideally ships with C example code for common microcontrollers. Confirm how settings (output format, baud rate, LED and buzzer behavior) are stored in non-volatile memory, how firmware is versioned, and whether it can be updated in the field over UART or USB. For USB smart-card style readers, PC/SC with the CCID class means standard operating-system drivers work without a custom driver.

Security starts with the credential. UID-only reading needs no keys but gives no protection against cloned or emulated cards. MIFARE Classic’s Crypto1 cipher is publicly broken, so use it for legacy compatibility only. For new secure designs, DESFire EV2/EV3 with AES-128 and key diversification (a unique key per card derived from a master key and the card UID) is the common choice. Our MIFARE Classic vs DESFire guide compares them in detail.

Then decide where keys live:

1. Host firmware. Simplest and weakest. Keys in host flash can be recovered if the firmware is read out, and they cross the UART in plain text whenever they are loaded.
2. Module protected storage. Keys are written once and cannot be read back; the module performs authentication internally and returns only the result or the data.
3. SAM (Secure Access Module). A contact smart card chip (ISO/IEC 7816, commonly in the plug-in ID-000 size) in a socket on the module. It stores keys and performs cryptography and key diversification, so master keys never leave it. The module needs both the socket and firmware support.

Certification considerations for the end device

The module is a component; regulators assess the product you ship.

• US (FCC Part 15, Subpart C). 125 kHz readers are typically evaluated against the general limits of §15.209, 13.56 MHz readers under §15.225, and 902–928 MHz UHF readers under §15.247. A module with a modular grant can be integrated without recertifying the transmitter, provided you follow the grant’s conditions (such as the approved antenna types) and label the host “Contains FCC ID: …”. The host still needs Part 15 Subpart B evaluation for unintentional emissions. Without a modular grant, the complete device needs its own certification. ISED Canada runs a parallel process.
• EU (Radio Equipment Directive 2014/53/EU). The company placing the finished product on the market under its own name performs the conformity assessment and signs the Declaration of Conformity. Commonly applied standards include ETSI EN 300 330 (short-range devices below 30 MHz, covering 125 kHz and 13.56 MHz readers), ETSI EN 302 208 (UHF RFID), ETSI EN 301 489-1 and -3 (EMC), EN 62368-1 (electrical safety) and EN 50364 (human exposure from RFID). RoHS (2011/65/EU) applies to materials.
• Other markets. The UK, Japan, Australia and others have their own radio rules; confirm them early if you sell there.

Ask which test reports exist for the module, against which standards, and with which antenna. Changing the antenna or its cable can take you outside the module’s tested configuration. For UHF, make sure the region setting is locked in firmware for each market.

OEM module vs hobby board

Hobby breakout boards are useful for a proof of concept. They are rarely the right part for a product that ships in volume.

Factor	OEM reader module	Hobby / breakout board
Documentation	Full command protocol, electrical data, mechanical drawing	Community examples, partial data
Operating temperature	Specified range (confirm per model)	Often unspecified
Supply continuity	Stable bill of materials; ask about change notification	Parts may change without notice
Connectors	Locking connectors or solder pads	Pin headers
RF tuning	Tuned for the specified antenna	Varies between batches
Compliance data	Test reports may be available on request	Rarely available
Firmware	Versioned and configurable	Your own code driving a bare reader IC

Sampling, validation and volume pricing

Order samples of each shortlisted module and test them in your product, not on the bench. A practical validation plan covers:

• Every credential type, in the final enclosure, at minimum and maximum supply voltage
• The product’s full operating temperature range
• ESD on user-touchable surfaces (IEC 61000-4-2)
• Multiple cards in the field, fast and slow presentations, and partial presentations
• Coexistence with other radios in the product (Wi-Fi, Bluetooth, LTE) and with switching supplies
• A long soak test for lock-ups, plus host recovery after a module reset
• The firmware update procedure, end to end

Volume pricing depends on quantity, customization (firmware defaults, output format, antenna size, connector, cable length, labeling), packaging and lead time. Once validation passes, freeze the firmware version and configuration and keep a reference sample for incoming inspection. Our OEM customization page explains what can be adjusted before production.

OEM integration checklist

• Every credential in the field listed with frequency, protocol and data to read
• Module supports the required protocols (ISO/IEC 14443 A/B, ISO/IEC 15693, NFC, EPC Gen2) and commands
• Interface and logic levels match the host; baud rate and framing agreed
• Supply rated for field-on and peak current; RF supply filtered
• Antenna position fixed, tuned and tested in the final enclosure
• Metal, batteries and displays kept clear of the antenna or shielded with ferrite
• Key storage decided: host, module protected storage or SAM
• Firmware version, update path and configuration locked for production
• UHF region configuration matches each destination market
• Certification path planned: FCC/ISED modular use, RED Declaration of Conformity, host emissions
• Samples validated across temperature, voltage and ESD
• Change-notification and lifecycle expectations agreed with the supplier

RFQ template (copy and paste)

Product / application:
Credentials to read (chip, frequency, protocol):
Data required (UID only / read memory / write / secure application, e.g. DESFire AES):
Key storage (host / module / SAM socket):
Host interface (TTL UART 3.3 V or 5 V, RS232, RS485, USB HID / virtual COM / PC/SC, Wiegand):
Supply voltage and current budget:
Antenna (on-board / external; enclosure material; distance to metal):
Target read distance with your credential:
UHF only: target region(s) and required output power:
Operating temperature range:
Mechanical limits (max board size, connector type):
Certifications required for the end product:
Firmware customization (output format, defaults, LED/buzzer behavior):
Annual volume, first-order quantity and samples needed:
Target sample and production dates:

Next steps

Send the completed template through our request-a-quote form. We shortlist modules that match your credentials and interface, confirm compatibility before quoting, and arrange samples for your validation build.