Odoo’s Subscriptions module just got noticeably lighter. Two features that have been part of the recurring revenue toolkit for years — Subscription Plans and Automation Alerts — are gone. Not hidden behind a setting, not moved to a different menu. Removed entirely, with their documentation pages deleted and redirects set up so old bookmarks land somewhere useful.
This isn’t a bug fix or a quiet deprecation notice buried in release notes. It’s a product decision that reflects how Odoo’s thinking about subscription management has evolved.
What Subscription Plans Were
Subscription Plans were templates that bundled together a set of products, a billing period, and pricing rules into a reusable configuration. The idea was that instead of manually assembling a subscription order line by line, you could define a “plan” — say, a monthly SaaS package with three included modules — and apply it to new subscriptions with a single click.
In practice, plans created an abstraction layer that many teams found confusing. New users would set up their subscription products, configure their pricing, and then discover they also needed to create a plan to tie it all together. The plan wasn’t the subscription. The product wasn’t the plan. And the quotation template was yet another thing. Three concepts where one or two would do.
The removal collapses this hierarchy. Subscription configuration now lives directly on the product and the quotation template, which is where most users expected it to be in the first place. You set a product as recurring, define its billing interval, and you’re done. No intermediate plan object to manage.
What Automation Alerts Were
The Automation Alerts feature let administrators define rule-based triggers that fired when subscription-specific conditions were met. A subscription hitting a certain MRR threshold, approaching its renewal date, or sitting untouched for a configurable number of days could trigger an email, create a task, or execute a server action.
It was, in essence, a domain-specific automation engine bolted onto the subscription workflow. The problem was that Odoo already has a general-purpose automation engine — Automated Actions — that does the same thing across every module. Having a separate subscription-specific version meant two places to configure similar logic, two different interfaces to learn, and two systems that didn’t always play well together.
With the removal, subscription-related automations move to the standard Automated Actions framework. The same triggers are achievable — “when a subscription’s stage changes,” “when MRR exceeds a threshold,” “when the next invoice date is within 7 days” — but they’re configured in the same place as every other automation in the system.
The Broader Pattern
These removals fit a pattern that’s been visible across Odoo’s recent releases: eliminating module-specific mechanisms when a platform-wide solution already exists. The Subscriptions module accumulated its own mini-ecosystem of features over the years — its own plans, its own alerts, its own reporting structures — because the general-purpose alternatives weren’t mature enough when those features were first built.
Now they are. Quotation templates handle product bundling. Automated Actions handle event-driven workflows. The subscription module can focus on what only it can do: managing the lifecycle of recurring revenue relationships, from trial through renewal through churn.
What This Means for Existing Users
If you were using Subscription Plans, the migration path is straightforward: recreate your plan configurations as quotation templates with recurring products. The end result for your sales team is nearly identical — they still select a template when creating a subscription — but there’s one fewer abstraction layer to maintain.
If you were using Automation Alerts, you’ll need to rebuild those rules as standard Automated Actions. The conditions and triggers translate directly, and you gain access to the broader set of actions available in the general automation framework (which includes things like webhook calls and multi-step sequences that the subscription-specific alerts never supported).
The documentation cleanup was thorough: over 270 lines of content were removed across two documentation pages, three sets of screenshots were deleted, and references to plans and automation alerts were stripped from eight other documentation pages covering quotation templates, upsells, renewals, and subscription reports. Old URLs redirect to the main Subscriptions documentation page.
Fewer Moving Parts, Fewer Surprises
There’s a cost to feature removal — existing users need to adjust, and some will miss the convenience of subscription-specific shortcuts. But there’s a larger cost to feature accumulation, and it compounds over time: every module-specific mechanism is another thing to learn, another thing to maintain, and another thing that can break in ways that don’t match how the rest of the platform behaves.
Odoo is choosing the leaner path. For a module that sits at the center of many businesses’ revenue operations, that’s probably the right call.