Identify the exact product
Record the model, version, materials, age grade, battery or radio features and package claims.
TOY IMPORT DOCUMENTS / SKU / MARKET
Check toy import documents against the exact SKU.
Toy import documents should match the exact model, sample, package claims and destination market. A general supplier statement does not replace product-level review by the buyer's responsible compliance team.
Match the destination market
Share the country and applicable buyer requirements with the responsible compliance team.
Review the product file
Compare model names, test sample, report version, package and requested documents.
Keep the approved record
Store the sample approval, specification, artwork and inspection points together with the order.
MARKETS AT A GLANCE
Toy requirements by destination.
Requirements change by country, product and age grade, and the buyer's responsible compliance team confirms what applies. The table below shows the schemes buyers most often ask our desk to map a Chenghai SKU against.
| Destination | Frequent toy requirements | What the file must match |
|---|---|---|
| United States | ASTM F963, CPSIA lead & phthalates limits, CPC, tracking label | Exact model, tested sample, age grade, package claims |
| European Union | EN 71 series, Toy Safety Directive, CE marking, EU Declaration of Conformity | Model version, materials, importer details, warnings |
| United Kingdom | UKCA marking, retained EN 71 standards, UK declaration | Same SKU version; separate UK responsible person |
| Canada | SOR/2011-17 Toys Regulations, CCPSA lead & phthalates | Tested sample and bilingual packaging where required |
| Australia & NZ | AS/NZS 8124 series, mandatory toy safety standards | Supplier declaration linked to the exact batch |
| Gulf markets | GSO toy requirements, G-Mark conformity | Arabic labeling and product version alignment |
REOPEN THE REVIEW WHEN DETAILS CHANGE
A document match belongs to one product version.
Before treating a file as current, compare its identifier and scope with the sample, written specification and package. A product name alone may not identify differences in materials, electronics, accessories or claims. Keep pending questions visible until the responsible reviewer confirms whether the file covers the order version.
- Model or component changes
- New battery, radio or electronic feature
- Different age grade or package claim
- Translation or artwork revision
- New destination market or sales channel
WHEN A FILE IS NOT READY
Keep the pending step visible.
Record which document is missing or unclear, who is expected to provide it, what sample or SKU it should cover and when the response is needed. Ask whether a current file exists for the exact version or whether new testing, inspection or translation needs to be scoped.
Do not describe a pending file as approved. Agree on any cost and timing before requesting third-party work, and route market-specific decisions to the buyer's responsible compliance team.
- File name and requested scope
- Product version and sample identifier
- Supplier or reviewer responsible
- Expected response date
- Testing or inspection cost assumption
- Approval status before production
ORDER FILE HANDOFF
Keep evidence and decisions together.
Store the accepted specification, package, sample approval and applicable product files with the purchase record. Add the reviewer, date and version for important approvals. When a later order changes its destination or product details, open a new review rather than silently carrying the old decision forward.
BEFORE ORDER RELEASE
Compare the purchase order with the reviewed file.
Check the final SKU, quantity, package, age statement, included parts, destination and approved document versions side by side. If the purchase order describes a different configuration, mark the difference and ask the responsible reviewer whether the current record still applies.
Store the final answer with the order and keep superseded files identifiable. A clear handoff lets purchasing and logistics see which evidence supports the order and which review items remain open. Keep the acceptance tied to this model and market; it is not blanket approval for related SKUs. The document index points to the review record; it does not replace the source report or its stated scope.
WHOLESALE TOY ORDER FILE
Match every document to the item being quoted.
For each SKU, connect the product name and model number to the sample, written specification, package artwork and destination. Check that the version on a report or certificate matches the product and claims in the order file. Similar product photos or category names are not enough to establish coverage.
When importing toys, the buyer's responsible compliance team should confirm which requirements apply to the intended sale. The sourcing request can make that review easier by listing the country, age range, toy function, materials, battery or radio features and package language.
SKU-LEVEL CHECKLIST
- Model, version and included components
- Sample identifier and approval date
- Destination and intended age grade
- Materials, electronics and package claims
- Report scope and issuing party
- Open questions and the person who will confirm them
KEEP CHANGES VISIBLE
Documents are checked by SKU and destination. A file for one model, material, version or market should not be assumed to cover another. If a component, package claim or destination changes, record the change and ask the responsible reviewer whether the current file still applies before production or shipment.
THE NEXT STEP
Need to check documents for a product?
Send the SKU reference, destination market and intended age range so we can identify the right file questions.
DOCUMENT FAQ
Document questions compliance teams ask.
01Does a test report for a similar toy cover my SKU?+
Only when the identifier, materials, components, decoration and factory of the tested sample genuinely match the version being ordered. A report belongs to one product version; a similar photo, name or category is not evidence of coverage. We compare model identifiers and report versions and reopen the review when anything changes.
02Does LowMOQ Toy guarantee that a toy passes every market's rules?+
No responsible supplier can guarantee that across markets, and we do not phrase it that way. We collect and organize product-level files against the named destination, keep open questions visible, and route the legal decision to the buyer's compliance team, which confirms what applies to the intended sale.
03What happens when a file is not ready before production?+
The pending step stays visible: which document is missing, who supplies it, what SKU and sample it must cover, and when it is due. Any third-party testing cost and timing is agreed before the work is ordered, and the item is not described as approved until the matching file exists.
04Which product details most often trigger a new compliance review?+
A material or component change, a new battery, radio or electronic feature, a different age grade or package claim, a translation or artwork revision, or a new destination market. When one of these changes, the SKU gets a fresh review rather than silently carrying the old decision.