1. Company Document Verification

Before submitting testing and certification documents, ensure that the company entity information is complete and consistent with the information registered on the platform. Applicable product examples: electronic appliances, toys, textiles, cosmetics, etc. Company documents typically include: business license (bilingual or with English translation), import/export license (if applicable), manufacturer authorization letter (if you are an agent or brand owner), FDA registration number or FEI number (if FDA-regulated products are involved), and the legal signature page of the CE/UKCA declaration of conformity. If the company name or address has changed, update the platform backend information first before uploading documents; otherwise, discrepancies may lead to rejection.

2. Product Information Verification

Product information is the core basis for review and should be checked against platform requirements item by item. Applicable product examples: consumer electronics, children’s products, food contact materials, dangerous goods, etc. Product information should include: product name, model number, batch number, key parameters (voltage, power, material composition, etc.), and a list of applicable standards or regulations (e.g., EN 71, ASTM F963, REACH Candidate List, etc.). If multiple models share a single test report, confirm that the report covers all differences among models (e.g., circuit, dimensions, material consistency). Platforms often require product photos to correspond with descriptions in the report to avoid issues where models are mixed without a statement of differences.

3. Label, Instruction Manual, and Image Verification

Labels, instructions and product images must simultaneously meet regulatory requirements and platform upload specifications. Applicable product examples: electronic appliances require CE marking and WEEE symbol; toys require age warning and CE marking; textiles and apparel require fiber composition labels and care instructions; cosmetics require ingredient list, net content, and expiry date. Platform review scenarios: Amazon requires clear, unobstructed images with readable text; Temu requires uniform file naming conventions (e.g., Model_ReportNo_Date.pdf). Common pitfalls: uploading only a single page label while omitting multi-page instructions, or low-resolution images causing review delays. It is recommended to compile labels, instructions, and product six-view images into a PDF file, named according to platform rules, and submit them together.

4. Reusability Assessment of Existing Reports

To determine whether an existing test report can be directly used for a new platform or new product, the following factors should be checked: whether the product models covered by the report match the submitted model numbers; whether the report issuance date is still within a reasonable period (although there is no fixed validity, if regulations have been updated, products have changed, or platforms require new standards, older reports may not be accepted); whether the testing standards in the report are still the current applicable versions (e.g., RoHS directive updated to 2011/65/EU and its amendments; REACH controlled substance Candidate List updated every six months). Applicable product examples: a series of products using an old report but with changed materials may require supplementary difference testing. Natural transition guidance: If you are unsure about report reusability, you may contact Prylem for a pre-review to confirm whether the report meets the target market and platform requirements.

5. Common Missing Document Issues

Based on platform rejection cases, the following document deficiencies are frequently encountered: declaration of conformity (DoC) or authorization letter not provided; only test report uploaded without other required compliance documents (e.g., CPC document, FCC supplier’s declaration of conformity); children’s products lacking CPSC or applicable product safety authorities or market surveillance authorities-accepted third-party lab test reports; food contact materials without FDA migration test report; dangerous goods without transport condition identification certificate or SDS/MSDS; labels or instructions missing the legally required language version for the importing country. Platform review scenarios: platforms such as Amazon and Temu usually specify the missing items in their rejection notice, but the opportunity to supplement is limited; therefore, thorough pre-submission checking should take priority over post-rejection amendments.

6. Pre-Submission Checklist

  • Company qualification document scans or PDFs (clear, stamped, English translation if needed)
  • Product specification sheets or technical documentation (including model, parameters, materials, circuit diagrams or ingredient lists)
  • Labels, instructions, product images (organized according to platform naming rules)
  • List of existing compliance documents (test reports, declarations of conformity, registration certificates, authorization letters, etc.)
  • Verify that the product description in the report matches the actual product
  • Confirm that the applicable regulation/standard version in the report is still the current valid version
  • Confirm the qualification of the report issuing body (if a third-party laboratory, verify CMA/CNAS or international scope of accreditation)
  • Platform-specific requirements (e.g., Amazon requires upload to specific categories; Temu requires batch upload)
  • If multiple models are involved, prepare a statement of differences or coverage confirmation letter

Prylem offers one-stop services including pre-review of testing and certification documents, report reuse assessment, and guidance on supplementary documents. If you are preparing platform compliance documents, you may send your current file list to us for a targeted review opinion.