Software contract
Confirm whether the application needs a manufacturer SDK, PC/SC or libNFC. A board-size choice does not establish the software interface.
OEM / EMBEDDED / INTEGRATION PATH
OEM integration brings the reader, enclosure and software into one design. Choose the software path first, then confirm the exact board, connection and mechanical drawing for the equipment.
See the matching modelsDEFINE THE APPLICATION
An OEM module is one part of the finished system. Panel material, nearby metal, power, cable routing and card placement affect the installation. Compare board formats against your drawing, and test the actual enclosure with the project’s cards before freezing the equipment design.
Confirm whether the application needs a manufacturer SDK, PC/SC or libNFC. A board-size choice does not establish the software interface.
Provide the panel drawing, mounting method, power arrangement and connector requirements. Ask for the precise board and cable configuration.
Define a repeatable card placement and operation in the real enclosure. Treat reading performance as a test result for that installation.
THE HARDWARE
Protocols and connections depend on the selected configuration. Review the model details.

µFR Zero
A large-antenna OEM module to evaluate in the finished equipment enclosure.

PC/SC Zero
An XL OEM module for embedded projects using the PC/SC host stack.

DL533N
An XL OEM USB module for embedded installations using libNFC.
MAKE THE INQUIRY SPECIFIC
The installed result depends on the card, enclosure and placement. Define a sample test for the actual equipment instead of assuming a guaranteed distance.
OEM and finished configurations differ in enclosure, cabling and installation requirements. Request the configuration that matches the intended use.
Tell us your card type, platform and quantity. We’ll help narrow the options.