Connecting an e-shop to POHODA is the most common integration in Czech e-commerce \u2014 and also the most common source of frustration. Orders get retyped by hand, the stock shown on the website doesn’t match reality, and invoicing catches up with the weekend rush on Monday evening. There are four solutions, each suited to a different stage of growth. This guide will help you choose right the first time.<\/p>\n
Connecting POHODA to an e-shop means the automatic transfer of orders, stock levels, prices and invoices. Four routes lead there \u2014 the platform’s native bridge, a ready-made connector, an integration platform and a bespoke integration. They differ in price, agenda coverage and reliability in operation.<\/p>\n<\/div>\n
Before you start choosing a tool, write down what exactly should flow and in which direction:<\/p>\n
Shoptet, Upgates and other platforms offer their own POHODA add-on. The advantages are clear: the fastest start and a price in the hundreds of K\u010d per month. The limits arrive with growth, though \u2014 the bridge covers only selected agendas of a single platform, runs on its own schedule, and when a transfer gets stuck, you usually hear about it from a customer. For a young e-shop with dozens of orders a day it is still a sensible first choice.<\/p>\n
Specialised bridges and connectors from independent vendors cover more agendas and often more platforms. They make sense when the native add-on is no longer enough but you don’t yet want to approach integration strategically. Watch out for two things: who keeps the connector alive when POHODA or mServer<\/a> changes \u2014 and what support looks like when a transfer crashes at midnight.<\/p>\n A platform like Symmy connects your e-shop to POHODA just like a connector does \u2014 but on top of that it adds monitoring, queues, retries on error and, above all, room to scale: carriers, a CRM<\/a>, a marketplace or a second e-shop plug into the same infrastructure without a new project. It pays off the moment the e-shop is just one of several systems that need to talk to POHODA. You will find specific combinations in our catalogue \u2014 for example Shoptet + POHODA<\/a> or WooCommerce<\/a>.<\/p>\n Custom development on top of mServer or the database gives you full control and makes sense for large volumes and heavily non-standard processes. But it is the most expensive route \u2014 from tens of thousands of K\u010d for a simple scenario to hundreds of thousands \u2014 and development is not the end of it: every change to POHODA, the platform or legislation means maintenance someone has to do.<\/p>\nRoute 3: an integration platform<\/h2>\n
Route 4: bespoke integration<\/h2>\n
Comparing the four routes<\/h2>\n