Shoptet powers tens of thousands of e-shops in the Czech Republic and Slovakia \u2014 and almost every one of them sooner or later hits the same moment: there are so many orders that retyping them into the accounting system or ERP stops scaling. There are three ways to connect Shoptet to an ERP, each suited to something different. This article compares them without the sales fog \u2014 including the things an add-on offer usually leaves out.<\/p>\n
For a standard scenario with a widespread ERP (POHODA, Money S3, ABRA Flexi), start with a ready-made add-on from the Shoptet marketplace<\/strong> \u2014 it is the fastest to deploy and the cheapest on day one. 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 manual exports and imports only as a temporary fix for a handful of orders a day.<\/p>\n<\/div>\n Shoptet offers three interfaces through which data gets in and out: add-ons<\/strong> from its own marketplace, a partner API<\/strong> and file exports\/imports<\/strong> (XML, CSV). One important detail decides the whole architecture: Shoptet has no public API for shop owners<\/strong>. The API is available to registered partners who build add-ons on top of it \u2014 and your e-shop grants them access by installing the add-on. In practice this means you cannot just click together \u201cyour own API connection\u201d; you either use a ready-made add-on, or an integrator who holds partner access. Higher Shoptet plans further extend the connection options.<\/p>\n For the most common pairs \u2014 Shoptet with POHODA, Money S3 or ABRA Flexi \u2014 ready-made add-ons exist: from ERP vendors, specialised companies and Shoptet itself. Installation takes hours, you pay a monthly fee and the standard scenario (orders into the ERP, stock and prices back) works out of the box. That is both the strength and the limit of this route: the field mapping is fixed. As soon as you need to convert units on the way, match product codes, split documents by VAT or connect a third system, the add-on can\u2019t do it \u2014 and every additional add-on in the shop is another separate thing to manage, with its own behaviour on errors and its own (often non-existent) logs.<\/p>\n The oldest route: orders out as XML or CSV, price list and stock in via import. It costs nothing and is enough for a few orders a day \u2014 the accountant downloads a file once a day and imports it into the ERP. But bear in mind the whole process depends on a person: forget the export and documents go missing; change the file structure and the import fails silently. There is no feedback loop (order statuses, real-time stock movements), and as volume grows, so does the room for human error. A good start, a bad permanent state.<\/p>\n A platform connects to Shoptet through the same partner interface as an add-on \u2014 but the mapping is not fixed. It transforms data on the way (units, codes, item matching), validates it before writing into the ERP, queues transfers with automatic retries on outages, and you learn about errors from a notification, not from a customer. The main difference shows with the third system: a warehouse (WMS), CRM or carrier connects with one connector into the same hub, whereas with add-ons you would be stacking several separate bridges next to each other. When each architecture pays off is covered in detail in our article on integration platforms<\/a>.<\/p>\n Shoptet gets along with practically every Czech ERP \u2014 the question is not \u201cwhether\u201d but \u201chow well for your modules\u201d. 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>. When choosing an ERP for e-commerce, look above all at integrability: what interface it has (API, XML), 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 ERP systems come in editions, and the editions differ exactly where integrations stand: POHODA Jazz, Komplet and E1 differ in mServer availability and modules, Money and Helios charge extra for interface modules. An add-on \u201cfor POHODA\u201d may not work with your edition \u2014 always ask about your specific edition, version and the list of modules that actually get transferred.<\/p>\n<\/div>\n Symmy is a cloud integration platform built for Czech and Slovak ERP systems. It connects to Shoptet 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 Shoptet is on the Shoptet detail page<\/a>; the pricing page with an online calculator<\/a> gives you an indicative price for your combination.<\/p>\n Not for shop owners \u2014 the API is meant for registered partners who build add-ons on it, and the e-shop grants them access by installing the add-on. You therefore can\u2019t write your own connection \u201cagainst a token\u201d; you need a ready-made add-on, or an integrator with partner access.<\/p>\n<\/details>\n A ready-made add-on runs from a few to tens of euros a month depending on scope. 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 There is no universal best \u2014 your modules and scale decide. Smaller e-shops usually do fine with POHODA or Money S3, growing companies with ABRA Flexi or Helios, larger operations with Microsoft Business Central. More important than the brand is how well the ERP connects to Shoptet \u2014 compare combinations in the catalogue<\/a>.<\/p>\n<\/details>\n It depends on the route: exports happen when somebody runs them; add-ons run on fixed intervals (typically tens of minutes); a platform can react to events and transfer at intervals from minutes. For last pieces of stock and multi-channel selling, stock frequency is the main selection criterion.<\/p>\n<\/details>\n For notifications and marketing automation, yes. With accounting documents you will run into the fact that general-purpose platforms don\u2019t know Czech and Slovak ERP systems, their editions and validations \u2014 and a document that fails validation in the ERP won\u2019t be returned to any queue. We compared the two approaches using POHODA as the example<\/a>.<\/p>\n<\/details>\n","protected":false},"excerpt":{"rendered":" A marketplace add-on, file exports, or an integration platform? What Shoptet exposes to the outside world, when a ready-made add-on is enough, when its fixed mapping stops you \u2014 and how to pick an ERP that gets along with Shoptet.<\/p>\n","protected":false},"author":0,"featured_media":72036,"template":"","erpedie-topic":[99],"class_list":["post-72029","erpedie","type-erpedie","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie\/72029","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\/72029\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/media\/72036"}],"wp:attachment":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/media?parent=72029"}],"wp:term":[{"taxonomy":"erpedie-topic","embeddable":true,"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie-topic?post=72029"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What Shoptet exposes to the outside world<\/h2>\n
Route 1: A ready-made marketplace add-on<\/h2>\n
Route 2: File exports and imports<\/h2>\n
Route 3: An integration platform<\/h2>\n
\n
An ERP for Shoptet: what gets connected most often<\/h2>\n
What to check before signing<\/h2>\n
\n
A trap: \u201cworks with POHODA\u201d doesn\u2019t mean it works with your POHODA<\/h2>\n
How we do it at Symmy<\/h2>\n
Frequently asked questions<\/h2>\n
Does Shoptet have a public API?<\/summary>\n
How much does connecting Shoptet to an ERP cost?<\/summary>\n
Which ERP is best for Shoptet?<\/summary>\n
How fast does stock synchronise?<\/summary>\n
Can Make or Zapier handle it?<\/summary>\n