Ecommerce ERP Integration That Works Both Ways
We connect your ERP to Shopify, Magento, PrestaShop or WooCommerce so web orders flow in on their own, the ERP's stock and price lists rule the store, and shipments go out without anyone retyping addresses. With middleware that logs every message and retries when something fails, not a connector nobody understands. We run it in production with Shopify and SAP Business One.
- 0 Web orders keyed into SAP by hand at Silicium
- 15 min From ERP stock to the store at Silicium
- 4 Connected systems: store, ERP, carrier and CRM
- 01 · Catalogue Products and prices in sync
- 02 · Experience Search, product page and cart
- 03 · Payment Gateways and anti-fraud
- 04 · Order ERP, stock and logistics
- 05 · Measurement Conversion and margin
- 06 · Operation Your team sells, the system scales
- Every sale refines the catalogue
Definition
What is ecommerce ERP integration?
Ecommerce ERP integration connects your ERP and your online store so data moves between them on its own: web orders and customers reach the ERP without anyone typing them in, and stock, prices, price lists and shipping status flow back from the ERP to the store. Each piece of data has one system of record, one direction and one sync frequency.
Summary
Executive Summary
What an ERP integration fixes and what changes day to day.
The symptoms are usually the same: someone copies every web order into the ERP, someone else updates store stock from a spreadsheet, and trade customers' price lists live somewhere other than where they buy. It works while orders are few. Then come typing errors, sales of out-of-stock products and customers who see a price that isn't theirs.
A well-built integration first decides which system owns each piece of data: usually the ERP for stock, prices, price lists and trade customers, and the store for web orders. Then it moves each piece of data in its direction and at its frequency: orders as soon as they are paid, stock every few minutes, prices every hour. And it keeps a log of every message, with retries and a sweep that picks up anything lost, so nobody has to guess whether an order arrived.
That is what we built for Silicium: its Shopify store connected to SAP Business One, SendCloud and HubSpot. Web orders reach SAP on their own, stock flows down to the store every 15 minutes and shipping labels come out of the ERP itself. We don't implement ERPs: your implementation partner does that. Our work is the layer that connects it to the store, logistics and CRM, and the store itself.
- 5 min SAP-originated orders showing up in the store (Silicium)
- 1 h ERP prices and price lists to the store (Silicium)
- 30 min Sweep that recovers orders whose notification never arrived
What's included
What We Sync Between Your ERP and Your Store
The usual flows. On each project we decide with you which ones you need, in which direction and how often.
- Orders from the store to the ERP as soon as they are paid, as sales orders nobody has to type in
- Customers: record created or updated in the ERP with each order, and ERP customers back to the store
- Stock from the ERP to the store every few minutes, so you don't sell what you don't have
- Prices and price lists: customer or group price lists and ERP discounts, with the final price in the store. Key in B2B ecommerce
- Orders created in the ERP (phone, sales reps, trade customers), also visible in the store
- Shipping: the warehouse marks the order as ready and the shipment is created with the carrier, label included
- Statuses: ready, shipped and delivered, reflected in the store without manual updates
- Invoices: issued by the ERP, which is what must comply with Spain's Verifactu and e-invoicing rules; the integration takes the data wherever it is needed
- CRM: ERP customers and companies in HubSpot, so sales can see what each account buys
Why
Middleware With a Log, Not a Black-Box Connector
The layer that translates between the ERP, the store and everything else.
Between the ERP and the store we put a layer of our own, a middleware, that receives the store's notifications (webhooks), writes to the ERP through its official interfaces and carries stock, prices and customers the other way at the frequency each piece of data needs. Every message is logged: what arrived, what was sent and what the other system replied. If the ERP doesn't respond, the message is retried; if a notification never arrives, a periodic sweep picks it up. It can run on your server, as at Silicium, or wherever we agree with you. And it's yours: code, documentation and access.
- 0 Orders typed
- 4 Systems
- 15 min Stock
Key points
ERPs We Work With
You choose the ERP, or already have one. We connect it through whatever route each product and version supports.
- 01
SAP Business One
The one we run in production: Shopify, SAP Business One, SendCloud and HubSpot at Silicium, covering orders, customers, stock, prices, price lists, shipping and CRM. Full detail on our SAP Business One integration page.
- 02
Odoo
Odoo has an API to read and write orders, products, customers and stock. If your store runs on Shopify, Magento or PrestaShop and you don't want to move it to Odoo's own ecommerce, we connect it to your Odoo through that API.
- 03
Microsoft Dynamics 365 Business Central and Navision
Business Central exposes APIs and web services, and Navision exposes web services. First we check which version you have and whether it runs in the cloud or on your server, because that decides the connection route and who has to give us access.
- 04
A3
A3 has several product families and they don't all integrate the same way. The first thing we do is check which route your product and version support and, if something needs changing in the ERP, coordinate it with your reseller.
- 05
Sage
Same as A3: each Sage product and version connects differently. We check the integration route before quoting and work with your Sage partner when the ERP configuration has to change.
- 06
Holded
Holded has a documented API for contacts, products and sales documents. We know it first-hand: our own platform, Nexo, syncs its invoicing with Holded through that API.
- 07
Logistics and CRM: SendCloud and HubSpot
The integration doesn't stop at the ERP. At Silicium, the SendCloud shipment is created when the warehouse marks the order as ready, handling multi-parcel, cash on delivery and customs outside the EU, and trade customers are pushed to HubSpot every night.
How we work
How We Do It
Flow by flow, with real data, and without switching off the manual process until the new one works.
- 01
Flow Inventory and System of Record
We list every piece of data that moves (orders, customers, stock, prices, price lists, shipments, invoices) and decide with you which system owns each one, which way it travels and how often. We check which integration route your ERP supports. The output is a data map and a fixed quote.
- 02
Middleware Design
Queues so no message is lost, retries when a system doesn't respond, sweeps that pick up whatever slipped through and a log of every message. We decide with you where it runs.
- 03
Development Flow by Flow
We start with the flow that costs you the most hours, almost always orders, and continue with stock, prices, shipping and CRM. Each flow is tested on its own.
- 04
Parallel Testing With Real Data
Before anyone stops typing, the integration runs in parallel with real orders and data, against an ERP test environment if there is one, and we compare the results with your team.
- 05
Go-Live
We switch flows on one by one, with the team informed and a rollback ready. If the project includes changing store platforms, as at Silicium, the migration is part of the same plan.
- 06
Monitoring
Alerts when a message fails or a system stops responding, and the integration covered by our maintenance: if an API or ERP version changes, we adapt it.
Who it is for
Is It Right for You?
It fits when your store sells enough that typing orders and reconciling stock costs hours every week.
Who it's for
- Companies with an online store that copy web orders into the ERP by hand.
- Stores that sell out-of-stock products because inventory is updated late or from a spreadsheet.
- B2B or mixed businesses with customer price lists, group pricing or sales-rep orders that must show in the store.
- Companies rolling out a new ERP or changing store platforms that want the integration solved in the same move.
- Teams that already have a connector and don't know why an order sometimes goes missing.
Who it's not for
- Anyone looking to implement or configure the ERP: your ERP partner or implementer does that; we come in to connect it. The exception is Odoo, which we also implement.
- Stores with few orders and standard processes: an app or connector module may be enough, and we'll tell you so.
- ERPs with no integration route at all (no API, no web services, no file exchange): that has to be solved with the vendor first.
Deliverables
What's In and What's Not
So the scope is clear before we start.
Included
- Flow inventory and data map with the system of record for each piece of data
- Middleware with queues, retries, recovery sweeps and a log of every message
- Development of the agreed flows between ERP, store, carrier and CRM
- Parallel testing with real data before go-live
- Alerts and monitoring of the integration after launch
- Code, documentation and access owned by you
Not included
- ERP implementation, configuration and licences (except Odoo, which we also implement)
- Licences for apps, connectors or third-party services such as SendCloud or HubSpot
The proof
Integrations in Production
At Silicium, which makes organic silicon supplements and sells them to consumers and healthcare professionals, we built middleware in Node.js and TypeScript that runs on its own server and connects its Shopify store to SAP Business One, SendCloud and HubSpot. Every paid order reaches SAP as a sales order, with the customer record created or updated; stock and customers flow down to the store every 15 minutes, prices and price lists every hour, and orders created in SAP appear in the store every 5 minutes. When the warehouse marks an order as ready, the shipment is created in SendCloud and the label comes back as a PDF to the SAP order. SAP was implemented by the client's SAP partner; our work was the integration, the PrestaShop to Shopify migration and the store. And our own platform, Nexo, syncs its invoicing with Holded via API.
- 0 Web orders keyed into SAP by hand
- 4 Connected systems: Shopify, SAP Business One, SendCloud and HubSpot
- 99.7% Of the PrestaShop order history migrated to Shopify (2018-2026)
- 5.0 Rating on Clutch
For the CTO
CTO Summary
How one of our integrations is built.
The store sends a webhook as soon as an order is paid; the middleware validates it, queues it and writes it to the ERP through its official interfaces. Because a webhook can get lost, a periodic sweep compares what was paid in the store with what is in the ERP and recovers anything missing, and every write is designed so that a repeated message never duplicates an order. In the other direction, the ERP is the source: stock, customers, prices and price lists are read at the frequency each piece of data needs.
Everything goes into a searchable message log, with alerts when something fails. ERP and store credentials are stored encrypted and with minimum permissions, under the same controls we are certified for in ISO 27001 and Spain's National Security Framework (ENS). The middleware can run on your server, as at Silicium, and the code is yours.
Technologies
- Node.js
- TypeScript
- Webhooks
- REST
- GraphQL
- SQLite
- SAP Business One
- Shopify
- SendCloud
- HubSpot
- One system of record per piece of data, decided before coding
- Webhooks for what is urgent, sweeps for whatever gets lost
- Queues and retries when a system doesn't respond
- A log of every message, plus alerts
- Code, documentation and access owned by the client
Risks and how we cover them
The Risks We Prevent
What we see in integrations that reach us broken or half-done.
- 01
Orders lost or duplicated between the store and the ERP
MitigationWebhook plus recovery sweep, retries that don't duplicate and a log of every message so you know what happened to each order.
- 02
Selling out-of-stock products because the sync runs late
MitigationFrequency set per piece of data: stock every few minutes (every 15 at Silicium), prices every hour.
- 03
Two systems that both think they own the same data
MitigationThe flow inventory sets one system of record per piece of data before a single line of code is written.
- 04
An ERP or store update that silently breaks the integration
MitigationAlerts when a message fails, testing before every change and the integration covered by maintenance.
Technologies
Systems We Connect
Stores, ERPs, logistics and CRM.
- Shopify
- Magento / Adobe Commerce
- PrestaShop
- WooCommerce
- SAP Business One
- Odoo
- Dynamics 365 Business Central
- Navision
- A3
- Sage
- Holded
- SendCloud
- HubSpot
- Node.js
- TypeScript
FAQ
Ecommerce ERP Integration FAQs
What we're asked most before connecting an ERP to a store.
What is ecommerce ERP integration?
It connects the ERP to the online store so data moves on its own: web orders and customers reach the ERP without being typed in, and stock, prices, price lists and shipping flow back from the ERP to the store. Each piece of data has one system of record and one frequency.
What data is synced between the ERP and the store?
Typically orders, customers, stock, prices and price lists, orders created in the ERP, shipments and their statuses, and the CRM. At Silicium all of them are synced: orders when paid, stock and customers every 15 minutes, prices and price lists every hour, SAP-originated orders every 5 minutes, and trade customers to HubSpot every night.
Which ERPs and stores do you work with?
Stores: Shopify, Magento, PrestaShop and WooCommerce. ERPs: SAP Business One (in production at Silicium), Holded (used by our Nexo platform), and Odoo, Business Central, Navision, A3 and Sage, which we connect through whatever route each product and version supports. We check that before quoting.
Off-the-shelf connector or custom integration?
If your processes are standard and the connector covers your flows, a connector is cheaper and we'll say so. A custom integration pays off when there are customer price lists, orders created in the ERP, your own logistics or a CRM, or when the connector loses orders and nobody knows why.
How often are stock and prices updated?
It's decided per piece of data. Orders travel as soon as they are paid. At Silicium, stock and customers flow to the store every 15 minutes and prices and price lists every hour. If your catalogue turns over fast, stock can sync more often.
What happens if the ERP is down or an order gets lost?
The message stays queued and is retried. If a store notification never arrives, a periodic sweep picks it up: every 30 minutes at Silicium. Everything is logged and, if something fails repeatedly, an alert goes off.
Do you implement the ERP?
No. ERP implementation, configuration and licences are handled by your partner or implementer. We build the integration layer and the store, and coordinate with them when the integration needs something inside the ERP. With one exception: Odoo we also implement ourselves.
How much does ERP integration cost?
It depends on the number of flows, the integration route your ERP supports and how many other systems are involved (carrier, CRM). That's why we start with the flow inventory and give you a fixed quote, not open-ended hours.
Do I need to change my store or my ERP?
No. We connect what you already have. If it coincides with a change, it's done in the same project: at Silicium, the store moved from PrestaShop to Shopify with 99.7% of its order history, and the SAP integration went live on the new store.
Who maintains the integration afterwards?
We do, as part of our maintenance. When the store's API changes or the ERP is updated, we adapt the integration, and alerts tell us if a flow stops working.
Next step
Tell Us Which ERP and Store You Have
A 30-minute video call with the person who will build the integration. If an off-the-shelf connector is enough, we'll tell you.
- No commitment
- Response in 24h
- Custom proposal
Case studies
Projects where we put it to work
Let's talk.
Initial technical consultation
AI, security and performance. Diagnosis with phased proposal.
- NDA available
- Response <24h
- Phased proposal
Your first meeting is with a Solutions Architect, not a salesperson.
Talk to an architect