Häufig gestellte Fragen
Which ERP is best for Shopify?
The right choice depends on size and business model, not on a one-size-fits-all ranking. For small, simple Shopify shops, lean solutions such as Billbee or Collmex are sufficient, while in the mid-market cloud ERPs such as weclapp, Myfactory or microtech offer more depth in warehousing, financial accounting and CRM. For Shopify Plus, multichannel and high order volumes, fully fledged multichannel or enterprise systems such as Actindo or Oracle NetSuite are typically the more robust foundation. What ultimately matters are the sync objects actually required (stock levels, variants, prices, taxes) and whether the vendor provides a native bridge or only a generic interface.
Doesn't Shopify already have ERP features itself?
Shopify covers storefront, checkout, payment, order processing and simple inventory management very well, but it does not replace a fully fledged ERP. What is missing above all is German financial accounting with a DATEV interface, multi-level warehousing with reservation and batch logic, production and production planning (PPS), and HR; native B2B features such as company accounts, customer-specific price lists and payment terms have been available on all paid Shopify plans since 2026, but a dedicated B2B storefront and unlimited price catalogs remain reserved for Shopify Plus. Roughly speaking, these gaps mean that Shopify masters the frontend and the order, while the commercial and logistical backbone sits in the ERP. Beyond a certain order and product-range size, a dedicated ERP that keeps Shopify in place as a modern frontend is therefore almost always worthwhile.
Does the Shopify-ERP integration cost extra?
With cloud ERPs, a Shopify bridge is often included in the standard scope or, depending on the vendor, costs an additional low two- to three-digit euro amount per month. Classic mid-market ERPs usually involve a one-off setup and customisation effort for the interface plus ongoing maintenance, the amount of which depends heavily on the data model and individual mappings. Important for budget planning: pure licence fees typically account for only around 20 to 35 percent of total costs in ERP projects, while the larger share goes to implementation, customisation, training and data migration. Anyone working with iPaaS or middleware solutions such as Celigo or Patchworks should additionally budget for a separate platform fee, but gains flexibility in field mappings and workflows in return.
How is the integration different with Shopify Plus?
Shopify Plus provides additional features and APIs that not every ERP fully supports, such as a dedicated B2B storefront with its own domain and unlimited price catalogs, Shopify Markets for up to 50 international markets, and checkout extensibility via Shopify Functions. Technically, Plus also doubles the rate limit of the GraphQL Admin API from 1,000 to 2,000 points per bucket, with replenishment of 100 instead of 50 points per second, which makes real-time synchronisation easier at high volumes. Bulk operations are also relevant for ERP integrations: in current API versions, several can run per shop simultaneously (one bulk mutation plus parallel bulk queries), and they are not subject to the same point limits as individual queries. Anyone using Shopify Plus should therefore specifically ask the ERP vendor about explicit Plus compatibility for the B2B storefront, Markets and multi-store.
Native interface, middleware or custom development — which makes more sense?
Native connectors from the ERP vendor are the fastest to set up, require no code and are maintained by the manufacturer, but at some point reach their limits with highly individual processes or large volumes. iPaaS or middleware platforms such as Celigo, Boomi or Patchworks offer more flexibility in field mappings, workflows and multiple connected systems, but cost an additional platform fee and mean one more vendor relationship. Custom development via the Shopify APIs is maximally adaptable, but shifts maintenance and responsibility entirely in-house. As a rule of thumb, stock levels, availability and order status should be synchronised in real time wherever possible, while accounting data can often be handed over in batches.
How are VAT and DATEV export handled for Shopify via the ERP?
Shopify itself calculates tax rates at the point of sale, for example via Shopify Tax with support for the EU OSS scheme, which requires taxation in the country of destination once the EU-wide delivery threshold of 10,000 euros net per year is exceeded. However, the proper accounting treatment, including GoBD-compliant archiving and DATEV export, does not take place in Shopify but in the connected ERP or via specialised tools such as Taxdoo or Lexware Office (formerly lexoffice). A good ERP interface therefore transfers not only orders but also tax logic, credit notes and refunds in such a way that they land correctly in the financial accounting and can be passed on to the tax advisor in DATEV format. Anyone selling cross-border should additionally check whether the system supports OSS filings and the reverse-charge procedure for EU B2B customers.