The verdict in three sentences
For a B2B distributor in Amsterdam, a custom API connector between Sage X3 and the portal costs, as a 2026 order of magnitude, between EUR 15,000 and 30,000 excl. VAT over an 8-week project. The payback comes mainly from removing 70% of manual order entry and ending customer pricing errors. The real risk is not technical: it is the quality of ERP data (item records, discount grids), which must be audited before writing a single line of code.
What the connector must sync, and how often
A technical distribution B2B portal lives on three flows. Stock and prices flow down from the ERP to the portal, orders flow up from the portal to the ERP. Each flow has its own frequency and level of criticality.
| Flow | Direction | Recommended frequency | Typical volume | Criticality |
|---|---|---|---|---|
| Stock per warehouse | ERP to portal | Every 15 minutes | 12,000 SKUs | High |
| Customer prices and discounts | ERP to portal | Nightly + on change | 450 customer grids | Very high |
| Item records and media | ERP/PIM to portal | Daily | 12,000 records | Medium |
| Orders | Portal to ERP | Real time (under 60 s) | 180 orders per day | Very high |
| Statuses and delivery notes | ERP to portal | Every 30 minutes | 220 updates per day | Medium |
| Outstanding balance and credit limit | ERP to portal | Hourly | 900 accounts | High |
The most sensitive point is the net customer price. In Sage X3, discounts often stack by product family, customer and quantity. The connector must either recompute these rules on the portal side or query the ERP on the fly. The second option is more reliable but requires a fast pricing API, with response times under 800 ms.
What a Sage X3 connector costs in 2026: options compared
Three approaches exist on the Dutch and European market. The choice depends on the number of business rules and on whether you want to own the code.
| Option | Initial cost excl. VAT | Annual cost excl. VAT | Timeline | Limits |
|---|---|---|---|---|
| Off-the-shelf connector (iPaaS + plug-in) | EUR 5,000 to 9,000 | EUR 6,000 to 12,000 | 3 to 5 weeks | Poor handling of complex discounts |
| Configured iPaaS platform (Boomi, Make Enterprise type) | EUR 10,000 to 18,000 | EUR 9,000 to 20,000 | 6 to 8 weeks | Vendor lock-in, per-flow pricing |
| Custom connector (Node.js or .NET, Sage X3 Syracuse API) | EUR 15,000 to 30,000 | EUR 2,500 to 5,000 (maintenance + hosting) | 8 weeks | Requires solid documentation |
| In-house development | EUR 25,000 to 45,000 (team time) | Variable | 12 to 20 weeks | Sage X3 skills are scarce |
| Scheduled CSV export (stopgap) | EUR 2,000 to 4,000 | Low | 2 weeks | No real time, frequent errors |
Over three years, custom often ends up cheaper than iPaaS once you go beyond four flows. Example: EUR 22,000 + 3 x 4,000 = EUR 34,000, against EUR 14,000 + 3 x 15,000 = EUR 59,000 for an iPaaS platform billed per flow.
Breaking down an 8-week project
| Week | Deliverable | Share of budget |
|---|---|---|
| 1 | ERP data audit, flow mapping | 10% |
| 2 | API specifications, interface contract, test data sets | 10% |
| 3 to 4 | Stock and item flows, message queue | 25% |
| 5 to 6 | Customer pricing and order upload | 30% |
| 7 | Monitoring, alerts, error recovery | 15% |
| 8 | Acceptance testing, cutover, sales-admin team training | 10% |
Monitoring is often underestimated. A dashboard flagging a flow blocked for more than 30 minutes prevents a sales rep from discovering the issue through an unhappy customer.
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.
Julien, operations director of a technical supplies distributor in Amsterdam (38 employees, EUR 14 M revenue), has about 180 portal orders per day re-keyed into Sage X3. Two sales-admin assistants spend 5 hours a day on it in total, with a 2.5% error rate on SKUs or quantities.
After a EUR 24,000 connector, 70% of that entry disappears: 3.5 hours saved per day, roughly 770 hours per year. At EUR 32 fully loaded per hour, the gain reaches EUR 24,600 per year. Adding fewer credit notes caused by errors (estimated at EUR 6,000 per year), payback is reached in under 10 months, maintenance included.
FAQ
Do you need a specific Sage X3 licence to expose an API?
SOAP web services and the Syracuse REST API are included in most recent contracts, but some integrators charge EUR 1,500 to 4,000 excl. VAT for activation and configuration. Check your version and maintenance contract before pricing.
Can you sync more often than every 15 minutes?
Yes, with event-driven triggers on the ERP side, stock updates can drop below one minute. This usually adds EUR 3,000 to 5,000 excl. VAT to the project and extra load on the Sage server.
What happens if the ERP is down?
A well-designed connector queues orders and replays them automatically once the service is back. No order is lost, and an alert fires after 15 minutes of downtime.
Does the connector work with a different portal later?
If the architecture relies on a documented intermediate API layer, switching portals affects only 20 to 30% of the code. That is a strong argument for custom over a plug-in tied to a single platform.
What does annual maintenance cost?
Plan EUR 2,500 to 5,000 excl. VAT per year for hosting, monitoring and adjustments during Sage X3 updates. A major ERP version upgrade may require 3 to 6 days of adaptation.
Let's scope your project. Send us your list of flows, your Sage X3 version and your order volume: we will price a connector between EUR 15,000 and 30,000 excl. VAT with an 8-week schedule. 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.
