Before You Read
- Check the report or certificate number exactly as shown on the issued document.
- Compare the public verification status with the document version and issue information.
- Prepare product information and platform notices when requesting document review support.
ContentsTap to expand or collapse
Key Points
Before submitting testing and certification documents, verify that company qualifications match the registered entity; product model numbers and descriptions correspond to the report coverage; labels, instructions, and images reflect compliance information; and existing reports are still within their valid scope. Verification does not guarantee that the platform retains final review authority, but it can reduce the risk of supplementary submissions or rejections due to basic information discrepancies.
Documents to Prepare
Document preparation varies by product category, target market, and platform rules. The following is a basic list of documents, subject to actual requirements:
- Company documents: business license, manufacturer/importer information, authorized representative documents (if applicable)
- Product documents: product name, model, specification description, user manual or technical file
- Compliance documents: test reports, Declaration of Conformity (DoC), FCC grant records, CPC document certificates, FDA registration numbers, etc.
- Labels and instructions: including importer/manufacturer information, country of origin, warnings, CE/FCC marks, etc.
- Product images: clearly showing labels, appearance, model identification
- Test sample information: sample ID, test date, test laboratory information
- Platform rejection screenshots (if previously rejected): to facilitate quick issue identification
Company Document Verification Focus
The company name and address on the business license should be consistent with the manufacturer/importer information in the compliance documents. If a third party holds the certificate, an authorization letter or agency agreement is needed. For FDA registration, the entity corresponding to the FEI number should match the declared entity. CE/UKCA technical files must record EU or UK Responsible Person information, which platforms may request during review.
Product Documents and Compliance Files
The product model number must be explicitly listed on the test report, DoC, and certificate. For multiple models, a list of acceptable differences (e.g., only the main model tested) may be accepted. Chemical restriction reports such as RoHS and REACH should cover all product components; otherwise, the platform may request supplements. For FCC wireless devices, the correct authorization path is required (Certification requires a TCB, SDoC requires a manufacturer’s declaration). The standard number on the report (e.g., ASTM F963-23) should correspond to the applicable version of the product.
Labels, Instructions, and Image Documents
Information on the label (e.g., FCC ID, CE mark, WEEE mark, recycling symbol) must correspond to the report content. Instructions should include necessary safety warnings and language requirements (e.g., English, French). Images should clearly show the label location and overall product appearance. Platform reviews often reject due to incomplete labels or incorrect marking positions.
Reuse and Limitations of Existing Reports
If the new product shares the same platform or involves a minor model change, existing reports may be reused. However, confirm that: the report is not expired (if an explicit validity period is stated, use that as reference); there are no substantial changes in product structure, materials, or electrical parameters; the standard version covered by the report has not been updated; and the platform accepts historical reports (e.g., Amazon generally accepts reports within 2 years, but final acceptance is subject to platform requirements). Reusing reports carries risks; consult a professional organization.
Common Document Omission Issues
Omission 1: Inconsistent company information — The business license name does not match the manufacturer name on the report. Solution: Provide proof of affiliation or update the report information.
Omission 2: Product model not covered — The report submitted is for Model A, but the product listed on the platform is Model B. Solution: Provide a difference declaration or test report for Model B.
Omission 3: Noncompliant labels — The label lacks importer information or compliance marks. Solution: Reprint labels and provide updated images.
Omission 4: Missing chemical restriction report — The product contains potentially restricted substances but no REACH / RoHS report was submitted. Solution: Provide the corresponding report or declaration.
Pre-Submission Check Suggestions
- Check the platform upload requirements list item by item, confirming file names, formats (PDF/JPG), and size limits.
- Ensure that product names, model numbers, and brands on all documents match the backend entries.
- Verify that the report issue date, report number, and laboratory name are complete and identifiable.
- Cross-check multiple reports (e.g., CE + RoHS + FCC) to ensure uniform product information.
- If there are platform rejection records, prioritize corrections based on the rejection reasons before resubmitting.
- Keep a complete copy of the documents for future appeals or re-reviews.
After verification, if you have any questions, contact Prylem (Dongguan) Testing Certification Co., Ltd. for document review and supplementary testing.
Pre-Submission Checklist
- Report or certificate number
- Product name, model and applicant information
- Issue date and applicable standard shown on the document
- Platform notice, QR code screenshot or document submission request when available
Public verification results are for document status checking only. Platform review outcomes depend on product information, applicable requirements and the platform review process.
Article FAQ
How long does it take for the platform to give a review result after submitting documents?
Review times vary by platform and product category, typically 1–5 business days. If documents are complete with no obvious issues, review is faster; if supplementary submissions are needed, the timeline extends. It is recommended to prepare in advance and allow sufficient time.
Can reports that have passed another platform's review be used directly for a new platform?
Not necessarily. Each platform has different document requirements; some may require reports to be in a specific format, issued by a designated laboratory, or include additional information (e.g., DoC declaration). It is advisable to first check the target platform's specific requirements and, if necessary, contact Prylem (Dongguan) Testing Certification Co., Ltd. for compliance pathway confirmation.
If the manufacturer name on the report has changed, can the report still be used?
Generally, proof of change or a new report is required. If only the company name has changed (e.g., company rename), a business change notice and an associated declaration may be attached; if the manufacturer entity has changed, retesting is needed. The final decision is subject to platform review.
Explore Compliance Topic Matrix
Browse services, knowledge articles, FAQ and case references by target market, compliance topic and platform review scenario.
View Compliance TopicsNeed document review support?
Send us your product information, target market and platform notice. We will help review the document path before arranging testing, certification or document preparation.