SAP Business One Integration With Shopify, Magento or PrestaShop
Your SAP partner implements and configures SAP Business One. We connect it to your online store, your logistics and your CRM: web orders arrive as sales orders on their own, SAP's stock, prices and price lists rule the store, and shipping labels come out of the ERP itself. We run it in production with Shopify, SendCloud and HubSpot.
- 0 Web orders keyed into SAP by hand at Silicium
- 15 min From SAP stock to the store at Silicium
- 4 Connected systems: Shopify, SAP Business One, SendCloud and HubSpot
- 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 SAP Business One ecommerce integration?
It is the software layer that connects SAP Business One to your online store so web orders reach SAP as sales orders without anyone typing them in, and SAP's stock, customers, prices and price lists reach the store on their own. It is not implementing SAP: it is what comes next, once SAP is up and running and the store has to talk to it.
Summary
Executive Summary
What your SAP partner does, what we do, and what changes day to day.
Search for "SAP consulting" and you will find implementers: companies that install SAP Business One, configure it and train your team. That is your SAP partner's job, and we don't do it. Our work starts where theirs ends: once SAP is running and the online store, the carrier and the CRM need to talk to it.
At Silicium we did it at the most delicate moment: they were rolling out SAP Business One while leaving PrestaShop. We migrated the store to Shopify with its history and built middleware that runs on their own server. Web orders reach SAP on their own; SAP sends stock and customers to the store every 15 minutes and prices and price lists every hour; orders created in SAP appear in the store every 5 minutes, and the warehouse triggers SendCloud shipments from the ERP itself.
The same architecture works with Magento or PrestaShop: the store side changes, the logic doesn't. And if you run a different ERP, our ecommerce ERP integration page explains how we work with Odoo, Business Central, A3, Sage or Holded.
- 5 min SAP-originated orders showing up in the store (Silicium)
- 1 h SAP prices and price lists to the store (Silicium)
- 8 years Of order history migrated from PrestaShop to Shopify (2018-2026)
Why
Your SAP Partner and Us: Who Does What
So there are never two vendors touching the same thing, or a gap between them.
Your SAP partner implements SAP Business One, configures it, manages the licences and supports the ERP. We build and maintain the integration layer and the store: the middleware, the flows with Shopify, Magento or PrestaShop, logistics and CRM. When the integration needs something inside SAP, such as a new field or an order status for the warehouse to set, we agree it with your partner and document it. At Silicium, the team also has custom reports on batches, new customers and sales inside SAP, and the discounts applied in SAP reach Shopify with the final price.
- Your partner Implementing SAP
- Kiwop Integrating it
What's included
What We Connect to SAP Business One
The flows running today at Silicium. On your project we decide with you which ones, in which direction and how often.
- Web orders into SAP: every paid order arrives by webhook and becomes a sales order
- Recovery sweep every 30 minutes that picks up any order whose notification never arrived
- Customers: record created or updated in SAP with each order, and SAP customers back to the store
- Stock from SAP to the store every 15 minutes
- Prices, price lists and discounts from SAP with the final price in the store, every hour. What B2B ecommerce needs
- Orders created in SAP (phone, trade customers) visible in the store every 5 minutes
- SendCloud shipments triggered from SAP: carrier, multi-parcel, cash on delivery and customs outside the EU
- PDF label attached to the SAP order and delivery reflected in the store
- HubSpot: every night, SAP's trade customers are synced as companies, with their invoiced revenue and contacts
Key points
What We Connect SAP Business One To
The store, the carrier and the CRM. The integration logic stays the same; the system on the other side changes.
- 01
Shopify
In production at Silicium: orders by webhook into SAP; stock, customers, prices and price lists from SAP to Shopify, and orders segmented by customer type and price list.
- 02
Magento and Adobe Commerce
For large catalogues, multi-store setups or B2B with customer-group pricing. Magento has REST and GraphQL APIs; the flows with SAP are the same as with Shopify: orders into SAP, and stock, prices and price lists back.
- 03
PrestaShop
PrestaShop has its webservice for orders, customers, products and stock, and the SAP integration follows the same logic. If you are thinking of leaving it, at Silicium we migrated to Shopify in the same project, with 99.7% of the order history.
- 04
SendCloud
When the warehouse marks the order as ready in SAP, the shipment is created in SendCloud with the right carrier, parcels and customs documents, and the label comes back to the order as a PDF.
- 05
HubSpot
SAP's trade customers are synced to HubSpot every night as companies, with their invoiced revenue and contacts, so sales works with ERP data.
- 06
Trade Customers and Price Lists
Orders created in SAP visible in the store, customer price lists and discounts with the final price. That is what turns a store into a real B2B channel.
How we work
How We Do It
Flow by flow, with real data, and in step with your SAP partner.
- 01
Flow Inventory and System of Record
Which system owns each piece of data and which way it travels: orders, customers, stock, prices, price lists and shipments. We review with your SAP partner what is needed inside the ERP. The output is a data map and a fixed quote.
- 02
Middleware Design
Webhooks for orders, recovery sweeps, queues and retries when SAP doesn't respond, and a log of every message. We decide with you where it runs: at Silicium, on their own server.
- 03
Development Flow by Flow
First orders into SAP; then stock, customers, prices and price lists back; then shipping and CRM. Each flow is tested on its own.
- 04
Parallel Testing With Real Data
The integration runs against an SAP test database if there is one and in parallel with the manual process, and we compare orders with your team before anyone stops typing.
- 05
Go-Live
Flow by flow, with the warehouse and customer service informed. If there is a store change, the migration is part of the same plan, as at Silicium.
- 06
Monitoring
Alerts when a message fails and the integration covered by our maintenance: when your partner updates SAP or the store's API changes, we adapt it.
Who it is for
Is It Right for You?
It fits when you already run SAP Business One, or are about to, and the store has to talk to it.
Who it's for
- Companies with SAP Business One and an online store whose orders are keyed into SAP by hand.
- Companies rolling out SAP Business One that want the store connected from day one, like Silicium.
- B2B or mixed businesses with price lists and discounts in SAP that must show exactly the same in the store.
- Warehouses that want to trigger shipments and print labels from SAP, without copying addresses.
- Sales teams that need SAP customers in their CRM.
Who it's not for
- Implementing, configuring or licensing SAP Business One: that is your SAP partner's job.
- SAP user training or support: your partner provides that too.
- Stores with few orders and standard processes: an off-the-shelf connector may be enough, and we'll tell you so.
Deliverables
What's In and What's Not
So the split with your SAP partner is clear from the start.
Included
- Data map with the system of record and the frequency of each flow
- Middleware with webhooks, recovery sweeps, queues, retries and logging
- Agreed flows between SAP Business One, the store, SendCloud and HubSpot
- Parallel testing with real data before go-live
- Documentation for your team and for your SAP partner
- Alerts and maintenance of the integration
Not included
- SAP Business One implementation, configuration, licences and support
- SendCloud, HubSpot or store app licences
The proof
SAP Business One Connected in Production
Silicium Laboratories Europe makes organic silicon supplements in Vila-seca and sells them online to consumers and healthcare professionals. In early 2026 its store ran on PrestaShop and it was rolling out SAP Business One. We migrated the store to Shopify with customers, orders since 2018 and store credit, and built middleware in Node.js and TypeScript on their own server. Every paid order reaches SAP as a sales order; SAP sends back stock and customers every 15 minutes, prices and price lists every hour, and phone and trade orders every 5 minutes; the warehouse triggers SendCloud shipments from SAP, and every night trade customers are pushed to HubSpot. SAP Business One was implemented by the client's SAP partner; our work was the integration, the migration and the store.
- 0 Web orders keyed into SAP by hand
- 15 min From SAP stock to the store
- 99.7% Of the PrestaShop order history migrated to Shopify (2018-2026)
- 5.0 Rating on Clutch
For the CTO
CTO Summary
How the SAP Business One integration is built.
The middleware writes to SAP Business One through its official interfaces (Service Layer or DI API, depending on version and installation) and talks to the store through its API and webhooks. Paid orders arrive by webhook and are written to SAP as sales orders; because a webhook can get lost, a periodic sweep picks up anything missing, and every write is designed so that a repeated message never duplicates an order. In the other direction, SAP is the source: stock, customers, prices and price lists are read at the frequency each piece of data needs.
Every message goes into a log, with alerts if something fails. SAP and store credentials are stored encrypted and with minimum permissions, under the controls we are certified for in ISO 27001 and Spain's National Security Framework (ENS). At Silicium the middleware is written in Node.js and TypeScript and runs on the client's server; the code and documentation are theirs.
Technologies
- SAP Business One
- Service Layer
- DI API
- Node.js
- TypeScript
- SQLite
- Shopify
- SendCloud
- HubSpot
- Writes to SAP Business One only through its official interfaces
- Store webhooks plus a recovery sweep every 30 minutes
- SAP as the source of stock, customers, prices and price lists
- A log of every message, plus alerts
- Middleware on the client's server, with code they own
Risks and how we cover them
The Risks We Prevent
What usually breaks when SAP Business One and the store are only half connected.
- 01
Web orders that never reach SAP, or reach it twice
MitigationWebhook plus recovery sweep and writes that don't duplicate, with every order logged.
- 02
Different prices in the store and in SAP for a trade customer
MitigationSAP owns prices, price lists and discounts, and the store receives the final price calculated in SAP.
- 03
An SAP update that silently breaks the integration
MitigationCoordination with your SAP partner before updates, testing, and alerts when a message fails.
- 04
Two vendors passing the buck when something fails
MitigationA written split: SAP belongs to your partner and the integration is ours, with a log that shows where each message stopped.
Technologies
Technologies
What sits on each side of the integration.
- SAP Business One
- Service Layer
- DI API
- Shopify
- Magento / Adobe Commerce
- PrestaShop
- SendCloud
- HubSpot
- Node.js
- TypeScript
- Webhooks
- REST
FAQ
SAP Business One Integration FAQs
What we're asked most before connecting SAP to a store.
What is SAP Business One ecommerce integration?
It is the software layer that connects SAP Business One to the online store: web orders reach SAP as sales orders without being typed in, and SAP's stock, customers, prices and price lists reach the store on their own.
Do you implement SAP Business One?
No. SAP Business One implementation, configuration, licences and support are handled by your SAP partner. We build the integration with the store, logistics and CRM, and coordinate with them when something is needed inside SAP.
Can SAP Business One be connected to Shopify?
Yes. We run it in production at Silicium: Shopify orders reach SAP on their own, stock and customers flow back to the store every 15 minutes, prices and price lists every hour, and orders created in SAP appear in Shopify every 5 minutes.
What about Magento or PrestaShop?
Yes. The logic is the same: orders into SAP, and stock, customers, prices and price lists back. What changes is the API on the store side: REST and GraphQL in Magento, the webservice in PrestaShop.
What gets synced, and how often?
At Silicium: orders when paid, with a sweep every 30 minutes; stock and customers every 15 minutes; prices and price lists every hour; SAP-originated orders every 5 minutes; shipments when the order is marked ready; and trade customers to HubSpot every night. On your project, the frequency of each piece of data is set in the inventory.
How does it connect to SAP Business One technically?
Through middleware that talks to the store's API and writes to SAP through its official interfaces, the Service Layer or the DI API depending on version and installation. No writing directly into SAP's database.
Off-the-shelf connector or custom middleware?
If your processes are standard, a connector may be enough and we'll tell you so. Middleware pays off when there are customer price lists, orders created in SAP, shipments triggered from the ERP or a CRM, as at Silicium.
What happens if SAP is unavailable?
Messages stay queued and are retried when SAP comes back. If a store notification gets lost, the periodic sweep picks it up. Everything is logged and, if something fails repeatedly, an alert goes off.
Where does the middleware run?
Wherever we agree with you. At Silicium it runs on the client's own server, next to their SAP. The code and documentation are yours.
How much does SAP Business One integration cost?
It depends on the flows, the store and whether logistics and CRM are involved. We start with the flow inventory and give you a fixed quote. SAP implementation and licences are separate, with your partner.
Who maintains the integration when SAP is updated?
We do, as part of our maintenance. We coordinate with your partner before each SAP update and test the flows before and after.
Next step
Tell Us How Your SAP and Store Are Set Up
A 30-minute video call with the person who will build the integration. If a 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