Product category

Bicycle helmets and CPSC eFiling

Prepare bicycle helmet records around model, size, shell/liner, warnings, test reports, and version changes.

Audience: Importers of bicycle helmets, kids' helmets, multisport helmets, and helmet variants.

Helmet model identity matters

Helmet records should tie test reports to the exact model, size range, shell, liner, retention system, warnings, and production run.

Track model, size, shell material, liner, buckle/strap, padding, color, and graphic variants.
Confirm whether the helmet is bicycle, skate, multisport, child, or adult marketed.
Keep warning labels, instructions, and packaging versioned with the product record.

Supplier and lab details

Ask for enough detail to connect the imported helmet to the tested sample.

Report number, test date, lab legal name/address/phone, and citations/standards tested.
Factory, manufacture date range, batch/lot, mold or material changes, and size coverage.
Whether shell, liner, strap, buckle, padding, label, or factory changed after testing.

Handoff workflow

Version tracking helps when colors, graphics, sizes, materials, or factories change.

Full PGA data pack for the supported helmet record.
Reference PGA Version ID when Product Registry is used.
Missing checklist for size coverage, report match, and broker workflow.

Copy-ready assets

Templates you can adapt

Helmet supplier request

Please confirm helmet model, size range, shell/liner materials, retention system, padding, warnings/instructions, tested sample report number, lab details, factory, manufacture date range, batch/lot, and whether shell, liner, strap, buckle, label, graphic, or factory changed after testing.

Mini FAQ

Common questions

Do color or graphic changes matter?

They may if they reflect material, coating, labeling, or version changes. Track them so the reviewer can decide with source records.

Next step

Prepare helmet packet records with model and size-range traceability.