Magento JTL-Wawi: Connect Merchandise Management and Shop Without Double Maintenance

JTL-Wawi is the merchandise management system of the vendor JTL-Software. It forms the core of many online retail businesses: article master, stock, customer master and orders lie here, and shipping and invoices are processed from here. Sales channels such as shops and marketplaces are connected to the Wawi and report orders to it.

For Magento JTL-Wawi that means: the shop becomes a sales channel of the Wawi. Articles, prices and stock come from the Wawi into the shop, orders and new customers go from the shop into the Wawi, and shipping and invoice status come back. The advantage is obvious: your employees keep working in the familiar Wawi and do not have to enter orders anew.

As with every ERP the implementation depends on version, operation and customizations. Some businesses use many additional functions and own processes in the Wawi, others get by with the standard. Magento JTL-Wawi therefore always begins with the question which version you use, how it is operated and which processes must not change.

Many businesses have set up automatic processes in the Wawi, for example rules that release orders after payment receipt or prepare shipping labels. These processes are part of your way of working, and the integration must adapt to them: an order from the shop may trigger them only when all data is complete. We clarify exactly such peculiarities in the inventory.

Which data flows in Magento JTL-Wawi you define with us in the inventory. Typically there are five areas.

Not every Magento JTL-Wawi project needs all five areas. Often it begins with orders and stock and later grows by article maintenance and invoices. This way you see results quickly and can use the budget in stages.

The table shows a typical pattern. In your business it may differ, and that is exactly what we clarify in the inventory.

With Magento JTL-Wawi a clear rule on data ownership prevents most disputes. Whatever can be changed in both systems leads to contradictions sooner or later. That is why we define exactly one leading system per type of data and describe the rule for the conflict case. Especially with variants, units and tax rates an assignment table that the department and the developers review together is worthwhile.

For Magento JTL-Wawi, JTL provides a programming interface for the Wawi that, according to the developer documentation of the vendor, is described according to the OpenAPI standard. It runs as a local service, and an application registers beforehand and receives an access key. There is also a cloud variant that forwards requests to the Wawi and handles the login through OAuth 2.0. In this interface a shop is kept as its own sales channel.

JTL continues to develop these interfaces. Which version you can use, which license terms apply and which functions are already available in your Wawi version we therefore check before the quote and tell you openly if something is not yet possible or only to a limited extent. For data that can be exchanged as a table, a file exchange with the import and export tool of the Wawi can also make sense.

We avoid direct access to the database of the Wawi wherever possible. It bypasses the rules of the software and can break on updates. If an interface is not enough, we first look for an official way before we build a makeshift.

For the connection of JTL-Wawi and Magento there are add-on products from third-party vendors. Whether one of them fits your process we check honestly before a decision. If an existing product covers your requirements, it is often the more economical choice, and we will tell you so. With every ready-made product pay attention to how it is maintained, what happens on updates of Magento or the Wawi and how far it can be adapted.

An individual development for Magento JTL-Wawi pays off if your processes deviate from the standard: special price rules, several warehouses, bundles and sets, own attributes or processes that a ready-made product does not know. It is more expensive at the start but fits exactly. Include the care as well: a ready-made product saves development time but causes license and update costs that count over the years, and an individual development needs someone who looks after it.

A middleware pays off if more than two systems are connected, for example shop, Wawi, marketplace connection and shipping provider. The decision aid is in the guide to ERP integration.

On the Magento side we build the integration as its own module according to the standards of the system, without interventions in the core. The module uses the interfaces and queues of Magento so that transfers run in the background and the shop does not become slower for visitors. Orders are placed in a queue on arrival and processed there until the ERP has confirmed them.

Prices by customer group, tier prices and several warehouses are mapped by Magento with its own functions that the integration fills. Where possible we use these standard functions instead of inventing our own tables. That keeps the shop update-capable and lets other developers join in later.

In the admin you see what was transferred: a log shows date, record and result, with a filter for errors. For the peculiarities of JTL-Wawi we add settings in the admin, for example assignments of payment methods, shipping methods and tax classes, so that changes need no development.

With JTL-Wawi multichannel often comes into play: if you also sell through marketplaces, stock must stay consistent across all channels. Magento JTL-Wawi is therefore built so that the shop is treated as one sales channel among several and makes no assumptions that disturb other channels.

We see these points again and again in projects. They can be planned if they are known early.

• Variants and attributes

  The structure of variants in the Wawi does not fit Magento one to one and needs a clean assignment.

• Several sales channels

  The stock is sold for marketplaces and shop at the same time, and overselling occurs.

• Unclear data ownership

  Prices or texts are changed in both systems and overwrite each other.

• Missing monitoring

  A failed transfer is noticed only after days because nobody looks at the log.

• Updates of the Wawi

  After a version change the integration no longer works because it was not tested.

• Special cases

  Partial deliveries, returns, credit notes and foreign orders are missing in the concept.

An integration connects two systems with business data, so clear rules apply. The exchange runs encrypted, credentials do not lie in the source code but in the protected configuration, and the integration receives only the rights it needs. Access belongs to a separate service account, never to a private account of a person.

When testing we work with test data or anonymized data as far as possible. As soon as developers get access to personal data, for example customer accounts or orders from JTL-Wawi, an agreement on commissioned data processing is needed. We clarify that before the start so that you are legally well set up.

The log of the integration contains what is necessary for operation but no credentials and no unnecessary personal data. Retention periods are defined with you. These notes are not legal advice, the concrete arrangement depends on your company.

We keep the start deliberately short so that you quickly know whether and how the integration is feasible.

The following constellations are examples from the practice of Magento JTL-Wawi projects, not statements about particular customers. The first is a merchant who has so far sold only through marketplaces and now builds an own shop. The Wawi remains the center, the shop becomes one more channel. At the center are the common stock and a clean assignment of the article numbers so that nothing is sold twice or not at all.

The second constellation is a merchant with many variants, for example sizes and colors. The challenge lies in the assignment of the variants and attributes between Wawi and Magento and in which texts and images are maintained where. We define early what stays in the Wawi and what arises in the shop.

The third constellation is a business that switches from another shop system to Magento and keeps the Wawi. Here the existing Wawi connection is the benchmark: what it achieves today the new shop should at least achieve. Part of the work is therefore the inventory of the old connection. How the switch itself runs is described on our page on migration.

An interface is not a one-off project but ongoing operation. After the start a log monitors every transfer: what was transferred when, what failed, what is repeated? Errors that cannot be fixed automatically are reported visibly so that nobody learns of them only through a customer complaint.

Updates change the situation. A Magento update, a new state at JTL-Wawi or a change of the vendor interface can affect the integration. Therefore the planning includes an agreement on how updates are tested and who approves them. Ongoing care can be regulated through a maintenance contract that covers monitoring, updates and error fixing.

Documentation is part of the delivery. You receive a description of the data flows, the assignments and the rules for special cases so that your team or another provider understands the integration and can continue it. Source code and access stay with you.

A flat figure for Magento JTL-Wawi would be unreliable because the effort depends on your constellation. It is determined by the number of data flows, the quality of the data in JTL-Wawi, the number of special cases with prices, warehouses and customers and the required timeliness. A data flow in one direction is built much faster than a synchronization in both directions with conflict rules.

We work with an open hourly rate of 30 euros net, without emergency surcharge. After the inventory you receive a written estimate that lists the data flows individually so that you can control scope and order yourself. For clearly defined packages a fixed price is also possible. All prices are on the page pricing.

Besides the development, include the running items: hosting, maintenance and, where applicable, licenses or fees for JTL-Wawi and for additional services. We show these items separately in the estimate so that you can compare quotes over several years.

An honest offer includes naming the limits. We do not sell a ready-made connector off the shelf but develop Magento JTL-Wawi project by project according to your processes. That means: we implement exactly what you need, but not in a day and not for a flat price that cannot be calculated beforehand.

We are a web agency in which fixed freelancers work together, all from home offices. We are not a large agency with a hundred employees and cannot take on every project at every time. We tell you early whether and when we have capacity. We name customers only with their consent, and in the first conversation we gladly talk about comparable constellations.

We give no legal advice. Questions about commissioned data processing, data protection and the license terms of JTL-Wawi you clarify with your legal adviser and the vendor. What is technically possible depends on version, operation and license of your system and is checked in the inventory.