Shopify ERP Integration for Brands Selling in DACH

Selling in several countries multiplies the data an integration has to carry. Each market can have its own price list, its own tax rate and its own currency, while stock often sits in one warehouse. The integration has to deliver the right price to the right market and book every order once.

The operator of the official CR7 online stores ran a proprietary ERP and warehouse system and had no shop system of its own. We built mycr7.eu and mycr7.ch on Shopify Plus and connected the client's system through a custom integration.

Switzerland, as a non-EU country, has separate price lists, tax rates and a checkout in CHF. The MYCR7 case study reports go-live after 6 weeks and revenue 120% above the earlier level from retail and marketplaces.

Gusti Leder sells in DACH, France, the UK and further European markets. In Shopware the brand had no uniform ERP connection for warehouse, orders and returns. Since the migration to Shopify Plus, the ERP exchanges inventory, orders and returns with the store through a REST API. The Gusti Leder case study reports a 45% higher conversion rate and more than 1,000 migrated products. Market setup is described on the Shopify internationalisation page.

When you also sell through marketplaces, several channels draw on the same stock. Every order has to arrive in the ERP exactly once, and every channel has to see the same stock level.

Kanela, a Swiss online drugstore, moved from PrestaShop to Shopify Plus. The store now connects more than 40,000 products with the ERP Pixi, with supplier data and with the marketplaces Zur Rose, Galaxus and Manor. Each marketplace has separate processes for data, orders, shipping and cancellations, with a unique channel source and protection against duplicates. Prices and stock are updated every 15 minutes.

A dedicated application combines Kanela's own stock with availability at Galexis and Avosana and automatically stops unusually large stock changes. The details are in the Kanela case study.

German merchants often run systems that are little known outside the region, such as JTL, weclapp, Xentral and Plentymarkets, with DATEV for accounting. A brand that acquires or partners with a German business meets these systems sooner or later. We describe each one under integrations, including JTL-Wawi, weclapp, Xentral and DATEV.

BlumeIdeal, an online flower delivery service in the DACH region, worked with Shopware 5 and JTL-Worker Cloud. We migrated the store to Shopify Plus and built a date logic that combines calendar, cut-off times and availability from the inventory system, so customers only see delivery dates that are logistically possible.

The move ran without a cutover, the DNS switch took about 5 minutes, and all open orders and the order history were carried over. The BlumeIdeal case study reports a 33% higher conversion rate and a 29% higher average order value.

A Shopify ERP integration consists of four data flows. Products, prices and stock run from the ERP to the store. Orders run from the store to the ERP. Shipping status and tracking numbers run back into the order. Returns and credit notes close the loop. Each flow needs a trigger, a field mapping, a validation and a route for the error case.

Data ownership comes before technology. We define for each object which system is the owner. If two systems write the same field, one overwrites the values of the other, and the error only surfaces with the customer. We settle this together with your IT team, in writing, before the first interface is built.

If the integration needs an interface inside the Shopify admin, it is built in Shopify app development.

The old system stays when it manages product data well and only reaches its limits as a storefront. Hairshop Pro kept Plentymarkets as its PIM and placed Shopify Plus in front as the storefront. The interface synchronises product master data, inventory, prices, orders, fulfilment status and custom fields. The Hairshop Pro case study reports a 35% higher conversion rate.

Blankroast keeps product information in weclapp. Flavour profile, origin, roast level and further attributes are transferred into Shopify metafields, so the team does not maintain product data twice. The Blankroast case study describes this.

Interfaces fail in four places. Data ownership is not settled. Orders are created twice because a unique key is missing. Errors disappear because nobody is notified. Testing was done with ten products instead of the whole range.

That is why every data flow we build gets a key against duplicate processing, an error channel and a documented way to replay a single record. Development runs against a test environment with realistic data volumes. Before go-live we sign off the processes for order, partial delivery, cancellation and return one by one.

When the integration is part of a change of platform, legacy data belongs to the project. For Sirocco, more than 40,000 customer records with the complete order history were carried over from Magento, as the Sirocco case study describes. The Shopify migration page shows how a move runs. SAP has a page of its own on Shopify SAP integration.