Automation CZEN

Automation · System integration

POHODA integration: orders, warehouse and reports without retyping

Customer orders, goods receipt with a scanner, invoices and a morning overview that flow into and out of POHODA on their own. We build on the official XML interface and mServer, so POHODA stays in charge of the data.

What the interface can do

POHODA API, XML and mServer: what they can do

Based on Stormware’s documentation. What exactly works for you depends on your POHODA edition, version and user permissions. We verify this in the audit.

  • Interface: XML and mServer

    Official XML interface for importing and exporting documents and lists, with validation against the schema. mServer is an HTTP server built into POHODA, through which XML is sent online. The E1 edition can run XML communication on its own at set intervals.

  • REST API

    The cloud-based mPohoda has a REST API (JSON, OpenAPI), in its Pro version.

  • Orders and customers

    Import of received orders and addresses. Export of stock, selling prices, individual discounts, promotional prices and online store categories. Duplicate check on import.

  • Warehouse

    XML import of goods receipts, issue slips, transfers, sales receipts, production and stocktaking lists. Receiving into stock from ISDOC with matching by code or barcode, including alternative supplier codes.

  • Invoices and documents

    Import of invoices, internal and cash documents, and bank records. ISDOC import and export. ARES and VIES verification when a document is saved.

  • Service and jobs

    XML import of service records, jobs and invoices. In POHODA a service record can also be created from a received order.

  • Reporting

    XML export of documents, balances, movements and the accounting journal; for some modules only new and changed records. For the SQL and E1 editions Stormware offers the Business Intelligence add-on in Excel.

  • AI and MCP

    Open-source MCP servers on top of mServer (e.g. pohoda-mcp) can read documents, stock and contacts and create invoices and orders.

Using mPohoda, or POHODA hosted by a provider? That is a valid starting point too. In the audit we verify what your edition and your hosting allow.

Sound familiar?

POHODA can do a lot. But data out of it and back in is often carried over by a person – by e-mail, over the phone and in Excel.

  • “Orders from our customers come by e-mail and someone retypes them into POHODA by hand.”

  • “Customers call to ask whether goods are in stock and how much they owe us.”

  • “We have POHODA on a server in the office. Apparently it can’t be connected to the web.”

  • “Off-the-shelf connectors are for e-shops. We have B2B customers and each has their own price list.”

  • “We retype the supplier’s delivery note into POHODA line by line.”

  • “Every month my boss wants revenue by customer and I piece it together in Excel.”

Flow

POHODA integration: where data flows and where we monitor it

The mServer in POHODA processes requests one at a time. So neither the portal nor the dashboard slows POHODA down, and no write gets lost.

  1. 01

    Origin

    An order in the portal, a scan in the warehouse or a service report is created outside POHODA.

    Person: The customer, warehouse worker or technician just clicks or scans.

  2. 02

    Handover

    No write gets lost. When the server with POHODA is off, it waits and goes out later.

    Person: Nobody has to watch anything or resend anything.

  3. 03

    mServer

    XML import with duplicate checks and validation against the schema. Connection only via VPN or a tunnel, not an open port.

    Person: Your IT administrator approves access.

  4. 04

    POHODA

    The document is created in POHODA. The response with the result or error is saved to the log.

    Person: The accountant only handles errors POHODA returns, such as a locked period.

  5. 05

    Back out

    Stock, prices, order status and account balances are regularly passed on to the portal and reporting.

    Person: The customer and the sales rep see the status without a phone call.

What we build on top of POHODA

You don’t have to take everything. We start with what slows you down the most.

01

B2B portal for customers

The customer sees the catalog, stock and their own prices and discounts from POHODA and orders on their own. The customer’s order is written to POHODA as a received order, without retyping from e-mail.

02

Client portal: invoices and balance

The customer downloads an invoice and sees what is overdue. Invoices and balances come straight from POHODA, so the accountant doesn’t have to send anything again.

03

Mobile warehouse app on top of POHODA

POHODA warehouse with a scanner: goods receipt, issue and transfers by scanning from a phone or terminal, stocktaking as an import of the stocktaking list. A supplier document in ISDOC is received into stock without retyping.

04

Batches and expiry dates

POHODA keeps batches and expiry dates in its batch register, which needs to be turned on in the settings. We add batch capture by scanning at goods receipt and monitoring of approaching expiry dates. How to pass batches via XML, we verify on a test accounting unit.

05

Reporting from POHODA to Power BI or Looker Studio

A morning overview by e-mail and a dashboard for management. In it, we combine data from POHODA with the e-shop, CRM or POS.

06

Service and jobs via XML

A service report from a mobile phone is written via XML into the Service module and turns into an invoice or the basis for one. The office no longer retypes service sheets.

07

AI assistant on top of POHODA

An AI assistant that answers from your documents, stock and contacts in POHODA. Writes only after human approval.

When you don’t need us

We don’t sell POHODA licenses or off-the-shelf connectors. When a ready-made solution is enough, we tell you.

You just want to connect a standard e-shop to POHODA
There are off-the-shelf connectors with a price list for that (e.g. Dativery, Shopsync, BHIT). If they cover what you need, we will recommend them.
A ready-made B2B e-shop is enough for you
There are ready-made B2B ordering systems for POHODA (e.g. GoOrder). A custom solution only makes sense with your own pricing rules, branches or several connected systems.
You only need reporting from POHODA SQL or E1
Try Stormware’s Business Intelligence add-on first. We only add what it can’t do: data from other systems, a morning e-mail and alerts.
You have POHODA E1 and want to download orders from your e-shop regularly
Automatic tasks in E1 can run set scenarios at intervals, such as downloading orders or updating stock. First we turn on what you already pay for.

How it works

  1. 01

    Free audit

    30 minutes. We go through what you use today and what slows you down.

  2. 02

    Proposal

    We tell you what makes sense to tackle, what you can leave out and how much it will cost.

  3. 03

    Rollout

    We set it up, connect it and migrate the data. We show your team how to work with it.

  4. 04

    Handover

    We hand over the finished solution and agree whether you also want ongoing maintenance.

Frequently asked questions

Does POHODA have an API?
Desktop POHODA has an official XML interface and mServer, a built-in HTTP server for exchanging XML. Stormware does not publish an official REST API for it; third parties offer REST. The cloud-based mPohoda has a REST API (OpenAPI, JSON) in its Pro version.
Does it work if we have POHODA on a server in the office or hosted by a provider?
Yes, if mServer can be run and connected to securely. We don’t expose mServer to the internet; the connection goes through a VPN or a tunnel. For hosting, we verify in the audit whether the provider supports mServer.
Do we need another POHODA license for this?
Often, yes. A running mServer takes up one POHODA instance, so a second one is needed for the accountant to work at the same time. With network licenses this means an extra license in practice. We tell you before the quote, not after.
Won’t it write nonsense into our accounting?
Writes go only through the official XML import. POHODA validates the data against the schema and returns errors, the duplicate check stops a duplicate import, and a document won’t go through into a locked period or after the data closing date. We develop on a test accounting unit and change live data only after you approve.
Which POHODA edition is enough?
XML integration works across editions. Only E1 can run XML communication automatically from within the program, and only the SQL and E1 editions allow reading the database directly. We tell you what is enough for you after the audit.
What happens when POHODA is updated?
After an update you need to check that mServer is running again, otherwise the integration may silently stop working. Stormware does not recommend running mServer as a Windows service; for automatic start it recommends the Task Scheduler. We monitor mServer availability as part of ongoing support.
Is this the same as Portál POHODA?
No. Portál POHODA is Stormware’s information website for accountants and business owners. We build integrations and portals on top of your data from POHODA.
Are you a Stormware partner?
No, we build integrations. We don’t sell licenses.
How much does it cost and how long does it take?
It depends on the systems and the scope. We don’t publish a price list on the website because no two companies are the same. You get the price and timeline after the audit, in advance and in writing.

Enquiry — POHODA

Tell us what you are dealing with. We start with a free 30-minute audit.

What are you interested in?