Subscription & Recurring Revenue Manager

Name: Subscription & Recurring Revenue Manager
Brand: ECOSIRE
SKU: subscription-recurring-revenue

主な機能

Recurring plan catalog: define billing cycles (weekly, monthly, quarterly, annual, custom N-days) as a subscription.plan model reusable across products and customers

Subscription contracts built on standard sale.order and account.move so quotations, tax and accounting stay 100% native Odoo

Automated renewal engine via ir.cron scheduled action that generates the next-period invoice and confirms it per contract terms

Automatic invoicing and email delivery of recurring invoices through QWeb report templates and Odoo's mail queue

Dunning workflow on failed or overdue payments: staged reminder emails, retry cadence, and auto-suspend/expire rules driven by automated actions

MRR and ARR computed fields on each contract using @api.depends, rolled up into normalized monthly recurring revenue across mixed billing cycles

Churn and retention dashboards (OWL/JS) showing gross churn, net churn, logo churn and MRR movement (new, expansion, contraction, churned)

Upgrade/downgrade with automatic proration: credit the unused period and re-bill the new plan mid-cycle via prorated invoice lines

Contract lifecycle states (draft, active, paused, past-due, churned) with visible status badges and full mail.thread chatter/audit history

Customer self-service portal pages so subscribers can view active plans, upcoming renewals and invoices, and cancel or request changes

Payment-provider hooks (Stripe/PayPal/manual) that mark invoices paid, trigger dunning on failure, and reactivate suspended contracts

Role-based security via ir.model.access.csv plus record rules — reps see only their assigned subscriptions, finance sees all, portal users see only their own

XML-RPC / JSON-RPC API endpoints to create, renew, upgrade and cancel subscriptions from your website, mobile app or external systems

Cohort and revenue-forecast reporting: projected MRR from the active book, plus filterable pivot/graph views by plan, product and salesperson

Multi-currency and multi-company aware, honoring your existing Odoo pricelists, taxes and fiscal positions

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

Odoo Enterprise ships a Subscriptions app — but if you run Odoo Community, or you're on Enterprise and want dunning logic, churn analytics and proration that actually match your business, you're stuck bolting recurring billing onto sale.order by hand. The Subscription & Recurring Revenue Manager is a net-new Odoo module that ECOSIRE designs, builds and installs specifically for your instance, giving SaaS and service teams a real subscription engine on Odoo Community (and Enterprise) 17, 18 or 19.

This is a build-to-order engagement, not an instant apps.odoo.com download. After purchase, our Odoo engineers scope your billing cycles, invoicing rules and dunning policy, then ship a clean, upgrade-safe module: a new subscription.plan and subscription.contract model layered on top of standard sale.order, account.move and res.partner, with computed MRR/ARR fields (@api.depends), scheduled cron actions (ir.cron) that generate renewal invoices, a QWeb dunning email flow for failed payments, and OWL dashboards for MRR, ARR and churn. Access is locked down with ir.model.access.csv plus record rules so account managers only see their own book of business, and every recurring flow is exposed over XML-RPC/JSON-RPC so your app, website or payment provider can create and update contracts programmatically.

Because we write the module to Odoo's ORM and view conventions — proper __manifest__.py dependencies, no core patching of sale or account you can't upgrade past — it survives Odoo point releases and stays yours. You get the source code, the configuration, documentation, admin training and a post-launch support window. The result: predictable recurring revenue reporting, automated renewals, fewer failed-payment write-offs, and a churn number you can actually trust — all inside the Odoo you already run.

得られるもの

Complete, installable Odoo module (source code) with a documented __manifest__.py declaring exact dependencies (sale, account, mail) and version-pinned for your Odoo 17/18/19

Configured subscription plans, billing cycles, dunning cadence and email templates matched to your real pricing and payment policy

Installation and deployment on your instance (staging first, then production) with a data-safe migration of any existing recurring customers

ir.cron scheduled actions and automated actions configured and verified end-to-end (renewal generation, dunning, suspension)

Security matrix delivered as ir.model.access.csv plus record rules, mapped to your finance and sales roles

Admin and end-user documentation (PDF/markdown) plus a recorded/live training session for your team

MRR/ARR/churn dashboards and reporting views wired to your data, with a walkthrough of how each metric is calculated

Post-launch support window with bug fixes and a defined SLA, plus a maintenance/upgrade path quote for future Odoo versions

これは誰のためのものですか

Community-edition SaaS founder

Runs Odoo Community to keep costs down but sells software on monthly and annual plans. Needs real MRR/ARR, automated renewals and churn tracking without paying for the Enterprise Subscriptions app or a separate billing SaaS.

Finance/RevOps lead at a services firm

Manages retainers and recurring service contracts and is tired of manually raising the same invoices each month. Wants automated recurring invoicing, dunning on failed payments, and a trustworthy revenue-forecast dashboard inside Odoo accounting.

Operations manager scaling a subscription book

Handles hundreds of active subscribers and needs upgrade/downgrade proration, staged dunning, and per-rep visibility via record rules so account managers only touch their own customers — all auditable in Odoo chatter.

Subscription & Recurring Revenue Manager の比較方法

基準	エコシエール	カスタムビルド	競合他社
Runs on Odoo Community (no Enterprise licence needed)	付属	付属	部分的なサポート
Automated renewals via scheduled ir.cron actions	付属	部分的なサポート	付属
Dunning workflow on failed/overdue payments	付属	部分的なサポート	部分的なサポート
MRR / ARR / churn dashboards	付属	部分的なサポート	部分的なサポート
Upgrade/downgrade with automatic proration	付属	部分的なサポート	部分的なサポート
Tailored to your exact billing cycles and pricing rules	付属	付属	含まれていない
Role-based access via ir.model.access.csv + record rules	付属	部分的なサポート	部分的なサポート
XML-RPC / JSON-RPC API for external integration	付属	部分的なサポート	部分的なサポート
Upgrade-safe across Odoo 17/18/19 with source handed over	付属	含まれていない	部分的なサポート
Includes install, training and post-launch support SLA	付属	含まれていない	含まれていない

Subscription & Recurring Revenue Manager に関するよくある質問

How long does delivery take and what happens after I buy?

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.

What support and updates are included, and what about future Odoo versions?

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.

Do I need Odoo Enterprise for this to work?

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.

How is MRR calculated across mixed billing cycles?

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.

Can it connect to my website, app, or payment provider?

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.

Will this break when I upgrade Odoo or interfere with my existing accounting?

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.