The verdict in three sentences
Connecting the customer portal of a wholesale SME in Nantes to its Sage ERP costs 12,000 to 30,000 EUR excl. VAT for a clean API layer, plus about 150 EUR a month for monitoring. The choice between file-based sync, direct API and middleware (iPaaS) depends mostly on the Sage version (Sage 100 or Sage X3) and on freshness needs: every 5 minutes is enough for invoices, real time is justified for stock. The realistic timeline is 8 weeks, provided the classic pitfalls are dealt with upfront: licences, master data and error handling.
The problem to solve
A portal that shows neither stock nor invoices generates calls. For a 70-employee SME with 1,200 business customers, the sales admin team receives dozens of requests a day such as "do you have 40 units in stock?" or "can you resend the March invoice?". The integration must expose four flows: available stock per warehouse, customer prices, orders and invoices with payment status.
Files, API or middleware: the comparison
| Criterion | File sync (CSV, SFTP) | Custom direct API | iPaaS middleware |
|---|---|---|---|
| Setup cost | 4,000 to 9,000 EUR excl. VAT | 12,000 to 30,000 EUR excl. VAT | 8,000 to 20,000 EUR excl. VAT |
| Recurring cost | 50 to 100 EUR a month | 150 EUR a month monitoring | 300 to 1,200 EUR a month licence |
| Data freshness | 1 to 4 times a day | Every 5 minutes or real time | 5 to 15 minutes as standard |
| Writing to Sage (orders) | Batch import, risky | Yes, controlled | Yes, depending on connector |
| Error handling | Manual | Log, automatic retry, alert | Dashboard provided |
| Vendor dependency | Low | Low if you own the code | High |
| Timeline | 3 to 4 weeks | 6 to 8 weeks | 4 to 6 weeks |
File export works for a catalogue but becomes a source of errors as soon as orders must flow back into Sage. iPaaS is attractive if you already have several applications to connect (CRM, e-commerce, logistics); otherwise its licence weighs heavily over 3 years.
Sage 100 or Sage X3: what changes
| Technical point | Sage 100 | Sage X3 |
|---|---|---|
| Data access | SQL Server database, Sage 100 business objects or third-party API | SOAP web services and native REST APIs |
| Access licence for integration | 1,000 to 3,000 EUR excl. VAT depending on module | Included depending on contract, sometimes an API user licence |
| Writing orders | Via business objects, never direct SQL | Via web services, business rules enforced |
| Hosting | Often on-premise server, secure access required | Often cloud or managed |
| Integration effort | Medium, depends on customisation | Higher, but more standardised |
| Typical API layer budget | 12,000 to 22,000 EUR excl. VAT | 18,000 to 30,000 EUR excl. VAT |
The most expensive pitfall is still writing straight into the SQL database to save time: it bypasses Sage's rules and breaks upgrades. Other recurring pitfalls are duplicate item records, customer prices kept in spreadsheets outside Sage and no alert when a sync fails overnight.
Mini case study
Claire, CFO of a 70-employee wholesale SME in Nantes running Sage 100, sees her 4-person sales admin team spend 2.5 hours a day answering stock and invoice questions. She approves an API layer at 18,000 EUR excl. VAT plus 150 EUR a month. Gain: 2.5 hours x 220 days = 550 hours a year, valued at 38 EUR per loaded hour, i.e. 20,900 EUR. First-year cost: 18,000 + 1,800 = 19,800 EUR. The project pays back in 11 months, and orders entered by customers themselves cut keying errors by about 70%.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
Can we skip the API and show Sage directly in the portal?
No, exposing the ERP to the internet is a major security risk. The API layer filters data per customer, caches stock and shields Sage from traffic spikes.
Is real time needed everywhere?
No, it is justified for stock and order creation. Syncing every 5 minutes is enough for invoices, which cuts the load on Sage by about 80%.
What happens if Sage is down for maintenance?
The portal shows the latest cached data and queues orders. They are pushed into Sage on restart, with an alert if a line is rejected.
How much does monitoring cost?
Allow about 150 EUR excl. VAT a month for flow monitoring, alerts and 1 hour of support included. Changes (new flow, new field) are priced separately, from 500 to 3,000 EUR excl. VAT.
Will the integration survive a Sage upgrade?
Yes, if it goes through official business objects or web services. Plan 1 to 2 days of regression testing for each major release.
Let's scope your project. Tell us your Sage version, the flows you need and your current portal: we will price the API layer between 12,000 and 30,000 EUR excl. VAT with an 8-week 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.
