Selling anything on a recurring basis in stock Odoo means fighting the grain of a system built around one-time sale orders and invoices. Teams end up manually cloning quotations every month, running spreadsheets to track who renews when, and firefighting failed card charges after the fact. Odoo Community has no native subscription engine at all, and even where recurrence exists it rarely matches how your plans actually price, prorate, upgrade, and dunning-retry. The result is revenue leakage, missed renewals, and a finance team reconciling by hand — exactly the busywork a recurring-revenue business cannot afford.

ECOSIRE builds a Sales Subscription module that lives natively inside the sales flow so a quotation can carry recurring lines instead of one-off ones. We introduce a sale.subscription model (with sale.subscription.line children) plus a configurable sale.subscription.plan defining billing period (monthly/quarterly/annual via a selection field), commitment term, and auto-renew behavior. Compute fields with @api.depends derive next-invoice date, MRR/ARR, and remaining commitment; a scheduled automated action (ir.cron) walks due subscriptions each night, generates the recurring invoice through the standard account.move pipeline, and advances the billing anchor. State is driven by a selection lifecycle (draft → in_progress → renewed/paused → closed) so churn and reactivation are first-class rather than manual status edits.

Technically it is a clean, upgrade-safe addon: a proper __manifest__.py declaring dependencies on sale (and sale_subscription/account where your edition provides them), access rules in ir.model.access.csv plus record rules for multi-salesperson and multi-company isolation, backend views in XML/OWL (list, form, a renewal kanban, and a subscriptions smart-button on the customer), and QWeb reports for subscription confirmations and renewal notices. Everything the model exposes is reachable over the XML-RPC/JSON-RPC API, so your website, payment provider, or external billing dashboards can create, pause, or query subscriptions programmatically. We handle the Community-vs-Enterprise gap explicitly — where Enterprise ships a subscriptions app we integrate with and extend it rather than duplicate it; on Community we deliver the full recurring engine ourselves.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, confirm your plans, proration rules, tax and payment-provider setup, and target Odoo version (17.0, 18.0, or 19.0), then build against a staging clone of your database. You get UAT on staging, a rollback plan, and a supervised go-live before the module touches production. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company consolidation, payment-gateway automation, custom proration/dunning logic, or migrating an existing book of subscriptions increases the quoted scope.