---
title: "How far can you customize JTL-Wawi? | Nucez Software"
url: https://nucez.com/en/blog/jtl-wawi-anpassen-grenzen
lang: en
description: "Plugins, direct database access, custom integrations: how far you can really customize JTL-Wawi when the standard isn't enough."
alternate_de: https://nucez.com/blog/jtl-wawi-anpassen-grenzen
---

# How far can you customize JTL-Wawi?

By [Bjarne Fomferra](https://nucez.com/en/about) · 10.08.2026

JTL-Wawi and JTL-Shop cover a surprising amount. For most businesses the standard is enough for a long time. But at some point almost everyone says: "There's this one thing it can't do." That's exactly where it gets interesting.

## [Level one: plugins](https://nucez.com/en/blog/jtl-plugins-fallstricke)

The first step is usually a plugin. For JTL-Shop and for the Wawi you can add features without breaking anything in the core. New fields, custom workflows, additional outputs. Much of what's missing in the standard can be solved cleanly as a plugin. What to watch out for so a plugin doesn't break with every update is covered in [three pitfalls with JTL plugins](https://nucez.com/en/blog/jtl-plugins-fallstricke).

## [Level two: straight to the database](https://nucez.com/en/blog/jtl-plugins-fallstricke)

When a plugin isn't enough, you go deeper. JTL stores its data in a SQL database, and you can have your own software work with it directly: read, write, link. That's powerful, but also delicate. If you go at it without understanding the structure, you do more harm than good. With the necessary respect for the database, you can build things with it that the standard never could.

## [Level three: custom integrations](https://nucez.com/en/blog/jtl-plugins-fallstricke)

The top tier is custom integrations that connect the Wawi to the outside world. Shop, marketplaces, accounting, shipping, or your own cloud modules. I described one example here: [a module that brings quotes straight from the shop into the Wawi](https://nucez.com/en/blog/jtl-wawi-angebote-aus-dem-shop), as if an employee had created them by hand.

## [The principle](https://nucez.com/en/blog/jtl-plugins-fallstricke)

For all of this I follow one simple rule: better to build the missing feature than to bend your process to the software. Too often businesses adapt their workflows to whatever the program happens to be able to do. It should be the other way around. The software has to fit your business, not the other way around.

## [What you can spare yourself](https://nucez.com/en/blog/jtl-plugins-fallstricke)

What I see again and again: manual work that counts as normal because it's always been done that way. Typing data from one system into the next, exports that someone kicks off by hand every morning. Almost all of that can be eliminated. The only question is whether it pays off, and I'll run the numbers honestly for you beforehand.

## [Conclusion](https://nucez.com/en/blog/jtl-plugins-fallstricke)

JTL-Wawi can be customized further in many places than most people think. If the standard hits a limit for you, that doesn't have to be the end.

Take a look at my [work in the JTL space](https://nucez.com/en/services/jtl) or [write to me](https://nucez.com/en/contact), and we'll figure out what's possible for you.

[Back to the blog](https://nucez.com/en/blog)

Author Bjarne Fomferra IT specialist for application development, owner of Nucez Software

In short

Plugins, direct database access, custom integrations: how far you can really customize JTL-Wawi when the standard isn't enough.

Questions about your project?

Send me a short message, I usually reply within one business day.

---

Nucez Software, Bjarne Fomferra, Enger (Germany). Contact: info@nucez.de, https://nucez.com/en/anfrage