The verdict in three sentences
A medical equipment importer in Amsterdam whose 40 sales reps capture orders in Salesforce and then have them re-keyed into SAP Business One loses about two days of admin work a week and builds up price and stock errors. A two-way integration (customers, items, prices, stock, real-time order creation, error handling) costs in the range of 20,000 to 45,000 EUR and ships in 8 to 12 weeks. The real decision is architectural: off-the-shelf connector, iPaaS middleware or custom build, depending on volume and master data quality.
The hidden cost of double entry
At a medical device importer serving Dutch hospitals and clinics, a typical order carries 15 to 40 lines, batch numbers, expiry dates and contract pricing negotiated per customer or purchasing group. When a sales assistant copies the order from Salesforce into SAP Business One, every line is a chance to go wrong: wrong item code, list price instead of contract price, stock already allocated to another customer.
| Metric | Double entry today | After integration |
|---|---|---|
| Orders per week | 180 | 180 |
| Re-keying time per order | 5 min | 0 (created automatically) |
| Weekly admin time | about 15 h, or 2 days | under 2 h reviewing rejects |
| Price or item error rate | 3 to 5 % of orders | under 0.5 % |
| Stock visible to sales reps | Monday Excel export | Real time or every 15 min |
| Order to picking lead time | D+1 to D+2 | Same day |
A rep promising delivery on stock that is already sold means an unhappy hospital buyer and sometimes a contractual penalty. The value lies as much in reliable stock data as in the hours saved.
Three architectures and their costs
| Option (2026 ballpark, Netherlands) | Setup cost | Subscription or running cost | When to choose it |
|---|---|---|---|
| Off-the-shelf connector | 20,000 to 28,000 EUR (configuration) | 400 to 1,200 EUR per month | Standard flows, few business rules |
| iPaaS middleware (Boomi, Workato, Make Enterprise) | 28,000 to 38,000 EUR | 800 to 2,500 EUR per month | More systems to connect later |
| Custom build on SAP B1 Service Layer and Salesforce APIs | 32,000 to 45,000 EUR | EU hosting, maintenance quoted to scope | Complex pricing, batches, expiry |
| Delivery time | 8 to 12 weeks |
In the Netherlands the main constraint is regulatory rather than currency: medical device traceability under the EU MDR means batch and serial numbers must flow correctly from SAP B1 to delivery documents. A custom integration built on SAP B1's Service Layer and the Salesforce REST API handles batch, serial and expiry rules more precisely, and avoids a recurring iPaaS licence that can exceed 25,000 EUR over three years.
What the integration must cover
The minimum scope is five flows. Customers are created in Salesforce and pushed to SAP B1 after finance validates VAT number and KvK registration. Items and prices flow from SAP B1, the master, to Salesforce. Available stock is published per warehouse. Orders approved in Salesforce create a sales order in SAP B1 and get the document number back. Delivery and invoice status flows back to the rep.
The most underestimated part is error handling: unknown item, blocked customer, price outside tolerance. Every reject must land in a readable queue with an alert to the right person, not vanish into a technical log. Budget 20 to 25 % of the project for this and for cleaning master data upfront.
For lighter automation options, read our piece on moving from Zapier to self-hosted n8n or see our custom web applications.
Mini case study
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Sanne, CIO of a medical equipment importer in Amsterdam Zuidoost, runs 40 sales reps and 180 orders a week. She chooses a custom integration at 38,000 EUR, delivered in 10 weeks.
- Re-keying time saved: 15 hours a week, about 690 hours a year over 46 weeks.
- Loaded cost of a sales assistant: about 42 EUR an hour, so 28,980 EUR a year saved on data entry alone.
- Errors avoided: 4 % of 8,280 annual orders, or 331 fewer corrections. At 120 EUR average per error (return, credit note, transport, time), that is 39,720 EUR a year.
- Total estimated gain: 68,700 EUR a year, a payback of about 7 months, before counting sales saved by reliable stock data.
FAQ
Salesforce or SAP Business One: which is the master?
SAP B1 stays the master for items, prices, stock and accounting; Salesforce owns opportunities and orders. This rule prevents about 90 % of sync conflicts.
Does the sync need to be real time?
For orders, yes, within seconds. For stock, an update every 5 to 15 minutes is enough in most cases and reduces load on the SAP server.
What happens if SAP rejects an order?
It goes into a visible error queue with the reason (blocked customer, unknown item, price out of tolerance) and an alert to the owner. The target is to clear every reject within 24 h.
Can the integration stay in the EU?
Yes. A custom build can run on EU hosting, keeping customer and traceability data under GDPR and avoiding transfers to third countries.
How long until go-live?
Plan 8 to 12 weeks, including 2 to 3 weeks of master data cleanup and 2 weeks of user acceptance testing with sales reps.
Let's scope your project. We map your Salesforce and SAP Business One flows, pricing rules and error handling for go-live in 8 to 12 weeks. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
