ERP with Shopify Interface

Shopify has displaced a substantial share of the German Mid-Market e-commerce platform footprint over recent years, particularly in direct-to-consumer brands, fashion, beauty and consumer electronics. Shopify Plus has extended the reach into upper Mid-Market and into B2B selling with the Shopify Plus B2B module. The ERP integration question is both common and consequential, because integration quality determines whether a merchant can scale on Shopify without the ERP becoming a bottleneck. This page describes the integration patterns, the API surface and the German tax handling that apply.

Shopify Admin API and GraphQL

The Shopify Admin API is the primary integration surface for ERP connectors. It exposes products, variants, inventory, orders, customers, fulfilments and refunds via both REST and GraphQL. Shopify has been progressively favouring GraphQL: bulk operations and recent capability extensions are GraphQL-first, with REST endpoints kept for backward compatibility. For ERP integration, mature connectors increasingly use GraphQL for bulk operations and REST for simpler per-record interactions. Authentication uses OAuth 2.0 with scoped access tokens; partners should renew their understanding of the API version each year because Shopify retires API versions on a published schedule.

Bulk import and inventory synchronisation

Shopify's bulk-operation framework handles catalogues of any practical size: a single bulk mutation can update tens of thousands of products or inventory levels asynchronously, with the result delivered via a webhook or polled status endpoint. Mature ERP-Shopify connectors use this framework for catalogue refresh, price updates and inventory sync, rather than per-record API calls which hit rate limits at higher volumes. Inventory synchronisation in Shopify is more sophisticated than it first appears because of the Locations model: a merchant with multiple physical or virtual locations (Shopify Fulfilment Network, dropship sources, retail stores) maintains stock by location, and the ERP integration must understand which location maps to which ERP warehouse. The salable-quantity calculation also accounts for committed stock against open orders.

Multi-store and Shopify Plus B2B

Shopify Plus offers up to ten storefronts under a single organisation, typically used for country-specific stores, brand splits or B2B-versus-B2C separation. The ERP integration must handle the multi-store case explicitly: one Shopify organisation maps to one ERP company structure, with country tax rates, currency, customer-group pricing and order routing differentiated per store. The Shopify Plus B2B module, matured substantially since 2023, introduces company accounts, payment terms, draft orders and B2B-specific catalogue assignments. ERP connectors that previously only supported B2C Shopify need explicit upgrades to handle the B2B object model.

Tax logic, OSS and DATEV-compatible accounting

Shopify computes tax at checkout based on the Shopify Tax engine or a manually configured tax-rate matrix per region. For German merchants this is generally adequate at checkout, but the ERP must own the canonical tax determination for accounting and OSS reporting. The integration should import Shopify orders into the ERP with the country-of-consumption tag, distinguish B2C and B2B (the latter retaining reverse-charge for valid VAT-IDs), and feed the resulting transactions into the DATEV-compatible export. For higher-volume merchants across multiple EU member states, specialist tax-tech providers (Taxdoo, Hellotax, Avalara) sit between Shopify and DATEV to handle the OSS quarterly return filed via the German Federal Central Tax Office (BZSt). KassenSichV does not apply to pure Shopify online flows; merchants operating Shopify POS in Germany must use a KassenSichV-compatible TSE on the POS side.

Frequently Asked Questions

Which German Mittelstand ERPs have the strongest Shopify connector?

Xentral, weclapp, JTL-Wawi (with a partner-built connector), billbee and plentyOne all have functional Shopify connectors at the SMB and lower-Mittelstand level. For upper Mittelstand and enterprise, Microsoft Dynamics 365 Business Central (via Sana Commerce, LS Retail or Insight Works), NetSuite (via Celigo or FarApp) and SAP S/4HANA (via partner-built connectors or CPI iFlows) are the typical paths. The connector's handling of multi-store, B2B and bulk operations matters more than the vendor branding.

Is Shopify Plus B2B a viable replacement for Magento B2B?

Increasingly, yes — particularly for merchants whose B2B catalogue is less complex than Magento's typical territory and where the operational simplicity of Shopify Plus is preferred over Magento's flexibility. Shopify Plus B2B has matured substantially since 2023 and now covers company accounts, payment terms, draft orders and price lists. Merchants with deeper configurable-product needs or complex approval workflows often still find Adobe Commerce or a specialist B2B platform a better fit. The ERP integration is comparable in scope for both platforms.

How does the Shopify Fulfilment Network affect ERP integration?

The Shopify Fulfilment Network (SFN) is treated as a Location in Shopify's inventory model and as a third-party fulfilment service. The ERP integration must therefore handle SFN as a separate logical warehouse, ingest SFN fulfilment events for accurate stock and order-status tracking, and reconcile SFN cost data into the appropriate cost-of-goods accounts. SFN's European presence remains more limited than its North American footprint, so German merchants using SFN are typically running it for transatlantic flows rather than domestic European fulfilment.

What about Shopify Markets for international expansion?

Shopify Markets allows a single store to serve multiple countries with localised pricing, currency, language and tax rules — an alternative to the multi-storefront approach for organisations that prefer a single backend. For ERP integration, Markets means that one Shopify shop carries orders from multiple countries with the appropriate tax tagging and currency, and the connector must preserve those tags into the ERP. OSS reporting is supported through the country-of-consumption tagging that Markets adds to each order, which the ERP then feeds into the DATEV export.