Recurring-revenue businesses outgrow Odoo's native subscriptions fast. Odoo Enterprise ships sale_subscription for basic recurring sales orders, but Community has no subscription engine at all, and neither covers the operational reality of a real membership or SaaS book: metered add-ons, tiered pricing bands, mid-cycle upgrades with correct proration, configurable dunning ladders, grace periods, and a member-facing portal where customers manage their own plan without emailing support. Teams end up bolting spreadsheets and manual invoices onto Odoo, and every failed card becomes a lost renewal that nobody chased. This is where Odoo native runs out of road.

ECOSIRE builds a dedicated subscription and membership module on top of your Odoo. At its core is a subscription.plan model (recurring interval, pricing tiers, trial period, setup fee) and a subscription.contract model linking res.partner, product/plan, billing anchor date and lifecycle state (draft, trial, active, past_due, suspended, cancelled) driven by a proper state machine. Renewals run from a scheduled ir.cron that generates account.move invoices via the standard accounting API, so revenue, tax and reporting stay native — nothing is faked outside the ledger. Compute fields with @api.depends derive next-invoice date, MRR/ARR and proration credits; ir.model.access.csv plus record rules keep each member scoped to their own contract, and the whole thing respects company_id for multi-company setups.

Dunning is a first-class workflow, not an afterthought. A configurable retry ladder (for example day 1, 3, 7) is stored as data and executed by automated actions: each failed payment advances the contract's dunning stage, fires a QWeb-rendered email, and — on exhaustion — suspends access and notifies your team. Upgrades and downgrades compute a proration credit or charge against the remaining cycle and post it as an adjustment line on the next invoice, so mid-term plan changes are accurate to the day. The member portal is built with QWeb/OWL controllers extending Odoo's /my website portal: customers see their plan, invoices and payment status, self-serve upgrades/downgrades, update payment methods, and download receipts — reducing support load. Where you use Stripe, GoCardless or another gateway, we wire the webhook and reconciliation path; integrations and headless flows can also use Odoo's XML-RPC/JSON-RPC API.

Because this is build-to-order, we start from your actual plan structure, billing rules and gateway rather than a generic template. After a scoping call we confirm the data model, dunning policy and portal scope in writing, build against Odoo 17.0, 18.0 or 19.0 (Community or Enterprise — we adapt to whether sale_subscription is present), and validate on a staging clone of your database. Typical delivery is one working week from confirmed scope depending on gateway and proration complexity. You receive the installable module source, a git repository, technical and user documentation, a training session, UAT sign-off on staging with a rollback plan, and a post-go-live support window.