Setup, integration, development and migration around JTL and the common shop platforms. Every service with a fixed price, a test run and one named contact.
The ERP is the centre. Items, customers, orders, invoices, stock, suppliers: everything comes together here. We set up JTL-Wawi from scratch or clean up an installation that has grown over years and where nobody knows anymore which workflow triggers what.
Then we stay on: apply updates, analyse errors, implement new requirements. You get a person who knows your installation, not a ticket number.
| Setup | Item master, variants, bills of material, clients, users and permissions, print templates, payment and shipping methods |
| Automation | Workflows for order release, invoice dispatch, dunning, supplier orders |
| Support | Updates, troubleshooting, changes on a time basis or with a service contract |
| Hosting | Advice on server, database and backup, move to new hardware |
| Starting point | ERP in use for 6 years, 40 workflows, three of them contradicting each other |
| Result | Workflows documented and reduced to 22, permissions per role, updates current |
| Duration | Typically 2 to 4 weeks for a clean-up, 1 to 2 weeks for a new setup |
From goods-in to the parcel on the dock: JTL-WMS runs bin locations, pick lists, packing desk and shipping. We design the warehouse layout so routes are short and stock is right, and set up the packing desk so the packer scans and prints without typing anything.
For fulfillment operators with several clients we make sure every client has its own items, senders and carrier accounts, cleanly separated.
| Warehouse layout | Zones, bin locations, pick strategies, replenishment, stocktaking |
| Packing desk | Scan flows, label printing, packaging logic, carriers |
| Clients | Separate items, senders, carrier accounts and reports per client |
| Hardware | Handheld scanners, label printers, scales, packing desk hardware |
The JTL-Connector links shop and ERP: items and stock go to the shop, orders and customers come into the ERP, tracking numbers go back. We are certified for every connector variant: Shopware, Shopify, WooCommerce, PrestaShop and custom development for systems without a ready-made connector.
Several shops on one ERP is the normal case, not the exception: separate price lists and currencies, one shared stock.
| Systems | Shopware 6, Shopify, WooCommerce, PrestaShop, JTL-Shop, Amazon and other marketplaces |
| Sync | Items, variants, images, categories, prices, stock, orders, customers, tracking numbers |
| Special cases | Custom fields, bundles, tiered prices, B2B price lists, multilingual content |
| Custom development | Connector for shop systems without a ready-made JTL integration |
Shopware 6 is the shop system we are most deeply certified for: Developer, Backend, Frontend, Template Designer, Solutions Architect, PaaS. We develop plugins and apps, customise themes and build interfaces to ERP, PIM and carriers.
If you are still on Shopware 5, you get a migration path with data transfer, theme rebuild and a test phase before the old shop is switched off.
| Plugins and apps | Custom functions in checkout, administration and storefront |
| Themes | Customisation or rebuild on the standard theme, responsive and fast |
| Interfaces | ERP, PIM, payment providers, carriers, newsletter systems |
| Migration | Shopware 5 to 6 with data transfer, SEO redirects and test phase |
| Starting point | Shopware 5 with 14 plugins, 5 of them without a successor for Shopware 6 |
| Result | Shopware 6 with 9 plugins, 3 of them custom built, all redirects in place |
| Duration | Typically 6 to 12 weeks depending on scope |
A system change rarely fails on technology and often on data: duplicate customers, items without a category, orders with line items that no longer exist. We export, clean, map and import into a test environment.
Then we count. Every table in the source against every table in the target. Only when the difference is zero do we switch over. The old system keeps running until the last minute.
| Sources | Other ERP systems, shop systems, spreadsheets, legacy systems with database access |
| Scope | Items, variants, images, customers, addresses, orders, invoices, history |
| Control | Count check per table, samples per record type, sign-off by you |
| Cut-over | Freeze, final import, switch, follow-up with standby |
Retail store and online shop share one stock: JTL-POS reports every sale to the ERP, the ERP supplies items and prices to the till. We set up tills, receipt printers and payment terminals and connect them to the ERP.
On top we build interfaces and exports for everything needed outside JTL: accounting, reporting, third-party systems. With permissions that allow only what is needed.
| POS | JTL-POS on tablet or till PC, receipt printer, cash drawer, payment terminal |
| Sync | Items, prices, stock, customers, vouchers between till and ERP |
| Exports | Accounting, reporting, reports in your format |
| Third-party systems | Integration via API or database, read-only wherever possible |
| Starting point | Two stores with their own till software, stock reconciled in Excel |
| Result | JTL-POS in both stores, one stock shared with the online shop, automatic day-end |
| Duration | Typically 2 to 3 weeks per store including training |