When v.4.2026 forces published API consumption through SAP Integration Suite, the BTP capacity bill arrives. The capacity unit model, the right sizing analysis, and the renewal cap pattern.
SAP Integration Suite is the cloud iPaaS that sits inside SAP Business Technology Platform. With v.4.2026 the Integration Suite shifts from a recommended option to an effective requirement for any cloud edition customer who wants policy compliant integration against the SAP digital core.
The product is priced in capacity units. The opening sizing SAP proposes is almost always larger than the customer needs, sometimes by a factor of three or four.
The buyer side response is to model the capacity from twelve months of real iFlow execution data, negotiate the right sized tier with explicit reduction rights at renewal, and bundle the Integration Suite commit with the broader SAP estate.
Read the SAP restricted third party API access pillar for the policy context and the SAP BTP licensing strategy for the broader BTP picture.
Key takeaways
SAP Integration Suite consumption is measured in Integration Suite capacity units, often abbreviated as CU or IU depending on the contract vintage. The metric blends message volume, iFlow steps, connector usage, and certain premium feature flags such as message persistence and trading partner management.
The list price varies, but the indicative anchor for 2026 is approximately twenty eight cents per capacity unit per month at the smallest tier, falling to between twelve and seventeen cents per unit at large volumes after volume tiering.
Indicative annual list price by enterprise size (2026)
| Segment | Capacity units sized | Annual list (pre discount) |
|---|---|---|
| Mid market | 500K to 1M CU | $140K to $280K |
| Large enterprise (low) | 2M CU | $500K |
| Large enterprise (high) | 5M CU | $1.5M |
The complexity of the metric is the negotiation surface. The customer who accepts SAP's opening sizing accepts an opaque commit. The customer who builds a real consumption model from the BTP cockpit export can challenge every assumption in the sizing.
That includes the average iFlow step count, the proportion of messages that need persistence, and the share of traffic that runs through premium connectors. Read the SAP Contract Negotiation Playbook for the metric challenge pattern we use.
The sizing model has four inputs. Each comes from the BTP cockpit export, not from SAP's proposal.
The four inputs combine into a capacity model that the customer owns, that the customer can reproduce, and that the customer can defend in the renewal conversation.
Across thirty Integration Suite engagements we have run in the last twenty four months, the right sized capacity calculated from real data lands at twenty to forty percent of the SAP opening framework.
The gap exists because SAP account teams size for the customer's three year roadmap rather than the customer's current state, and because the metric blending favors SAP at the headline price. The customer who right sizes, then negotiates a structured ramp for the genuine growth, captures the gap as savings rather than absorbing it as overage.
The Integration Suite discount stack has three layers. Each carries its own justification and its own clause set in the contract.
The combined discount stack at strong relationship depth lands between sixty five and eighty percent off list for the first commit, with renewal terms that protect the discount at refresh.
The single most important clause in the Integration Suite contract is the capacity reduction right at renewal. Without it, the capacity is a one way ratchet.
The customer commits to a tier, the consumption grows or stays flat, and the renewal carries the tier forward at whatever price increase the contract permits. With the reduction right, the customer can right size again at renewal based on the actual consumption of the last twelve months.
The right has to be written with specificity: a defined notification window, a defined percentage band, and a defined process for the reduction.
The price increase cap is the second important clause. The SAP standard cloud terms permit annual increases of three to five percent on subscription products.
The negotiable position is a flat freeze for the first three years, a capped increase of two percent for any renewal year beyond, and an explicit floor on the discount if the contract is materially expanded. The cap and the floor together create a known cost envelope that the customer can budget against.
The Integration Suite negotiation is almost always running in parallel with other SAP commercial conversations. RISE migrations, S/4HANA expansions, Datasphere commitments, and Joule consumption all sit on the same account team's pipeline.
The buyer side play is to package the Integration Suite commit into the broader conversation, not to negotiate it in isolation. The combined package gives the customer more leverage on each individual item, because SAP's account team is incentivised by the total contract value, not the line item count.
The bundling has to be done carefully. The customer who agrees to a five year multi product commit without right sized capacity at the line item level still ends up overcommitted, just on a bigger contract.
The right move is to right size each line item first, then bundle the right sized items for the discount, then negotiate the renewal mechanics across the bundle. Read the SAP BTP licensing strategy for the broader bundling discipline.
The three most common sizing failures we see across enterprise engagements are these.
The corrective in each case is the same. Build the model from real data, separate the line items, negotiate each on its own merit, and tie the whole package together at the contract amendment level. Read our coverage at SAP third party tools and API access for the related carve out work.
The buyer side response to the BTP integration mandate has eight moves. Run them in order, not in isolation.
Read the SAP knowledge hub and the SAP advisory practice.
Capacity units (CU or IU) blend message volume, iFlow steps, connector usage, and premium feature flags such as message persistence and trading partner management. The 2026 anchor is around twenty eight cents per unit per month at the smallest tier.
Across thirty engagements in twenty four months, real iFlow data lands the right sized capacity at twenty to forty percent of the SAP opening framework. SAP account teams size for the three year roadmap and the metric blending favors the publisher at the headline price.
Three layers stack. The standard product discount lands thirty to fifty percent off list. The bundling discount applies inside BTP, RISE, or S/4HANA expansions. The strategic discount applies on multi year ramps. Combined at strong relationship depth, the stack lands sixty five to eighty percent off list.
The clause lets the customer right size the tier at renewal based on the last twelve months of actual consumption. Without it, the capacity is a one way ratchet. The right needs a defined notification window, a defined percentage band, and a defined reduction process.
Right size each line item first, then bundle the right sized items for the discount, then negotiate the renewal mechanics across the bundle. The combined package gives more leverage on each item because SAP's account team is incentivised by total contract value.
If you are sizing an Integration Suite commit or renegotiating an existing one, a forty five minute scoping call is the right starting point. Schedule a call with the SAP practice or download the SAP API Restrictions Negotiation Playbook.
The eight move negotiation playbook, the Integration Suite capacity model, the discount stack, and the contract amendment patterns we use across more than five hundred enterprise software engagements.
Independent. Buyer side.
