Wawi mapping and the attributes' naming convention
Keep the battery data in JTL-Wawi; Produktpass takes it into the passports.
Produktpass helps you with the battery passport and the battery QR code under Regulation (EU) 2023/1542. The plugin's texts, templates and notes are not legal advice. You remain responsible for your duties and for the accuracy of your data. For a binding answer on your own case, ask a lawyer.
The naming convention
Every field of a passport has a key, such as capacity_ah. You name the attributes in JTL-Wawi after it:
- Function attribute
dpp_<key>, for exampledpp_capacity_ah: one value for all languages. Upper and lower case do not count. - Text attribute "DPP <field name>" with the field's German or English name or its key, for example "DPP Capacity": texts with their translations per language, all other fields with one value.
dpp_energy_kwh(ordpp_energy_wh) is the battery's energy. It fills no field but, with the category, chooses the template: an industrial battery above 2 kWh needs the battery passport.
Documents (such as the declaration of conformity) and the details of individual batteries do not come from JTL-Wawi: you upload documents in the passport editor, and you create batteries under "QR codes and labels" or with the CSV import.
| Name in JTL-Wawi | Content | Kind |
|---|---|---|
dpp_battery_category | Category of the battery: portable, lmt, sli, industrial or ev (or the label, such as "Portable battery") | Function attribute |
dpp_energy_kwh | Energy in kWh; chooses the template (industrial battery above 2 kWh: battery passport), fills no field | Function attribute |
dpp_chemistry | Chemistry, for example li_ion, nimh, lead_acid (or "Li-ion") | Function attribute |
dpp_rechargeable | rechargeable or non_rechargeable | Function attribute |
dpp_capacity_ah | Capacity in Ah, for example 3.4 | Function attribute |
dpp_weight_kg | Weight in kg (otherwise the product's weight, if you create a rule for it) | Function attribute |
dpp_model_identifier | Model identifier | Function attribute |
dpp_place_of_manufacture | Place of manufacture | Function attribute |
dpp_date_of_manufacture | Month of manufacture, for example 2026-07 | Function attribute |
DPP Role of end-users in contributing to waste prevention | one of the six waste-information texts (also "DPP waste_prevention"), text per language | Text attribute per language |
DPP hazardous_substances | hazardous substances other than mercury, cadmium or lead, text per language | Text attribute per language |
The keys of all fields are in the header row of the CSV template under "Import".
"Map automatically"
Under "Wawi mapping", "Map automatically" creates a rule for every attribute of your shop that follows the naming convention and has no rule yet, with the transform that the field needs. The products with these attributes are queued for the mapping.
Rules of your own
If your attributes have other names, create a rule at the bottom of the page:
- Field of the passport and kind of source: function attribute, text attribute, characteristic or a field of the product (GTIN, product number, manufacturer, manufacturer number, weight).
- Name in JTL-Wawi and the languages that are taken over.
- Transform: none; a number with a number format (decimal separator and a unit after the number, such as "kWh"); a date; or a list of values that maps your values to the field's choices (the page lists values not yet mapped to a choice).
- Priority: if several rules fill the same field, the first with a value counts (the lower number first).
A number takes thousands separators only between groups of three and only of one kind; an ambiguous value such as "2.000" without a unit is not taken and is named as a problem.
When the mapping runs
- Every sync with JTL-Wawi queues the changed products; that costs the sync only one statement per product.
- The shop's cron maps up to 500 queued products at most every 15 minutes, those synced from JTL-Wawi first.
- Every night it queues the products whose data in JTL-Wawi changed since the last mapping.
- If the cron is not running, "Overview" and "Wawi mapping" show a note and map up to 500 products when they open; "Map up to 500 waiting products now" does it at any time.
- The mapping fills drafts and the unpublished changes of published passports; it publishes only if you switched on "Publish automatically" under "Settings".
- A variant gets only what differs from its parent product.
Fields changed by hand
If you change a field in the passport editor, it keeps your value even when JTL-Wawi delivers another. "Wawi mapping" lists such fields with the value from JTL-Wawi; "Take the Wawi value" takes it, and the field follows JTL-Wawi again. If JTL-Wawi delivers the same value as yours, the field also follows JTL-Wawi again.
Values that do not fit
A value that does not fit (a number that is none, a value without a choice, a text that is not valid UTF-8) leaves its field open; the other values are taken. "Overview" and "Wawi mapping" name the product with the problem. If a whole run ends with a database error, no product is marked for it; after three such runs in a row, "Wawi mapping" shows that the mapping is paused, with the error, and it tries again at the next run.
Waste-information texts from JTL-Wawi count as your own texts and as confirmed if they differ from the supplied draft.
Attributes on the product page
With "Hide mapped text attributes on the product page" (switched on), NOVA no longer shows the text attributes that fill passports in the product details; the information is on the passport page.