Customer Confirms
Sales countries, brand, product definition, platform account, applicant, importer, and launch plan.
Certification and Compliance
Confirm the target market and responsible entity before ecosystem or regulatory certification begins.
Apple Find My, Google Find Hub, Samsung SmartThings Find, CE, FCC, RoHS, REACH, and battery transport each involve different accounts, samples, documents, and legal roles.
Yuli supports hardware, firmware, samples, test documentation, and corrective work. The customer controls the product, brand, market, and agreed account, applicant, or commercial-release responsibilities. Final responsibility follows applicable rules and project documents.
Before Certification
Certification covers the product, responsible entity, and controlled revision, not just a sample.
At project start, confirm target countries, sales brand, applicant or certificate holder, importer, model, hardware and firmware revisions, battery, labels, and launch date. A change to any of these items may require review or additional testing.
Yuli Prepares
Hardware and firmware revisions, samples, relevant BOM documents, RF and power self-tests, corrective samples, and production-test support.
Jointly Frozen
Test revision, test scope, labels, change rules, document ownership, and production-release criteria.
Finding Ecosystems
Three tracker ecosystems have three separate onboarding and release processes.
Ecosystem names and badges may only be used under platform rules. The responsibilities below describe project support and do not claim that Yuli or any product is already certified.
Apple Find My
Customer / brand: Confirm the MFi participant, brand, and commercial product information; manage platform agreements and final release.
Yuli: Support hardware, firmware, low power, acoustics, samples, self-testing, and corrective work.
Google Find Hub
Customer / brand: Confirm the device proposal, agreements, Model ID, brand assets, and commercial-release entity.
Yuli: Support chipset and firmware integration, DULT requirements, ringing, reset, self-tests, 3PL samples, and production tests.
Samsung SmartThings Find
Customer / brand: Confirm partner eligibility, Samsung account, device profile, brand information, and ecosystem publication.
Yuli: Support Device SDK integration, configuration, key provisioning, onboarding, ringing, RF tests, and test samples.
Regulatory and Material Compliance
The market, brand, and legal role determine final compliance responsibility.
Yuli can provide manufacturing and technical documents but cannot replace the legal duties of the brand owner, importer, authorized representative, or other responsible party. A qualified compliance body should confirm applicable rules for the finished product.
CE / EU
The customer confirms markets, brand owner, EU importer or representative, and applicable legislation. Yuli supports technical documents, samples, BOM/material data, and corrective work. The legal manufacturer remains responsible for conformity assessment, technical documentation, the EU DoC, and CE marking.
FCC / US
The customer confirms the U.S. applicant, grantee, importer, or other responsible party. Yuli supports RF hardware, firmware revisions, samples, and corrections. Authorization, labeling, continued compliance, and responsibility for modifications follow FCC rules and the project agreement.
RoHS / REACH
The customer confirms market roles and finished-product requirements. Yuli gathers available component, material, and supplier declarations and supports testing. The final assessment must cover the finished product, all materials, exemptions, and the current SVHC list rather than relying on one component report.
Lithium Battery Transport / UN 38.3
The customer confirms transport mode, destination, and carrier requirements. Yuli supports cell/battery identification, supplier test summaries, assembly information, samples, and packaging data. The shipper, forwarder, and carrier confirm classification, packing, marks, and documents under current rules.
Revision Changes
Changes to the controller, RF circuit, battery, antenna, PCB, structure, firmware, model name, or labels require an impact review before retesting, filing, or a new application is decided.
Production Consistency
Test samples, approved samples, BOM, firmware, critical suppliers, and production tests must remain traceable. Unapproved substitutions or revisions cannot automatically inherit prior certification conclusions.
Project Deliverables
Certification support requires a traceable document set.
Product and Revision
Model, hardware and firmware revisions, BOM, critical parts, battery, antenna, and appearance variants.
Samples and Tests
Sample IDs, self-test records, issue list, corrective revisions, lab submissions, and results.
Production and Changes
Approved samples, production tests, labels and packaging, key or serial-number process, change requests, and release records.
Primary Sources
Platform and regulatory requirements change; use current official documents for each project.
This page summarizes public primary sources available in July 2026. Restricted partner specifications must be reconfirmed by the relevant account holder at project start.
Share the market and product details to define certification responsibilities.
Provide sales countries, brand, product form, ecosystem, hardware and firmware status, battery, expected volume, and planned launch date.