Skip to content
Pairlot Request the stock list

Kids shoes and CPSIA: testing and certificates

Children's footwear is regulated differently from adult shoes in the US, and the difference is paperwork you cannot improvise after bulk. Three items - testing, a certificate and tracking labels - all have to be planned before production, not after.

Children's footwear is its own rulebook

Shoes for children are not adult shoes with smaller sizes. In the US, products designed or intended primarily for children aged 12 and under fall under the Consumer Product Safety Improvement Act, and that changes the paperwork around a kids' program in three concrete ways: the product needs third-party testing at a lab the CPSC accepts, the shipment needs a Children's Product Certificate, and the shoe needs tracking labels. None of the three can be improvised after bulk arrives - testing answers for a specific build, and a certificate is only as good as the evidence behind it.

The desk coordinates kids' programs the way it coordinates any program - spec sheet, samples, inspection - with the testing scope added early, because in children's products the testing plan is part of the design. A kids' style with the wrong trim is not a compliance problem discovered at the lab; it is a design decision made in week one. This note is general information for buyers: the scope that applies to your program is confirmed with a CPSC-accepted testing lab and a compliance adviser.

Where risk sits in a shoe

A sneaker is mostly textile, foam and rubber, but children's products are assessed with small hands in mind. The points that matter most in practice:

Notice what that list suggests about design. A kids' style with fewer loose trims, printed decoration instead of stitched-on charms, and plain colorways is not only simpler to test - it is simpler to make, faster to inspect and cheaper to run. In children's footwear, compliance and clean design point the same direction, which is why the kids' lines on the stock list - chunky builds and trail-style runners at EU 36-41 - stay plain-face.

The three documents, in order

ItemWhat it isWhere it comes from
Third-party test reportTesting of the product to the applicable children's product rulesA CPSC-accepted testing lab, on a sample that represents the bulk build
Children's Product CertificateA certificate stating the product meets the applicable rules, based on the test evidenceThe importer of record, built from the testing - not instead of it
Tracking labelsPermanent marks on the product linking it to its maker, its location and its production runApplied in production, with details fixed in the program sheet

The order matters. Testing evidence supports the certificate; the certificate travels with the shipment; the tracking labels go on at the line. A program that leaves any one of the three to the end discovers that the other two were waiting on it - which is why the desk puts the testing scope on the timeline at the brief, not at the packing list.

What the desk does, and never claims

The desk never claims to hold certificates, and it does not issue them. Where a program needs testing, the desk coordinates the scope with the lab and the partner factory, tracks the samples through testing, and verifies the test reports by report number per program. A report number your team can check is worth more than any wording on a website, which is why that is the form the desk's verification takes.

The buyer remains the importer of record, and the obligations that come with that role stay with the buyer. The desk's job is to make sure the facts, the samples and the documents line up - the spec sheet declares what the shoe is, the sample matches the spec, and the lab tests what the spec declares.

A sequence that avoids write-offs

  1. Brief with the age range. The intended age range drives the scope. Say it in the first email, alongside sizes - kids' runs on the stock list sit at EU 36-41.
  2. Spec sheet with every trim. Each charm, print, coating and material goes into the bill of materials, because the lab tests what the spec declares.
  3. Scope agreed before sampling. The lab confirms which rules apply to the build; sampling then targets the confirmed scope.
  4. Testing on a representative sample. Pre-production or first production samples, not a special build that differs from bulk.
  5. Documents verified by number. The desk checks the reports and the certificate before shipment, and your team can do the same.
  6. Tracking labels applied and recorded. Batch and run details recorded per carton, per program.

The reason for the discipline is arithmetic. Testing that fails before bulk costs a sample. Testing that fails after bulk costs the order. School and uniform buyers working on annual cycles feel this hardest - see school and uniform shoe programs for how those calendars run, and why testing belongs at the front of them.

Stock kids' lines and the testing question

A fair question: does the fast stock route skip all this? It does not. The stock route moves finished cartons quickly, but a children's product going into US commerce carries the same three obligations as a custom program - testing, certificate, tracking labels - and the channel decides how they are met. For marketplace and retail channels, the desk plans the same sequence on compressed time: scope agreed with the lab while the carton plan is being confirmed, testing started on a sample from the pick, documents verified before dispatch. What the fast route removes is development time, not compliance time. If your channel has its own documentation requirements, put them in the brief; they shape what is possible on the clock.

Questions the desk will ask first

The first reply on a kids' program works from a short list: the age range the product is intended for, the full trim list, who the importer of record is, whether a lab is already appointed, and who holds the documents at shipment. With those answers, the testing plan can be scoped before samples are made, which is the only cheap moment to do it. For the compliance commitments behind every program, read the compliance page; for how inspection checks labels and trims, see quality control; and to put a kids' program in motion, send the request form - the desk replies with the route, the sampling plan and the open questions in writing.

Questions buyers ask

Do kids' shoes always need CPSIA testing?

Footwear designed or intended primarily for children 12 and under sold in the US falls under CPSIA, which asks for third-party testing at a CPSC-accepted lab. The exact scope for your program is confirmed with the lab and a compliance adviser before sampling.

Who issues the Children's Product Certificate?

The certificate is issued by the importer of record, based on third-party test evidence. It certifies the product meets the applicable rules; it does not replace testing, it rests on it.

Does Pairlot hold safety certificates?

No. The desk never claims to hold certificates. Where a program needs testing, reports are verified by report number per program, so your team can confirm them directly with the lab.

What are tracking labels on children's shoes?

Permanent marks on the product that link it to its maker, location and production run. They are applied in production, and the details are fixed in the program sheet before bulk starts.

Send the styles, sizes and a quantity in cartons. The desk replies in writing with the live stock list, the OEM sampling plan, and the figures that still need deciding.

Request the stock list