Why Verifying Documents Before Submission Matters

When submitting testing and certification documents on cross-border e-commerce platforms (such as Amazon, TEMU, SHEIN, Walmart, TikTok Shop) or in offline trade, incomplete documents, incorrect formats, or expired reports are common reasons for rejection. Systematically verifying the document checklist in advance helps reduce the time cost of repeated communication and resubmission. This article provides a practical verification reference covering aspects such as business documentation, product documentation, labels/instructions/images, reuse of existing reports, and common missing issues.

Business Documents: Basic Files to Prepare

Regardless of product category, platforms generally require business or seller identity information. Common documents to prepare include:

  • Business license or commercial registration certificate (clear scanned copy)
  • Product brand information (such as trademark registration certificate or authorization letter)
  • Manufacturer or supplier information (such as factory registration number, contact person)
  • Importer information (if applicable, especially for EU CE and UKCA scenarios)

Different platforms may require documents in languages such as Chinese/English or the target market language; it is advisable to confirm in advance. Business information should match the manufacturer information in the product test report to avoid rejection due to name discrepancies.

Product Documents: Test Reports and Compliance Documents

The required testing and certification documents vary significantly depending on product category and target market. Common document types include:

  • Test reports: For example, RoHS reports, REACH reports, toy test reports, electrical safety test reports according to applicable standards. Reports should cover the main risk points of the product.
  • Declarations of Conformity (DoC): For example, CE Declaration of Conformity, UKCA Declaration of Conformity, which should include product model, applicable standards, manufacturer signature, etc.
  • Authorization documents: For example, FCC authorization (depending on device type, some devices require Certification through an FCC-recognized TCB), FDA registration confirmation (if medical devices or food contact materials are involved), etc.
  • Other platform-specific documents: For example, CPC document (Children’s Product Certificate) with corresponding children’s product test reports, SDS/MSDS (Safety Data Sheets), etc.

Note: In the CE/UKCA route, whether a notified body is required depends on the applicable regulation, product category, and conformity assessment procedure. Most low-risk products can be self-declared by the manufacturer based on applicable standards and technical documentation. It is recommended to judge based on actual product conditions.

Key Points for Verifying Labels, Instructions, and Product Images

During platform review, clear versions of labels, instructions, and product images are often requested. Key points to verify include:

  • Whether the label contains product model, rated parameters, manufacturer/importer information, safety warnings, and CE/UKCA/FCC marks (if applicable)
  • Whether the instructions are in the target market language (e.g., English, German, French)
  • Whether product images clearly show label location, appearance, and internal structure (if needed)
  • Whether warning statements and compliance marks are consistent with the description in the report

It is recommended to retain original packaging label photos and electronic design drafts for multiple submissions on different platforms.

How to Reuse and Verify Existing Reports

If test reports are already available, confirm the following:

  • Whether the report number corresponds to the specific product model and batch
  • Whether the report date is within a reasonable range (report validity depends on regulatory requirements, product changes, platform rules, and report coverage; no fixed validity period is set)
  • Whether the report was issued by a qualified laboratory (e.g., ISO 17025 accredited laboratory, but this must be assessed in conjunction with product category and platform requirements)
  • Whether the standard version in the report is still accepted by the target market or platform (e.g., CE non-mandatory requirements for low-voltage toys should be judged according to specific directives)

If the product scope, materials, or structure covered by the report have changed, retesting or supplementary testing may be necessary. It is recommended to consult with the testing organization to confirm reusability.

Common Missing Document Issues and Responses

Based on experience, the following situations are more likely to be rejected by platforms:

  • Providing only a test report but lacking the corresponding Declaration of Conformity (e.g., CE DoC) or authorization documents (e.g., FCC Certification)
  • Company name does not match the manufacturer name on the report
  • Label lacks CE/FCC/UKCA marking (if applicable) or the marking is non-compliant
  • Missing SDS/MSDS (for chemicals or products containing batteries)
  • Battery products not providing UN38.3 report

It is recommended to check against the specific guidelines published by each platform before first submission. Review requirements may differ between platforms (e.g., Amazon, TEMU, Walmart). If necessary, consult a testing and certification compliance review team for a pre-assessment.

Pre-Submission Checklist

  • Business license or company registration document (scanned copy with clear information)
  • Product test report (covering applicable standards and risk points)
  • Declaration of Conformity or authorization document (prepared according to product route)
  • Labels, instructions, product images (language, markings, information complete)
  • Verification of existing report validity (report number, date, scope)
  • Platform rejection records (if any, for targeted supplements)
  • Test sample information (if retesting is required)

Before submission, it is recommended to archive files with clear names and prepare them in the file format required by the platform (PDF, JPG, etc.). The final review result is subject to platform rules, product documentation, and actual submitted content.

Risk Notice and Platform Review Boundaries

The content described in this article is a reference for document preparation and does not constitute a guarantee of platform acceptance. Platform requirements for documents may be updated at different times. Product compliance routes need to be assessed based on specific product category, target market regulations, and platform rules. It is recommended to confirm key information with a testing and certification compliance review team or platform support channels before submission.