TL;DR

The build vs buy decision for an SAP integration comes down to two questions most SaaS teams skip: which SAP do your customers actually run, and do you need to write data back into it? Off-the-shelf SAP connectors from iPaaS vendors and unified APIs mostly cover S/4HANA with a narrow set of objects, and ECC usually means an on-prem agent your customer's IT team has to install. If you only need read-only data from S/4HANA Cloud, buying is fine. If your customers run ECC or on-prem S/4HANA, or you write orders, invoices or master data, plan to build, ideally with a team that already has SAP experience and its own SAP sandboxes.

You're working on a deal. It's in security review, legal is done, the champion is happy, and then the prospect's IT lead sends one line: "Which SAP release do you support, and how do you connect to it?" If your answer is "we have an SAP connector", the next question is which one, because their SAP is ECC 6.0 with a few hundred custom fields, the finance team's subsidiary runs S/4HANA Cloud, and nothing gets through their firewall without a ticket.

That's the moment a lot of B2B SaaS teams find out that "SAP" isn't one integration target. This article walks through the five real options for getting your product connected to your customers' SAP, what each one actually covers, and how to pick based on where you are. If you need the basics first (which SAP systems exist and which protocols they use), start with our guide to SAP integration services for B2B SaaS teams.


Should you build or buy an SAP integration for your SaaS?

Whether you should build or buy an SAP integration depends on which SAP variants your customers run and whether you need to write data into them, far more than on the price of any connector. A bought connector that covers S/4HANA Cloud reads is a good deal if every SAP customer in your pipeline is on S/4HANA Cloud and you only read. It's a bad deal if half of them are on ECC and your product needs to post supplier invoices.

In practice, B2B SaaS teams pick from five options:

  1. Build in-house with your own engineers.
  2. Buy a connector from an embedded iPaaS or unified API that lists SAP.
  3. Integrate through the customer's SAP Integration Suite, so their SAP team builds the flow.
  4. Get certified and listed on SAP Store, which is a distribution decision layered on top of one of the others.
  5. Outsource the build to a team that does SAP integrations for a living, and own the code.

Most teams end up combining two of these. The rest of this article is about knowing which two before the first SAP deal forces the decision for you.

OPTION WHO BUILDS WHO OWNS THE CODE 01 BUILD IN-HOUSE your engineers YOU 02 BUY A CONNECTOR iPaaS / API vendor THE VENDOR 03 CUSTOMER’S INTEGRATION SUITE customer’s SAP team EACH CUSTOMER 04 SAP STORE / CERTIFICATION on top of a build YOU 05 OUTSOURCE THE BUILD specialist partner YOU
The five options, by who builds the integration and who owns the code. SAP Store and certification sit on top of a build.

Why is SAP integration build vs buy harder than for other ERPs?

SAP integration build vs buy is harder because "SAP" covers several systems with different integration models, and your customers are spread across all of them. With NetSuite or HubSpot, one connector reaches every customer. With SAP, the same customer list can include:

  • SAP ECC 6.0, on-prem, where real business logic lives in BAPIs and RFC function modules, and documents move as IDocs.
  • SAP S/4HANA on-prem or private cloud, which adds OData APIs but still runs most serious write flows through BAPIs and custom code.
  • SAP S/4HANA Cloud Public Edition, where external systems connect through Communication Management: a communication user, a communication system and a communication arrangement built on a predefined or custom communication scenario, as SAP's help documentation describes. SAP's model here is released objects and public APIs published on the SAP Business Accelerator Hub.

Then there's access. On-prem systems usually aren't reachable from your cloud at all. SAP's own answer is the Cloud Connector, an on-prem agent that acts as a reverse invoke proxy so SAP BTP can reach the system without opening the customer's firewall to inbound traffic. Whatever you choose, someone on the customer side installs, configures and approves something, and their timeline becomes yours.

And every SAP install is customized. Z-fields, custom document types, company-code rules and approval workflows mean the same API call behaves differently at two customers. A connector's spec sheet can't show you any of that, which is why most of our SAP scoping calls are about the customer's configuration.

VARIANT RFC / BAPI IDOC ODATA COMM. ARRANGEMENT ON-PREM AGENT ECC 6.0 on-prem S/4HANA on-prem / private S/4HANA CLOUD public edition
One customer list, three SAP variants, different ways in. ECC and on-prem S/4HANA need a path through the customer’s firewall.

How long will ECC customers stay on ECC?

ECC customers can stay on supported ECC until the end of 2027 under mainstream maintenance, and until the end of 2030 if they pay for optional extended maintenance. SAP set those dates in 2020 and restated in October 2026 that they haven't changed. Customers who don't buy extended maintenance move to customer-specific maintenance, which means many will keep running ECC past 2027 anyway.

There's also a later exit for large, complex customers. SAP's "SAP ERP, private edition, transition option" lets customers who have already moved their ECC system into SAP's private cloud by the end of 2030 keep using it until the end of 2033. SAP is explicit that this isn't a maintenance extension, but for your product the effect is the same: some enterprise customers will run ECC-style processes well into the next decade.

For a SaaS company, that has a practical consequence. You won't get to support "ECC, then S/4HANA". You'll support both side by side for years, often at the same customer during a migration. Any option you pick has to handle RFC and IDoc on one side and OData and communication arrangements on the other, or you'll build twice.

2026 2027 2028 2029 2030 2031 2032 2033 ECC mainstream END 2027 ECC extended (paid) END 2030 ECC transition option END 2033 S/4HANA all editions ONGOING TODAY YEARS OF ECC + S/4HANA SIDE BY SIDE
ECC support ends in stages through 2033 while S/4HANA customers keep growing, so most SaaS vendors serve both at once.

What does building an SAP integration in-house actually take?

Building an SAP integration in-house takes SAP-specific skills, a working SAP sandbox, and a per-customer onboarding process, on top of the connector code itself. The code is usually the smallest part.

The skills are the first problem. Your engineers know REST and OAuth. SAP adds BAPI semantics, IDoc segments, SAP authorization objects, and the difference between what an API accepts and what the customer's configuration will post. An engineer can learn this, but they'll learn it on your first customer's production deadline.

The sandbox is the second. You can't test SAP writes against documentation. You need an SAP system configured close enough to your customer's to catch the field that's mandatory in their company code. Getting that environment from a customer or from SAP is often the longest step in the whole project. In our S/4HANA case study, the client's own estimate for sandbox access alone was 4 to 6 weeks.

The third is everything after launch: per-customer connection setup, credentials, field mapping for each customer's custom fields, regression testing when they upgrade, and a second code path when they move from ECC to S/4HANA. We've broken down where those costs come from in what custom API integrations really cost, and why testing against real instances is now the hard part in connector validation.

Building in-house makes sense when SAP is core to your product, you'll have many SAP customers, and you're willing to hire or grow at least one engineer who becomes your SAP person.


Can you buy an SAP connector from an iPaaS or unified API?

You can buy an SAP connector from some embedded iPaaS, unified API and AI integration vendors, but coverage is uneven: most cover S/4HANA through OData with a defined set of objects, write support varies a lot, and ECC access goes through an on-prem agent. Here's what the vendors' own documentation shows today:

VendorTypeSAP coverage in their docsECCWrites
WorkatoiPaaSSAP RFC connector for ECC 6.0, S/4HANA on-prem and private edition, via IDocs and RFC/BAPIYes, through Workato's on-prem agentThrough BAPIs and IDocs, so as far as the customer's SAP allows
PrismaticEmbedded iPaaSSAP ECC connector (BAPI via RFC, IDoc, SOAP); S/4HANA Cloud connector over ODataYes, through an on-prem agentBAPIs on ECC, OData on S/4HANA Cloud
StackOneIntegration platform for AI agentsS/4HANA connector with 555 OData actions; separate SuccessFactors, Concur and Fieldglass connectorsNot listedCreate and update actions for sales orders, products, business partners and suppliers
ParagonEmbedded iPaaSS/4HANA actions for suppliers, customers and supplier invoicesNot listedLimited to those objects
ApideckUnified APISAP S/4HANA Cloud, 15+ data models including customers, suppliers, bills and credit notesNot listedRead and write within those models
RutterUnified APIS/4HANA over OData; the customer's admin activates each OData service first; bank feeds not yet validated on Public EditionNot listedNot stated on its SAP page
Merge, CodatUnified APIMerge lists SAP SuccessFactors for HR and recruiting data only. Neither lists SAP S/4HANA or ECC in its accounting integrationsNoNo SAP ERP writes

A listed connector answers "can we reach SAP?", which is only the first question. Before you buy, check three things against your actual pipeline. First, the exact objects and operations you need, especially writes: a connector that reads business partners won't post a goods receipt. Second, which SAP variants it supports, matched against what your customers run. Third, who installs and maintains the on-prem agent, because for ECC customers that's a conversation with their IT team either way.

Platforms also put a layer between you and SAP. When a posting fails on a customer-specific validation, you're debugging through someone else's abstraction and support queue. For read-heavy, S/4HANA-only use cases that's a fair trade. For write-heavy workflows into a customized ECC, it usually isn't. We compare the platforms in more depth in the best integration platforms and embedded iPaaS in 2026.


Should you integrate through the customer's SAP Integration Suite?

Integrating through the customer's SAP Integration Suite works when that customer has an SAP team willing to build and own the flow, but it hands control of your timeline and integration quality to them. SAP Integration Suite is a subscription on SAP BTP that bundles Cloud Integration, API Management, Event Mesh and related services. The customer licenses it, and SAP prices it per message.

The appeal is that you only expose a clean API on your side and let the customer's SAP team map it into SAP with the tools they already use. Large enterprises with an SAP center of excellence often prefer this. Their team has to learn, validate and approve anything that goes in and out of SAP anyway, including your integration, so many would rather build it themselves from scratch, following their own patterns, naming rules and monitoring.

The cost is that every customer builds their own version. You can't ship a fix once, you can't guarantee how your data lands in SAP, and your go-live date depends on another team's backlog. It also doesn't help the mid-market customer with no SAP team at all. What closes part of that gap is a ready-made integration package published on SAP Store or the SAP Business Accelerator Hub, so the customer's SAP team can reuse and review it instead of starting from a blank page. That's where certification comes in.

EACH TEAM BUILDS YOUR API 3 BUILDS ONE PACKAGE, REUSED SAP STORE PACKAGE 1 BUILD
Through Integration Suite, every customer’s SAP team builds its own flow. A published package gives them one build to reuse and review.

Is an SAP-certified integration or SAP Store listing worth it?

An SAP-certified integration or SAP Store listing is worth it when SAP customers buy through procurement processes that ask for certification, but it's a distribution decision that sits on top of a build. You still need a working integration before anything gets certified or listed.

The certification rules changed in 2026. In January, the SAP Integration and Certification Center announced two tracks. Use-case certification is now limited to SAP's strategic priorities (BTP, Business AI, clean core and public cloud). A new interoperability review is open to all software vendors and comes with a listing on SAP Notes. The new framework launched in Q3 2026.

The SAP Store side runs through SAP PartnerEdge. SAP says a Store listing gives exposure to more than 440,000 SAP customers, and the Build track requires a market-ready solution, an application readiness check and an annual business plan. If your product targets SAP customers as a core segment, that discovery and the procurement credibility are real. If SAP is one of ten ERPs you connect to, a working integration and two happy SAP references will do more for your deals. We cover the process for SAP Store and other marketplaces on our marketplace publishing page.


When does outsourcing an SAP integration make sense?

Outsourcing an SAP integration makes sense when you need SAP depth now, don't want to hire an SAP specialist yet, and still want to own the code at the end. It's the option that separates "who builds it" from "who owns it": a specialist team builds it, the code lives in your repository, and your engineers maintain it or hand it back for changes.

The real advantage is starting point. We maintain our own sandbox environments for almost every SAP product and version, including SAP S/4HANA, ECC, Business One, SuccessFactors and Ariba, as well as NetSuite, Oracle Fusion, D365, Workday and Coupa, so we start building day one. Our team has years of hands-on work with SAP's BAPIs, IDocs and OData services, so the first weeks go into your customer's configuration. As Rossum's delivery partner, we shipped 22 projects for 17 enterprise customers into 9 ERPs, SAP among them.

A typical SAP integration with Inovaflow takes 3–4 weeks. Pricing is EUR 3,000–15,000 per integration, depending on system complexity and scope, and a scoping call produces a fixed quote. For write-heavy flows into S/4HANA, such as postings an AI agent triggers, we add patterns like two-phase write confirmation where they're needed.

Outsourcing is the wrong choice if SAP is the core of your product and you'll eventually need a full in-house SAP team anyway. In that case, use an outside team to ship the first customer and train your people, then bring it in-house.


Which SAP integration option fits your stage?

The SAP integration option that fits your stage depends mostly on how many SAP customers you have and how much you write into SAP. Here's how the five options compare:

Build in-houseBuy a connectorCustomer's Integration SuiteSAP certification and StoreOutsource the build
Upfront costHigh (SAP hire, sandbox)Platform subscriptionLow for you, high for the customerProgram requirements on top of a buildEUR 3,000–15,000 per integration, depending on system complexity and scope
Time to first customerMonths, gated on sandbox accessFast if the objects you need existDepends on the customer's SAP teamAdded on top of the build3–4 weeks
ECC coverageWhatever you buildSome vendors, via on-prem agentYesDepends on the buildYes
Write supportFullLimited to supported objectsFull, built per customerDepends on the buildFull
Who owns the codeYouThe vendorEach customerYouYou
Ongoing effortYour team, per variantVendor, plus your support ticketsEach customer's teamRecertificationYour team or the same partner

A simple way to decide:

  • Your first SAP deal is on the table. Check which variant the customer runs. S/4HANA Cloud and read-only: buy a connector if it covers your objects. Anything else: outsource the build so you can ship in weeks and keep the code.
  • You have three to five SAP customers. You now know your real variant mix. Own the connector, through your team or a partner, and support the customer's Integration Suite for the enterprises that insist on it.
  • SAP is a core segment. Build an in-house SAP capability, and look at the interoperability review and SAP Store once the integration is stable.

One more factor is moving fast. SAP spent 2026 opening its systems to AI agents: at TechEd in October it said every SAP agent is natively an A2A endpoint and made its Agent Gateway generally available, and it released an ABAP MCP server earlier in the year. We track what SAP has shipped for agents, and where it stops, in our overview of MCP servers across the SAP portfolio. If your product's AI agents need to read and write in your customers' SAP, the same build vs buy logic applies, with a much lower tolerance for wrong writes, and the MCP governance checklist covers what to settle before an agent gets write access. We cover how MCP fits next to your existing APIs in MCP vs REST API, and what we build for agentic products on our MCP connector page.

STAGE CHECK OPTION 01 FIRST SAP DEAL one customer S/4HANA CLOUD and read-only? YES NO BUY A CONNECTOR if it covers your objects OUTSOURCE THE BUILD ship in weeks, keep the code 02 3–5 SAP CUSTOMERS OWN THE CONNECTOR + customer’s Integration Suite 03 SAP CORE SEGMENT IN-HOUSE SAP TEAM + SAP Store, certification
Pick by stage: how many SAP customers you have, which SAP they run, and whether you write into it.

Frequently asked questions

Can I integrate with SAP without being an SAP partner?

Yes. Your customer licenses SAP and grants your integration access through their own users, communication arrangements or middleware, so no partner status is needed to build or run an integration. Partnership and certification matter for SAP Store listing and for procurement teams that ask for them. Joining SAP's partner program is still a good idea, though, because it gets you your own SAP sandbox at a favourable price, so you can build and test without relying on a customer's system.

Do I need SAP Cloud Connector to integrate with on-prem SAP?

Not always, but you need some secure path into the customer's network. SAP Cloud Connector is SAP's own option when the traffic goes through BTP. iPaaS vendors use their own on-prem agents, and some customers expose specific services through a gateway or VPN. In every case, the customer's IT team approves and installs it.

Does Merge or Codat support SAP?

Not for SAP ERP. Merge lists SAP SuccessFactors for HR and recruiting data, and neither Merge nor Codat lists SAP S/4HANA or ECC in its accounting integrations today. Apideck and Rutter list SAP S/4HANA, and Paragon and StackOne offer S/4HANA actions. None of the unified APIs we checked lists ECC, so check the vendor's current integration page against your customers' SAP versions before you commit.

Should I build for ECC if customers are moving to S/4HANA?

If your customers run ECC today, yes. Mainstream maintenance runs to the end of 2027 and extended maintenance to the end of 2030, and migrations take years, so ECC customers will be signing contracts with you for a while. Design the integration so the SAP-specific layer can be swapped from RFC and IDoc to OData without rewriting your product logic.

What's the difference between OData and BAPI for a SaaS integration?

OData is SAP's REST-style API layer, used heavily in S/4HANA and the only realistic route into S/4HANA Cloud Public Edition. BAPIs are function modules called over RFC, available in ECC and on-prem S/4HANA, and they often carry the full business logic for complex postings. Many on-prem integrations end up using both.

How many SAP customers do I need before building a native connector?

One, if the deal is big enough to pay for it. The bigger question is how similar your SAP customers are: three customers on S/4HANA Cloud can share one connector, while three on differently customized ECC systems need a mapping layer per customer, whatever you choose.

Who pays for SAP Integration Suite?

The SAP customer does. It's a BTP subscription priced per message, so integrating through it moves the cost and the build effort to the customer's side. That's acceptable for enterprises with an SAP team and a hard sell for mid-market customers who bought your product to avoid integration projects.

Can one connector cover S/4HANA Cloud and on-prem?

Partly. S/4HANA Cloud Public Edition only accepts its released APIs through communication arrangements, while on-prem systems also offer BAPIs, IDocs and custom code. A well-designed connector shares the product-facing logic and keeps a separate adapter per SAP variant.