Subscription & Recurring Revenue Manager

This is a build-to-order module, not an instant download. Typical delivery is 2 to 4 weeks depending on how custom your billing cycles, dunning rules and proration logic are. After purchase we hold a short scoping call, confirm requirements, build the module, deploy to a staging copy of your Odoo for your sign-off, then install on production and train your team.

Every engagement includes a post-launch support window with bug fixes and a defined response SLA. Because we build to Odoo's ORM and view conventions without patching core sale/account in unmaintainable ways, the module upgrades cleanly across Odoo point releases. Moving between major versions (17 to 18 to 19) is a small, quoted migration — we hand you the source, so you're never locked in.

No. The whole point of this module is to give you subscription and recurring-revenue management on Odoo Community. It depends only on standard modules (sale, account, mail) that ship in Community. If you're on Enterprise, it still works and adds dunning, churn analytics and proration behavior you can tailor beyond the stock Subscriptions app.

Each subscription contract carries computed fields (using @api.depends) that normalize its price to a monthly value — an annual plan divides by twelve, a quarterly plan by three, and so on. Those normalized values roll up into MRR and ARR, and MRR movement is split into new, expansion, contraction and churned so your dashboards reconcile with your accounting.

Yes. All subscription operations — create, renew, upgrade, downgrade, cancel — are exposed over Odoo's XML-RPC and JSON-RPC APIs, so your website or external app can drive them. We also wire payment-provider hooks (Stripe, PayPal, or manual/bank transfer) so a successful charge marks the invoice paid and a failed charge triggers the dunning workflow automatically.

No. Recurring invoices are standard account.move records, taxes and pricelists use your existing configuration, and the module adds new models rather than overwriting core behavior. Security is enforced with ir.model.access.csv and record rules. This keeps your books clean and the module upgrade-safe, which is exactly why we deliver it as a proper module instead of a pile of manual customizations.