Product compliance
Declarations, verifications or certificates associated with the covered models and intended regulatory scope.

KEYPLUS · Company
Find the evidence that applies to the product, model and market you are evaluating. KEYPLUS organizes available compliance, testing and related documents by scope instead of presenting one certificate as proof for an entire portfolio.
Certification requirements depend on product category, radio functions, power, materials, intended use and market. Begin with the exact model and configuration, then identify the applicable standard, document type and current evidence.
Logos alone do not answer whether a document covers the selected product. Customers and partners should be able to see the model or family, issuer or laboratory, standard or test method, issue date, report or certificate reference, language and access status where disclosure is approved.
Declarations, verifications or certificates associated with the covered models and intended regulatory scope.
Functional, radio, electrical, material, environmental, ingress, durability or other reports identified by sample and test scope.
Relevant software records, patents or company qualifications presented separately from product certification.
Inspection, sample, integration or acceptance records created for an agreed customer scope and shared under the applicable permission.
Model scope: Which product, series or tested sample is named?
Configuration: Which hardware, radio, power or firmware characteristics matter?
Standard and version: What requirement or method was used?
Date and status: When was the document issued, and is a current copy required?
Market and purpose: Where and for what evaluation is the evidence relevant?
Access: Is the file approved for public download or available through a request?
The existing KEYPLUS material library includes product-specific examples such as RoHS testing, CE-related verification, FCC supplier documentation, ingress-protection evidence and product type-test reports. Each record must remain tied to the models and scope stated in its source document.
Select the product
identify the target country or region
state the required document or approval purpose
review the available scope
identify any gap
confirm responsibility for additional evaluation where needed.
Documents shared during sales evaluation should not be altered, detached from their scope or represented as a broader approval.
No. The named model, configuration, standard, version, date and scope must be checked.
Document control, customer relevance, third-party rights and current-status checks may require a model-specific sharing process.
Yes. Customers should confirm current requirements with qualified local parties and evaluate the selected product accordingly.
Compliance test report
KX2 sample and the model families identified in the report
2023-12-06 · English
CE compliance verification
The M1, HT, HTY, RF and N3T models listed in the verification
2021-01-08 · English
FCC SDoC verification
The M1, HT, HTY, RF and N3T models listed in the verification
2020-12-30 · English
Ingress-protection certificate
T Series smart door lock identified in the certificate
2022-11-29 · English
Product type test report
K6 model and the tested configuration described in the report
Request current copy · Chinese
Provide the product model or category, target market and required document type. KEYPLUS will confirm which approved files are available and what still requires evaluation.