Shopify is the world\u2019s largest e-commerce platform, and more and more Czech and Slovak shops run on it \u2014 often the ones selling abroad. Sooner or later they all hit the same moment: orders need to get into the accounting system or ERP, and stock levels need to flow back. There are four ways to connect Shopify to an ERP. The good news: unlike the local Czech platforms, Shopify has an open API. The catch: the success of the integration is decided by the other side \u2014 how well the solution understands your ERP, its documents and VAT.<\/p>\n
For a standard scenario with a widespread ERP, start with a ready-made app or a connector from a specialised company<\/strong> \u2014 for pairs like Shopify \u00d7 POHODA they exist and work out of the box. You need an integration platform as soon as data has to be transformed on the way, you are connecting a third system (warehouse, CRM, carrier), or your dispatch depends on the transfers.<\/strong> Treat CSV exports as a temporary fix, and a custom API build only if somebody will maintain it long-term.<\/p>\n<\/div>\n Technically, Shopify is the most open platform you can choose for an e-shop: it has a public Admin API<\/strong> (today primarily GraphQL), every shop can create its own custom app with an access token right in the admin, it announces events via webhooks<\/strong> (new order, stock change), and on top of that there is a huge App Store<\/strong> and native CSV exports and imports<\/strong>. That sets it apart from Czech platforms like Shoptet, where the API is partner-only \u2014 we compared the two in a separate article<\/a>. But openness solves only half the task: the API gives you the orders, yet somebody has to understand them on the ERP side \u2014 editions, modules, documents, VAT.<\/p>\n The App Store holds thousands of apps, but the global ones don\u2019t know Czech and Slovak ERP systems. Fortunately, connectors from specialised companies exist \u2014 typically for pairs like Shopify \u00d7 POHODA or Money S3. Deployment is quick, you pay a monthly fee and the standard scenario (orders into the ERP, stock and prices back) works out of the box. The limit is the same as with every ready-made solution: fixed mapping. Unit conversions, code matching, splitting documents by VAT or a third system are beyond it \u2014 and every additional app in the shop is another separate thing to manage, with its own (often non-existent) logs.<\/p>\n Shopify can export orders to CSV and import products from CSV without any app at all. For a few orders a day that is enough \u2014 the accountant downloads a file once a day and processes it in the ERP. But the whole process depends on a person: a forgotten export means missing documents, a changed file structure means a silently broken import. There is no feedback loop (order statuses, stock movements), and as volume grows, so does the room for human error. A good start, a bad permanent state.<\/p>\n Thanks to the open API you can build the connection yourself \u2014 with your own script, or in tools like Make and Zapier, which have official Shopify connectors. The Shopify side works beautifully; you will get stuck on the ERP side. General automation platforms don\u2019t know Czech and Slovak ERP systems (you won\u2019t find POHODA, Money or Helios in them), so you end up building that half by hand anyway \u2014 and a custom script needs an owner: watching API changes, rate limits, error states and documents that fail validation in the ERP. What DIY automation can and cannot handle is covered in our POHODA case study<\/a>.<\/p>\n A platform connects to Shopify through the API like a custom app \u2014 but it already has both sides built: a connector to Shopify and to your ERP. It transforms the data on the way (codes, units, item matching), validates it before writing, queues transfers with automatic retries on outages, and you learn about errors from a notification, not from a customer. With a third system (warehouse, CRM, carrier) the difference deepens: it connects with one connector into the same hub. When each architecture pays off is covered in our article on integration platforms<\/a>.<\/p>\n Smaller e-shops most often connect POHODA<\/a> or Money S3<\/a>, growing companies ABRA Flexi<\/a> or Helios iNuvio<\/a>, and larger operations Microsoft Business Central<\/a>. Since Shopify is typically chosen by shops selling abroad, also look at multi-currency documents and the EU OSS scheme when picking an ERP \u2014 and above all at integrability: what interface the ERP has, how fast it handles stock movements and whether a proven connection exists for your combination. All supported pairs are listed in the integration catalogue<\/a>.<\/p>\n \u201cShopify has an API, we\u2019ll wire it up in an afternoon.\u201d Half true: in an afternoon you will get orders out of the API. The rest of the project is the other side \u2014 which ERP module the document belongs to, how your edition behaves, what to do with an order in a foreign currency, what happens to a document that fails validation, and who finds out the transfer stopped overnight. The price of an integration isn\u2019t made by downloading data, but by delivering it correctly and under supervision.<\/p>\n<\/div>\n Symmy is a cloud integration platform built for Czech and Slovak ERP systems. It connects to Shopify through its API, automatically monitors, transforms and validates the data between the e-shop and the ERP, and operations run under 24\/7 supervision. The build is priced per module (usually 6\u201312 hours of work per module), so you pay for the flows you actually need. Everything we can transfer with Shopify is on the Shopify detail page<\/a>; the pricing page with an online calculator<\/a> gives you an indicative price for your combination.<\/p>\n Three realistic options: manually via CSV export (a temporary fix), with a custom script over both systems\u2019 APIs (ABRA Flexi has a REST API, but somebody has to maintain the script), or with an integration platform that has both connectors ready \u2014 it transfers orders automatically, matches items via SKU and returns statuses to Shopify. The details are on the Shopify \u00d7 ABRA Flexi page<\/a>.<\/p>\n<\/details>\n Yes \u2014 the Admin API (primarily GraphQL) plus webhooks. You create a custom app with an access token right in the shop admin. That sets Shopify apart from platforms like Shoptet, where the API is partner-only. An open API, however, solves only the e-shop side \u2014 the other half of any integration is always the ERP.<\/p>\n<\/details>\n A ready-made app runs from a few to tens of euros a month. A platform integration is priced per module \u2014 the build usually takes 6\u201312 hours of work per module, plus a monthly operations fee. The online calculator<\/a> prices your specific pair of systems.<\/p>\n<\/details>\n The Shopify side, yes \u2014 official connectors are there. You will get stuck on the ERP side: these platforms don\u2019t know POHODA, Money or Helios, so you build the ERP half by hand anyway, without queues or validation. Great for notifications and marketing, not for accounting documents \u2014 see our POHODA case study<\/a>.<\/p>\n<\/details>\n Shopify handles VAT rates at checkout, but tax documents and returns are the job of your ERP or accounting system. The integration must carry the order over including country, rate and currency so the ERP issues the correct document \u2014 OSS scheme included. This is exactly where global apps without local-legislation knowledge break down.<\/p>\n<\/details>\n","protected":false},"excerpt":{"rendered":" An App Store app, file exports, a custom API connection, or an integration platform? Shopify has an open API \u2014 which makes the other side matter all the more: how well the solution understands your ERP, invoices and VAT.<\/p>\n","protected":false},"author":0,"featured_media":72041,"template":"","erpedie-topic":[99],"class_list":["post-72034","erpedie","type-erpedie","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie\/72034","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie"}],"about":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/types\/erpedie"}],"version-history":[{"count":0,"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie\/72034\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/media\/72041"}],"wp:attachment":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/media?parent=72034"}],"wp:term":[{"taxonomy":"erpedie-topic","embeddable":true,"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie-topic?post=72034"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What Shopify exposes to the outside world<\/h2>\n
Route 1: A ready-made app or connector<\/h2>\n
Route 2: CSV exports and imports<\/h2>\n
Route 3: A custom API build (and Make or Zapier)<\/h2>\n
Route 4: An integration platform<\/h2>\n
\n
An ERP for Shopify: what gets connected most often<\/h2>\n
What to check before signing<\/h2>\n
\n
A trap: an open API is not a finished integration<\/h2>\n
How we do it at Symmy<\/h2>\n
Frequently asked questions<\/h2>\n
How do I get orders from Shopify into ABRA Flexi?<\/summary>\n
Does Shopify have a public API?<\/summary>\n
How much does connecting Shopify to an ERP cost?<\/summary>\n
Can Make or Zapier handle it?<\/summary>\n
What about invoices and VAT when selling abroad?<\/summary>\n