Structure the stable identity facts — product type, series, variant, age grade, the standards edition a report was tested against, and the responsible party — and keep volatile commercial and internal details in a private inventory record. That split is the practical answer, because regulatory and certification status attaches to a specific product configuration, age grade, standard edition and responsible party, not to a factory or brand name in the abstract.
Nothing in the official texts cited here requires schema.org markup, and no search engine publishes a required field list for toys. What the regulations do require is that safety information travels with the exact goods — which is why a compliance claim must be traceable to a SKU, a report and a version. This page covers which SKU facts are safe to publish as structured data, which should stay internal, and how to check a supplier's data before you commit to an order.
Key Benefits
Structured SKU facts reduce the cost of verifying a compliance claim. When a product page states the age grade, the standard edition tested against, and the party responsible for conformity, a buyer can match those fields against the certificate instead of trusting a supplier's summary. According to CPSC business guidance, children's toys generally require testing at a CPSC-accepted laboratory and a Children's Product Certificate, and the product, age grading and applicable rule set must be mapped before a compliance statement is drafted. That mapping is the work — the structured field is just where the result lives.
The benefits fall into four practical groups.
1. Traceability. Tracking information should be permanent and support product identification where applicable, according to CPSC tracking-label guidance, and packaging, product markings and lot control should be reviewed together. A structured SKU record is what lets you follow a claim from a listing back to a carton and a report.
2. Scope accuracy. A Children's Product Certificate is product-specific and should not be described as a blanket factory certificate. Structuring the SKU as the unit of identity prevents the common error of treating a factory-level audit document as proof for every item that factory makes.
3. Change control. After a change that can affect safety or compliance, the retest decision should be documented even if the product name and SKU stay the same. A schema field that names the report version makes that change visible instead of silent.
4. Fewer listing disputes. Carton marks should identify the SKU, quantity, destination, handling information and the lot or shipment reference needed by the warehouse. When the digital SKU record and the physical carton mark agree, receiving and marketplace checks stop generating exceptions.
Types & How to Use
Not every SKU fact deserves the same treatment. Split them into three buckets: publish, publish-with-conditions, and keep internal.
Publish: the stable identity layer. Product type, series or subcategory, variant, and a sequential identifier form the backbone. A widely used internal pattern is four parts — a short product-type abbreviation such as TOY, a subcategory or series code, a three- or four-digit sequential number, and an optional condition or variation code. Assign the code before photography or listing so the identifier never changes after sales history attaches to it.
Publish with conditions: safety and conformity facts. Age grading and small-part risk are connected and must be assessed for the actual product configuration, and assemblies, detachable accessories and packaging components need the same review discipline. So the age grade you publish belongs to the tested configuration, not to the product family. Likewise, a test report should identify the product configuration, age grade and standard edition. If your structured data names a standard, name the edition the report actually cites, and check the current regulation before quoting it — the applicable edition should be read from the current regulation, not from an older report copy.
Keep internal: commercial terms and volatile state. Molded-toy MOQ is a factory- and SKU-specific commercial term affected by resin, mold, decoration, packaging and production quantity; it should not be published as one universal industry fact, and it has no business sitting in a shared product schema. Cost, supplier identity, warehouse bin location, condition grade, photo history and reorder points belong in the inventory record. One operational rule from the SKU-design literature is worth keeping: the SKU identifies the item, the inventory record explains it.
Two structural cases need extra care. First, split production: if one SKU is produced across factories or lots, the split should be visible in the order, carton code and compliance evidence. Second, market scope: the GPSR is a separate legal instrument from the Toy Safety Directive, and importer, manufacturer and product-identification information should be mapped to the relevant market role before publication. A US-bound SKU and an EU-bound SKU can share a product family but not a compliance record.
Expert Q&A
Q: Does the EU Digital Product Passport replace the certificate fields I already collect?
A: No — treat them as different systems with different timelines. Digital product passport data must use open standards and an interoperable format and should be machine-readable, structured, searchable and transferable as appropriate, but the passport is not the same instrument as the Toy Safety Directive or the GPSR, and the three should not be collapsed into one deadline. Where the official text does not confirm an application date for a specific product category, write that the timeline is not confirmed from official text rather than asserting a mandatory date.
Q: Can I publish "CE certified" or "CPC certified" as a structured product attribute?
A: Not as a factory-level claim. CE marking and an EU Declaration of Conformity belong to the conformity process and must be matched to the product scope, and a CPC is product-specific rather than a blanket factory certificate. Never turn a standard, guidance page or audit framework into a claim that a specific factory or SKU is certified. Publish the basis instead: the rule set applied, the report version, the age grade, and the responsible party.
Q: Which standard edition do I put in the field — the newest one or the one on my report?
A: The one your report actually cites, paired with a note that the edition should be re-checked against the current regulation. The applicable edition should be read from the current regulation before a report is quoted, and the exact edition and incorporated regulatory status of ASTM F963 should be checked before quoting it. A structured field that says "latest" tells a buyer nothing auditable.
Q: My supplier offers one certificate covering an entire factory. Is that usable?
A: Only as context, not as product proof. Children's toys generally require testing at a CPSC-accepted laboratory and a Children's Product Certificate, and that certificate identifies the applicable rules and responsible parties for that product. A document that names a factory but not a configuration cannot support a SKU-level claim.
Q: How do I handle a toy sold in both the US and the EU under one internal SKU?
A: Keep one internal identity and two compliance records, because the market roles differ. The GPSR sets a horizontal general safety requirement for consumer products and covers distance and online selling, with safety assessed across physical, mechanical and chemical characteristics, presentation, intended and foreseeable use, and the entire lifespan. The EU instrument and the US rule set are separate; map each to its own scope, responsible party and document set.
FAQ
Is schema.org markup legally required for toy listings?
No. Nothing in the official texts cited here requires schema.org markup, and the GPSR does not prescribe structured-data fields — it sets a general safety requirement for consumer products and treats online listings as in scope when targeted at EU consumers. Structured data is a commercial and traceability choice, not a legal one.
What changes for US toy importers in 2026?
Beginning July 8, 2026, importers of most regulated consumer products will be required to electronically file Children's Product Certificates, according to CPSC. Practically, that raises the value of keeping certificate data as a discrete, product-linked field rather than a PDF buried in an email thread.
Can I put the SKU in the product title?
Keep the internal code out of customer-facing titles and in private listing fields. The SKU is an internal identifier; the title and descriptive attributes carry the buyer-facing meaning. Mixing the two makes both harder to maintain.
How many SKU fields should I actually publish?
Start with the stable identity layer plus the safety facts you can document. Adding fields you cannot evidence — a standard edition nobody can point to, an age grade that does not match the tested configuration — creates risk rather than search value.
What should I ask a supplier to send before I approve a SKU?
Ask for the tested configuration, the age grade, the standard edition cited, the responsible party, and the conformity document that names the product. If one SKU is produced across factories or lots, ask how that split appears in the order, carton code and compliance evidence.
Do I need a Digital Product Passport now?
Treat it as a separate system from the Toy Safety Directive and the GPSR with its own timeline. The passport is expected to be machine-readable and use open, interoperable formats, but where the official text does not confirm an application date for a given product category, the timeline is not confirmed from official text.
Sources
Reviewing toy SKU data before you commit?
If you are preparing a toy range for the US or EU and want a second pair of eyes on how SKU-level facts, age grades and conformity references line up with your listings, send the product data pack for review and we will tell you which fields hold up and which need a document behind them.