What Information Needs to Be Prepared?

Before determining whether a product meets the compliance documentation path of a platform or target market, compliance review teams typically need to collect a series of basic information. This information helps in preliminary assessment of applicable regulatory requirements, possible testing items, and report types. The following sections detail the information by type so that enterprises can prepare in advance accordingly.

Basic Enterprise Information

Enterprise information is the foundation for assessing the documentation path. Typically needed:
– Enterprise full name (Chinese and English), registered address, Unified Social Credit Code or business registration number;
– Contact person and contact information;
– If exporting to the EU or US, EU REP or US Agent information may be required (if applicable);
– If FDA registration is involved, relevant identification numbers such as FEI number or DUNS number should be prepared.
During platform review, the accuracy and consistency of enterprise information directly affect document matching results.

Product Information and Specifications

The technical parameters and intended use of the product itself are core to determining the compliance path. It is recommended to prepare:
– Product name, model number, SKU, and product category description;
– Main materials, parts list (e.g., electronic components, batteries, chemical substances);
– Applicable age or use scenario (e.g., children’s toys, electronic devices, cosmetics);
– Intended target market (EU, US, UK, Japan, etc.);
– Product change history (if existing reports exist but the product has been modified, describe the changes).
Different product categories (e.g., toys, low-voltage electrical appliances, cosmetics) have significantly different applicable regulatory paths. Accurate product information helps compliance review teams preliminarily map to the regulatory framework.

Labels, Instructions, and Images

Labels and instructions usually need to include:
– Product name, model number, manufacturer information, country of origin;
– Safety warnings (e.g., for children, contains small parts);
– Compliance marks (e.g., CE, UKCA, FCC), but note that marks must be based on a compliance path and cannot be affixed arbitrarily;
– Instructions in the language required by the target market (e.g., EU requires local language).
Providing clear product photos (including labels, packaging, instructions) helps compliance review teams quickly confirm product category and mark conformity.

Existing Test Reports and Compliance Documents

If the enterprise already has third-party test reports or compliance documents, they should be provided together. Common types include:
– Test reports (e.g., RoHS, REACH, LFGB, FCC, CE related standard tests);
– Children’s Product Certificate (CPC document) and corresponding test reports;
– Declaration of Conformity (DoC) or manufacturer’s declaration;
– FCC authorization letter (if applicable);
– SDS/MSDS (Safety Data Sheet), etc.
Service providers will assess whether the reports can be reused based on coverage, test standard version, report validity, and whether the product has changed. If reports have expired or the product has changed, supplementary testing or document updates may be needed. Report numbers can serve as a basis for version verification and upload matching, but whether the platform ultimately accepts them is subject to platform rules.

If the product is sold or planned to be listed on e-commerce platforms (Amazon, TEMU, SHEIN, Walmart, TikTok Shop), it is recommended to additionally provide:
– Product link or ASIN on the platform (if applicable);
– Compliance documents already requested by the platform or rejection screenshots (if any);
– Applicable platform terms or policy links (optional).
Different platforms may have different documentation requirements for the same product category. Providing platform information helps compliance review teams recommend a documentation path according to platform rules. Note: The platform retains final review authority. This article is only for reference in document preparation and does not constitute a guarantee of platform acceptance.

Common Missing Documentation Issues

In practice, enterprises often face the following missing documentation situations:
– Lack of enterprise information in English or EU/US representative information;
– Incomplete product material list (e.g., not listing all components);
– Missing warning labels or compliance marks on labels;
– Existing reports cover versions that are too old or do not cover all target markets;
– Platform rejection screenshots not provided, making it impossible to pinpoint specific issues.
It is recommended to complete the above information as much as possible before formal submission to improve documentation matching efficiency.

Pre-Submission Checklist Suggestions

Before submitting information to a compliance review team or platform, enterprises are advised to verify the following:
1. Whether the enterprise name and address match the business license or registration documents;
2. Whether the product model number matches the model number on the packaging, instructions, and reports;
3. Whether the compliance marks on labels correspond to the completed compliance path (not arbitrarily added);
4. Whether the version of existing reports covers the current product status;
5. Whether all platform requirements have been read and preliminarily cross-checked.
If uncertain, consult a compliance review team for a preliminary assessment to avoid repeated supplementation due to incomplete documentation.

If you need help organizing the above information or assessing the applicable documentation path, the following services may be relevant: product compliance documentation review, target market regulatory assessment, test report applicability analysis, platform rejection reason diagnosis, etc.