JTL integration
PROWERB connects agreed JTL data with warehousing and fulfilment. Products, orders and updates have clear ownership across inventory management, shop and operations.
Products and order lines arrive with their unique references.
Operations checks stock and shipping requirements before processing.
Agreed status and stock information is returned with the correct references.
Example workflow. Data scope, approvals and technical requirements are agreed with your team.
The platforms shown belong to the described workflow. We agree the exact scope, required access and responsibilities for your setup.
Inventory management, shop and stock
An item may sell through several channels while its stock sits in the same warehouse. Before integration, we clarify tenants, warehouse locations, item identifiers and reservations. A test order is then followed from receipt to the shipping update. For ongoing operations, we agree who maintains master data and how discrepancies between systems are resolved.
A variant is offered through a shop and another channel at the same time. Order import, reservation and available quantity need to work together. Before connecting, define which system owns inventory and which updates the other channels need.
Map products, storage locations and channels. Physical inventory must not accidentally appear freely available more than once.
Check import through to stock effects and shipment through to status return. Explicitly include partial quantities.
Assign owners for new products, changed mappings and outstanding transfers. The integration remains part of everyday operation.
Whether JTL stays leading or connects to CORE — the chain behind it is the same.
These steps describe the integration project. In larger fulfillment takeovers it is part of the seven-phase introduction; around 14 weeks is a planning guide for that overall scope. An individual integration is scheduled according to its data, counterpart and acceptance tests.
Which JTL (WaWi, eazybusiness, JTL-Shop), which modules, which trading partners, which messages — we map the real system landscape.
Field mapping for articles, orders and stock, clarification of interface and sync direction.
Setup of converters or endpoints, test messages against your system, sign-off against real transactions.
Controlled first load, parallel operation until stable — no big bang without a way back.
We run the interface in continuous operation: monitoring, exception handling, changes. One contact, not a ticket call center.
PROWERB manages the agreed handoff into its operations. Your IT team or system partner owns changes in the source system. Before launch, we agree who handles each type of error and approves a corrected transmission.
Both possible. Either JTL stays the leading system with CORE as fulfilment behind it, or orders run directly into CORE.
Yes, as a managed service on request — order handling, article maintenance and invoicing.
We agree which system owns stock and reservations and which orders and status updates are transferred. Direction, update frequency and error handling are defined for your JTL setup and checked using test orders.
Yes. We take over master data and stock and run the move in a controlled way.
Range, volume, WaWi or shop setup — a first briefing needs no more.
