Toy Safety & Certification Guide

Toy safety requirements differ by destination market: the US requires a Children's Product Certificate (CPC) based on third-party lab testing under 16 C.F.R. part 1250 and ASTM F963; the EU currently applies the Toy Safety Directive 2009/48/EC, with harmonised standards such as the EN 71 series providing a presumption of conformity to its essential safety requirements (a new EU Toy Safety Regulation, (EU) 2025/2509, entered into force on 1 January 2026 and will fully replace the Directive from 1 August 2030 — see the note below); the UK's Toys (Safety) Regulations 2011 currently allow either CE or UKCA marking in Great Britain. This page is general regulatory education, not legal advice, and does not replace checking the current official rules for your specific product.

Toy safety checklist

• Confirmed the exact destination market(s) and their current toy safety framework
• Confirmed the target age bracket and how it affects which rules apply
• Identified whether the product has commonly-regulated features (small parts, magnets, batteries, chemical content)
• Confirmed current testing/certification requirements via the official source for that market — not assumed from another market's rules
• Confirmed with your sourcing partner exactly what's verified for this specific product, rather than assuming general coverage

EU regulatory transition — what's changing and when

The EU's toy safety framework is mid-transition as of this writing. The current framework is the Toy Safety Directive 2009/48/EC, under which the EN 71 series of harmonised standards is a primary route to a presumption of conformity with its essential safety requirements — meeting the relevant EN 71 standard is not itself the legal requirement, the Directive's safety requirements are, but it is the standard route to demonstrating compliance with them. A new EU Toy Safety Regulation, (EU) 2025/2509, entered into force on 1 January 2026 and will apply in full from 1 August 2030, at which point it repeals and replaces the 2009 Directive. Buyers sourcing toys for the EU market during this transition period should confirm which framework applies to their specific timeline directly with an official EU source, not assume the Directive remains unchanged indefinitely.

Common mistakes

Assuming one market's certification covers another market — A US CPC does not satisfy the EU's toy safety requirements, and neither automatically satisfies UK requirements — each market's rules are separate.

Not confirming the target age bracket early — Age thresholds affect which specific rules and tests apply, and can change a product's regulatory category entirely.

Treating certification as a formality instead of a real testing process — Certificates like the CPC are based on genuine third-party lab testing against specific standards, not a paperwork step alone.

Assuming the EU's toy safety rules are static — The EU is mid-transition from the 2009 Toy Safety Directive to a new 2025 Regulation, fully applicable from 2030 — confirm which framework and timeline applies to your specific shipment.

Frequently asked questions

Does LYBAM certify toys to these standards?

This page is general regulatory education, not a certification claim. Certification status for a specific product is confirmed individually as part of that project — raise your certification requirements directly when you submit your inquiry.

Is this legal advice?

No. This is general educational information about publicly available regulatory frameworks. Requirements change and vary by product and market — verify current requirements via the official regulator for your destination market before making a compliance decision.

Do I need different certification for the US, EU and UK?

Generally yes — each market has its own separate framework (CPC/16 CFR 1250 in the US, the Toy Safety Directive/Regulation with EN 71 harmonised standards in the EU, and the Toys (Safety) Regulations with CE/UKCA marking in the UK). A product sold in multiple markets typically needs to satisfy each market's own requirements.