This comparison covers 3 official alert references, including toy tricycle, toy pushchair, published from 2014-12-12 to 2026-03-27. The recorded risks raise separate evidence questions about packaging exposure, stability/load, entrapment/cords. Compare the product features and dated findings below before scoping an investigation. These historical observations do not determine your product’s compliance or a market failure rate.
Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.
Dated official observations
Compare the product features and reported failure mechanism
The source wording below describes the reported case at that time. Read each complete report before using it in an investigation.
Toy tricycle · SR/00826/26
Report published 2026-03-27 · notifying country Poland · reported origin Poland
The tricycle is not stable enough. When used on uneven ground, it could easily overturn, causing injury to the child. Moreover, inadequate distances between the moving parts of the wheels and frame can cause injuries in case of feet entrapment between moving parts. Furthermore, the plastic bag packaging is too thin. If a child places the plastic bag over their head, they could suffocate. The product does not comply with the requirements of the Toy Safety Directive nor with the European standard EN 71-1. [1]
Reported measures, verbatim
Type of economic operator taking notified measure(s): ManufacturerCategory of measure(s): Withdrawal of the product from the marketDate of entry into force: 16/02/2026Type of economic operator taking notified measure(s): ManufacturerCategory of measure(s): Warning consumers of the risksDate of entry into force: 16/02/2026 [1]
Report published 2024-03-08 · notifying country France · reported origin People's Republic of China
Reported product description
Pink plastic toy pushchair with pink printed textile seat of a width of 16 cm. [2]
Reported risk explanation
The tubes of the toy pushchair’s structure are not strong enough. If a child sits in the pushchair, it can collapse, leading to a risk of entrapment and/or injuries to the child's fingers.The non-permeable plastic bag is not thick enough, and if a child puts the head inside, it can suffocate. The product does not comply with the requirements of the Toy Safety Directive nor with the European standard EN 71-1. [2]
Reported measures, verbatim
Type of economic operator taking notified measure(s): DistributorCategory of measure(s): Withdrawal of the product from the marketDate of entry into force: 08/01/2024Type of economic operator taking notified measure(s): DistributorCategory of measure(s): Recall of the product from end usersDate of entry into force: 08/01/2024 [2]
Report published 2014-12-12 · notifying country France · reported origin People's Republic of China
Reported product description
Pink, toy pushchair supplied in a plastic bag. [3]
Reported risk explanation
null The locking device is not adequate and the pushchair is not sufficiently strong and may collapse. Children may be injured due to entrapment, mainly of fingers, between moving parts. The packaging is a thin, impermeable plastic bag which could cause suffocation.The product does not comply with the requirements of the Toy Safety Directive and with the relevant European standard EN 71-1. [3]
Reported measures, verbatim
Type of economic operator to whom the measure(s) were ordered: OtherCategory of measure(s): Withdrawal of the product from the marketDate of entry into force: 17/11/2014Type of economic operator to whom the measure(s) were ordered: OtherCategory of measure(s): Recall of the product from end usersDate of entry into force: 17/11/2014 [3]
3 distinct official alert references, published between 2014-12-12 and 2026-03-27. Counts describe the acquired reports, with no market denominator.
Report year
Recorded alerts
2014
1
2024
1
2026
1
Recorded risk labels within this evidence task
Label combinations are source facts within one comparison; they do not create separate guides with identical preparation tasks.
Entrapment, Injuries, Suffocation: 1 recorded references
Injuries, Suffocation: 2 recorded references
Source selection, exclusions and calculation method
Filter the acquired, completely parsed English weekly XML releases. Deduplicate official alert references. Group by product category and the complete set of conditional evidence-question topics supported by actual risk text. Risk-label combinations remain recorded cohort facets and do not create buyer intents. Brand, product name, model, origin, notifying country, measurement-only changes and different wording of the same questions do not create intents. Unrecognized mechanisms stay internal for enrichment. Count report years and notifying countries deterministically. Display at most eight newest descriptions with at least 40 characters after whitespace normalization, nonempty reported measures and distinct casefolded descriptions; break date ties by official identifier. All cohort records count even if their description is shorter or not displayed. This is not a representative sample. Counts concern this acquired corpus only.
One acquired version per official public alert reference. Display at most eight newest distinct product descriptions whose normalized whitespace-collapsed text contains at least 40 characters and has nonempty reported measures; ties sort by official identifier. The complete cohort includes shorter descriptions. This is an explicit display selection, not a representative sample.
3 distinct descriptions displayed; 0 cohort records not displayed. Missing fields: {}.
These are selected, dated enforcement observations in the acquired weekly reports, not a random market sample, market-wide failure rate, proof of current product status, or a determination about your product. Notification country is not a complete sales-market or jurisdiction-coverage field. A quoted legal/standard reference is the report’s statement, not independently verified current law or a mandatory test panel.
Calculation safety-gate-evidence-comparison-10; units recorded alerts; no incidence denominator.
Turn the reported failure mechanism into a scoped investigation
Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.
Cord, opening and entrapment configuration — what evidence do we have?
Record the relevant cord/strap, loop, opening or restraint geometry and the intended user/use context. Ask which specific configuration could create the reported trapping/strangulation mechanism; do not infer a universal dimension or release-force limit.
Stability and load-bearing use — what evidence do we have?
Identify the intended loads, support/attachment design, adjustment positions and use surface. Compare the reported collapse or instability mechanism with the actual configuration and agree a supported investigation rather than copying another case’s response.
Packaging bags, films and exposure — what evidence do we have?
Document the supplied bag or film, dimensions, openings and accessibility to the intended or foreseeable users. Compare the report’s packaging exposure mechanism separately from the product’s detachable parts. Ask for justified current criteria for the actual packaging and use.
Useful evidence: Packaging drawings/specifications and openings, supplied configuration, user/accessibility assessment and existing packaging evidence.
Can we trace the affected component, formula or design revision across our supplied products?
Compare the reported descriptions with your own identifiers and change records. Treat missing or “Unknown” source fields as unresolved; they do not establish that no action was needed.
Useful evidence: Product identifiers, revision history, supplier/batch traceability and market/operator records.
Who would own an evidence review and any resulting corrective-action decision?
Read the reported measures as historical observations. Establish your own operator roles, sector-specific rules, decision owner and communication responsibilities before adopting another case’s response.
Conditional: Product-risk evidence and operator-role review — Compare the recorded product features and failure mechanism with your product. Confirm the applicable product regime, deciding evidence, operator responsibilities and justified next steps. This does not assume that GPSR or a representative appointment applies to every alert category.
Questions for providers
Which specific product features and reported risk mechanism make these cases relevant or irrelevant to our product?
What current legal, standards or scientific sources support your proposed investigation criteria, and what cannot be concluded from these dated alerts?
Which existing evidence can answer the risk question, what additional work is justified, and who owns any resulting corrective-action decision?
Sources and data dates
Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.
