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
What Documents Need to Be Prepared
When compliance review teams evaluate testing and certification pathways, they need to systematically collect relevant documents based on product category, target market, and platform requirements. Different products correspond to different regulatory pathways. The more complete the document preparation, the faster compliance review teams can analyze applicable standards, test items, and compliance processes. The following are common documents categorized for your reference.
Company Information
The following company information is typically needed: full company name, registered address, contact person, email, phone number; company registration certificate or business license (some platforms may require upload); if you are the manufacturer, also specify the factory address and FEI number (applicable for FDA-related products). Company information is used to match the seller identity on the platform, the registered entity, and the responsible person identification under regulations.
Product Information
Product information is the core for determining testing and certification pathways. Typical checklist includes: product name, model number, series number, product description, intended use, intended user (adult or child); product material list, ingredient list, specification sheet; for electronic/electrical products, provide input voltage, frequency, power parameters; for toys, provide applicable age group; for chemicals, provide SDS/MSDS or ingredient ratios. The more detailed the product information, the more accurately the compliance review team can identify applicable regulations (e.g., CE, FCC, FDA, CPSC or applicable product safety authorities or market surveillance authorities, REACH, RoHS, etc.).
Label/Instructions/Images
Labels, instructions, and product images help confirm whether compliance markings are complete. For example: whether the CE mark is affixed; whether the UKCA mark is applied; whether the FCC identifier is on the label; whether warning statements (e.g., toy warnings, battery safety) are drafted according to regulations. Provide actual label photos or designs, instruction content (in Chinese or target market language), product front/back/electrical parameter images. These materials help compliance review teams assess whether compliance declarations and technical documents need adjustment.
How to Reuse Existing Reports
If you already hold test reports, certificates, or compliance documents, provide them together. Existing reports include: original test reports (with report number, report date, testing laboratory name), CE declaration or UKCA declaration, FCC authorization records, CPC document children’s product certificate, RoHS/REACH reports, UN38.3 summary, etc. Service providers will evaluate whether the report coverage meets platform requirements, whether the report is still valid (some reports have no fixed validity period, but platforms may require reports within 12 or 18 months), and whether the product has changed. Note: Report numbers alone cannot serve as universal verification; report content and laboratory accreditation still need to be reviewed. Some platforms require reports issued by ISO 17025 accredited laboratories; specific requirements are subject to platform rules.
Common Missing Document Issues
Common missing items in actual submissions include: absence of product model list (series products only provide one model, but the platform may require coverage of all variants); incomplete label content (missing importer information or warning statements); existing reports not provided in English; SDS/MSDS format not meeting target country requirements; CPC document certificate missing manufacturer address and date. In addition, some sellers mistakenly believe the same report can be used for similar products, but if the material, structure, or voltage changes, the original report may not apply. It is recommended to verify report coverage with a professional compliance review team.
Pre-Submission Check Recommendations
Before submitting documents to a compliance review team or platform, it is recommended to check the following: 1) Ensure all files are in clear, readable PDF or image format; 2) File naming is consistent, including product model and file type; 3) If translations are involved, provide the original together with a reviewed translation; 4) Verify the report types currently accepted by the platform (e.g., Amazon may request CPC document + test report, TEMU may request REACH or RoHS); 5) Save platform rejection screenshots or review feedback to help compliance review teams analyze the reason. Platforms retain the final review right; this article does not constitute a guarantee of platform acceptance.
Related Services
If you need further assistance in preparing testing and certification documents, you can consult our technical team for document pre-review, report assessment, testing coordination, and document organization services.
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
Can the testing and certification pathway be determined without existing reports?
Yes, service providers can preliminarily determine applicable regulations and testing standards based on product information, company details, and target market requirements. However, without existing reports, the final pathway must be confirmed through actual testing. It is recommended to provide complete product information first for assessment.
Can report numbers be used to verify report authenticity?
Report numbers are mainly used to locate report files, check versions, and match uploaded documents. Whether further verification via the number on a laboratory's public platform or regulatory authority is possible depends on the report type, laboratory accreditation, and inquiry channels. It generally cannot serve as the sole verification basis.
If a product is sold on multiple platforms, can the documents be reused?
Some basic test reports (e.g., RoHS, REACH, UN38.3) may be accepted by multiple platforms, but each platform may have different requirements regarding file format, report validity, and supplementary declarations.
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.
