The verdict in three sentences
A SAP-to-web-app integration costs between 20,000 and 50,000 EUR in 2026 for a standard case via API/BAPI, and 60,000 to 120,000 EUR for real-time multi-flow scenarios. The real hidden cost is not the initial build but the orchestration (iPaaS 500-2,500 EUR/month) and flow maintenance (15-20 %/year) after each upgrade. A CIO who budgets only the project, not the run, underestimates total cost by 30-40 % over three years.
What the budget actually covers
Connecting a new web app (customer portal, B2B e-commerce, configurator) to SAP means synchronizing four data families: items, stock, orders and customers. Each flow has a direction (SAP to web, web to SAP, or bidirectional), a frequency (nightly batch, near real-time, event-driven) and business rules.
| Integration scope | Flows covered | 2026 range (EUR) | Timeline |
|---|---|---|---|
| Standard one-way | Items + stock (SAP to web) | 20,000 - 32,000 | 8-10 wks |
| Standard bidirectional | + orders + customer accounts | 32,000 - 50,000 | 10-12 wks |
| Advanced multi-flow | + customer pricing, balances, deliveries | 55,000 - 85,000 | 12-14 wks |
| Real-time critical | All flows + event-driven + high availability | 85,000 - 120,000 | 14-16 wks |
The gaps come from SAP version (ECC vs S/4HANA), BAPI/OData availability, master-data quality and the number of mapping rules.
Middleware, direct connection or iPaaS
The architecture choice weighs heavily on cost of ownership. A direct connection (the app calls SAP BAPI/OData) is cheapest to build but most fragile to upgrades. A middleware/iPaaS (an orchestration layer between SAP and the app) costs more upfront but isolates systems and stabilizes the run.
| Approach | Upfront cost | Recurring cost | Robustness | When to pick it |
|---|---|---|---|---|
| Direct API/BAPI connection | Low (15-30 kEUR) | None (excl. maintenance) | Medium | 1-2 simple flows, tight budget |
| Custom middleware | Medium (30-60 kEUR) | Hosting 150-600 EUR/month | High | Rich business logic |
| iPaaS (SAP BTP, Boomi, MuleSoft) | Medium-high | 500-2,500 EUR/month | Very high | Multi-system, real-time |
| Batch ETL (nightly) | Low-medium | 100-400 EUR/month | Good (non real-time) | Slow-changing catalog |
Then budget 15-20 % of the project cost per year for maintenance: fixing flows after SAP upgrades, adding fields, handling rejects and monitoring.
Mini case study
Claire, CIO of a 240-person industrial mid-cap in Lyon, launches a B2B ordering portal for her 600 resellers. She picks custom middleware syncing items, near real-time stock, orders and customer pricing: quote 58,000 EUR, 13-week timeline. Flow hosting: 400 EUR/month. Annual maintenance at 17 %: 9,860 EUR/year.
Before, 3 people rekeyed orders received by email and phone: around 180 hours/month at a loaded 32 EUR/h, i.e. 5,760 EUR/month. The portal removes 80 % of that data entry, saving 4,600 EUR/month (55,200 EUR/year). Payback on project + run in about 15 months, before counting the drop in order errors.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
Do I really need an iPaaS to connect to SAP?
No. For 1-2 simple, non real-time flows, a direct connection or a batch ETL at 100-400 EUR/month is enough. An iPaaS (500-2,500 EUR/month) is justified once you wire several systems or require real-time with high availability.
Does S/4HANA change the budget versus ECC?
Yes, usually downward on greenfield work. S/4HANA exposes modern, documented OData APIs that cut development time by 15-25 % versus legacy ECC BAPIs, but an in-progress migration can freeze or complicate flows.
How much is annual flow maintenance?
Budget 15-20 % of the project cost per year. On a 50,000 EUR integration, that is 7,500 to 10,000 EUR/year, mostly to absorb SAP upgrades and field changes.
What is a realistic timeline for a first production release?
From 8 weeks for a one-way items/stock flow to 16 weeks for real-time multi-flow. The bottleneck is rarely code: it is master-data quality and the availability of your internal SAP team.
Can we start small then expand?
Yes, and it is recommended. Deliver the most profitable flow first (often items + stock), stabilize it, then add orders and customer pricing. This spreads the budget and de-risks the project.
Let's scope your project. Tell us your SAP version, priority flows and order volumes, and we will frame the architecture (direct, middleware or iPaaS) plus an indicative budget. 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.
