The age rating is a toy retailer's most double-edged attribute: a legal EN 71 duty and the top shop filter at once — yet suppliers rarely deliver it the same way twice.
In a toy shop, one attribute does more work than almost any other: the age rating. A parent shopping for a three-year-old filters by age before they look at brand, price or theme. And the same field is a legal signal — the EN 71 safety standard requires a clear „not suitable for children under 3 years“ warning on any toy with small parts. The age rating is a duty and a sales filter in a single number, and getting it clean across every supplier is harder than it sounds. This is a focused piece under the broader toy retail product-data challenge.
Product data for toys by age is the discipline of turning one legal-and-commercial fact — the appropriate age — into a clean, complete, filterable attribute on every product. Sounds trivial. It isn't, because your suppliers don't agree on how to state it.
Two things collide in a single field. First, the age rating is a compliance obligation: under EN 71, a toy with small parts must carry the „not suitable for children under 3“ warning, usually shown as the crossed-out 0–3 symbol, and the shop is expected to surface it. Second, it is the most-used shopping filter in the category — age band beats every other facet for gift buyers and parents.
Making it worse, there isn't one „age“ but two:
A customer-facing shop needs both: the compliance warning displayed, and a structured age band to filter on. Confuse them, or leave either blank, and the product is either non-compliant or un-findable.
Because there is no field everyone fills the same way. Across a multi-supplier assortment, the exact same fact — „suitable from age 3“ — arrives in wildly different shapes:
Consolidate a few dozen suppliers and you're staring at all five patterns at once. The manual work is reading each one, deciding what the minimum age really is, and typing it into a single consistent attribute — thousands of times.
There are standards in play, but each covers only a slice. Here's the honest split:
| Data layer | What the standard delivers | Where it stops |
|---|---|---|
| Safety warning | EN 71 defines the „not under 3“ warning and 0–3 symbol | It's a warning, not a filterable age field |
| Structured master data | GDSN / ETIM can carry a minimum-age attribute | Only if the supplier actually fills it — many don't |
| Article identity | GTIN/EAN identifies the product cleanly | Says nothing about age suitability |
| Recommended play age | No binding standard at all | Pure supplier free text and marketing ranges |
| Sales content | Not the job of any of these standards | Descriptions, benefit copy, imagery absent |
In short: EN 71 gives you the legal warning but not a filter; GDSN/ETIM can carry a clean minimum age but only when the supplier bothered to fill it; and the recommended play age has no standard behind it at all. The gap — a complete, normalized, filterable age attribute on every SKU — is exactly the part left to manual work.
Productbay treats the age rating as a first-class attribute and closes the gap in three moves:
Nothing publishes without a review step — the point is to make a large toy catalog complete and filterable by age without a human retyping every rating by hand. Productbay is built for specialist retailers running multi-supplier catalogs, and the age attribute is one example of the wider job: consolidating, normalizing and enriching inconsistent supplier data into one clean structure. For the full category picture, start with the toy retail overview.
Age ratings that are a duty and a filter, delivered four different ways by four suppliers — that's exactly the gap Productbay closes. See how it normalizes and scores the age attribute across your whole toy catalog in a 30-minute walkthrough.
Get started