In short and in plain language
If you sell toys online, you must show warnings before the purchase. This includes the age a toy is meant for. A picture of the box is usually not enough.
Many warnings have a fixed text. The program for stock and buying therefore stores only a short code. The shop turns it into the right sentence in German.
The age is kept in its own fields. This lets the shop filter by age. It can also check if something is missing.
If a detail is missing, the item does not go online. It goes on a list. The buying team then asks the supplier.
New rules with a digital pass for toys start in August 2030. It is not required today. But you can already create the fields for it.
A building block set sits in the cart, one click away from checkout. The box in the warehouse says "Achtung: Nicht für Kinder unter 36 Monaten geeignet", the German form of "Warning: not suitable for children under 36 months" (Annex V Part B No. 1 Dir. 2009/48/EC). The product page does not say it, because the ERP field is empty or the sentence is buried in a long description the shop does not display. This is exactly the gap the German Toy Safety Ordinance (Zweite Verordnung zum Produktsicherheitsgesetz, 2. ProdSV) closes: warnings that determine the purchase decision, such as minimum and maximum age, must be clearly visible before purchase, including when the purchase is concluded electronically (Sec. 11(4) 2. ProdSV). During the holiday season the range grows, seasonal items and new suppliers arrive, and with them records that nobody has checked against the packaging yet. This article covers which warnings exist, why they belong in the ERP as codes rather than free text, how age limits reach shop properties and feeds as separate fields, what a mandatory field check before publishing looks like, and which fields you can prepare for the digital product passport that the new EU Toy Safety Regulation will require from August 1, 2030 (Art. 59 Reg. (EU) 2025/2509).
Key takeaways
- Warnings that determine the purchase, such as minimum and maximum age, must be clearly visible before purchase, including online purchases (Sec. 11(4) 2. ProdSV). In Germany they start with the word "Achtung" and are written in German.
- Annex V Part B of Directive 2009/48/EC lists ten toy categories with their own warnings, and for numbers 2 to 10 the wording is prescribed (Sec. 11(1) 2. ProdSV). In the ERP they are codes with a text module per language, not free text.
- Minimum age, maximum age, weight limits and adult supervision are separate fields, kept apart from the age recommendation for play value. The shop builds the age filter and the warning box near price and buy button from them.
- Feeds and marketplaces draw on the same codes; every distance sales offer contains the required warnings (Art. 19(d) GPSR). Wording that does not fit a field is not shortened; the item is held back for that channel instead.
- A mandatory field check holds back toys that lack an age limit, German wording or CE marking, and flags contradictory codes, such as the under-36-months warning on a baby rattle (Sec. 11(1) 2. ProdSV).
- Regulation (EU) 2025/2509 applies from August 1, 2030 and introduces the digital product passport for toys (Art. 59 Reg. (EU) 2025/2509). It is not mandatory today, but a product identifier and a data carrier field can be set up now.
What Section 11 of the Toy Safety Ordinance requires before purchase
The German Toy Safety Ordinance transposes the European Toy Safety Directive 2009/48/EC into German law. For online retailers, one subsection is decisive. Warnings that determine the decision to purchase a toy, such as the minimum and maximum age of users, and the other applicable warnings in Annex V of the directive must appear on the packaging or be clearly visible to the consumer in another form before purchase. The second sentence of the same subsection expressly includes online retail: this also applies when the purchase is concluded electronically (Sec. 11(4) 2. ProdSV). The box in the warehouse does not help a buyer in the shop. Whatever is printed there and affects the purchase decision has to appear on the product page as readable text before anyone presses the buy button.
Two further subsections define the form. Warnings must begin with the word "Achtung" (Sec. 11(3) 2. ProdSV), and warnings and safety notes must be written in German (Sec. 11(5) 2. ProdSV). For a shop with several language versions, this means the German version is mandatory for the German market; other languages can be added but do not replace it. If you ship to other EU countries, check their language rules separately, because the directive leaves them to the member states (Art. 11(3) Dir. 2009/48/EC). For data management, it follows that a warning is not one text but a set of texts, one per language, with the German version as a mandatory field.
What counts as a toy is set by the definition: all products designed or intended, whether or not exclusively, for use in play by children under 14 years of age (Sec. 2 No. 24a 2. ProdSV). The words "whether or not exclusively" are why the question comes up in a product range more often than expected: plush animals in the gift range, bath toys in the drugstore section or key rings with a play figure are candidates that need checking. Exceptions include playground equipment for public use, toy vehicles with combustion engines, and slings and catapults (Sec. 1(3) 2. ProdSV). There is also the list of products that are not considered toys, including decorative items for festivities and celebrations and puzzles with more than 500 pieces (Annex I Dir. 2009/48/EC). In the ERP, a separate flag "toy within the meaning of the Toy Safety Ordinance" with a short justification pays off. It decides which check rules an item goes through, and it does not belong in the product group, because the same product group can contain Christmas decorations and toys.
The retailer is more than a messenger here. Before making a toy available on the market, the retailer checks whether it bears the required conformity marking and whether documents, instructions for use and safety information in German are included (Sec. 7(2) 2. ProdSV). For the online store, the General Product Safety Regulation adds a rule: every distance sales offer contains at least any warnings or safety information that must be affixed to the product or its packaging (Art. 19(d) GPSR). Manufacturer details and product identification are covered in the article on GPSR economic operator data from the ERP. This article is about the toy-specific warnings and the age limit, the details parents and grandparents actually choose by.
What "clearly visible" means in a shop
Which warnings Annex V provides for
Annex V of the directive has two parts. Part A describes the general user limitations: they include at least the minimum or maximum age of the user and, where appropriate, the abilities of the user, the maximum or minimum weight of the user and the need to ensure that the toy is used only under adult supervision (Annex V Part A Dir. 2009/48/EC). Part B lists ten toy categories with their own warnings (Annex V Part B Dir. 2009/48/EC). For numbers 2 to 10 the wording is prescribed (Sec. 11(1) 2. ProdSV); for number 1 the directive gives example wordings. The table below lists the categories with the wording of the official English version and assigns each category a code that sits on the item in the ERP. In a German shop, the German wording of the same annex is what appears on the page.
| Code | Category (Annex V Part B) | Warning according to the directive |
|---|---|---|
| B1 | Toys not intended for use by children under 36 months | 'Not suitable for children under 36 months' or 'Not suitable for children under three years' or a graphic, plus a brief indication of the specific hazard |
| B2 | Activity toys | 'Only for domestic use' |
| B3 | Functional toys | 'To be used under the direct supervision of an adult' |
| B4 | Chemical toys | 'Not suitable for children under ... years. For use under adult supervision', age specified by the manufacturer |
| B5 | Skates, roller skates, inline skates, skateboards, scooters and toy bicycles for children | 'Protective equipment should be worn. Not to be used in traffic' |
| B6 | Aquatic toys | 'Only to be used in water in which the child is within its depth and under adult supervision' |
| B7 | Toys in food | 'Toy inside. Adult supervision recommended' |
| B8 | Imitations of protective masks and helmets | 'This toy does not provide protection' |
| B9 | Toys intended to be strung across a cradle, cot or perambulator | 'To prevent possible injury by entanglement, remove this toy when the child starts trying to get up on its hands and knees in a crawling position' |
| B10 | Packaging for fragrances in olfactory board games, cosmetic kits and gustative games | 'Contains fragrances that may cause allergies' |
Three features of the list affect the data model directly. The warning on the 36-month age limit must be accompanied by a brief indication of the specific hazard calling for the precaution, such as small parts that can be swallowed; this indication may also appear in the instructions for use (Annex V Part B No. 1 Dir. 2009/48/EC). For chemical toys, the wording contains a gap for the age, which the manufacturer specifies (Annex V Part B No. 4 Dir. 2009/48/EC). And no warning from Part B may be used if it contradicts the intended use of the toy (Sec. 11(1) 2. ProdSV). The directive explicitly justifies this with the misuse of the 36-month warning in particular to circumvent safety requirements (Recital 30 Dir. 2009/48/EC). A baby rattle labeled "not suitable for children under three years" is therefore not an especially careful offer but a contradiction that a check rule can detect.
Warnings as codes instead of free text
In many merchandise management systems, the warning currently lives in the item's long text: typed in by purchasing, copied from the supplier catalog or transcribed from the packaging. That works until the first discrepancy shows up. A missing "Achtung", a "3 years and up" instead of the formula from the annex, an English sentence from the manufacturer's data sheet, a warning cut off mid-word when shortened for a marketplace. Because the wording is fixed for most categories, it does not belong on the individual item but in a master table. The item carries only the code, and the text is assembled when it is output to shop, feed or catalog.
The structure of the annex provides the split. Part A becomes fields, Part B becomes codes. The code master table has few columns: code, legal basis, wording per language, a flag stating whether the wording is fixed or contains a parameter, and a validity period. The item carries a list of codes, the value for parameterized warnings and, for B1, the hazard note specified by the manufacturer. If a wording changes, one row of the master table is versioned, and every affected offer receives the new text at the next sync. The translation exists once, not a thousand times in item texts. To decide which system leads for which field, see the approach in the article on master data synchronization.
{
"sku": "BS-2210",
"name": "Building block set Farm, 120 pieces",
"is_toy": true,
"age_min_months": 48,
"age_max_months": null,
"age_max_status": "no_limit",
"age_recommendation": "4 years and up",
"adult_supervision": false,
"max_user_weight_kg": null,
"warnings": [
{
"code": "B1",
"hazard": {
"de": "Kleine Teile. Erstickungsgefahr.",
"en": "Small parts. Choking hazard."
}
}
],
"ce_marking": true,
"safety_info_languages": ["de", "en"],
"source": "Manufacturer data sheet 2026-09, packaging photo at goods receipt",
"checked_on": "2026-10-14"
}The record separates three things that sit side by side on the packaging. The age recommendation "4 years and up" describes the play value and is sales information. The user limitation lives in the age fields and is checked. Code B1 together with the hazard note produces the sentence shown on the product page: "Achtung: Nicht für Kinder unter 36 Monaten geeignet. Kleine Teile. Erstickungsgefahr." The base formula comes from the directive (Annex V Part B No. 1 Dir. 2009/48/EC), the hazard note from the manufacturer. Source and check date are stored alongside, so it stays traceable later whether a value came from the manufacturer or was added in-house. The maximum age field is empty, and a separate status states that there is deliberately no upper limit.
Chemical toys show why the parameter needs its own field. The wording reads "Not suitable for children under ... years", and the directive states that the age is to be specified by the manufacturer (Annex V Part B No. 4 Dir. 2009/48/EC). If the value is stored as a number on the code, the shop places it correctly in every language, and the check detects a missing value. If it sits in free text, no check can reach it, and a chemistry set can go online with a gap in the sentence.
Age limits as separate fields
The age limit is a detail buyers filter by, and at the same time one that carries considerable legal weight. In the ERP it therefore belongs in two numeric fields, minimum age and maximum age, both in months. Months rather than years, because the decisive limit in Annex V is 36 months (Annex V Part B No. 1 Dir. 2009/48/EC) and baby toys are sold in monthly steps. The display converts to years where it makes sense. An empty maximum age means "no upper limit" and is something different from a field nobody has filled in yet. The record needs a status for this, otherwise the check cannot tell the two apart and either lets everything through or holds everything back.
The other user limitations from Part A are fields as well: maximum and minimum weight of the user with a unit, a flag for adult supervision and a code for required abilities where the manufacturer states them. For activity toys, meaning swings, slides or climbing frames for domestic use (Sec. 2 No. 1 2. ProdSV), a maximum weight can be one of the limitations, and the buyer needs it before purchase because it decides whether the toy suits an older child. Anyone who writes such values into the long text can neither filter nor check them, and every translation has to copy them again.
- Flag "toy within the meaning of the Toy Safety Ordinance" with a short justification
- Minimum and maximum age in months, each with a maintenance status
- Age recommendation for play value as a separate text field, apart from the limitation
- Maximum or minimum weight of the user with a unit
- Adult supervision required (yes or no)
- Warning codes B1 to B10 with parameter and hazard note
- CE marking present and languages of the safety information
- Data source, check date and checking department
An age recommendation does not belong in the same fields. Many boxes also carry a statement such as "for children aged 4 to 7", describing who the game is meant for. It is useful for the age filter, but it is not a warning within the meaning of the annex. Writing both into one field loses the distinction that matters when someone asks: is "4 years and up" a recommendation or a limitation for safety reasons? With two fields, the record answers the question.
From ERP to shop: mapping to properties
In the shop, the fields have two jobs. The age limits feed the filter, the warning codes feed the warning box. In Shopware Community Edition, the age group is a property on the product so that it can be filtered in the category navigation; the limit values themselves are also passed as custom fields, because a property "4 to 6 years" is a range and not a number. The warnings arrive either as fully assembled text per language in a custom field or as a code that the template resolves via text snippets. The second route keeps the wording in one place, but requires every language version of the sales channel to know the snippets.
Translating field to property is a mapping task and belongs in the integration layer, not in an import sheet someone maintains by hand. A minimum age of 48 months and an empty maximum age turn into the filter values of all age groups from 4 years up; code B1 with its hazard note becomes the German sentence for the warning box. The rules are documented and versioned in the data mapping and implemented in the middleware between ERP and shop. If the manufacturer changes an age limit, the change travels the same route and reaches filter, text and feeds at the same time.
Where the warning sits decides whether it is "clearly visible". The obvious place is a box directly above the buy button, in the same screen area as price and delivery time, as text and readable without a click. It starts with "Achtung" (Sec. 11(3) 2. ProdSV); if you show several warnings, it is best to start each one that way. On a smartphone it belongs before the sticky buy button, not in a tab below it. And it also appears wherever people buy without a product page: quick buy from the category list, reorders from the customer account and quick order entry by item number in a B2B shop. Where that is not technically possible, it is cleaner to disable direct purchase for items with warning codes.
A photo is not a warning
Feeds and marketplaces from the same codes
A toy is rarely sold in your own shop only. Marketplaces, price comparison sites and the catalogs of retail customers need the same details, each in a foreign field schema with its own names, value lists and length limits. The obligation travels along: every distance sales offer contains the warnings and safety information that must be affixed to product or packaging (Art. 19(d) GPSR), whatever platform it appears on. If you keep the codes clean once, every channel becomes a mapping task: code B6 becomes the marketplace's warning attribute, the minimum age becomes its age attribute in its unit, the German wording becomes the text field with its length limit. How such channels run through an integration layer is described in the article on marketplace integration via middleware.
Length limits call for care. A warning with prescribed wording must not be shortened just to fit a field. If it does not fit, the mapping picks another field or holds the item back for that channel instead of publishing it with half a sentence. The interface reports this as an error, not as a log note nobody reads. Wholesalers also need a return channel: retailers who take over items from a catalog interface need codes and wording, not just a picture of the packaging. An interface with these fields saves them the transcription and the errors that transcription brings.
The new regulation makes this explicit for marketplaces. Their providers must design their interface so that economic operators can provide the CE marking, warnings and access to the digital product passport, with the warnings clearly visible before purchase (Art. 14(3) Reg. (EU) 2025/2509). This applies from August 1, 2030 (Art. 59 Reg. (EU) 2025/2509). If your data already lives in codes and fields today, you add one more mapping then and do not have to take apart a stock of long texts. Connecting the channels themselves is part of our marketplace integration.
Mandatory field check before publishing
The check is a gate in the data flow. An item with the toy flag is reported as active to the shop only when all rules are met; if something is missing, it remains available internally in the ERP but does not appear in the catalog. The rules derive from what the retailer checks before making a toy available (Sec. 7(2) 2. ProdSV), from the CE marking requirement (Sec. 13(1) 2. ProdSV) and from the fields the shop needs for display. The table below shows a rule set that can be built into existing interfaces.
| Rule | Check in the record | Consequence |
|---|---|---|
| Age limit | Toy flag set, minimum age maintained or status "no limit" | do not publish without it |
| German wording | for every warning code the German text exists and starts with "Achtung" | hold item, add text module |
| CE marking | CE field set (Sec. 13(1) 2. ProdSV) | hold item, query supplier |
| Safety information | instructions and safety information available in German (Sec. 7(2) 2. ProdSV) | hold item |
| B1 contradiction | code B1 with a minimum age below 36 months (Annex V Part B No. 1 Dir. 2009/48/EC) | report conflict, ask manufacturer |
| Hazard note | code B1 without an indication of the specific hazard | hold item or add note |
| Parameter | code B4 without the manufacturer's age | hold item |
| Change | warning code or age field changed | republish product page and all feeds |
The direction of the report matters. An item that fails the check does not disappear silently but lands on a work list with a reason: "B1 without hazard note", "minimum age missing", "wording only in English". Purchasing works through the supplier queries from this list. It is also the proof that the control runs; a rule that holds back not a single item for months is more likely wired incorrectly than unnecessary. It can be tested with an item that deliberately contains every error: if it gets published, the rule is not live.
The check usually does not work alone. The same mechanism runs for manufacturer details under the GPSR, and for food with a toy inside, the toy rules meet the mandatory information from the article on food labeling data from the ERP. A shared check step with rule sets per area of law, applying all relevant sets to each item, makes sense. That keeps the work list one list instead of three, and purchasing sees all open points for a supplier at once.
Data sources, records and private labels
The details come from the manufacturer, not from the shop. Useful sources are structured supplier data, such as a catalog exchange in BMEcat format, manufacturer data sheets and the packaging photo taken at goods receipt. Goods receipt is more than a warehouse step: comparing the packaging with the record there finds discrepancies before the item goes online. The ERP records where goods came from anyway, and there is a legal reason for it. Economic operators must name to the market surveillance authorities on request the economic operators from which they obtained a toy and to which they supplied it, and retailers keep this information for ten years after obtaining the toy (Sec. 9 2. ProdSV).
Private labels and direct imports play a special role. Anyone who places a toy on the market under their own name or brand, or modifies it in a way that may affect compliance with the requirements, counts as the manufacturer and takes on the manufacturer's obligations (Sec. 8 2. ProdSV). Then nobody else supplies the warnings. The data is created in-house, and the code master table becomes a tool for product development. Manufacturers keep the technical documentation and the EC declaration of conformity for ten years from placing the last unit of the toy series on the market (Sec. 3(3) 2. ProdSV); for that, too, the ERP needs storage linked to the series and not only to the individual item.
Outlook: the product passport from 2030
Regulation (EU) 2025/2509 replaces the Toy Safety Directive and applies from August 1, 2030 (Art. 59 Reg. (EU) 2025/2509). The principle for warnings stays the same: they must be clearly visible to the consumer before purchase, including when the purchase is made at a distance (Art. 6(3) Reg. (EU) 2025/2509). The user limitations include at least the minimum age (Art. 6(1) Reg. (EU) 2025/2509), and warnings are preceded by the word for "warning" or a pictogram, which does not have to be repeated for each warning (Annex III No. 1 Reg. (EU) 2025/2509). When agreement was reached in April 2025, the German environment and economy ministries summarized the aim as making the product passport, CE marking and warnings easily accessible to consumers in online retail as well (BMUV and BMWK, press release No. 028/25).
The digital product passport is new. Manufacturers issue it before placing the toy on the market (Art. 19(1) Reg. (EU) 2025/2509). It relates to a specific toy model, is linked through a data carrier to a persistent unique product identifier and must remain available for ten years after the toy is placed on the market (Art. 19(2) Reg. (EU) 2025/2509). The data carrier must be clearly visible to consumers before purchase, including in distance sales (Art. 19(7) Reg. (EU) 2025/2509). So that retailers can do this, the economic operator placing the toy on the market provides them with a digital copy of the data carrier or the product identifier, on request within five working days and free of charge (Art. 19(12) Reg. (EU) 2025/2509). Retailers check before making a toy available whether the data carrier is affixed (Art. 10(2) Reg. (EU) 2025/2509).
None of this is mandatory today. Toys placed on the market in conformity with the directive before August 1, 2030 may still be made available afterwards (Art. 57(1) Reg. (EU) 2025/2509). If you are restructuring your item master data anyway, you can set up the fields now instead of starting a second project in 2030. The mandatory content of the passport is listed in Part I of the annex; under Part II it may also contain safety information and warnings (Annex VI Reg. (EU) 2025/2509). How a product passport is fed from ERP and PIM in general is shown in the article on the digital product passport under the ESPR.
- unique product identifier per toy model, independent of the internal item number
- field for the link to the product passport or the digital copy of the data carrier
- customs tariff commodity code, where purchasing already maintains it
- identifier of the manufacturer and of the responsible economic operator
- list of allergenic fragrances for toys containing fragrances
- manufacturer details on harmonized standards and conformity
What applies today
The sequence in a project
Define the toy range
Find items related to toys, set the flag according to the definition and document borderline cases such as decorations or collector items with a justification.
Create the master table
Set up codes B1 to B10 with the German wording from Annex V, parameters and further languages; map Part A as fields for age, weight, abilities and supervision.
Migrate existing data
Convert warnings from long texts and supplier data into codes, mark discrepancies and resolve them using the packaging or the manufacturer.
Switch the check rules live
Introduce the mandatory field check before publishing, set up the work list for purchasing and prove with faulty test items that the rules hold them back.
Connect shop and channels
Feed the warning box at the buy button, the age filter, quick buy and feeds from the same codes; create the product passport fields but do not display them yet.
Find items related to toys, set the flag according to the definition and document borderline cases such as decorations or collector items with a justification.
Set up codes B1 to B10 with the German wording from Annex V, parameters and further languages; map Part A as fields for age, weight, abilities and supervision.
Convert warnings from long texts and supplier data into codes, mark discrepancies and resolve them using the packaging or the manufacturer.
Introduce the mandatory field check before publishing, set up the work list for purchasing and prove with faulty test items that the rules hold them back.
Feed the warning box at the buy button, the age filter, quick buy and feeds from the same codes; create the product passport fields but do not display them yet.
The effort rarely lies in the technology. It lies in the existing data: warnings buried in a thousand long texts and age limits that exist only as a word in the item name. Once you convert this stock into codes and fields, you have a data flow in which a new item without an age limit does not go online, and a foundation on which the product passport from 2030 is one more field and not a new project. How we connect merchandise management and shop for mandatory data like this is described on the page on ERP and inventory integration; you already know the system behind such mandatory details from the article on energy labels and EPREL.
Related Articles
Energy label and EPREL: required data from ERP to the shop
Energy label and product information sheet in the online store: which fields belong in the item master, how the EPREL number reaches every channel and how cut-over works.
Food Labelling Data from the ERP in Your Storefront
Ingredients, allergens and nutrition come from the item master, shelf life and lot number from the batch: how both mandatory data sets reach the shop.
Hazardous Goods Data from the ERP into the Shop
Transferring hazard fields from section 14 of the safety data sheet into the shop: field list, quantity totals in the cart, labelling in the offer and handover to the shipping interface.