What the solution is
JTL-Shop is one half of a German ecosystem. The other half is JTL-Wawi, an inventory and order management system that most JTL stores use, and which is the real reason JTL is strong among German mid-sized storefronts.
That creates a particular situation when Business Central enters the picture. JTL-Wawi and Business Central overlap: both want to be the place where items, stock and orders live. Before choosing a connector you therefore have to decide which of the two systems owns what, and that is a larger decision than the integration itself.
The integration to Business Central is a connector from ZahlenGrafik, a small German house. We have not been able to find technical documentation, a version history or a named reference customer, and the solution therefore carries low confidence in our research.
How the integration works
We cannot describe it, and we will not guess. The directions, the interval and the error handling stand as not stated in the table below.
What can be said with certainty is that there are three systems to keep track of if JTL-Wawi stays in the setup: the storefront, the inventory system and the ERP. Every transition between them is a place where data can disagree, and every transition needs an owner. That is the most important risk in the solution, and it is structural rather than technical.
If you instead let Business Central replace JTL-Wawi, the picture becomes simpler, but then you are using a storefront built to work with a system you have taken out. That can be done, and it is done, but it should be a deliberate decision with a name attached to whoever made it.
Prices, discounts and agreements
JTL-Shop has customer groups with their own prices, and the pricing logic normally lives in JTL-Wawi or in the storefront. We have found no documentation that agreed prices are fetched from Business Central.
The solution therefore carries the label for logic set up in two places, and in practice it can become three places if JTL-Wawi also holds prices. That is worth drawing on a piece of paper before going further.
For German consumer selling with one price list it is of no practical significance. For business selling with agreed prices it is the decisive limitation.
The order and the finance function
The purpose of the connector is getting orders and financial data into Business Central. Whether that happens directly from the storefront or through JTL-Wawi is a central part of what has to be settled.
VAT is decided by the storefront, and JTL-Shop, like Gambio, is built for German rules on price display and right of withdrawal. That is a real strength in the German market.
Reconciling the payment settlement is a separate job, and with three systems in the chain it does not get simpler.
Who the solution fits
The solution can fit a German company already running JTL-Shop and JTL-Wawi that has been given Business Central as its ERP and now needs the pieces to line up. That is a common situation, and the connector solves a concrete problem.
It can also fit if JTL-Shop was chosen for marketing reasons and a clear agreement exists on which system owns what.
The solution does not fit if you are choosing from scratch. If you pick a storefront and an ERP integration at the same time, there are solutions in the catalogue where the two are designed together and where there is no third system in the middle. dynamic commerce and Shopware with Ecomwise are the closest comparisons in the same market.
What to settle before you decide
Settle the JTL-Wawi question first. Does the inventory system stay in the setup, or does Business Central take over its tasks? That is the decision everything else hangs on, and it cannot be deferred to the implementation.
Then ask for a technical description of the connector, a version history and a named reference customer. Without those we cannot assess the solution, and neither can you.
Our large scenario stands as not served. Three companies and eight countries is not what this combination is built for.