What changes if a chip is not NFC Forum compliant?
It may work on some phones and not others, which is worse for a deployment than failing outright. Compliance with an NFC Forum tag type is what guarantees an arbitrary phone can read a tag without special software, and it is the property most listings omit.
What compliance means
That the chip implements one of the five NFC Forum tag types, so a compliant reader knows which commands to send and where to find content.
Without it, reading the tag requires software that already knows its memory layout and command set. The operating system does not, so a tap produces nothing.
The NFC Forum publishes the tag type specifications, and compliance is what a supplier is claiming when they state a tag type.
Inconsistency is the real cost
A tag that fails everywhere is a bad tag, discovered immediately and returned.
A tag that works on the buyer's Android handset and does nothing on half the visitors' phones is a deployment failure discovered gradually, blamed on the phones, and expensive to diagnose. That is what non compliance usually produces.
MIFARE Classic is the well documented example: it uses the same radio layer and a proprietary protocol above it, and Android states plainly that support depends on the device.
Where you meet non compliant chips
Marketplace listings that say "NFC compatible" and name no tag type. The phrase is unregulated and appears on products that no phone will read as a tag.
Very cheap bulk lots, where the saving comes from somewhere and that somewhere is often conformance.
Access control stock, where cards designed for a specific reader system were never intended to be read by phones and are sold on as generic NFC tags.
And clones of known chips, which imitate the packaging and diverge in behaviour under conditions the original handles.
Avoiding them
Ask for the NFC Forum tag type before ordering, and treat an answer of "NFC compatible" as no answer.
Order a sample and read it with a tool that reports the tag type. If the tool reports a technology but no tag type, that is the signal.
Tap the sample with an iPhone as well as an Android device, since the narrower platform surfaces this problem faster.
And repeat per delivery. A supplier who shipped compliant tags last time may ship a substitute this time, and nothing about the packaging will say so.
Frequently asked questions
Is a non compliant chip useless?
Not in a closed system where you control the software and the readers. It is unusable for anything the public taps, which is what most deployments are.
How do I tell from a listing?
You often cannot, which is why a sample matters. A listing stating a Forum tag type is making a checkable claim, and one saying NFC compatible is making none.
Do cheap tags always mean trouble?
No. Plenty of inexpensive tags are fully compliant, and price alone is not the signal. The absence of a stated tag type is the signal.
Can a non compliant tag be made compliant?
No. Conformance is a property of the chip's command set and memory layout, neither of which can be changed after manufacture.