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
1. What Documents Need to Be Prepared?
Before submitting testing and certification documents to platforms (e.g., Amazon, Temu, SHEIN, etc.), ensure the documents are complete and information is consistent. may requestd documents include: company qualification documents (business license, manufacturer information), product information (product name, model, description, photos), labels/instructions/packaging images, existing test reports or compliance documents (e.g., CE Declaration of Conformity, FCC authorization records, CPC document certificate, FDA registration number, etc.), and other proofs requested by the platform (e.g., DoC, SDS/MSDS, etc.). Required documents vary significantly by product category (e.g., electronics, toys, food contact materials, chemicals) and should be checked against the target market and applicable regulations.
2. Key Points for Verifying Corporate Documents
Corporate documents form the basis of compliance files. Check whether the company name on the business license matches the report applicant and manufacturer, and whether the registered address matches the address in the certificate. Some platforms may require information on trading companies or importers (e.g., EU representative, US importer); confirm that they have been registered or authorized under relevant regulations. For FDA registration, verify that the FEI number corresponds to the facility information; for CPSC or applicable product safety authorities or market surveillance authorities, confirm that the manufacturer is registered and holds the applicable report number. If corporate information changes (e.g., company name, address), update relevant documents or provide a change certificate.
3. Product Information and Labels
The product name, model, and batch number must exactly match the report, instructions, and packaging labels. Check whether the label includes necessary markings, such as CE marking (where applicable), FCC marking (where applicable), date of manufacture, manufacturer information, warning statements, etc. Food contact materials should indicate “suitable for food contact”; chemicals require hazard communication rules labels and SDS. Platform reviews are often rejected due to incomplete label information or mismatched model numbers. It is recommended to take multi-angle photos and compare text content with uploaded files.
4. Reuse and Review of Existing Reports
Existing test reports or compliance documents are not automatically applicable. Need to confirm the following: whether the report is still within its validity period (subject to regulations and platform requirements); whether the product name, model, and manufacturer in the report match the currently submitted product; whether the standards or regulations covered by the report meet the latest version of the target market (e.g., ASTM F963-23, EN 71 series, etc.). If the product has design or material changes, the original report may no longer apply and a gap analysis or retesting may be required. The report number can serve as a reference for verification, but authenticity should be further assessed based on report format and issuing body information.
5. Common Missing Document Issues
Based on platform review feedback, common missing issues include: lack of product photos or packaging images; missing translations (e.g., non-English instructions); CPC document certificate missing 7 required elements (product description, applicable standards, manufacturer information, etc.); CE DoC without signature or stamp; FCC SDoC missing US local responsible party information; SDS not prepared according to the latest version (e.g., hazard communication rules Rev.8); FDA registration number not linked to the corresponding product line. In addition, some platforms may request independent test reports (not manufacturer self-declaration), which should be confirmed in advance.
6. Pre-Submission Inspection Recommendations
It is recommended to follow these steps: 1) Compare corporate documents, product information, and test reports one by one with the platform upload requirements; 2) Use report query functions (if available) to verify whether the report number can be found in public systems; 3) If multiple documents are involved, ensure product information is consistent across all files; 4) For sensitive items (e.g., children’s products, electrical appliances), conduct an internal pre-review. If documents are missing or questionable, contact the testing body to supplement or update documents to avoid extended review cycles due to incomplete data.
7. Risk Notice and Platform Review Explanation
Platforms reserve the final review authority. This article is for document preparation and risk checking only and does not constitute a guarantee of platform acceptance. Whether a product complies with target market regulations depends on the product category, applicable standards, report scope, and current platform rules. Report validity periods vary by regulation and product type; it is recommended to periodically assess report applicability.
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 to receive review results after submitting documents?
Review timelines vary by platform, product category, and document completeness. Typically it takes a few days to a few weeks. Submitting complete and consistent documents can reduce back-and-forth communication. The final answer is subject to platform notification.
Can existing reports be used directly for all platforms?
Different platforms have different requirements (e.g., Amazon may accept some self-declarations, while Temu may request third-party test reports). It is recommended to check the target platform's upload guidelines first to confirm whether the report type, format, and scope match.
What if product information does not match the report?
First identify the reason for the discrepancy. If it is a model alias or batch change, a change statement or supplementary test report may be prepared. If core parameters (e.g., material, structure) differ, retesting may be required.
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.