Maintaining product data in JTL-Wawi: a practical workflow

JTL-Wawi will hold whatever you put into it. The question that decides how much work product maintenance is: what shape the data has before it gets there.

Jakob Feinböck, Gründer von ProductbayJuly 24, 20266 min read
☝️Key takeaways
  • The bottleneck is usually the inbound supplier data, not JTL-Wawi itself.
  • Define a canonical attribute set per product group and map supplier naming onto it.
  • Make completeness visible and fill gaps systematically instead of product by product.
  • A PIM layer pays off when many supplier formats meet several channels.

JTL-Wawi is a capable system, and it will faithfully store whatever product data you give it. That's precisely why the quality of what you put in decides how much work maintenance turns out to be. For multi-brand retailers, the difficulty is rarely the software — it's that forty suppliers deliver forty different versions of the same kind of information.

Where the time actually goes

Ask a team where the hours disappear and the answer is usually not “entering products”. It's the work before that: reformatting a supplier file, figuring out which column means what, researching the three attributes the supplier didn't send, resizing images, and writing a description because the supplied one is a single sentence.

A workflow that scales

  1. Define canonical attributes per product group. Decide once what a product in each group must have — and name it consistently.
  2. Map every supplier onto that set. Supplier column “Farbe”, “colour” and “Color-Code” all point to your one colour attribute. Store the mapping so it applies to every future delivery.
  3. Make completeness visible. You can't fix what you can't see. Knowing that 40% of a group is missing a mandatory attribute turns a vague problem into a task.
  4. Fill gaps systematically. Handle a whole product group at once rather than product by product — AI enrichment can generate missing attributes, descriptions and translations, with a review step before anything is applied.
  5. Publish per channel. Each channel gets what it needs from the same maintained record.

When JTL-Wawi alone is enough

If a handful of suppliers deliver consistently and you sell on one or two channels, this workflow can live inside your existing setup with some discipline. It's worth saying plainly: not every retailer needs another system.

When to add a PIM layer

The calculation changes when many supplier formats meet several channels and manual enrichment is consuming hours every week. At that point the work is product content production, and a PIM automates the consolidation, normalization and enrichment in front of JTL-Wawi — which keeps doing merchandise management. If you want the deeper comparison, see best PIM for JTL.

Frequently Asked Questions

Stop reformatting supplier files

Book a demo — we'll take one of your supplier files and show the consolidated result.

Get started