Operations & WaWi · 9 min
JTL-Wawi Shopify Integration 2026: Connector vs. Custom
JTL-Wawi + Shopify in 2026: what the standard JTL-Shopify-Connector covers, where it breaks (B2B prices, multi-warehouse, edge cases), and when custom middleware is cheaper.
JTL + Shopify Is The Default DACH Stack — And It Has Specific Limits
For stores with anything beyond simple flows, the standard JTL-Shopify-Connector hits limits that are well-known inside the JTL community but rarely surface until a project is mid-rollout. This article maps where the connector covers you, where the published add-ons help, and where the realistic answer is a piece of custom middleware that sits between the two systems and handles the specific edge case your business runs on.
What The Standard JTL-Shopify-Connector Does
- Article master data — products, variants, descriptions, images, categories, base prices.
- Stock levels — inventory per SKU, syncing on a scheduled interval (not real-time).
- Orders — orders flow from Shopify into JTL-Wawi for picking, packing, and invoicing.
- Customers — customer master data, with the caveats below.
- Basic price lists — catalog price; one default price per item.
- Order status — once JTL ships, status and tracking flow back to Shopify.
For a single-warehouse, mostly-B2C, single-price-list operation, this covers ~80% of the operational work. The connector is well-documented inside the JTL ecosystem and is the right answer for most mid-size DACH stores. The 20% gap is what the rest of this article is about.
Where The Connector Breaks Down
B2B customer-specific pricing. JTL-Wawi handles customer price tiers natively in the back office. The standard Shopify connector does not push those per-customer prices into Shopify B2B catalogs at scale. Stores with more than ~20 negotiated B2B price lists usually end up either maintaining catalogs manually in Shopify or building a custom price-sync layer.
Multi-warehouse stock allocation. JTL handles multi-warehouse fulfillment well. Shopify's locations work too. But the routing logic — "send this order from Warehouse A if SKU is in stock there, otherwise Warehouse B, with these regional priorities" — is rarely covered cleanly by stock-sync alone. The connector typically syncs aggregate stock, not per-location.
Sammelrechnung / collective invoicing for B2B. JTL-Wawi can generate Sammelrechnungen natively. But coordinating which Shopify orders go into which Sammelrechnung, when to close the period, and how to feed the resulting invoice back to the customer is operational glue the connector doesn't ship.
Variant attribute mapping. JTL's Merkmale (custom variant attributes) don't map 1:1 to Shopify's metafields without explicit configuration. For stores with rich attribute taxonomies (fashion, technical equipment), this becomes a maintenance burden.
Real-time stock for high-velocity SKUs. Scheduled sync (typically every few minutes) is fine for most stores. Stores selling out fast SKUs across Shopify + a physical store + a marketplace simultaneously hit oversells that scheduled sync can't prevent.
Custom workflows tied to invoicing or compliance. The B2B e-invoicing rules taking effect 2027 require XRechnung/ZUGFeRD output. JTL handles the format generation, but the trigger logic (which Shopify order needs structured output and which doesn't) sits at the boundary the connector doesn't natively own.
The Three Paths When The Connector Isn't Enough
1. JTL-Connector + paid add-ons / partner connectors. A small ecosystem of JTL-Servicepartner connectors (e.g. for B2B price lists, multi-warehouse logic) extends the standard. Lower risk, but you stack vendors and add monthly fees, and the add-ons rarely cover the exact edge case your operation has.
2. Move the workflow out of Shopify into JTL. Issue invoices in JTL (not Shopify), handle B2B portal logic in JTL-Shop instead of Shopify, etc. Works for stores where Shopify is essentially a B2C-only front end. Doesn't work when Shopify B2B is the strategic surface — you're back to running two storefronts.
3. Custom middleware between JTL and Shopify. A piece of code that sits between the two systems and handles the specific transformations your business needs: customer-specific price sync, per-location stock, Sammelrechnung coordination, structured-invoice triggering. Fixed-price custom development, source code yours, no per-order fees afterwards.
The right path depends on which limits you hit. For one or two narrow gaps, partner connectors are usually right. For three or more, or a single deeply business-specific gap, custom middleware pays back quickly.
What Custom JTL-Shopify Middleware Looks Like
Customer-specific B2B price sync. Read price lists from JTL-Wawi, push them into Shopify B2B catalogs (or as customer-tagged price overrides), keep them in sync as JTL updates. Often the single biggest unlock for DACH-Großhandel stores.
Per-location stock with routing logic. Pull stock per JTL warehouse, expose it in Shopify per location, and apply order-routing rules (regional priority, fallback warehouse). Solves the oversell problem and the "ship from nearest warehouse" requirement together.
Structured-invoice trigger. Detect which Shopify orders need XRechnung/ZUGFeRD output (B2B with German recipient, valid USt-IdNr), pass the right metadata to JTL so JTL generates the right structured format, and write the result back to the order record for the customer. Bridges the Wachstumschancengesetz implementation cleanly.
Sammelrechnung orchestration. Tag and group Shopify orders into period buckets per B2B customer, trigger Sammelrechnung generation in JTL at period close, and feed the resulting invoice (with archival) back to the customer.
Variant/Merkmal mapping. Explicit mapping layer between JTL Merkmale and Shopify metafields, with bulk-import flows so the attribute taxonomy doesn't drift between the two systems.
None of these are a full JTL replacement or a Shopify rebuild — they're surgical pieces of glue that handle the specific operational reality the off-the-shelf connector doesn't.
Cost Model: When Custom Middleware Pays Back
Stack approach (JTL connector + 2–3 partner add-ons + manual operations): typically €350–€900/month in connector and partner-app fees, plus 5–15 hours/month of manual back-office work for cases the connectors don't handle. Annualised including labour: €8K–€20K/year.
Custom middleware for the same scope (price sync + multi-warehouse + structured-invoice trigger + Sammelrechnung): typically €12K–€28K as a fixed-price build. Hosting and minor maintenance afterwards: €60–€180/month. Break-even against the stack approach lands inside 18–24 months, and from year two onward the savings compound because connector add-ons keep adding fees and the manual hours don't go away.
The decision is not really about technology — it's about how operationally critical the specific gap is. If your team is patching the same operational pain weekly, the middleware is the right call. If the connector covers you with one or two manual workarounds per month, the stack is fine. Most stores discover which they are within six months of running JTL + Shopify at real volume.
FAQ
Frequently Asked Questions
What does the standard JTL-Shopify-Connector cover?+
Article master data, variants, base prices, stock levels (aggregate, scheduled sync), orders from Shopify into JTL-Wawi, customer master data, and order-status updates back to Shopify. It's the right answer for most mid-size DACH stores with a single warehouse and a single price list. It doesn't natively cover customer-specific B2B pricing at scale, per-location stock routing, Sammelrechnungen, or structured-invoice triggers.
When do I need custom JTL-Shopify middleware instead of the standard connector?+
When you hit three or more operational gaps the connector doesn't cover, or one deeply business-specific gap that you're patching manually every week. Common triggers: 50+ negotiated B2B price lists, multi-warehouse fulfillment with routing rules, regular Sammelrechnungen, or the structured B2B e-invoicing requirements taking effect 2027.
Can JTL-Wawi handle the B2B e-invoicing (XRechnung/ZUGFeRD) requirement?+
Yes. JTL-Wawi can generate XRechnung and ZUGFeRD-compliant invoices natively. The challenge is the trigger logic — knowing which Shopify orders require structured output and feeding the right metadata into JTL. That trigger sits at the Shopify–JTL boundary and is one of the most common reasons custom middleware gets built for the 2027 deadline.
How much does a custom JTL-Shopify integration cost?+
A typical custom middleware scope (price sync + per-location stock + structured-invoice trigger + Sammelrechnung) sits in the €12K–€28K range as a fixed-price build, with €60–€180/month for hosting and maintenance afterwards. For stores at 1,500+ orders/month with active operational gaps, the break-even against connector add-ons and manual hours is typically inside 18–24 months.
Can I do JTL-Wawi + Shopify without any connector at all?+
Technically yes — both systems have APIs. Operationally no, unless you have very small order volume or a developer on staff: manual order entry into JTL doesn't scale past a few orders per day, and stock drift between systems leads to oversells. The standard JTL-Shopify-Connector is the default starting point for any real volume; custom middleware extends it rather than replaces it.