The verdict in three sentences
Exposing SAP in a modern web portal is a 30,000-90,000 EUR project in 2026, and half the cost comes from the integration, not the interface. The real trade-off is architectural, not technical: an integration middleware (SAP Integration Suite, MuleSoft) to decouple and secure, or a direct API (OData/BAPI) to move fast on a narrow scope. For a large account with many flows, middleware pays off from the second integration; for a single-purpose portal, the direct API is more rational.
Middleware vs direct API: the true cost
Calling SAP S/4HANA OData services directly is appealing: no extra layer, minimal latency. But it couples your portal to SAP's internal structure, exposes technical credentials and complicates version upgrades. A middleware layer adds 8,000 to 25,000 EUR but becomes a reusable platform.
| Criterion | Direct OData/BAPI API | Middleware (Integration Suite) |
|---|---|---|
| Upfront cost | 30,000-45,000 EUR | 55,000-90,000 EUR |
| Timeline | 4-5 months | 5-7 months |
| Security (SAP exposure) | High to manage | Isolated by the layer |
| Reusability | Low | High (multi-app) |
| Annual maintenance | 6,000-10,000 EUR | 10,000-18,000 EUR |
| Resilience to SAP upgrades | Fragile | Robust |
Real-time or batch: the decisive question
Synchronisation drives cost as much as experience. A nightly refresh is enough for a product directory; an order-tracking portal needs real time via SAP events.
| Sync mode | Latency | Relative cost | Use case |
|---|---|---|---|
| Nightly batch | 24 h | Base | Catalogues, master data |
| Hourly batch | 1 h | +15% | Stock, pricing |
| Event-driven (SAP webhooks) | < 5 s | +30-40% | Orders, deliveries |
| OData on demand | Immediate | +20% | Ad-hoc lookups |
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.
Thomas, CIO of a 400-employee industrial distributor in London, wants a customer portal exposing stock and orders from SAP S/4HANA. Chosen quote: 62,000 EUR with a middleware layer, event-driven sync on orders and hourly batch on stock. Before the project, 3 staff answered tracking requests: estimated 1.5 FTE redeployed, roughly 55,000 EUR/year. Add connector maintenance at 14,000 EUR/year. Payback (2026 order of magnitude): around 18 months, before counting fewer delivery disputes.
FAQ
Do we have to use SAP Integration Suite? No. For a single app and a simple flow, a custom OData connector is enough and saves 15,000-25,000 EUR. Middleware becomes relevant from 2-3 integrations or strong security requirements.
How long for a first SAP portal? Expect 4 to 7 months depending on flow complexity and the availability of your internal SAP teams, which are often the real scheduling bottleneck.
Is real time essential? Rarely everywhere. Reserve event-driven sync for high-value data (orders, deliveries) and keep hourly or nightly batch elsewhere, cutting the bill by 20-30%.
Who maintains the connector after delivery? Maintenance of 6,000 to 18,000 EUR/year covers SAP upgrades, fixes and monitoring. Without it, an S/4HANA version bump can silently break your flows.
Can we secure without re-exposing everything? Yes: the integration layer filters fields, applies least privilege and logs every call, without exposing the SAP core directly to the web.
Let's scope your project. Describe your SAP flows (OData, BAPI, IDoc), volume and real-time or batch needs, indicative budget 30,000-90,000 EUR, timeline 4-7 months. 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.
