What Specifications Should You Send to an RFID Card Manufacturer?

An RFID card manufacturer cannot quote or produce a technically correct card from the phrase “custom RFID card” alone. For a reliable quotation, sample, and production plan, the manufacturer needs enough information to understand the application, reader environment, RFID technology, chip, antenna, card construction, data requirements, quantity, testing criteria, and delivery expectations.

For a typical B2B RFID card project, the most useful RFQ information is:

Application → Existing system → Reader → Frequency → Protocol → Exact chip → Memory/security → Antenna/RF requirements → Card material and dimensions → Printing/personalization → Encoding → Quantity → Sample testing → Delivery

The more complete these specifications are, the less risk there is of receiving a card that looks correct but does not work with the intended reader or software.

What Information Does an RFID Card Manufacturer Need?

A manufacturer normally needs information in five major groups:

For complex projects, the manufacturer may also need existing cards, reader documentation, sample credentials, or application-specific acceptance criteria.

A useful RFQ should therefore answer two questions:

What must the card physically be?

and

What must the card do inside the customer’s system?

The second question is often more important.

Start With the Application and Existing System

Before specifying a chip, describe the application.

For example:

·access control

·hotel key cards

·employee identification

·transportation

·membership

·ticketing

·NFC interaction

·product authentication

·asset tracking

·another application

The application helps define the technical requirements.

An access-control card may require authentication and reader compatibility. A hotel card may need to match a particular lock system. An NFC business card may need smartphone compatibility. A UHF inventory application may have completely different antenna and reading requirements.

Tell the Manufacturer Whether the Project Is Existing or New

This is one of the most important pieces of information in an RFQ.

State whether the order is:

1. Existing-system replacement

2. Migration project

3. New project

The same chip should not automatically be recommended in all three situations.

For an installed legacy system, compatibility may be the primary requirement.

For a migration project, compatibility and future security requirements must be considered together.

For a new high-security project, the buyer should evaluate current-generation chip options rather than automatically reproducing a legacy credential specification.

RFID Chip and Frequency Specifications

Should You Specify the Exact RFID Chip?

When the project already has a defined chip architecture, provide the exact IC or part family.

Examples include:

·MIFARE Classic

·MIFARE Plus EV2

·MIFARE DESFire EV3

·NTAG 213/215/216

·ICODE

·UCODE

·another specified RFID IC

If the chip has not been selected yet, provide the application, reader and security requirements and ask the manufacturer to recommend compatible options.

Do not write only:

“13.56 MHz RFID card.”

13.56 MHz identifies the operating frequency, but not the complete credential architecture.

For example, NXP’s NTAG 213/215/216 operate at 13.56 MHz and comply with NFC Forum Type 2 Tag and ISO/IEC 14443 Type A, with different memory options. (nxp.com)

MIFARE DESFire EV3 is also a 13.56 MHz-class contactless smart-card technology, but its application architecture and security capabilities are very different. NXP lists DESFire EV3 as an active product with ISO/IEC 14443 Type A support, mutual authentication, multiple application keys, AES and other security functions. (nxp.com)

Specify the Chip Generation

A chip family name may not be enough.

For example, NXP currently states that:

·MIFARE Classic EV1 is active but not recommended for new designs, with MIFARE DESFire Light recommended instead.

·MIFARE DESFire EV1 is not recommended for new designs, with DESFire EV3 identified as the replacement.

·MIFARE DESFire EV2 is still listed as active but is not recommended for new designs, with DESFire EV3 identified as its replacement.

Therefore, an RFQ for a new system should specify the exact generation and should not assume that an older IC is the correct choice simply because it is widely used.

How Should Frequency Be Specified?

Specify both:

frequency + technology

Examples:

·125 kHz LF

·13.56 MHz HF / NFC

·13.56 MHz ISO/IEC 15693

·UHF / EPC Gen2v2

For UHF projects, the exact regional operating requirements and reader system should be confirmed rather than treating “860–960 MHz” as a universal single operating condition.

The frequency also needs to match the reader architecture.

A 13.56 MHz card should not be specified without confirming that the reader supports the appropriate HF technology and protocol.

Reader and Protocol Requirements

One of the most commonly overlooked RFQ items is the reader.

Always Provide the Reader Model When Possible

Instead of:

“The customer uses RFID.”

provide:

“Reader manufacturer + model + application/lock/controller.”

The exact reader model can reveal important compatibility requirements.

For example, a buyer may have:

·an access-control reader

·a hotel lock

·a transportation validator

·a mobile NFC environment

·a UHF fixed reader

The RFID card must be compatible with the actual system, not simply with the frequency on paper.

Specify the Communication Standard

Where known, specify:

·ISO/IEC 14443

·ISO/IEC 15693

·NFC Forum technology

·EPC Gen2 / Gen2v2

·another project-specific protocol

NXP’s MIFARE DESFire EV3 documentation, for example, identifies ISO/IEC 14443 Type A and ISO/IEC 14443-4 transmission support.

For ICODE products, NXP specifies ISO/IEC 15693 and ISO/IEC 18000-3 interfaces for applicable products.

For UHF RFID, product selection is likewise tied to the UHF reader and EPC/RFID air-interface architecture. NXP’s UCODE family materials describe EPC Gen2v2 support for UHF applications.

Memory, Security and Data Requirements

Memory

Do not specify memory just because a larger number sounds better.

Instead, explain what the card needs to store.

For example:

·card ID only

·small NDEF record

·access-control data

·multiple applications

·transportation application

·authentication-related data

·EPC data

·custom application data

NTAG 213/215/216, for example, provide different user-memory capacities, so the model should be selected according to the actual application.

Security

Specify the required security functions rather than simply writing:

“High security.”

More useful information includes:

·authentication required

·encryption required

·AES requirement

·secure messaging

·key management

·application separation

·transaction security

·backend security requirements

For a new high-security smart-card project, current chip architecture should be evaluated rather than automatically copying the legacy chip.

NXP’s MIFARE DESFire EV3 currently includes mutual authentication, AES-128, secure RF-channel encryption, multiple key sets and other security mechanisms.

Data Structure

Tell the manufacturer what kind of data must be encoded.

Examples:

·UID reference

·card serial number

·application ID

·NDEF message

·EPC

·customer number

·employee number

·hotel credential data

·access-control credential data

However, not every value can be arbitrarily changed.

For example, some chip identifiers are programmed and protected during semiconductor production. Therefore, buyers should distinguish between:

chip UID

and

customer-assigned application/card number.

The manufacturer should confirm which fields can actually be programmed.

Antenna and RF Performance Requirements

Should Read Range Be Specified?

Yes, but read range should not be specified as an isolated number.

Instead of:

“Read distance: 100 mm.”

provide:

·reader model

·operating environment

·intended orientation

·card type

·required interaction

·whether the figure is a target or a measured acceptance criterion

NXP’s product documentation illustrates why this matters. DESFire EV3’s stated operating distance depends on power provided by the reader and antenna geometry.

NTAG 213/215/216 similarly state operating distance up to 100 mm depending on parameters including field strength and antenna geometry.

What Antenna Information Should You Provide?

If the antenna is already defined, provide:

·antenna type

·dimensions

·coil geometry

·existing inlay

·target resonance, if specified

·reference card

·reader information

If it is not defined, tell the manufacturer:

“Antenna design to be proposed and validated with our reader.”

That allows the supplier to engineer the card as a complete RF system.

Card Material, Size and Construction

Material

Specify the required card material where the project already defines it.

Common choices include:

·PVC

·PET

·PETG

·PC

·ABS

·paper

·other project-specific materials

Choose the material based on:

·durability

·environment

·bending requirements

·printing

·lamination

·surface finish

·expected service life

Size

Specify:

·CR80 / ID-1

·another standard

·custom dimensions

ISO/IEC 7810:2019 defines physical characteristics for identification cards, including materials, construction and dimensions. ISO states that the 2019 edition remains current after review in 2025.

For a standard ID-1-style card, ISO/IEC 7810 uses nominal dimensions of approximately 85.60 × 53.98 mm.

Thickness

Specify the finished-card thickness, not just the thickness of an inlay.

For example:

·0.76 mm

·thinner card

·thicker card

·custom thickness

The actual achievable structure depends on the chip, inlay, material and production process.

Card Construction

Tell the manufacturer whether you need:

·standard contactless card

·transparent window

·layered construction

·dual-interface

·dual-frequency

·key card format

·custom shape

·reinforced construction

The manufacturer should confirm whether the requested structure is technically compatible with the RFID assembly.

Printing, Encoding and Personalization

A complete RFQ needs both visual specifications and electronic specifications.

Printing

Specify:

·artwork file

·logo

·colors

·front/back printing

·surface finish

·variable data

·numbering

·barcode

·QR code

Personalization

Possible requirements include:

·name

·photo

·employee number

·card number

·serial number

·laser engraving

·variable printing

Encoding

Specify:

·whether encoding is required

·data format

·encoding tool/software, if relevant

·card numbering logic

·sequential or random numbering

·application data

·NDEF

·EPC

·authentication/key-loading requirements where applicable

A useful RFQ should also identify how encoding will be verified.

For example:

“The printed card number must match the encoded application number.”

That is much more useful than simply writing:

“Encoding required.”

Quantity, MOQ, Samples and Delivery

Quantity

Tell the manufacturer:

·sample quantity

·pilot quantity, if applicable

·first production quantity

·expected annual or repeat quantity

Quantity can influence production economics and the appropriate manufacturing process.

MOQ

Do not assume that every RFID product has the same MOQ.

MOQ can vary according to:

·chip

·material

·card size

·customization

·artwork

·encoding

·packaging

·tooling

·special antenna

·production setup

Current manufacturer pages illustrate this variability. Some suppliers state that MOQ depends on the degree of customization rather than a single universal number.

Therefore the RFQ should say:

“Required quantity: 20,000 cards. Please confirm MOQ and pricing for this configuration.”

Samples

State whether you require:

·stock sample

·engineering sample

·custom printed sample

·encoded sample

·fully personalized production sample

For a system-integrator project, the most useful sample is usually the same technical configuration intended for mass production.

Delivery

Provide:

·destination country

·required arrival date

·desired sample date

·desired production date

·shipping method, if already known

Lead time can depend on chip availability, card material, artwork, encoding, personalization and packaging.

Some current supplier pages explicitly quote lead times only after the specification is frozen.

What Should You Test Before Bulk Production?

A buyer should approve more than the appearance of the card.

A suitable acceptance process may include:

Physical Testing

·dimensions

·thickness

·flatness

·printing

·surface finish

·artwork

·variable data

RFID Testing

·reader detection

·read/write behavior where applicable

·authentication

·data integrity

·required interaction distance

·repeated operation

System Testing

Use the actual:

·access-control reader

·hotel lock

·transportation terminal

·NFC smartphone

·backend software

where applicable.

Encoding Verification

Verify that:

·encoded data is correct

·printed data matches encoded data

·serial numbering is correct

·application data is correctly structured

Sample Acceptance Criteria

Define these before mass production.

For example:

“The sample must be detected by the specified reader, pass the required authentication, contain the agreed application data, and match the approved artwork.”

This turns “sample approval” into an objective production checkpoint.

Legacy System, Migration or New Project?

This should be explicitly stated in the RFQ.

Existing Legacy System

Provide:

·current reader model

·current card model

·current chip

·frequency

·protocol

·existing credential format

·required compatibility

The objective is:

replace the credential without unexpectedly changing the system architecture.

Migration Project

Provide both:

current technology

and

target technology.

MIFARE Plus EV2 is an example of a product designed to support migration from legacy infrastructure toward AES-128-based higher security levels, with backward compatibility modes for certain legacy environments. NXP currently lists it as Active.

The RFQ should therefore describe:

·old readers

·new readers

·old credentials

·new credentials

·migration period

·compatibility requirements

·security target

New High-Security Project

For a new project, avoid specifying an old chip simply because it is familiar.

NXP currently marks MIFARE Classic EV1 and DESFire EV1 as not recommended for new designs, while DESFire EV3 is currently listed as Active.

The RFQ should therefore specify:

·security objective

·reader architecture

·protocol

·exact chip generation, if already selected

·memory

·application architecture

·authentication

·personalization

·testing

·long-term supply expectations

RFID Card RFQ Specification Table

The following table can be copied directly into an RFQ.

Which Specifications Should the Buyer Define, and Which Can the Manufacturer Recommend?

Not every item should be chosen by the buyer alone.

Usually buyer-defined

·application

·existing reader

·existing system

·security requirements

·card size

·artwork

·quantity

·delivery requirement

·required data

·acceptance criteria

May be manufacturer-recommended

·antenna geometry

·card construction

·suitable material combination

·manufacturing method

·packaging method

·some chip alternatives

·production process

Should be mutually validated

·exact chip

·protocol

·antenna

·read performance

·encoding method

·card thickness

·sample acceptance criteria

This division can prevent a common procurement mistake:

Asking a manufacturer to choose a technically critical component without providing enough system information.

Questions to Ask an RFID Card Manufacturer

Before approving a supplier, ask:

1. Can you support the exact chip and protocol required?

2. What reader information do you need for compatibility confirmation?

3. Can you recommend the antenna for our reader environment?

4. Can you provide an encoded sample?

5. Can the sample use the same materials and card construction as mass production?

6. How is RF performance tested?

7. How is encoding verified?

8. Can printed and encoded data be cross-checked?

9. What QC checkpoints are used?

10. What is the MOQ for this exact configuration?

11. What is the sample lead time?

12. What is the bulk-production lead time?

13. How is the approved sample used as a production reference?

14. Can repeat orders use the same locked specification?

15. What changes would require new samples or requalification?

The best supplier evaluation is therefore based on the supplier’s ability to freeze, manufacture, test and reproduce the complete specification, not simply provide a low initial unit price.

RFID Card Manufacturing: From RFQ to Bulk Production

A well-defined B2B project typically moves through:

RFQ

↓

Technical review

↓

Chip / antenna / construction confirmation

↓

Quotation

↓

Engineering sample

↓

Customer testing

↓

Sample approval

↓

Specification freeze

↓

Bulk production

↓

Encoding / personalization

↓

Final QC

↓

Packaging and shipment

The important stage is specification freeze.

After sample approval, buyers should clearly define which parameters are fixed, including:

·chip

·artwork

·dimensions

·thickness

·antenna

·encoding

·personalization

·packaging

·acceptance criteria

This reduces the risk of receiving a production batch that differs from the approved sample.

A Practical RFQ Template

A concise RFQ can be written like this:

Application: Access control

Project Type: New project

Reader: [Manufacturer + model]

Frequency: 13.56 MHz

Protocol: ISO/IEC 14443 Type A

Chip: MIFARE DESFire EV3

Security: Secure authentication required

Memory: According to selected application architecture

Antenna: Supplier to recommend and validate

Read Performance: Must work with specified reader

Card Material: PVC

Size: CR80 / ID-1

Thickness: 0.76 mm

Artwork: Attached

Personalization: Employee name + card number

Encoding: Application data according to attached format

Quantity: 20,000 pcs

Sample: Encoded production-spec sample required

Testing: Reader compatibility + encoding verification

Packaging: 100 pcs/bag

Destination: [Country / City]

Required Delivery: [Date]

This is substantially more useful to a manufacturer than:

“Please quote 20,000 custom RFID cards.”

Final Recommendation

A strong RFID card RFQ should provide enough information for the manufacturer to answer four questions:

Will the card work with the customer’s system?

Can the card be manufactured according to the physical and electronic requirements?

How will the finished card be tested and approved?

Can the approved configuration be reproduced consistently in bulk production?

At minimum, provide:

Application → Reader → Frequency → Protocol → Chip → Security → Memory → Antenna/RF requirements → Material → Size → Thickness → Artwork → Encoding → Personalization → Quantity → Sample → Testing → Delivery

For an existing system, prioritize compatibility.

For a migration project, document both the current and target architectures.

For a new high-security project, confirm current chip status and evaluate the exact generation rather than simply copying an older credential specification.

The most useful RFQ is not necessarily the longest one. It is the one that removes ambiguity from the technical decisions that can affect compatibility, production, testing and total project cost.

Request a Quote

Send the application, reader model, chip requirement, card construction, data requirements, quantity and delivery target to obtain a project-specific quotation.

Get Samples

For reader- or encoding-sensitive projects, request a production-spec sample and test it before approving bulk production.

Talk to an RFID Expert

When the chip, antenna or reader architecture has not yet been finalized, ask the manufacturer to review the system requirements before the RFQ is frozen.

FAQ

What specifications should you send to an RFID card manufacturer?

At minimum, provide the application, existing system status, reader model, frequency, protocol, chip, memory/security requirements, material, size, thickness, artwork, encoding, personalization, quantity, sample requirements, testing criteria and delivery schedule.

Do I need to specify the RFID chip?

If the system already requires a specific chip, yes. If the chip has not been selected, provide the application, reader and security requirements and ask the manufacturer to recommend compatible options.

Should I provide the RFID reader model?

Yes. The exact reader model is often one of the most valuable pieces of information for determining card compatibility.

Is frequency alone enough to specify an RFID card?

No. Frequency should normally be accompanied by the relevant technology, protocol, reader information and chip requirement.

Do I need to specify the antenna?

You should state whether the antenna is already defined or should be designed by the manufacturer. If the reader and card system are already established, providing a reference inlay or card can be especially useful.

What should I specify for RFID card memory?

Specify the actual application data requirement or the required chip model. Do not select memory only by choosing the largest available capacity.

What information is needed for RFID card encoding?

Provide the data format, numbering logic, application data, NDEF or EPC requirements where applicable, and explain how the encoded data should be verified.

What should I provide for RFID card personalization?

Provide the artwork and all variable elements, such as names, card numbers, photos, barcodes, QR codes or serial numbers. Explain whether printed data must match encoded data.

What should I test before bulk RFID card production?

Test the approved card with the intended reader and application, including RFID communication, authentication where applicable, encoded data, printed data, dimensions and overall card quality.

What is an RFID card MOQ?

MOQ depends on the exact configuration, including chip, material, customization, printing, encoding, packaging and production requirements. The manufacturer should confirm MOQ for the complete specification rather than a generic RFID-card category.

Should I order samples before bulk production?

For system-dependent projects, yes. A production-spec sample provides an opportunity to validate reader compatibility, encoding, personalization and physical construction before the bulk order.

What is the difference between an RFQ and a simple product inquiry?

A product inquiry may only ask for price and availability. An RFQ defines the technical and commercial requirements needed to manufacture and evaluate the exact product.

Should legacy and new RFID projects use the same chip?

Not necessarily. A legacy project may prioritize compatibility, while a new project may have different security and lifecycle requirements. NXP, for example, currently identifies MIFARE Classic EV1 and DESFire EV1 as not recommended for new designs, while DESFire EV3 is currently listed as Active.