Business systems don’t talk to each other on their own. The e-shop doesn’t know what’s in stock, the sales rep can’t see invoices, and the accountant retypes orders by hand \u2014 in the evening, with mistakes. That is exactly what ERP integration solves. In this guide we cover what integration involves, the four routes that lead to it, what a typical project looks like, what it costs and which mistakes to avoid.<\/p>\n
ERP integration is the automatic exchange of data between a business system (POHODA, Money, Helios, ABRA\u2026) and other applications \u2014 an e-shop, CRM, bank or warehouse. Orders, invoices and stock levels travel between the systems on their own: no retyping, no errors, always up to date.<\/p>\n<\/div>\n
The ERP is the heart of the company \u2014 it runs the accounts, the warehouse and the invoicing. But a whole ecosystem gradually grows up around it: e-shop, CRM, POS systems, carriers, banks, reporting tools. Each of them holds a piece of the truth about customers and money, and until they are connected, people carry the data between them. Integration means the systems hand data to each other themselves \u2014 by clear rules and with error checking.<\/p>\n
In practice, three situations come up most often:<\/p>\n
Whatever the brief, technically it always comes down to one of four routes. They differ in deployment speed, price and how well they hold up in day-to-day operation.<\/p>\n
The most common dilemma isn’t \u201cwhich API\u201d but \u201cwho builds it and who will look after it\u201d. A bespoke bridge \u2014 a script moving data from point A to point B \u2014 is quick and cheap to acquire. But integration isn’t a project that ends one day; it is a service that has to run every single day.<\/p>\n
It works right up until the API, the data format or the ERP version changes. Then comes the question: who fixes it \u2014 and how quickly will you even notice?<\/strong> An integration platform carries the monitoring, notifications and queues for you. To be fair, though: if you are connecting two systems in one direction and have your own developer, a bridge will do. Three or more systems, two-way flows, or nobody to watch over the operation \u2014 that is a job for a platform.<\/p>\n<\/div>\n Good news: integration is no longer a months-long IT project. With ready-made connectors we are talking days to two weeks; with bespoke solutions, weeks. The process is always similar:<\/p>\n Prices span a wide range, and scope is the main driver:<\/p>\n The price is driven up by the number of connected agendas, two-way flows, non-standard processes and data quality. For your specific combination of systems, we will prepare a quote<\/a>.<\/p>\n Integration has historically meant connecting system to system. Since 2025 there has been a third participant: the AI assistant. Thanks to the MCP standard, Claude or ChatGPT can connect directly to the ERP<\/a> and answer questions over live data \u2014 \u201chow much does company ABC owe us?\u201d or \u201cprepare the VAT documentation\u201d. MCP doesn’t replace classic integrations, it complements them: integrations keep data flowing between systems, MCP answers people. What it is and how it works is explained in a separate article<\/a>.<\/p>\n Usually yes. Where an API is missing, file exchange or direct database reads step in \u2014 with certain limitations in older editions (POHODA without SQL, for example). This is exactly where an integration platform proves useful, since it can combine several routes at once.<\/p>\n<\/details>\n With a ready-made connector, days to two weeks including testing; bespoke builds usually take a few weeks. Most of the time typically goes into aligning code lists and mapping fields, not the programming itself.<\/p>\n<\/details>\n Someone has to adapt the connector. With a bespoke bridge that is your developer; with an integration platform it is the provider \u2014 connector maintenance is part of the service. Ask this question before signing the contract, not after the first broken update.<\/p>\n<\/details>\n For reads, yes \u2014 with a dedicated account, rights limited to the necessary tables and a secured connection. Writes belong exclusively in the official interfaces (for POHODA that is mServer<\/a>) so they pass the application’s validations.<\/p>\n<\/details>\n A simple rule: two systems, one direction and your own developer \u2192 a bridge will hold up. Three or more systems, two-way flows, or nobody to maintain it \u2192 an integration platform pays for itself in reliability and time saved.<\/p>\n<\/details>\n","protected":false},"excerpt":{"rendered":" What ERP integration is, the four routes that lead to it and what it costs. A practical guide from agenda analysis to live operation with monitoring.<\/p>\n","protected":false},"author":0,"featured_media":67153,"template":"","class_list":["post-71878","erpedie","type-erpedie","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie\/71878","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":1,"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie\/71878\/revisions"}],"predecessor-version":[{"id":71949,"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie\/71878\/revisions\/71949"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/media\/67153"}],"wp:attachment":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/media?parent=71878"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}How an integration project runs<\/h2>\n
\n
What ERP integration costs<\/h2>\n
\n
The most common mistakes<\/h2>\n
\n
What about AI? A new layer on top of integrations<\/h2>\n
Frequently asked questions<\/h2>\n
Can an ERP without an API be integrated?<\/summary>\n
How long does connecting an ERP to an e-shop take?<\/summary>\n
What if the ERP version or its API changes?<\/summary>\n
Is reading directly from the ERP database safe?<\/summary>\n
Bridge or platform \u2014 how to decide?<\/summary>\n