Skip to content
PROWERB
Services
Industries
Cases
Lab & Software
Company
DENeeds Check →
Services
Industries
Cases
Lab & Software
Company
LanguageDEEN
Start Needs Check →
PROWERB — Elevating Brands

Marketing Operations Backbone since 1979. Promotional products, logistics, kitting and digital commerce. One partner with its own operations in Kleve.

Elevating Brands — since 1979.Kleve · Düsseldorf · Dortmund · Lüdinghausen
Services
Logistics & fulfillmentPromotional products & merchandiseDigital commerce & marketplaceEvents & campaignsKitting, textile & ESGTech & AI
Company
About usLocationsHow we workSustainabilityCareersContactInternationalPress & news
Resources
GuidesInsights archiveGlossaryDownloadsTools & calculatorsCosts & calculationCompare operating models
Contact
PROWERB, Huissener Str. 7–947533 Kleve+49 (0)2821 7218-0info@prowerb.de
© 1979–2026 Prowerb GmbHLegal notice (German)Privacy policy (German)Terms (German)BrandDEEN

All rights reserved. Subject to change. Text and images on this website have in part been created or edited using artificial intelligence.

  1. PROWERB
  2. Integrations

Shop systems

The shop and fulfilment belong together.

Whether Shopify, Magento, Shopware or JTL: PROWERB aligns the integration with your shop and agreed operations. Orders, products and updates follow a clear path.

Discuss the integration →Explore the details ↓

A common workflow behind different shops

  1. 1

    Align the catalogue

    Map products, variants and identifiers between shop and operations.

  2. 2

    Execute orders

    Receive released orders with recipients and shipping requirements.

  3. 3

    Connect the status

    Return stock and shipping information within the agreed scope.

Example workflow. Data scope, approvals and technical requirements are agreed with your team.

Platforms and their role

The platforms shown belong to the described workflow. We agree the exact scope, required access and responsibilities for your setup.

  • Magento

    B2B portals and custom shop logic

  • Shopify

    D2C and brand shops

  • JTL

    Commerce and inventory management

  • Shopware

    Connect an existing shop system

Exchange shop data that warehouse and customer service teams can use.

The platform and theme are only part of the planning. Fulfillment depends on item mapping, order status, shipping methods and the handling of changes. We review your existing shop and define the data it sends and receives. The service scope depends on whether you outsource logistics alone or also want us to manage the shop.

Example · Data handoff

Not every shop integration needs the same scope.

An existing shop needs to connect to warehouse and shipping without rebuilding the whole website. Define the necessary handovers: product mapping, orders, stock and status. Add further functions when their purpose and data source are clear.

  1. 1

    Assess the starting point

    Review the platform, extensions and available interfaces. Custom checkout fields may matter for shipping.

  2. 2

    Accept the essential workflow

    Test a typical order completely, including its return status. Add required exceptions explicitly rather than promising blanket integration.

  3. 3

    Support changes

    Establish checks for platform updates, new products and changed fields. Responsibility continues beyond the first successful import.

Systems

The shop systems we operate.

Direct integration or existing middleware: the route depends on version, extensions and data ownership. The systems below need different preparation; order handoff and responses are accepted together for each setup.

01Shopify Fulfillment →Shopify: map shop orders and variants to fulfillment and agree shipping and stock updates; shop operations on request.
02Magento Fulfillment →Magento/Adobe Commerce: review version, extensions, customer groups and custom order fields; connect directly or through existing middleware.
03ShopwareShopware: review shop and channel structure, variants and existing extensions; agree data paths and responses for the specific setup.
04JTL Integration →JTL: decide whether JTL-WaWi or CORE owns stock; map tenants, warehouse locations and shop channels unambiguously.
05System connectionOrder import, stock reconciliation and shipping status are agreed per data type. Direct integration, middleware or file transfer determines how often the information is updated.
06Shop operation →On request we take on shop operation: order handling, article maintenance, invoicing.
Onboarding

How we bring your integration into operation.

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.

  1. 01

    01 · Assessment

    Which shop system (Shopify, Magento, Shopware, JTL), which modules, which trading partners, which messages — we map the real system landscape.

  2. 02

    02 · Specification & mapping

    Field mapping for articles, stock and orders, clarification of direct connection or middleware.

  3. 03

    03 · Build & test

    Setup of converters or endpoints, test messages against your system, sign-off against real transactions.

  4. 04

    04 · Go-live

    Controlled first load, parallel operation until stable — no big bang without a way back.

  5. 05

    05 · Operation

    We run the interface in continuous operation: monitoring, exception handling, changes. One contact, not a ticket call center.

Own stack

Who owns data, approvals and enquiries.

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.

01Business clarificationA missing item mapping, incomplete address or different quantity goes to the named data owner. Operational approval follows clarification.
02Technical handlingAvailability, processing and responses are monitored within the agreed scope. PROWERB and your system partner investigate using the same transaction reference.
03Correction and resumptionBefore repeating a transfer, the processed state is checked. The operating agreement assigns correction, retransmission and confirmation of completion.
Evidence

A fan shop on Shopify — and behind it the full physical chain.

For a German heritage brewery, PROWERB operates the official fan shop: goods receipt, inventory, picking and dispatch behind a Shopify frontend — shop and fulfilment from one source.

Read on

There's more behind the shop than dispatch.

01Shopify Fulfillment →The depth: shop operation, warehouse and dispatch in one system.
02Magento Fulfillment →Integration, operation and migration for Adobe Commerce.
03REST, GraphQL & Webhook API →The open interface when your shop connects via API.
04Promotional-Products Fulfillment →The physical chain behind every shop.
FAQ

What to clarify before connecting the shop.

Which shop systems do you connect?

Shopify, Magento/Adobe Commerce, Shopware and JTL. We establish whether to use a direct interface or middleware based on your version and extensions. Other systems can connect through available interfaces or files.

Do you also operate the shop yourself?

Yes, as a managed service on request: order handling, article maintenance and invoicing.

How does stock get into the shop?

From the agreed source system. Data scope, reservations and update frequency are defined in the project. Event-driven updates and periodic reconciliation are different routes; a real-time warehouse booking alone does not guarantee an immediate shop update.

Migration from another system?

Yes. We take over master data and stock and run the move in a controlled way.

Briefing

Describe your shop.

Range, volume, system and planned campaigns — a first briefing needs no more. We answer with the chain behind it.

Start Needs Check →Your contact replies within 24 hours on business days.