Guides

ERP integration: what it is, how it works and what it costs

What ERP integration is, what syncs between the ERP and the webshop, ways to connect, common mistakes, timelines and prices. A guide for Croatian wholesalers and retailers.

Published: November 19, 2026

ServiceWebshop and ERP integration for wholesaleItems, prices, discounts and stock from the ERP into the webshop, orders back without retyping. From €2,500, 2 to 4 weeks.Open

What ERP integration is

ERP integration is an automatic connection between your ERP system (the business software where you keep items, prices, stock, customers and invoices) and the other systems the company uses: the webshop, a B2B portal, the warehouse, a CRM or BI analytics. Once it is in place, data moves both ways on its own and nobody retypes it.

For a wholesaler it usually looks like this: the webshop or B2B portal pulls items, price lists, per-customer discounts and stock from the ERP, and every order a customer places is written back into the ERP as if your sales rep had entered it. The ERP stays the single source of truth; the webshop is a shop window that always shows what the ERP says.

Why a wholesaler without integration loses money

Without an integration, a person sits between the webshop and the ERP. An order arrives by e-mail, through the portal or by phone, and someone retypes it into the ERP, code by code, quantity by quantity. At 40 orders a day and four minutes per order that is about 56 hours a month, a third of one person's working time, spent on retyping.

The consequences cost more than the time: a wrong code or quantity on the delivery note, goods sold through the webshop that are no longer in stock, a customer seeing an old price because nobody updated the webshop after the price list changed. Each of those mistakes costs a return, a complaint or a customer.

What syncs between the ERP and the webshop

A good integration doesn't move everything, but exactly what the business needs, in the right direction and at the right pace. A typical scope for a wholesaler:

  • Items and codes (ERP → webshop): names, units, pack sizes, groups, with variants grouped into products a customer understands.
  • Price lists and per-customer discounts (ERP → webshop): each partner sees their own price, discount and payment terms after logging in.
  • Stock per warehouse (ERP → webshop): refreshed often, so nothing is sold that isn't there.
  • Customers, delivery addresses and credit limits (both ways, depending on where they are kept).
  • Orders (webshop → ERP): with the correct customer and item codes, price and payment method, written exactly once.
  • Statuses, delivery notes and invoices (ERP → webshop): the customer sees in the portal whether goods have shipped and downloads the invoice.

Four ways to connect an ERP

Which way is right depends not on what would be nice, but on what your ERP offers at all. That is why every serious project starts by reviewing the ERP.

  • API: the cleanest path. Data is read and written in real time, with error handling. Most modern ERPs have one, sometimes as an extra module the ERP vendor charges for.
  • File export and import (CSV, XML): the ERP exports items, prices and stock at set intervals and imports orders from a file. Slower than an API, but reliable and often the only option for older systems.
  • Direct database access: reading (more rarely writing) the ERP's database. Fast, but it needs care and agreement with the ERP vendor, because a change in their database can break the link.
  • A middle layer (middleware, EDI): a separate service that translates between systems and holds orders when the ERP is down. Worth it when several channels connect to the ERP: webshop, B2B portal, marketplace, mobile app.

How often data refreshes

Not everything has to be real time, which is good news for cost and stability. Orders go to the ERP immediately. Stock refreshes every few minutes or on demand, when a customer opens an item. Items and price lists change less often, so a few times a day is enough. The pace is agreed per data type, based on what the ERP can handle and how much it matters to the customer.

The most common ERP integration mistakes

Most integrations that fail don't fail on technology, but on details nobody planned for:

  • Duplicate orders: the same request sent twice (a dropped connection, a retry) creates two orders. The fix is idempotency: each request carries a key and is written exactly once.
  • Lost orders while the ERP is down: the order must be kept and sent later, not vanish behind an error message nobody reads.
  • Wrong prices: per-customer discounts, promotions and quantity breaks are calculated in the ERP. The webshop must take them over, not calculate its own.
  • Variants and codes: the ERP often keeps each size and colour as a separate item. Without grouping, the customer sees thousands of near-identical products.
  • Integration without monitoring: when sync stops, someone must find out the same day, not when a customer calls.

ERP systems in Croatia

Croatian companies mostly run domestic and regional ERPs (for example Pantheon, Minimax, e-računi, KISERP) or international systems such as SAP Business One and Microsoft Dynamics 365 Business Central. What matters for an integration is not which ERP it is, but what it offers: an API, data export or database access.

For KISERP by Micronic we have ready-made solutions running in production. For other ERPs, the first step is a short technical review: what the ERP provides, on what terms and what its vendor charges.

ERP integration, fiscalization and e-invoicing

Since 2026 Croatia runs Fiscalization 2.0: invoices to business buyers go out as e-invoices through an intermediary, and invoices to consumers are fiscalized. The integration must know who issues the invoice, the ERP or the webshop, and make sure the same invoice is never issued twice. Usually the ERP issues it and the webshop only shows the document to the customer. When the ERP doesn't, the webshop itself can issue it, with fiscalization and e-invoicing.

What an ERP integration project looks like

With us a project runs in this order, and the client knows what they get at every step:

  • ERP and process review: what is done by hand today, what the ERP offers and what the risks are.
  • Documentation: what syncs, in which direction and how often, with an exact price and timeline.
  • Building the connector and testing it on a copy of the data, never straight on production.
  • Go-live under monitoring, then the first three months of maintenance free.

What ERP integration costs and how long it takes

Connecting an existing webshop to an ERP starts at €2,500 with us and takes 2 to 4 weeks. A B2B portal for wholesale connected to the ERP starts at €8,000 and takes 4 to 6 weeks. The price depends most on what the ERP provides: with a good API the work is faster, without one there is more work on exports and checks. You get the exact amount in a written offer after the review, before paying anything.

How to choose an ERP integration partner

Before signing, ask the contractor these five things. The answers quickly show whether someone builds integrations or just webshops:

  • What happens to an order when the ERP doesn't respond?
  • How do you prevent duplicate orders?
  • Where are discounts and per-customer prices calculated?
  • Who finds out, and how, that sync has stopped?
  • Can you show an integration running in production?

Frequently asked questions

What is ERP integration?
An automatic connection between the ERP and the company's other systems, usually a webshop or B2B portal. Items, prices and stock come from the ERP, and orders go back into it without retyping.
How much does ERP integration cost?
Connecting an existing webshop to an ERP starts at €2,500, and a B2B portal connected to the ERP at €8,000. The exact price depends on what the ERP offers and comes in a written offer after a review.
How long does ERP integration take?
Usually 2 to 4 weeks to connect an existing webshop, or 4 to 6 weeks for a new B2B portal with integration.
Do we have to change our ERP?
Usually not. The integration is built on the ERP you already use. A new ERP only makes sense when the current one gives data neither through an API nor through an export.
Does ERP integration work with Pantheon, Minimax or SAP?
An integration is feasible when the ERP has an API or a data export. For KISERP we have ready-made solutions; for other ERPs the first step is a technical review of what the ERP offers.
What if the ERP is temporarily down?
A well-built integration keeps the order and sends it as soon as the ERP is back, without duplicates. The customer orders normally in the webshop and notices nothing.

Get compliant in 15 minutes

Fiskalizator issues fiscal receipts (JIR/ZKI) and e-invoices - for Shopify, WooCommerce or manually. 14-day free trial.

Tell us what you need. Within 24 hours you get a rough price and timeline

We reply within 24 hours. Your details reach us only and are not used for anything else.