How does subscription management work in Salesforce?

Subscription Management in Salesforce: The Complete Guide for Revenue Teams

By Kuldip Hillyer, Founder & CEO, Kugamon · Published September 15, 2026

Subscription management in Salesforce works by adding a subscription data model and renewal automation on top of the objects Salesforce already has. Out of the box, Sales Cloud gives you Accounts, Opportunities, Products, Price Books, Contracts, Orders, and Assets — but no subscription object, no renewal automation, no proration engine, and no invoicing. To manage subscriptions in Salesforce you add one of three things: Salesforce's own Revenue Cloud Advanced, a Salesforce-native AppExchange package that stores subscriptions as native records, or an external subscription platform synced into the CRM.

Which one you pick decides where your subscription data lives, who can report on it, and how much of the renewal motion runs itself. It also decides whether your reps work renewals in the pipeline they already use or in a second tool with a synced copy.

This guide covers what standard Salesforce gives you and what it doesn't, the three ways to add subscription management, how a native implementation works step by step, how to manage renewal products, how to evaluate the options, and where a Salesforce-native package like Kugamon Subscription Management fits.

What Standard Salesforce Gives You (and What It Doesn't)

Standard Salesforce is a strong foundation for subscription management and a poor substitute for it. The objects are there. The subscription logic isn't.

Two things to notice. First, Salesforce's standard Contract object already has a start date, a term, and a calculated end date — it's a perfectly good container, which is why native packages build on it rather than replace it. Second, nothing in the standard model knows that an Opportunity worth $12,000 might be $1,000 a month for twelve months or $12,000 once. That's the root of most subscription reporting errors in Salesforce.

Three Ways to Add Subscription Management to Salesforce

1. Salesforce Revenue Cloud Advanced

Salesforce's first-party successor to Salesforce CPQ — which is end-of-sale since March 2025, with existing customers able to renew — covers configuration, pricing, quoting, contracts, orders, and asset lifecycle on a new data model. Revenue Cloud Billing is sold separately for invoicing and collections. Subscription data is native to Salesforce. Pricing is published: $200 per user per month for Advanced, $150 for Growth, billed annually on an annual contract. Implementations are usually partner-led.

2. A Salesforce-native AppExchange package

A managed package that adds a Subscription object and renewal automation on Salesforce's standard Product, Price Book, Opportunity, Contract, Order, and Asset objects. Subscriptions are native records — same reports, same permissions, same Agentforce access as everything else in the org. Kugamon is the published-price example: Subscription Management at $95 per user per month, the full Subscription Billing edition at $125, a 10-user minimum, and admin-led implementations of four to eight weeks (AppExchange listing).

3. An external subscription platform synced to Salesforce

Zuora, Chargebee, and similar platforms manage subscriptions and billing on their own infrastructure and push a synced copy — usually account-level summaries and subscription headers — into Salesforce. The system of record is the vendor's platform. This suits finance-led organizations with billing complexity beyond what a CRM-side package handles, at the cost of a sync and a second admin. If you're already there and want out, see migrating from Zuora to Salesforce-native billing.

For the full cost picture on the first option, read how much Revenue Cloud Advanced costs. For the category definition, start with What Is Subscription Management?

How Native Subscription Management Works, Step by Step

Here's the lifecycle when subscriptions are native Salesforce records. Package names differ; the mechanics below are what to look for in a demo.

1. A new sale creates the contract, subscriptions, assets, and the renewal opportunity

The rep works a New-type opportunity, generates a quote, and converts it to an order. Releasing the order creates the contract (the container), a subscription record for each service line, an asset record for each product line, and a renewal opportunity dated for the end of the term. The renewal exists in the pipeline from day one, not from the day someone remembers it.

2. An expansion co-terms to the contract

Mid-term upsells run as Expansion-type opportunities tied to the existing contract. Added lines are co-termed and prorated to the contract end date automatically, so the customer keeps one renewal date. Releasing the expansion order adds the new subscriptions and assets to the contract and updates the renewal opportunity to match.

3. Renewal notices and renewal orders run on a schedule

Scheduled jobs email the contract's buying contact a renewal notice — typically 120 to 90 days before the contract end date — and generate the renewal order, typically 60 to 30 days out, optionally emailing it as well. The rep's job becomes handling exceptions, not tracking dates. More on this in how to automate subscription renewals.

4. Uplift applies by rule

A renewal price uplift percent, set as an org default and overridable per account, flows to the renewal opportunity and adjusts the sales price on products flagged for uplift. Releasing the renewal order extends or replaces the contract, generates the invoice where billing is included, and creates the next renewal opportunity.

5. ARR and MRR roll up to the contract and report natively

Because subscriptions are native records under the contract, ARR, MRR, subscription count, total quantity, and start and end dates roll up to the contract without a data warehouse. Cancelled subscriptions keep their history, so churn is reportable in the same place as growth.

In Kugamon specifically, this is the New, Expansion, and Renewal record-type flow on Opportunities, Quotes, and Orders: the standard Contract is the container, subscriptions and assets are created on order release, the renewal opportunity is created and kept current automatically, and a scheduled Subscription Active Check keeps each subscription's active status in step with contract status and dates.

How to Manage Renewal Products in Salesforce

Renewal products are managed on the product record, not deal by deal. That's the whole trick. In a native package, three product-level settings do most of the work:

• Renewable flag. Marks a product or service as something that rolls into the renewal opportunity and renewal order when the original order is released. Non-renewable lines — implementation, training, hardware — don't.
• Uplift flag. Says whether this product's price is subject to the renewal uplift percent. Flag the subscription; leave the one-time services alone.
• Renewal product substitution. A lookup that says "renew this as that" — the legacy tier renews onto the current tier, the promotional SKU renews onto list. Substitution happens when the renewal is built, not at a rep's discretion.

Two more settings decide what the sale creates: a create-subscription flag for services and a create-asset setting for products. Only services create subscriptions; only products create assets; renewable lines roll into the renewal either way.

What rolls into the renewal opportunity: every renewable line from the contract's contributing orders, at current quantities — expansions added, cancelled subscriptions removed — with uplift applied to flagged products and substitutions swapped in. If the contract changes after the renewal was created, a refresh rebuilds the renewal's products from the contributing orders rather than relying on someone to edit them by hand.

How to Evaluate Subscription Management for Salesforce

• Ask where the subscription record lives, then run a report. If you can't build a standard Salesforce report on ARR by account without an export, it's not native.
• Run the expansion test. Add seats in month seven. Check that the proration, the contract roll-up, and the renewal opportunity all change together.
• Check that the renewal exists before you ask for it. The renewal opportunity should be created when the sale is released, not when a job runs thirty days out.
• Count the products on the order form. Subscription management, billing, and CPQ from one vendor may be one package or three.
• Ask who implements it. Admin-led or partner-led moves the three-year cost more than license price does. Compare on the 3-year cost calculator.
• Confirm the amount field. Does the opportunity amount reflect the full term, and does your forecast use that field?

Common Mistakes

• Building it with Flows and custom objects. A custom Subscription object, a Flow that clones opportunities at term end, a formula for ARR. It works until the first co-termed expansion, the first partial cancellation, or the admin who built it leaves. You end up maintaining a product nobody sells.
• Using the standard Amount field. Standard Opportunity Amount doesn't factor time — a $1,000-per-month, 12-month service and a $1,000 one-time service look identical. Use a term-aware opportunity amount field and update page layouts, reports, and forecasts to read it.
• Storing subscriptions outside the CRM and syncing summaries. Reps see a number, not a record. Every renewal question becomes a login to another system, and every discrepancy becomes an integration ticket.
• Renewing without uplift rules. If the uplift lives in a rep's head, it's applied inconsistently or not at all. Set it at the org and account level and let the renewal inherit it.
• Creating renewals by hand. Cloning last year's opportunity copies last year's products, last year's price, and last year's mistakes — and misses everything the expansion added.

Frequently Asked Questions

Q: How does subscription management work in Salesforce?

By adding a subscription data model and renewal automation on top of the standard objects. A new sale creates a contract, subscription and asset records, and a renewal opportunity; expansions co-term to the contract; scheduled jobs send renewal notices and generate renewal orders; and ARR and MRR roll up to the contract for native reporting. You get that layer from Revenue Cloud Advanced, a Salesforce-native AppExchange package, or an external platform synced into Salesforce.

Q: Does Salesforce have a subscription object?

Not in standard Sales Cloud. Salesforce has Contract, Order, and Asset objects, but no Subscription object, renewal automation, or proration engine. Legacy Salesforce CPQ added a subscription object in its managed package but is end-of-sale since March 2025. Revenue Cloud Advanced adds its own data model, and native AppExchange packages add a Subscription object on the standard Product and Price Book.

Q: Is Salesforce a good CRM for subscription management?

Yes, with the right addition. Salesforce already has the account, opportunity, product, price book, contract, order, and asset objects a subscription business needs, plus native reporting, permissions, and Agentforce. What it lacks is the subscription object and renewal logic, and both Salesforce and AppExchange vendors supply that. The result is subscription management inside the CRM your reps already use.

Q: What is the best CRM for subscription management?

The one where subscriptions, contracts, renewals, and pipeline are native records in a single system your sales and finance teams both work in. For teams on Salesforce, that means keeping subscriptions as Salesforce records rather than syncing summaries from a separate platform, so a renewal opportunity, its contract, and its ARR roll-up sit in one report.

Q: How do I manage renewal products in Salesforce?

On the product record. Flag products as renewable so they roll into the renewal opportunity and order, flag which ones take a renewal uplift, and use a renewal-product lookup to substitute a different product at renewal. Then let the release of the original order build the renewal, and refresh it from the contract's contributing orders when the contract changes.

Q: Can I build subscription management in Salesforce with Flows?

You can build parts of it — a custom object and a Flow that creates a renewal opportunity at term end. What's hard to build and maintain is co-terming and proration on expansions, partial cancellations that update the renewal, uplift rules, renewal-order generation, and contract roll-ups that stay correct through all of it. Most teams that start with Flows end up buying a package to replace them.

Q: How are renewals automated in Salesforce?

With a native package, the renewal opportunity is created when the original order is released and dated for the end of the term. Scheduled jobs then email a renewal notice to the contract's buying contact, typically 120 to 90 days before the end date, and generate the renewal order, typically 60 to 30 days out, with any uplift applied. Releasing the renewal order extends the contract and creates the next renewal.

Q: Does subscription management in Salesforce include billing?

Depends on the option. Revenue Cloud Advanced handles quote through order, with Revenue Cloud Billing sold separately for invoicing. A native package may bundle invoicing and payments in a higher edition or sell them as an add-on, so check which edition you're quoted. External platforms such as Zuora and Chargebee are billing systems first, with subscription data living on their side.

Next Steps

Pull up your org and check three things: whether a Subscription object exists, whether renewal opportunities exist before anyone creates them, and whether your opportunity amount reflects the term. That tells you which of the three options you're really evaluating. Then explore Kugamon Subscription Management, read What Is Subscription Management? and how to automate subscription renewals, compare costs in how much Revenue Cloud Advanced costs, or schedule a demo and bring a real mid-term expansion. No pitch — just your renewals, as native Salesforce records.