Skip to content

Solution

Shop and ERP integration

We connect your online shop to the ERP: shop orders automatically become sales orders, stock levels and prices in the shop are up to date, and delivery status and invoices flow back. The interface is monitored, so that a failure is noticed before customers complain.

Who it is for: For retailers and manufacturers with Shopify, WooCommerce or Medusa and an ERP such as Abacus, Business Central or SAP Business One.

Starting point

How the process runs today

The shop runs, the ERP runs, and a person sits in between. Orders are exported or keyed in, stock levels updated by hand once a day. Prices are maintained in two places. With every additional order, the error rate rises.

What it costs

  • Overselling, because the shop shows stock that no longer exists.
  • Wrong prices after a price change, because one system was forgotten.
  • Customers ask about the delivery status, which only the ERP knows.
  • Seasonal peaks can only be handled with overtime.

Process

What the process looks like afterwards

  1. 01

    Order

    The customer orders in the shop and the payment is confirmed.

  2. 02

    Validation

    Address, customer number and items are validated, and duplicates are intercepted.

  3. 03

    Order in the ERP

    The sales order is created automatically, including customer, terms and shipping method.

  4. 04

    Stock and price

    Availability and prices flow continuously from the ERP into the shop.

  5. 05

    Status back

    Delivery note, tracking number and invoice appear in the customer account.

Shop and ERP integration: which system leads for which data?

For each type of data, there is exactly one system of record. The ERP leads for items, prices and stock levels. The shop leads for orders and customer accounts. Information is changed only in its system of record. The other system takes it over automatically.

If a price is corrected in the shop rather than in the ERP, the next synchronisation overwrites it, or the customer sees a different price from the one on the invoice. The table shows the usual split. In the preliminary study we define it bindingly for your ERP.

For business customers, the customer number and terms usually come from the ERP. The shop leads for the login, contact persons and delivery addresses.

Which data flows in which direction

Type of dataSystem of recordDirectionTypical frequency
Items and variantsERPfrom the ERP to the shopat intervals, for example nightly or hourly
Prices, customer prices and volume tiersERPfrom the ERP to the shopat intervals and immediately after a price change
Stock levels and availabilityERPfrom the ERP to the shopusually within seconds
OrdersShopfrom the shop to the ERP, as a sales orderwithin seconds of payment confirmation, as a target
Customer accounts and delivery addressesShopfrom the shop to the ERPwith the first order and with every change
Order status and tracking numberERPfrom the ERP to the customer account in the shopwith every status change
Invoices and credit notesERPfrom the ERP to the customer account in the shopafter invoicing
Cancellations and returnsdepends on the processboth directionsimmediately, rules defined in the preliminary study
Usual split as a guideline. What applies in your case depends on your ERP and your processes.

Monitoring and error handling: what happens if the integration fails?

A failure is not an exception. ERP updates, maintenance windows or a disrupted connection happen in every business. What matters is that no order is lost, none ends up in the ERP twice, and someone knows in good time. Four mechanisms take care of this:

  • Queue: every order is first stored safely. If the ERP cannot be reached, the shop keeps selling, and the orders are delivered as soon as the ERP responds again.
  • Automatic retry: if a transfer fails, the integration tries again several times at increasing intervals. Short disruptions resolve themselves without anyone stepping in.
  • Protection against duplicate orders: every order carries a unique number. Before creating it, the integration checks whether the sales order already exists in the ERP. Even after a retry, it is created only once.
  • Alerts in plain language: if retrying does not help, or an item number is missing in the ERP, for example, the person responsible receives an alert stating the reason. Once corrected, the order is resent at the click of a button.

Project timeline: a shop and ERP integration in 6 to 14 weeks

  1. Weeks 1 to 3

    Preliminary study with cost ceiling

    We clarify data types, systems of record, special cases and access to the ERP. You receive a cost ceiling. Fixed price CHF 4,000 to 9,000.

  2. From week 3

    Mapping the data

    Item numbers, customer numbers, shipping methods, payment methods and VAT rates from shop and ERP are mapped to each other. Gaps become visible before any code is written.

  3. From week 4

    Delivery in stages

    Orders flow into the ERP first, then stock levels and prices, and finally status and invoices back. Each stage is checked in the test environment.

  4. Before go-live

    Testing with real cases

    Your team runs through typical orders and special cases, such as partial deliveries, cancellations, vouchers or customer prices, and signs off the integration.

  5. Weeks 6 to 14

    Go-live

    The switch happens on a quiet day. During the first weeks we watch alerts and processing times particularly closely.

  6. Afterwards

    Operation and maintenance

    Shop and ERP receive updates, and the integration keeps pace. Plan on 15 to 20 percent of the project cost per year for this.

What to prepare for your ERP integration

Access via your ERP partner

The integration needs its own technical user in the ERP with precisely defined permissions. This is usually set up by your ERP partner, who invoices it separately. Find out early who is responsible there, whether licence fees apply and how much lead time they need.

Test environment

Testing never takes place in the live ERP. You need a test company or test installation with a current copy of your master data. The shop also needs a test version, so that test orders do not trigger real deliveries.

Clean item numbers

Every item and every variant in the shop needs exactly one valid item number in the ERP. Export both lists and compare them. Typical findings are missing numbers, old items, duplicate customers and different units, such as pieces in the shop and cartons in the ERP. An integration only transfers errors faster.

Collect special cases

Note down what deviates from the normal case in daily business: partial deliveries, vouchers, collective invoices, returns, orders on account. In the preliminary study, this list becomes the basis for rules and tests.

Responsibility in operation

Name one person who receives the integration's alerts and acts on them, plus a deputy. This person also decides business questions, such as what happens to an order for a blocked item.

Integrations

Which systems are connected

For each type of data we define which system leads. As a rule, the ERP is responsible for items, prices and stock levels, the shop for orders and customer accounts.

ERP and accounting
  • Abacus
  • bexio
  • Odoo
Banking and payments
  • QR-bill
Shop and PIM
  • Shopify
  • WooCommerce
  • Medusa

Make or buy

Off-the-shelf or custom?

Off-the-shelf software is enough if

  • A proven connector exists for your combination of shop and ERP.
  • You sell standard items at list prices.
  • Volume is a handful of orders a day.

Finished products for this case: Ready-made connectors from the ERP vendors and integration platforms such as Make or Zapier.

Custom is worth it if

  • Customer prices, volume tiers or framework agreements have to apply in the shop.
  • Variants, bills of materials or configured products are ordered.
  • Several warehouses, legal entities or currencies are involved.
  • A standard connector exists but is too unreliable or too rigid.

Effort

Price range and duration

Price range
CHF 15'000 to 60'000
Duration
6 to 14 weeks

Non-binding estimate, excl. VAT.

What drives the effort

The effort depends on the ERP's interface, the pricing logic and the number of data types. Transferring only orders and stock levels sits at the lower end.

The price becomes binding after the fixed-price discovery phase.

Your case in numbers

400
6
70
90 %
Hours per year tied up
480
Cost per year today
CHF 33'600
Possible saving per year
CHF 30'200

432 hours freed up for other work

Check the numbers in an intro call

Rough calculation based on your figures. Not a quote.

Shop and ERP integration

Frequently asked questions

Are stock levels and prices synchronised in real time?

Where it pays off. Orders and availability usually sync within seconds, master data and prices at intervals. What matters is what your ERP allows and where delays cost money.

What happens if the ERP is unavailable?

The shop keeps selling. Orders are held in a queue and delivered as soon as the ERP responds again. Failed transfers show up in monitoring and trigger an alert.

What if our system has no interface?

Then there is usually another route: file exports, database access, an import folder or an add-on module from the vendor. We clarify this with your ERP partner before a single franc goes into implementation. If there is no reliable route, we say so.

Let us talk about your case.

20 minutes are enough to find out whether a custom solution is worth it for you.