Services
Integrations
Interfaces that connect your systems so that data is entered only once.
We build interfaces between ERP, shop, bank, CRM and specialist applications so that data flows automatically. Every interface is monitored and logged, and errors trigger an alert. That puts an end to retyping between systems, without you having to change your ERP.
Typical triggers
Typical triggers
Clients get in touch when one of these situations arises.
- 01Orders from the shop are transferred into the ERP by hand.
- 02Incoming payments are matched to open items manually.
- 03A new system is being introduced and has to talk to the existing ones.
- 04An existing interface fails regularly and nobody notices.
Integrations
What you get
Interface concept
Which data flows when and in which direction, and which system leads.
Robust implementation
Queues, retries and protection against duplicate postings.
Monitoring and alerting
A dashboard shows the current state, and errors are reported before your customers notice them.
Coordination with your ERP partner
We sort out access, test environment and approvals directly with the vendor or integrator.
In practice: SAP integration for Bandex's B2B shop
At textile manufacturer Bandex in Vorarlberg, items, prices, stock levels and product images flow automatically from SAP into the new B2B shop. Nobody maintains data twice, and orders are confirmed to the customer and the sales team without anyone retyping them.
The connection is built to be replaceable: if Bandex changes its ERP later, only the integration is swapped, not the shop.
- 795 items with prices from SAP
- Product images and attributes straight from the ERP
- Test orders running through since October 2026
Off-the-shelf connector or a custom interface?
An off-the-shelf connector is enough when
- there is a proven connector for your combination of shop and ERP
- you sell standard items at list prices
- there are only a few orders a day
- an outage of a few hours is annoying but not expensive
A custom interface pays off when
- customer prices, volume tiers or framework agreements have to apply
- variants, bills of materials or configured products are ordered
- several warehouses, companies or currencies are involved
- an outage costs revenue or customer trust
Price ranges by option
| Option | Price range | Note |
|---|---|---|
| Integration platform such as Zapier, Make or n8n | Subscription from around USD 20 per month | plus setup, for simple cases |
| Simple interface for one data type | CHF 8,000 to 25,000 | for example only orders into the ERP, 4 to 10 weeks |
| Shop and ERP interface | CHF 15,000 to 60,000 | orders, stock, prices and status, 6 to 14 weeks |
| Each additional system integration | CHF 3,000 to 15,000 | for example shipping or point of sale |
| Maintenance and operation | 15 to 20 % of project costs | per year |
Integrations
Approach
01
Trigger
An event in one system, for example an order or an incoming payment.
02
Validation
Data is validated and checked for duplicates.
03
Translation
Fields, codes and formats are converted into the language of the target system.
04
Handover
The target system receives the data. If that fails, the transfer is retried.
05
Log
Every transfer can be traced, and errors trigger an alert.
Matching solutions
Matching solutions
Specific business cases with process and price range.
Effort
Price range
- Price range
- CHF 8'000 to 60'000
- Duration
- 4 to 12 weeks
Non-binding estimate, excl. VAT.
What drives the effort
Connecting to an ERP with a documented API sits in the lower range. It takes more effort with older systems that have no API, with two-way synchronisation and with high volumes.
Technologies
- REST / GraphQL
- EBICS
- ISO 20022
- C# / .NET
- n8n
Integrations
Frequently asked questions
How much does an integration between an online shop and an ERP cost?
A shop-to-ERP integration costs CHF 15,000 to 60,000 and takes 6 to 14 weeks. A simple integration for a single data type, such as sending orders to the ERP, costs CHF 8,000 to 25,000. The main factors are the ERP's interface, your pricing logic and the number of data types. Maintenance and operation add 15 to 20 percent of the project cost per year.
Is Zapier or an off-the-shelf connector enough to link our shop and ERP?
Yes, if there is a proven connector for your shop and ERP, you sell at list prices and you handle only a few orders a day. Subscriptions for integration platforms start at around USD 20 per month, plus setup. As soon as customer-specific prices, variants or multiple warehouses come into play, a custom integration is the more robust choice.
What does our ERP partner need to contribute to the integration?
Usually they set up API access and permissions and provide a test environment. With some ERP systems they also add fields or build a custom API. They bill this work separately, so it belongs in the budget from the start.
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.
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 does a project with Natter Solutions cost?
A single automation or interface starts at around CHF 8,000. Business applications such as customer portals or the replacement of an Excel solution usually come to between CHF 25,000 and 100,000, larger platforms more. Every solution page shows a price range. It becomes binding after the discovery phase, which you receive at a fixed price.
Let us talk about your case.
20 minutes are enough to find out whether a custom solution is worth it for you.