How a configuration is verified, documented and confirmed for a market.
Quality in RFID is not a certificate on a wall. It is knowing which model, which radio region and which configuration you have, and being able to show the evidence for each.
01 / THE PROBLEM
A certificate is
not an answer.
Buyers ask for "the certificate" as if it were one document. It is not. Certification is granted per model, per variant, per radio band and per market, and a document that lacks any of the five fields below cannot be checked.
This page states how we confirm a configuration for a destination, what we document, and where the limits of our own evidence are. It is written so that you can hold us to it.
02 / FIVE FIELDS
What makes a conformity
document checkable.
Standard and revision
A certificate against a superseded revision does not evidence the current requirement. "EN 301 489-3" without a version is an incomplete answer.
Certification body
Which laboratory or notified body issued it, and under which scheme. A self-declaration and a third-party certificate are different kinds of evidence.
Certificate number
The identifier that lets you look the record up rather than trust the document in front of you.
Scope in words
The exact model, variant and radio band covered. A certificate for a family member does not cover the unit in your order.
Issue and expiry dates
Conformity documentation has a lifetime. A document that lapsed is not evidence that today's shipment conforms.
03 / HOW WE VERIFY
Five stages,
each with an output.
Verification is only meaningful if it produces something you can read later. Each stage below ends in a document, a record or a decision, not in an assurance.
Written confirmation before the order
You receive the model, variant and radio region in writing on the quote, and which conformity documentation is available for that market. Anything we cannot evidence is named as unavailable rather than implied.
Evidence checked against the record
Where you ask for a certificate, we are expected to be able to produce the standard and revision, the issuing body, the number, the scope and the dates. If a field is missing, we say so instead of sending the document anyway.
Acceptance criteria agreed before the test
Read-zone acceptance is written down before validation starts, so a "working" result is measured against a target rather than discovered after the fact.
A frozen baseline at handover
Configuration, tag placement, physical layout, event rules, test conditions and sign-off are recorded together. That record is what makes a later fault diagnosable and a later change reviewable.
Re-validation on change
A changed item mix, moved reader, edited rule or new firmware invalidates the baseline. The page states which changes require a new acceptance run rather than assuming the old result still holds.
04 / INSIDE THE BUSINESS
How we run
our own operation.
A named owner for every configuration
Each project has someone who owns the configuration, the acceptance record and the change history. Not a shared inbox.
Reconciliation against a system of record
A validated event is checked against the system that consumes it, so "the reader saw it" and "the system accepted it" are never treated as the same statement.
Exceptions with an owner and a reason
Missing, duplicate, unexpected or out-of-sequence reads resolve to a named action. A workflow that only defines the happy path is not yet a workflow.
Corrected in public, not just internally
If a published figure, specification or statement turns out to be wrong, the page changes. A site that never corrects anything is not more accurate, only less honest.
A stated evidence boundary on every claim
Portfolio direction, catalogue name and verified model-and-type are different levels of fact, and each product profile says which one you are reading.
05 / THE LIMITS
The limits we
hold ourselves to.
Our claim is narrower than a certificate and easier to check. Each limit below is self-imposed, and each one can be verified against the page it governs.
- We publish no quality badge we have not earned. A mark is shown on this site only where it is held and can be evidenced. A process certificate would say something about how we work; it would still say nothing about the model in your order, which is why the verification below carries the weight instead.
- Portfolio direction is never dressed as a specification. Some catalogue entries state a direction or a catalogue name rather than verified model-and-type facts. Each profile says which of the three you are reading, and nothing unverified is published as a specification.
- Planning prices are references, not offers. A figure shown before your configuration is known can only be indicative. The binding number is the one on your quote, which names the model, the radio region and the commercial scope in writing.
- Illustrative imagery is captioned for what it does not show. Context and illustration images are captioned with their scope, so a representative scene is never read as a photograph of a specific installation or of a product in service.
- Case studies carry their evidence boundary. A published case states the operating context it was approved for and the results it reports. It is not presented as a guaranteed outcome for a different site, item mix or configuration.
- We name what we cannot evidence for your combination. Conformity documentation is held per model, per variant, per radio band and per market. Where a field cannot be evidenced for the combination you need, we say so rather than send a document that does not cover it.
Last reviewed 2026-09-14 · Guangzhou Dadong Intelligent Technology Co.,Ltd.
RFIDBRIDGE / EVIDENCE REQUEST
Ask for the
document.
Name the destination market and the model, and ask which conformity documentation is available for that combination. That is a fair question and we will answer it in writing.
Contact RFIDBridge