How to connect an e-shop to POHODA accounting
, 7 min read
Orders come in through the e-shop, while the accountant works in POHODA. Invoices are retyped by hand or sent over in export files. Stock in the e-shop does not match stock in POHODA. This article explains the ways to connect the two and where errors usually happen.
What POHODA is and how it talks to other systems
POHODA is a widely used Czech accounting and invoicing program made by Stormware. It has an XML communication interface. Data is exchanged as XML files that follow schemas published by Stormware. Each import is wrapped in a dataPack envelope. POHODA returns the result in a responsePack envelope.
XML import supports, among others, invoices, orders, sales receipts, bank movements, addresses and stock items. XML export from POHODA covers, for example, stock items, selling prices, addresses, orders and invoices. The full list of agendas is on Stormware's website.
To process XML by hand, use File/Data Communication and the XML import/export command (Soubor/Datová komunikace in the Czech interface). You can pick one file or a whole folder. POHODA then processes every valid file in the folder. Results are shown in the XML log.
Five ways to connect
- Manual XML export and import. The e-shop exports documents in POHODA format and the accountant imports them. It is cheap and transparent, but needs regular manual work.
- E-shop platform features and add-ons. Both Shoptet and Upgates can export invoices as POHODA XML. They also offer add-ons for ongoing sync.
- Third-party connectors and services. They run as a program next to POHODA or as an online service. They transfer orders, products and stock according to their settings.
- POHODA mServer. An HTTP server built into POHODA. Another application sends it XML requests and receives responses.
- Custom integration. A purpose-built program reads data from the e-shop API and writes it to POHODA via XML or mServer.
POHODA can also download orders automatically on a schedule. The POHODA Portal describes this for the POHODA E1 series. Stormware's variant comparison also ties automatic XML communication to E1. Check this for your licence.
Comparison at a glance
| Option | Data direction | Usually enough when | Limits |
|---|---|---|---|
| Manual XML export and import | E-shop → POHODA (invoices, credit notes) | Lower document volume, one warehouse | Manual work, risk of missed or double imports |
| Platform add-on | Depends on the add-on, often both ways | Standard e-shop on Shoptet or Upgates | The add-on decides which data moves, not you |
| Third-party connector | Depends on the connector | Common processes the connector supports | Fees, vendor dependency, desktop connectors run on Windows |
| POHODA mServer | Both ways, continuous | You have a developer or integration partner | POHODA must be running, a dedicated instance, internal network only |
| Custom integration | Anything the e-shop API and POHODA XML allow | Non-standard processes, several warehouses, custom e-shop | Higher upfront cost, ongoing maintenance |
Shoptet and POHODA
Shoptet can export tax documents, advance invoices and credit notes as POHODA XML. The export is in the overview of each document type. Every export is recorded in a log. Documents for received payments can also be exported as POHODA XML.
Shoptet's own POHODA add-on uses POHODA's Internet Shops module. According to Shoptet's help, the module is available from the Jazz variant. Sync is started manually from POHODA. Shoptet says the add-on will not get new features. For new connections it recommends third-party add-ons.
The add-on transfers only new orders. It does not resend edited orders, because POHODA would not accept them. Stock levels flow from POHODA to the e-shop, not the other way.
WooCommerce and POHODA
For WooCommerce, the connection is handled by plugins or external services. The offer changes over time. For example, Toret no longer offers its POHODA plugin. Before choosing, check who develops the plugin, when the last version came out and how it sends data to POHODA.
Upgates and POHODA
Upgates offers a manual invoice export as POHODA XML and a free add-on called Pohoda konektor. According to its description, the connector sends orders to POHODA every five minutes. It transfers products, prices and availability from POHODA to the e-shop once an hour.
The connector runs on Windows or Windows Server. One connector belongs to one running POHODA instance. Only one POHODA warehouse can be configured. Orders are not updated in POHODA after transfer. Regular product import may require a paid service.
Custom e-shops
For a custom e-shop, a ready-made add-on usually does not exist. The e-shop can write XML files that POHODA imports from a folder. Or it can talk to mServer directly.
POHODA also has a so-called generic internet shop. It communicates over HTTP and XML with any e-shop that supports this exchange. It brings addresses, orders and stock items back into POHODA. If the e-shop needs another format, XSLT templates convert it.
POHODA mServer for ongoing sync
mServer is an HTTP server built directly into POHODA. An application sends it XML with the POST method and gets a response. GET is not supported. Each request must carry the STW-Authorization parameter in its header.
POHODA itself must be running. Each mServer run reserves one POHODA instance, which cannot be used for manual work. Stormware recommends a server operating system and use on an internal network only, not on a computer with a public IP address.
Stormware's pages do not say which variants include mServer. Before you plan around it, confirm it for your licence with Stormware or your reseller.
What data flows between the e-shop and POHODA
- Orders from the e-shop to POHODA. In POHODA they become invoices or stock issues.
- Invoices, advance invoices and credit notes, if the e-shop issues them.
- Customer addresses. According to Shoptet's help, POHODA shortens a full name longer than 25 characters.
- Stock, prices and availability from POHODA back to the e-shop.
- Payments. POHODA can load bank statements and automatically match, settle and post the payments.
Common pitfalls
- Duplicate documents. POHODA can check during XML import whether a document was already imported. The check uses the id attributes of the dataPack and dataPackItem elements. It is optional, so turn it on and use unique ids.
- Number series. Advance invoice and tax document numbers must not overlap. Shoptet recommends importing advance invoices first and tax documents afterwards.
- VAT rates. If an XML item has no rate, a text item gets 0 % and a stock item takes the rate from its stock card. Rates other than the current ones require historical VAT rates to be enabled.
- Non-VAT payers. According to Shoptet's help, they set a zero rate for all rates in the export.
- Rounding. POHODA recalculates item amounts on import and adjusts them if needed. It accepts your own VAT amount only within the tolerance set in global settings. Settle rounding differences in advance.
- Missing unit price. Since version 10 800, the XML must include a unit price. Otherwise the item amount will be zero.
- Changes after transfer. Neither Shoptet's add-on nor the Upgates connector transfers later order edits. Cancellations and changes need an agreed process.
- Testing on live data. Test any connection on a copy of the accounting unit first. Check documents, VAT and stock. Only then connect the live company.
Ready-made connector or custom integration?
A ready-made add-on or connector is usually enough with a common platform, one warehouse and a standard order, invoice, payment flow. It is quick to set up and the vendor handles updates.
A custom integration makes sense when:
- you run a custom e-shop with no add-on available,
- you need more warehouses or price lists than the connector handles,
- you want to transfer order changes and cancellations, not only new orders,
- you connect several systems at once, such as e-shop, warehouse and carrier,
- you need control over what is written to POHODA and when.
A custom integration costs more upfront and needs maintenance. POHODA gets updated and its XML schemas evolve. Whoever builds the integration should also be able to maintain it.
This article is based on public documentation from Stormware, Shoptet and Upgates as of 3 November 2026. Feature availability differs by POHODA series and variant. Always confirm your licence and settings with Stormware, your POHODA reseller or your accountant.
Sources
- Stormware – POHODA XML API communication (CZ)
- Stormware – Supported documents for XML import (CZ)
- Stormware – Supported documents for XML export (CZ)
- Stormware – List of XML schemas (CZ)
- Stormware – VAT rate on a document item (CZ)
- Stormware – Calculating the amount on a document item (CZ)
- Stormware – POHODA mServer (CZ)
- POHODA manual – XML import/export (CZ)
- POHODA manual – POHODA mServer (CZ)
- POHODA manual – Internet shops (CZ)
- POHODA manual – Homebanking (CZ)
- Stormware – POHODA variants (CZ)
- POHODA Portal – Automate data exchange (CZ)
- Shoptet Help – Stormware Pohoda (CZ)
- Shoptet Help – Document export (CZ)
- Upgates – POHODA connection guide (CZ)
- Upgates Marketplace – Pohoda konektor (CZ)
- Toret – WooCommerce and POHODA connection (CZ)
Need to connect your e-shop to POHODA? At BeDigit we first review your e-shop, your POHODA licence and which data needs to go where. Then we recommend a ready-made connector, or design and build a custom integration. Our rate is €50 per hour (1 250 CZK), and we are not VAT registered.
Free consultation