Certification & Documentation Guide for Smart Tracking & Identification

What the Documentation Package for Smart Tracking Products Should Actually Contain #

A barcode scanner locks up on a conveyor line at a European distribution center. The root cause traced back not to hardware failure but to a CE marking that covered the reader module only — not the complete integrated unit shipped to the buyer. The importer was liable. The cost was not the product. The cost was the recall, the re-certification, and six weeks of line disruption.

That scenario is not unusual. Smart tracking and identification products — RFID tags, readers, barcode scanners, handheld terminals, IoT asset trackers, fixed UHF portals — sit in a documentation gray zone. They combine radio frequency transmission, electronic circuitry, and in many cases software firmware. Each of those elements can trigger a separate regulatory obligation, and Chinese suppliers frequently treat them as independent line items rather than a unified compliance package.

The minimum documentation set for any smart tracking product entering regulated markets should include: a Certificate of Conformity (CoC) signed by an authorized representative, a full test report from an accredited third-party lab, a Declaration of Conformity (DoC) for the target market, a component-level COA for key parts (chip, antenna substrate, housing material), an MSDS or SDS for any chemical-bearing elements (battery cells, adhesive substrates), and a firmware version declaration where software affects radio behavior. Six documents. In our intake reviews, fewer than 40% of first-submission documentation packages from Chinese suppliers are complete against this list.

The gap that causes the most downstream problems is the firmware version declaration. Suppliers update firmware to fix read-rate bugs without issuing a new test report. The radio behavior changes. The CE or FCC authorization becomes technically void. This is not a theoretical risk — we flagged it in three separate supplier audits in 2023 and 2024.

The Parameters That Separate a Valid Test Report from a Paper Filing #

The test report is where documentation review does real work. A CoC is a declaration. A test report is evidence. They are not equivalent, and treating them as interchangeable is the single most consistent documentation error we see procurement teams make.

For a UHF RFID reader operating in the 860–960 MHz band, a valid test report should confirm: conducted emissions per CISPR 32 (or FCC Part 15 Subpart B for the US market), radiated emissions measured in a calibrated anechoic chamber, ERP (effective radiated power) at the antenna port, receiver sensitivity expressed in dBm, and environmental conditioning results including operation across the rated temperature range (typically −20°C to +55°C for industrial-grade equipment, or 0°C to +40°C for commercial grade). The report should also state the firmware version and hardware revision tested.

What we frequently receive instead is a test report that covers conducted emissions only, references a chip-level IC datasheet for sensitivity, and has no environmental section at all. That report may satisfy a checkbox on a procurement form. It will not satisfy a customs authority conducting post-market surveillance.

The firmware version column is the one that matters most for ongoing compliance. Once a product clears initial qualification, procurement teams stop checking it. Suppliers know this.

For passive RFID tags specifically, the test report should reference ISO 18000-63 (UHF EPC Gen2, equivalent to EPC Global Class 1 Gen2v2) for air interface protocol conformance, and should include read range measurements at both minimum and maximum ERP allowed in the target market — 2W ERP in Europe under ETSI EN 302 208, 4W EIRP in the US under FCC Part 15. A report that only tests at one power level is incomplete for dual-market deployment.

Certification Requirements by Market: What Is Mandatory vs What Is Optional #

Mandatory versus optional is not a static answer — it depends on product type, end application, and whether the product is sold as a component or as a finished system. Here is where buyers consistently make errors.

If the product is a standalone RFID reader or handheld barcode terminal sold as a finished consumer or industrial device:

• EU market: CE marking under the Radio Equipment Directive (RED) 2014/53/EU is mandatory. RoHS compliance under EU RoHS Directive 2011/65/EU is mandatory. REACH substance declaration is required for any article containing SVHCs above 0.1% w/w under ECHA REACH Regulation. WEEE registration is required if the importer is the first entity placing the product on the EU market.

• US market: FCC authorization under 47 CFR Part 15 is mandatory for any intentional or unintentional radiator. The FCC ID must be physically marked on the product or its packaging. California Prop 65 warning requirements apply for products containing listed substances. UL 60950-1 or UL 62368-1 is not legally mandatory federally but is required by most large US retailers and distributors as a condition of purchase.

• China domestic market: CCC (China Compulsory Certification) under CNCA administration applies to specific product categories. SRRC (State Radio Regulation of China) type approval is mandatory for any device transmitting in licensed or shared frequency bands — this includes UHF RFID readers operating at 840–845 MHz and 920–925 MHz per Chinese regulations. Products without SRRC approval cannot legally be sold or operated in China.

• Japan: GITEKI mark under the Radio Act (電波法) is required for radio transmitting devices. The GITEKI mark must be displayed on the product. Third-party testing through MIC-designated labs is required.

If the product is sold as an OEM component for integration into a larger system, the compliance picture changes. The downstream integrator typically assumes regulatory responsibility. However, Chinese suppliers frequently provide CE or FCC documentation marked “module certification” — which covers the embedded radio module but does not extend to the host system. Buyers integrating these modules into their own products must conduct a separate system-level assessment. This distinction gets missed regularly in procurement review.

The optional certifications worth requesting for specific applications: ISO 9001 quality management certification from the supplier’s facility (relevant to process consistency, not product performance), IP rating test reports per IEC 60529 for outdoor or washdown deployments, and MIL-STD-810 drop/vibration test reports for handheld devices used in harsh environments.

In our supplier qualification program for industrial IoT trackers, we require a minimum of three consecutive production batch test reports before recommending a supplier for approved vendor list entry. Qualification sample reports are treated as pre-production data only.

Decision Framework: Matching Documentation Requirements to Your Deployment Scenario #

If your product is entering the EU as a finished device under your brand, the Red Equipment Directive DoC must be signed by the EU-based importer or authorized representative — not the Chinese manufacturer. Chinese suppliers will sometimes provide a pre-filled DoC with their own company name and address. That document is legally invalid for CE marking purposes unless they have an established EU presence. Request a blank DoC template and complete it yourself, or appoint an EU-authorized representative.

If your product contains a pre-certified radio module (common in handheld terminals and IoT trackers), confirm whether the module certification is a “modular grant” that permits integration without re-testing, or a component certification that requires host system evaluation. In the US, FCC modular grants are specific — check the grant conditions on the FCC Equipment Authorization database before assuming you inherit the certification. We run this check as part of our standard documentation review, logged under our CR-12 compliance intake procedure.

If you are sourcing passive RFID tags only (no reader, no active electronics), the regulatory footprint is smaller. RoHS and REACH apply to the tag as an article. FCC/CE radio authorization applies to the reader system, not the passive tag. However, if the tags contain battery-assisted functions or NFC with active boosting, re-evaluate — the product may cross into intentional radiator territory.

If the deployment is in a food, pharmaceutical, or medical logistics environment, additional documentation layers apply. FDA 21 CFR Part 11 may be relevant if the tracking data feeds into regulated electronic records. NSF International certification is not universally required but is frequently demanded by food-grade facility operators in North America. For pharmaceutical serialization applications, GS1 EPCIS conformance documentation and DSCSA compliance records (for the US) or FMD/EMVO records (for the EU) become part of the technical file.

The non-obvious recommendation with a hard boundary: for any product that combines Bluetooth, Wi-Fi, and UHF RFID in a single device (increasingly common in asset tracking terminals), verify that the test report covers all three radio technologies simultaneously under multi-radio coexistence conditions, not as three separate single-radio tests. Chinese test labs frequently test each radio in isolation. The multi-radio coexistence test is the one that fails in practice.

Practical Guidance for Buyers #

When sourcing smart tracking products from China, start your documentation review with the test report accreditation credentials — not the report content itself. A test report issued by an unaccredited or self-operated lab has no regulatory standing, regardless of what it says. Check the lab’s ILAC-MRA signatory status or, for US-market products, confirm the lab holds FCC Telecommunications Certification Body (TCB) authorization.

The specific risk to watch for: suppliers who provide a valid test report for an initial sample and then substitute the antenna design at volume production to reduce cost. Antenna geometry directly affects ERP and read range. We have seen read range drop by 18–25% after an undisclosed antenna change that the supplier characterized as a “minor tooling adjustment.” Incoming inspection should include a read range spot-check against the qualified sample baseline — not just a visual inspection and COA review.

Before committing to volume, request three things: the test lab’s accreditation certificate (current, not expired), the FCC Equipment Authorization grant or CE notified body opinion (whichever applies), and the production batch traceability mapping that links the test report serial number to a specific manufacturing lot. If the supplier cannot provide lot-to-lot mapping, the documentation package is incomplete for regulatory purposes.

For EU-bound products specifically, request the complete technical file index. Under the RED, the technical file must be retained for 10 years after the last product is placed on the market. Chinese suppliers rarely maintain files to this standard. Catching the gap before production commitment saves significant remediation cost.

Frequently Asked Questions

Does a Chinese supplier’s CE certificate mean the product can be sold in the EU without additional steps?
Not automatically. If the supplier is not an EU-established entity, the CE declaration must be re-issued by an EU importer or authorized representative. The Chinese manufacturer’s DoC is a reference document, not the legally binding declaration for EU market access — that obligation falls on whoever is first placing the product on the EU market.

What is the difference between FCC ID certification and a Declaration of Conformity under FCC Part 15?
FCC ID certification (Equipment Authorization) is required for intentional radiators — devices that deliberately emit RF, like RFID readers and barcode scanners with wireless connectivity. A Supplier’s Declaration of Conformity (SDoC) is the self-certification path for unintentional radiators (devices that emit incidentally, not by design). Most smart tracking readers require Equipment Authorization, not SDoC. The FCC ID must be physically marked on the device.

How do I verify that a CE test report from a Chinese lab is legitimate?
Cross-check the lab name against the ILAC MRA signatory database or the EA (European Accreditation) members list. Then confirm the report number is real by requesting the lab’s verification service or calling the lab directly. We have encountered fabricated test reports in roughly 1 in 12 first-submission documentation packages — always verify independently for high-volume or regulated-market procurement.

Is SRRC approval required if I am only exporting from China and not selling domestically?
No. SRRC type approval is a China domestic market requirement under the Radio Regulation of China. If the product is manufactured in China but exported directly without Chinese domestic sales, SRRC is not required for the product itself — though the manufacturing facility may still need relevant production licenses. Confirm the export-only status in writing with the supplier; some factories pre-apply SRRC approval for dual-market flexibility, which is useful but not obligatory for pure export.

What should I do if the test report serial number does not match the production batch COA?
Treat it as a documentation non-conformance and issue a formal correction request before accepting the shipment. The report must reference the batch being shipped, not a prior qualification sample. Our internal intake form QR-04 flags this as a Category A non-conformance requiring supplier response within 5 business days before goods release proceeds. If the supplier cannot reconcile the references, escalate to a third-party incoming inspection before acceptance.

Related categories: Sensors & Detection | Industrial Electrical & Cables

Published by sinoraw.com Technical Team | Request a sourcing consultation