What Are Basic Fields in Certificate Verification?

When submitting test reports or compliance documents to cross-border platforms (e.g., Amazon, TEMU, Walmart), platform review systems typically compare several core fields in the document. These fields include, but are not limited to: report number (Report No.), product name/model, manufacturer name, test standard or regulation number, issuance date, laboratory name, etc. Different platforms and product categories may have varying matching requirements, so verifying basic fields is the first step in document preparation.

Key Business Information Fields to Verify

For business information, common fields that need to be checked include:

  • Legal business name (must match or relate to the manufacturer name on the report)
  • Address (registered address and production address may differ; choose based on platform requirements)
  • Contact information (email, phone; some platforms use this for review result notifications)
  • Registration number or identifier (e.g., FDA FEI number, EORI number, depending on product and target market)

It is recommended to compare business information with the manufacturer details in the report field by field before submission to avoid rejection due to spelling discrepancies or address mismatches.

Key Product Information Fields to Verify

Product information fields include:

  • Product name (should match the report and label; avoid abbreviations or unverified marketing names)
  • Model/style number (a product may have multiple models; the report must cover all models or submit multiple reports as per platform rules)
  • Batch number or serial number (if applicable, must correspond to the label)
  • Applicable regulations/standards (e.g., CE directives, FCC rules, RoHS/REACH clauses; must be clearly listed in the technical documentation)

For electronic products, the FCC authorization path depends on device type: some devices require Certification issued by an FCC-recognized TCB, while others may follow the SDoC path. Do not generalize that all FCC 路径需根据设备类型判断。部分设备适用 Certification，由 FCC-recognized TCB 发出授权；部分设备可能走 SDoC 等路径。.

Verification of Labels, Manuals, and Images

Platform reviews often require uploading product label photos, user manuals, packaging images, etc. Key fields in these documents include:

  • Product name and model (must match the report)
  • Manufacturer information (name, address)
  • Compliance marks such as CE, FCC, UKCA (position, size must meet regulatory requirements)
  • Warning statements or usage precautions (if applicable)

It is recommended to take or scan clear, complete, non-reflective images with legible text. For CE/UKCA marks, 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; some high-risk scenarios may require a notified body.

Reusing Existing Reports and Field Matching

If you have historical test reports, check the following fields to see if they meet current platform requirements before submission:

  • Report number (used for file versioning and matching during upload; cannot be used as a universal verification tool)
  • Whether the standard covered by the report is still the current version (regulatory updates may render old reports invalid)
  • Whether the product models include all variants currently sold
  • Whether the laboratory accreditation is recognized by the platform (recognition lists may differ across platforms)

Note: There is no fixed validity period for test reports. Whether they can continue to be used for platform review depends on regulatory requirements, product changes, platform rules, and report scope. Do not broadly claim ‘报告是否仍可用于平台审核，取决于法规要求、产品是否变更、平台规则和报告覆盖范围，不应简单按固定年限判断。’.

Analysis of Common Missing Documents

Common missing documents include:

  • Failure to submit a Declaration of Conformity (DoC) while only submitting test reports (some regulations require DoC as a separate document)
  • Product labels not showing manufacturer information or address
  • Incomplete model list leading to rejection of some variants
  • Missing platform-specific documents (e.g., CPC document for children’s products on Amazon)
  • FCC SDoC document not properly retained (some products follow the SDoC path)
  • FDA registration information inconsistent with the FEI number in the report

It is recommended to read the platform’s rules on ‘acceptable compliance documents’ in advance and prepare corresponding documents based on product category and technical documentation.

Pre-Submission Checklist

  • Item-by-item verify business information matches the manufacturer name and address on the report
  • Confirm product name, model, and batch are consistent across the report, label, and platform listing
  • Check image clarity to ensure compliance marks (e.g., CE, FCC, UKCA) are legible and sized according to regulations
  • Ensure the report covers the current version of the standard (e.g., latest EN 71, latest FCC Part 15)
  • Review the platform’s upload system for accepted file formats, sizes, and color modes
  • If there is a rejection history, analyze the reason and supplement the corresponding missing fields

Platform review results remain subject to platform rules, product information, and actual submitted content. This article is intended for document preparation and risk verification only and does not constitute a guarantee of platform acceptance.