Subscription & Recurring Commerce for Website Sale

This is a build-to-order module, not an instant apps.odoo.com download. After a short scoping call we build, integrate and test it against your Odoo instance, then deploy to production. Typical delivery is 2-4 weeks depending on the complexity of your catalog, payment providers, box logic and dunning rules. You are never charged for a download you then have to make work yourself — you receive a working, installed module.

Every engagement includes a post-launch support and bug-fix window. Because the module ships as isolated custom code with a clean __manifest__.py (no core patches), it upgrades cleanly with your Odoo version. We can quote an ongoing maintenance retainer covering Odoo 17-to-18-to-19 version upgrades, new features and priority support, or you can maintain it yourself using the documentation and code we hand over.

It works with both, targeting Odoo 17, 18 and 19. We build against your edition and reuse what you already have — Community's website-sale plus our recurring layer, or Enterprise's sale_subscription where present. During scoping we confirm which core apps are installed so the module extends rather than duplicates existing functionality.

A scheduled automated action attempts each renewal charge against the customer's saved payment token via your acquirer. On failure it enters a configurable dunning sequence: retry attempts on a cadence you choose, escalating QWeb reminder emails, and a grace period before the subscription is suspended. Every attempt is logged as an Odoo record so you can audit and report on involuntary churn.

Yes. The Odoo website portal gets self-service actions to pause, skip the next delivery, swap the product or variant, change the billing interval, update the saved card and cancel. Access is enforced with ir.model.access.csv permissions and record rules so each customer can only view and modify their own subscriptions, reducing support tickets.

Yes. Subscriptions, renewal invoices (account.move) and payment attempts are all first-class Odoo records, so MRR, active-subscriber and churn figures appear in native pivot and graph views. The same records are accessible over Odoo's XML-RPC / JSON-RPC API, so external analytics, CRM or fulfillment systems can read subscription and billing data programmatically.