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
01
Order
The customer orders in the shop and the payment is confirmed.
02
Validation
Address, customer number and items are validated, and duplicates are intercepted.
03
Order in the ERP
The sales order is created automatically, including customer, terms and shipping method.
04
Stock and price
Availability and prices flow continuously from the ERP into the shop.
05
Status back
Delivery note, tracking number and invoice appear in the customer account.
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
- Microsoft Dynamics 365 Business Central
- SAP Business One
- 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
- 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
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.