← Back to Blog
· 3 min read COMPLIANCE CPSIA CPSC

Tracking labels: what has to be on a children's product

The statute asks for two different sets of information for two different audiences, and most labels we see satisfy only one of them. Here is both.

JC
James Chang Written with AI
Two people packing online orders in a small business setting with a laptop.
Photo by Kampus Production on Pexels

Tracking labels look like the easiest CPSIA requirement, and they're among the most commonly mishandled, because almost everyone reads half the statute.

Checked on 6 September 2026. If you are still working out whether your product needs one, start with GCC vs CPC.

Two audiences, two lists

The requirement is 15 U.S.C. 2063(a)(5), originally section 103 of the CPSIA, effective one year after 14 August 2008. It requires permanent, distinguishing marks on the product and its packaging, to the extent practicable, that enable two separate things.

So the manufacturer can determine:

  • the location and date of production
  • cohort information — batch, run number or other identifying characteristic
  • any other information the manufacturer determines will help ascertain the specific source

So the ultimate purchaser can determine:

  • the manufacturer or private labeler
  • the location and date of production
  • cohort information

Read the two lists side by side and the trap is obvious. The manufacturer's name or private labeler appears only in the purchaser's list. A batch code that means something in your internal system, printed alone, satisfies your half and fails the customer's — they cannot tell whose product it is.

Conversely, a brand name and nothing else fails your half: no date, no cohort, nothing that narrows a recall to a run.

"Permanent" and "to the extent practicable"

The statute asks for permanent, distinguishing marks, and it asks for them on the product and the packaging. The qualifier "to the extent practicable" is doing real work for products where marking is genuinely difficult — but it is an exception you should be able to justify, not a default.

The practical test is whether the mark can reasonably be expected to survive the product's useful life. That is what makes hangtags and adhesive labels weak candidates for the product itself: a recall happens after the tag is gone. Packaging is where the removable formats belong, and packaging is separately required anyway.

There is no prescribed format

This surprises people who go looking for a template. The statute specifies the information that must be ascertainable, not a layout, a symbol or a fixed field order. A date code your customer service team can decode is fine, provided the required information is genuinely ascertainable from it.

That flexibility cuts both ways. Nobody will reject your format, and nobody will tell you it is insufficient until you need it — which is during a recall, the one moment when "we can work out which run that was" has to be true rather than aspirational.

Where this actually bites

The purpose is recall scope. Without usable cohort information, a defect found in one run becomes a recall of everything you ever sold under that model number, because you cannot prove which units are affected. The label is not a formality; it is the difference between recalling a batch and recalling a product line.

A short self-check

  • Can a customer holding the item alone name the brand, the production date and the batch? If not, the (ii) list is unmet.
  • Can you narrow a complaint to a run and a factory from the mark? If not, (i) is unmet.
  • Is the mark on both the product and the packaging, or do you have a practicability reason you would be comfortable stating?
  • Will the mark survive normal use, or is it on something that comes off in the box?
  • Does your supplier know the format is fixed for the life of the SKU? A factory that changes its date-code convention silently breaks your ability to read your own history.

That last one is the failure we see most: the label is correct at first production and nobody checks it again. Keeping the mark format on the product record — with the date it was confirmed — turns it into something you can re-verify instead of rediscover.


General information, not legal advice. The statute is linked above; check it and talk to counsel about your products.

James Chang

Founder of Aleph. Building import compliance tools for US importers who are tired of spreadsheets and six-figure enterprise software.