The verdict in three sentences
A connector between Sage X3 and a B2B e-commerce site costs 15,000 to 45,000 EUR excluding VAT in 2026, depending on pricing complexity and the number of data flows. The right architecture is almost always hybrid: customer prices calculated synchronously at basket time, stock and catalogue asynchronously every 5 to 15 minutes. What derails projects is not development but acceptance testing, 4 to 8 weeks, because every X3 pricing rule must be checked against real cases.
What the connector must do
A merchant selling online to professionals needs the site to show exactly what a sales rep would see in Sage X3: available stock per warehouse, the customer's net price after discounts, payment terms and the authorised credit limit. In the other direction, every web order must land in X3 as a normal sales order, with the right customer account, warehouse and VAT code, without re-keying by the sales admin team.
| Flow | Direction | Recommended frequency | Complexity | Indicative cost (EUR excl. VAT) |
|---|---|---|---|---|
| Item catalogue and attributes | X3 to site | Once a day + on change | Low | 3,000 to 6,000 |
| Stock per warehouse | X3 to site | Every 5 to 15 minutes | Medium | 3,000 to 7,000 |
| Customer prices and discounts | X3 to site | Synchronous at basket or nightly | High | 5,000 to 15,000 |
| Customer accounts, credit, contacts | X3 to site | Hourly | Medium | 2,000 to 5,000 |
| Web orders | Site to X3 | Real time or every 5 minutes | Medium | 3,000 to 7,000 |
| Statuses, delivery notes, invoices | X3 to site | Every 15 to 30 minutes | Low | 2,000 to 5,000 |
The total ranges from 18,000 EUR for a merchant with simple pricing to 45,000 EUR for a multi-company, multi-warehouse business with cascading pricing conditions.
Synchronous or asynchronous: the choice that drives performance
Depending on the version, Sage X3 exposes data through legacy SOAP web services and a more recent GraphQL API. Querying X3 live on every page view is tempting but fragile: an ERP slowdown makes the site unusable. Copying all data to the site every night is robust but shows wrong stock during the day.
| Criterion | Synchronous (direct X3 call) | Asynchronous (scheduled feeds) | Recommended hybrid |
|---|---|---|---|
| Customer price freshness | Exact | Up to 24 h lag | Exact at basket |
| Stock freshness | Exact | 5 to 15 minutes | 5 to 15 minutes |
| Page load time | 1.5 to 4 s | 0.3 to 0.8 s | 0.3 to 0.8 s, basket 1 to 2 s |
| Dependency on X3 availability | Total | None | Limited to basket |
| Load on X3 server | High | Low and scheduled | Moderate |
| Development cost | Medium | Medium | +10 to 15% |
| Best fit | Under 200 orders a month | Simple catalogue, public prices | B2B trading with negotiated prices |
In the hybrid approach, the site shows a base price calculated overnight, then queries X3 once at basket time for the exact net price. If X3 does not respond within 3 seconds, the order is accepted at base price with a note "price confirmed by sales admin".
Realistic timelines
| Phase | Duration | Watch point |
|---|---|---|
| Scoping pricing rules and flows | 2 to 3 weeks | Inventory of specific conditions in X3 |
| Connector development | 4 to 8 weeks | X3 version and available web services |
| Acceptance testing on real data | 4 to 8 weeks | 50 to 100 customer cases checked by sales admin |
| Pilot with 20 to 30 customers | 3 to 4 weeks | Price and stock discrepancies |
| Annual maintenance | ongoing | 12 to 18% of connector, X3 updates |
In total, allow 3 to 5 months from scoping to opening to all customers.
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.
Nicolas, CIO of a building materials merchant in Bordeaux, manages 1,800 trade customers on Sage X3. The existing site receives 80 orders a day, re-keyed by hand by sales admin in 7 minutes each, i.e. 2,050 hours a year. At 38 EUR per loaded hour, re-keying costs 77,900 EUR. Price errors affect 3% of the 17,600 annual orders, at 60 EUR handling each, i.e. 31,700 EUR.
The hybrid connector costs 32,000 EUR, plus 5,000 EUR of annual maintenance. It automates 85% of re-keying (66,200 EUR saved) and removes 80% of price errors (25,400 EUR). Annual gain: 91,600 EUR, minus maintenance, i.e. 86,600 EUR net. Payback in about 4.5 months.
FAQ
Do we need a recent version of Sage X3?
No, but it helps. V12 and later expose a GraphQL API that cuts development by 15 to 20%. On older versions, SOAP web services work, with a budget at the top of the range.
Can we use an off-the-shelf connector?
Yes, packaged connectors exist for Magento, Shopify or PrestaShop, billed 300 to 1,200 EUR per month. They handle stock and orders well, but cascading customer pricing often needs 8,000 to 15,000 EUR of customisation.
Which stock sync frequency should we choose?
Every 5 minutes if you sell fast movers or limited quantities, every 15 minutes otherwise. Beyond 30 minutes, unshown stockouts generate customer calls.
What happens if Sage X3 is down?
With the hybrid architecture, the site stays browsable and orders are queued, then pushed as soon as X3 is back, usually within 10 minutes.
How much does maintenance cost?
Allow 12 to 18% of connector cost per year, i.e. 2,000 to 8,000 EUR, to follow X3 updates and fix edge cases.
Let's scope your project. Tell us your Sage X3 version, customer count and pricing rules: we will price the connector and B2B platform with an indicative budget and a 3 to 5 month plan. 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.
