Integrating your e-shop with ERP and accounting: A pain-free guide

You know the drill. A customer orders on the e-shop, you manually re-key it into Pohoda, check stock in Excel, issue an invoice, email it, and at month-end spend two days matching bank statements. Every step is a chance for error — wrong quantity, wrong price, missed invoice. And the more orders, the bigger the chaos.

Yet e-shop integration with ERP and accounting is not a luxury for large corporations. It is a necessity for any e-shop processing more than 30 orders a day. Without process automation you become a bottleneck in your own business — and competitors who have solved it will overtake you not on product quality but on process speed and accuracy.

Typical e-commerce chaos

Picture a typical e-commerce company. The e-shop runs on Shoptet or WooCommerce. Accounting is in Pohoda or Money S3. Inventory is tracked in Excel (in the better case, Google Sheets so colleagues can see it). Payments arrive through the bank, but matching is manual. The carrier has its own system that orders get copied into manually. CRM? Outlook contacts.

Result? The accountant spends half the day moving data between systems. The warehouse manager does not know what is actually in stock because the e-shop shows different numbers from the spreadsheet. Customers get invoices late, or not at all. And the owner has no real-time view of earnings — because data is scattered across five different systems that do not talk to each other.

What integration should solve

Proper e-shop integration with ERP is not about one specific connection. It is about building an ecosystem where data flows automatically between all systems without human intervention. Five key areas:

1. Automatic order transfer (e-shop → ERP)

   Every new order from Shoptet or WooCommerce flows instantly into the ERP system — including line items, prices, shipping, and customer data. No manual re-keying, no typo errors. At 100 orders a day that saves 3–4 hours of admin work daily.

2. Real-time inventory sync

   When a product sells on the e-shop, stock updates automatically in ERP and on the website. When new goods arrive, the e-shop reflects it immediately. No more situations where a customer orders a product that is out of stock.

3. Automatic invoicing and payment matching

   After order confirmation, an invoice is generated automatically in Pohoda or Money S3 and sent to the customer. Payments from banks or payment gateways (GoPay, Stripe) are matched to invoices automatically. Accountants handle only exceptions, not routine.

4. Pricing sync and promotions

   Prices and discount campaigns are managed in one place and propagate automatically to the e-shop and ERP. No “forgotten” old prices, no mismatches between displayed and invoiced price.

5. Customer data in one place (CRM)

   Order history, contacts, communication — all centralised. When a customer calls, the operator instantly sees orders, payments, and past inquiries. Better service, higher retention.

3 approaches to integration

There is no single right way to connect an e-shop with ERP and accounting. It depends on your stack, order volume, and budget. Three main approaches:

1. Native connectors (plug-and-play)

Shoptet has its own connector for Pohoda and Money S3. WooCommerce offers plugins for popular ERP systems. Advantage: fast deployment, low cost, no developer needed. Disadvantage: limited flexibility — they work well for basic scenarios (orders, invoices) but fail on specific requirements like custom pricing rules, multiple warehouses, or complex payment flows. Ideal for e-shops up to 50 orders/day with simple processes.

2. Middleware platform (n8n, Make, Zapier)

Middleware works as “glue” between systems. You define scenarios: when an order arrives on Shoptet, create a record in Pohoda, update stock, generate an invoice, send a notification. Platforms like n8n (self-hosted) or Make (cloud, visual editor) can handle complex logic — conditional rules, error handling, retry mechanisms. Costs are medium (€50–300/month plus implementation), flexibility high. For most e-shops with 50–500 orders a day, this is the best price/performance.

3. Custom API integration

For high-volume e-shops, specific processes, or combinations of systems where no ready connector exists, custom API integration is the answer. Direct e-shop → ERP → accounting → bank → carrier integration tailored to your needs. Advantage: no compromises, maximum speed and reliability. Disadvantage: higher upfront costs (typically €5,000–20,000) and ongoing maintenance. Makes sense at 500+ orders a day or revenue above a million euros a year, where every minute of delay costs real money.

How to choose the right solution

Consider four key factors when picking an integration approach:

• Order volume. Under 50 a day? Native connector. 50–500? Middleware. Over 500? Custom API.
• Process complexity. Simple single-warehouse sales is different from a B2B+B2C model with multiple warehouses and cross-border sales.
• Budget. Native connectors are free or dozens of euros/month. Middleware implementation runs €2,000–8,000 one-time plus operating costs. Custom API is €5,000–20,000.
• Growth plans. If you plan to double revenue in two years, invest in a solution that scales without rewrites. Middleware scales well, custom API scales best.

A fully integrated e-shop saves an average of 15–25 hours of admin work per week. At average employee costs that means ROI within 4 months of go-live.

Every e-shop is different — different stack, different processes, different volume. So there is no universal “out of the box” solution. But there is a proven approach: map the current state, identify the most painful spots, design the integration, and implement it in steps — including AI implementation where it has the biggest impact.