SAP CPQ Licensing Explained: What You Pay For and What You Do Not

Licensing is the part of an SAP CPQ project everyone agrees to look at later. The consultants want to configure, the buyers want to sign, and the order form sits in a folder until an administrator hits a wall: a new user cannot be created, an approver needs access, or an extra test tenant turns out to be a separate purchase. I spent a day reading what SAP actually publishes, in the contract supplement, on the product page, in the Help Portal, on SAP Community and in support notes. The picture is more useful than I expected, and also less consistent.

This is not a price guide to SAP CPQ licensing. Prices differ by region and by contract, so I will point you to where SAP publishes them instead of quoting figures. It is a guide to the structure: what the metric is, what comes with it, what you buy on top, and where SAP’s own sources disagree with each other. Where I could not confirm something at an SAP source, I leave it out or say so.

Where SAP CPQ Licensing Is Actually Written Down

The one-page supplement behind the subscription

The contract wording that matters most for standalone SAP CPQ is a single page called SAP CPQ Supplemental Terms and Conditions, marked version 10-2025. It sits in the SAP Trust Center among the cloud services agreements, and you find it by filtering for CPQ. It covers three services: SAP CPQ, standard edition, SAP CPQ, test tenant, and SAP CPQ, external user.

For standard edition the usage metric is User, defined as any individual authorized to access the Cloud Service. One GB of disk storage is included per User and can be shared across all Users for the subscription term. The test tenant is counted in Tenants, and the number of Users in a test tenant cannot exceed the licensed number of Users in standard edition. The external user service is sold in blocks of one.

Just as telling is what the page leaves out. It says nothing about Quote 1.0 versus Quote 2.0, API calls, document generation or cloud integration. If a quote from SAP ties cost to any of those, that wording lives in your order form, and it is the reason I keep telling buyers to write the licensing questions into your RFP as written requirements instead of discovering the answers after signature.

What the Help Portal tells you, and what it does not

The SAP CPQ Help Portal, version 2609 when I read it, has no licensing guide. What it does have are three administration pages that touch licenses in a practical way, and I come back to each of them below. SAP’s own SAP CPQ product page lists the editions and add-ons with list prices. On the US site, as I read it in October 2026, it also states a minimum purchase quantity of 50 users for standard edition and contract terms of one to five years with auto-renewal.

SAP shows a local site as well, so check the page for your region. I would treat it as a reference point for the conversation with your account executive, not as your quote.

What the Subscription Includes and What You Buy on Top

According to the supplement and the product page, standard edition comes with one productive tenant and one non-productive tenant. The non-productive one lives in a non-production environment, may only be used for development and testing, and may not be used to process Personal Data. In practice that means you have a sandbox from day one, but it is not a place to load real customer records to see how a template behaves.

Storage is the other included item, at 1 GB per User, pooled. That sounds generous until a team stores many generated documents and images, which is why the Setup Home analytics I describe further down show storage next to licenses.

Sold separately

Additional non-productive tenants are bought as SAP CPQ, test tenant, and the supplement says they are counted together with the one productive and one non-productive tenant that come with standard edition. Extra storage is a separate add-on at one additional GB per user. Non-employee access is its own product, which I cover in the last section.

Variant configuration follows the same logic. The supplement for SAP Advanced Variant Configuration and Pricing, add-on for SAP CPQ (version 4-2023) says the add-on includes SAP Variant Configuration and Pricing and SAP Intelligent Product Recommendation, licensed per User, with use limited to Users who hold a standard edition license. There is also a different package, SAP CPQ, add-on for SAP Commerce, which uses Orders in blocks of 50,000 per contract year and includes 10 Users. Different metric, different rules, so do not carry assumptions from one package to the other.

What no license covers

A subscription is not a project. What an implementation costs depends on your products, rules and data, and I walk through those drivers in the implementation budget breakdown. Over a longer horizon, my colleague Milos lists sandbox, testing and staging systems next to licensing in his three-year ownership view, which is a useful sanity check against a quote that only shows seats.

Support deserves the same care. The supplement says nothing about support, so check the support terms in your order form, and the support models for your own configuration are worth settling before go-live, not after the first incident.

Checking and Managing Users Against the Limit

Administrators do not need to guess how SAP CPQ licensing plays out in their own tenant. Setup Home, which SAP describes in the Getting Started Guide for Administrators, includes a User Licenses widget showing the total number of user and administrator licenses, the number of currently active users and the number of unused licenses. Next to it sit Storage Status in Current Month and Storage Usage per Data Type.

If the number shown does not match what you purchased, SAP knowledge base article 3342045, titled “CPQ User license count is not up to date under CPQ Setup Home”, says to create an incident for the CPQ Support team, who check with their internal cloud operations team and adjust the count to the purchase details. Comparing daily active users with licensed users is also one of the items I would put into a health check of the tenant, because unused seats are money and missing seats are blocked sales reps.

When you add a user in Quote 2.0 administration, the General tab carries User Type, License Type, Administrator, Active, Is SSO and Grant Access to support. The Create a User page says License Type contains Standard by default and that you select External for external users. It also says you cannot change the License Type of an existing user, although copying a user lets you choose between Standard and External. Get the field right on the first pass.

External users come with documented limits. They cannot be assigned as Administrator, they have no access to Manage Companies, Manage Users, Manage Content Documents, Manage Document Templates, Bulk Quote Reassign or Manage Global Document Templates, they do not get the Teams and Solution Design tabs on the Quote 2.0 engine, and their name cannot be used as a CRM User Name in the CRM Integration User Mappings. The same page notes that the Audit Trail does not split users by license type, so do not expect to reconstruct your seat mix from there.

Inactive users: three SAP statements that do not agree

This is the question practitioners actually ask: if we deactivate a user, does that user still count? SAP’s answers point in different directions. A 2023 SAP Community answer from SAP Support says inactive users are counted in User Licenses, and that to create a new user you first need to delete another. Knowledge base article 3558649 is titled “Inactive Users Counting Towards License Limit in SAP CPQ”, with the symptom that new users cannot be added because the limit has been reached. Its cause section says inactive users are counted towards the limit by default, and its resolution is to reassign their quotes and delete them.

Then the Help Portal page on blocking users from deletion says that a blocked user’s status is considered for licenses: a blocked user who is active counts as a license user, and one who is inactive does not. And a 2024 thread about the error “Already reached active user count limit, as per subscription license agreement” has an SAP product expert advising two things: contact your SAP account executive for more licenses, and in the meantime review accounts and deactivate unused ones to free some quota.

The knowledge base article and the 2023 answer agree with each other, the blocked-user page covers a special case, and the 2024 advice to deactivate users is the one that sits awkwardly with the rest, so I would not assume deactivation frees a seat. What I would do is test it in your own tenant: deactivate one unused user, read the User Licenses widget before and after, and if the unused count does not move, delete the account or raise the incident described above.

External Approvers and the License Question

A thread from March 2026 describes a very common wish: executives, partners and compliance officers should approve quotes without getting CPQ accounts, because accounts add licensing cost and administration. SAP’s answer was clear. Every action on a quote requires authentication, CPQ records the identity of whoever performed it, and approval without a user therefore cannot be supported. The same conclusion shows up in my timeline write-up for approvers who hold no CPQ login, where the mitigation is a license type, not a configuration change.

One license, four names

That license type goes by several names depending on where you read. The supplement calls it SAP CPQ, external user. The Create a User page calls the option External. The product page and the SAP Community answer call it External Subscription, and SAP’s reply says it arrived with release 2602. In my own write-up I called it an External User license when I covered what release 2602 introduced as a license type for non-employees. As far as I can tell, they all describe the same thing.

The wording of the supplement decides who qualifies: Customer’s non-employees and individuals with whom the customer has only a limited or temporary employment relationship. The product page gives dealers, distributors and partners as typical examples. So the executive on your own payroll who approves large discounts is not an external user under that definition. Before promising anyone a cheaper seat, check who counts as a non-employee in your contract.

Whatever you plan to buy, I would put these questions to your SAP account executive in writing:

• Which edition and add-ons does my quote cover, and which version of each supplement applies?
• How many tenants are included, and what do additional test tenants cost on top?
• How are inactive and blocked users counted against my limit?
• Who qualifies for the external seat in my organization?
• What happens, contractually and in the tenant, when I reach the user limit?

The last question matters because I found no public SAP source that describes overage or true-up for SAP CPQ, only the error message and the advice to talk to your account executive. Good SAP CPQ licensing work is mostly about getting these answers on paper while you still have leverage, and a second pair of eyes on the quote and on the tenant is a small cost compared with a blocked rollout.