ERP with JTL Integration

JTL-Wawi is the most widely deployed e-commerce ERP in the German SMB segment, with a long tail of agencies, hosting partners and add-on developers around it. Hilden-based JTL Software has built a stack that covers warehouse management (JTL-WMS, JTL-WMS-mobile), shop frontend (JTL-Shop), marketplace listings (JTL-eazyAuction) and point-of-sale (JTL-POS). The integration question therefore splits into two: within the JTL stack itself, and between JTL-Wawi and adjacent systems. This page describes both, with a focus on what to verify when JTL becomes the operational backbone of a German e-commerce business.

JTL-Wawi as the ERP core

JTL-Wawi is a Windows-client application backed by a Microsoft SQL Server database, with WAWI-Worker services handling asynchronous flows. The architecture is decidedly on-premise: the SQL Server typically runs on the customer's server or in a JTL-hosting partner's data centre, and the client connects directly. JTL has been adding cloud and web-client capabilities incrementally, but the core deployment model has shaped which integrations are easiest. Native interfaces include comprehensive coverage of JTL-Shop, JTL-WMS, JTL-eazyAuction (Amazon, eBay, Kaufland, Otto), DATEV (mature, several format versions), DPD, GLS, DHL and a long list of payment providers. Adjacent ERPs (Sage 100, Microsoft Dynamics 365) are integrated by partner connectors rather than by JTL natively.

JTL-Shop and JTL-WMS

JTL-Shop is a PHP-based e-commerce platform tightly coupled to JTL-Wawi via a shop-sync mechanism. Master data (products, prices, stock, customer groups) is pushed from Wawi to Shop on a configurable schedule; orders flow back from Shop to Wawi for picking, packing and invoicing. The coupling is strong by design and is a competitive advantage in the JTL stack, but it also constrains some customisations: shop features that diverge from Wawi data structures require careful design or a separate PIM layer. JTL-WMS extends the picture into the warehouse with mobile scanning (JTL-WMS-mobile on Android handheld terminals), pick paths, batch management and serial numbers. For Mid-Market e-commerce sellers in the EUR 5-30 million revenue band, the JTL-Wawi-Shop-WMS triplet is typically the lowest-friction option in the DACH market.

JTL-eazyAuction for marketplaces

JTL-eazyAuction is the marketplace-listing module within the JTL stack. It handles listing creation, attribute mapping, repricing rules and order ingestion for Amazon (SP-API), eBay, Kaufland Marketplace, Otto Market (the German legacy Otto-EDI flows for parts of the catalogue), Idealo and several smaller platforms. eazyAuction is licensed separately from JTL-Wawi and priced on a per-marketplace or bundled basis. For sellers operating multi-marketplace at scale, the alternative is to keep JTL-Wawi as the ERP and use specialist middleware such as Tradebyte, ChannelEngine or Channable for the marketplace layer; this is sometimes preferred for richer attribute handling and faster onboarding of new marketplaces, at the cost of an additional subscription.

DATEV, KassenSichV and OSS in the JTL stack

JTL-Wawi ships a mature native DATEV interface covering vouchers, accounts, fixed assets and master data; format versions are kept current. For multi-channel sellers using JTL-POS, the KassenSichV (Kassensicherungsverordnung) requirement for a certified technical security element (TSE) is satisfied by JTL-POS's integrated TSE support, with cloud TSE options from fiskaly and Epson hardware TSE as alternatives. OSS reporting is supported by tagging transactions in JTL-Wawi by country-of-consumption and exporting the consolidated dataset to DATEV for the quarterly return filed via the German Federal Central Tax Office (BZSt). The Verfahrensdokumentation required under GoBD is well-templated by the JTL partner ecosystem — several JTL-Servicepartner offer a starter document that customers complete to match their own configuration.

Frequently Asked Questions

Is JTL-Wawi appropriate for a EUR 30 million-plus e-commerce business?

It can be, but the architecture becomes more demanding. At higher volumes the SQL Server sizing, the WAWI-Worker concurrency model and the on-premise client deployment all need attention; some sellers in this band move to JTL-Wawi on dedicated hosting with a JTL-Servicepartner managing the database. Above roughly EUR 50 million, the case for upper-Mittelstand ERPs (Microsoft Dynamics 365 Business Central, weclapp, NetSuite, Sage 100) with specialist e-commerce middleware grows.

Can JTL-Wawi run in parallel with another ERP?

Yes, in a common pattern where JTL-Wawi runs the e-commerce front-end operations (shop sync, marketplace listings, fulfilment) and an upper-tier ERP runs finance and group consolidation. The two are reconciled through nightly or hourly synchronisation, with JTL-Wawi typically authoritative for product, stock and order data and the parent ERP authoritative for financials. This is operationally workable but introduces a clear boundary that must be designed rather than left to ad-hoc behaviour.

Which marketplaces does JTL-eazyAuction cover?

Amazon (SP-API), eBay, Kaufland Marketplace, Otto Market, Idealo, Real (where still relevant) and a number of smaller German and European platforms. The Otto-EDI legacy flow for part of the Otto catalogue is supported, although newer Otto Market API flows are increasingly the primary path. The exact marketplace coverage and the depth of attribute mapping should be verified against the actual catalogue and target marketplaces.

Is JTL-Wawi a SaaS application?

No, not in the strict sense. The core JTL-Wawi client is a Windows application, and the SQL Server backend can be hosted locally or in a partner data centre. JTL has been adding web and cloud components incrementally — JTL-Wawi-Cloud, JTL-Connect and Shop 5 features — but customers should expect a hybrid architecture rather than a pure browser-based SaaS experience for the foreseeable future.