System Integrations and APIs

The most common request we get from companies is: "We copy e-shop orders into accounting by hand." The second most common: "The stock levels in the e-shop do not match reality." Both are a connection of two systems through an API, which we can build in 2 to 4 weeks.

Connecting an e-shop to accounting looks like this in practice: a new order in Shoptet, WooCommerce or Shopify triggers a workflow, which turns it into an invoice or a received order in Pohoda, Fakturoid, iDoklad, Money S3 or ABRA Flexi, fills in the right VAT rates and payment method, and after payment sends the document to the customer. Statuses flow back the other way: paid, shipped, the tracking number from Zásilkovna, PPL or DPD. In the same way we connect CRMs (Pipedrive, Raynet, HubSpot) to web forms, e-mail and calendars, the warehouse to the e-shop, and payment gateways (GoPay, Comgate, Stripe) to accounting. We distinguish a one-off data transfer, such as migrating customers to a new CRM, from ongoing synchronisation that runs every few minutes or on an event. For ongoing synchronisation we handle what happens when the API on the other side is unavailable: the transfer retries automatically, after repeated failures an alert goes to Telegram or e-mail, and nothing is lost or duplicated. Every transfer is logged, so you can trace which order went where and when. We build integrations in n8n and where a ready-made node is not enough, we write custom code. The systems listed are categories we can connect; we always confirm the exact scope against the API documentation of the given system and your plan.

• E-shop to accounting: Pohoda, Fakturoid, iDoklad, Money S3, ABRA Flexi
• Payment and shipment statuses back into the e-shop and CRM
• Automatic retry on API outage and an alert on a permanent error
• A log of every transfer, no lost or duplicated records