Odoo's native subscription engine (sale_subscription) lives behind the Enterprise licence, leaving Community users to bolt recurring revenue onto manual sale orders and cron-triggered invoices that never quite handle mid-cycle changes, failed cards, or trials cleanly. This is a build-to-order module: ECOSIRE designs, develops, installs, and supports a purpose-built Subscription & Recurring Billing Manager on YOUR Odoo Community database (17, 18, or 19). It is not an instant apps.odoo.com download — after purchase our team scopes your billing rules, builds the module, and hands it over live in 2-4 weeks.

At its core sits a subscription.plan model (recurring price, interval, trial length, tax and product mapping) and a subscription.subscription model that tracks each customer's lifecycle — trial, active, past-due, paused, cancelled — as a proper Odoo state machine with @api.depends computed fields for MRR, next invoice date, and remaining trial days. A scheduled ir.cron job (the same automated-action mechanism Odoo core uses) walks due subscriptions each night, generates account.move customer invoices, and — where you connect a payment provider — charges the saved token automatically. Mid-cycle upgrades, downgrades, and add-ons are calculated with true line-item proration, crediting unused time and billing the new plan pro rata rather than forcing you to cancel-and-recreate.

Failed payments enter a configurable dunning sequence: smart retries on your schedule, branded reminder emails via QWeb templates, and automatic status transitions to past-due or churned, with churn-risk alerts surfaced to your revenue team. Customers manage everything themselves through a self-service portal built on Odoo's website/portal controllers — view active subscriptions, download invoices, update payment methods, upgrade, pause, or cancel — reducing support load and involuntary churn.

Everything ships with correct security: ir.model.access.csv access rights plus multi-company record rules so a portal user only ever sees their own subscriptions and your staff see only their company's data. Views are delivered as clean XML (list, form, kanban pipeline, and a subscriptions dashboard), with OWL components where interactivity helps. A documented XML-RPC / JSON-RPC surface lets your website, mobile app, or external billing tools create and query subscriptions programmatically. The module respects Community constraints throughout — no Enterprise-only dependencies — so you get Enterprise-grade recurring revenue on the licence you already run, fully owned by you, with source code handed over.