产品详细信息以英文显示。翻译即将推出。
速览
- 价格
- $299.00 USD
- Odoo 版本
- 17, 18, 19
- 设置时间
- 20160分钟
- 许可证
- 一次永久
- 语言
- 11 语言
一次性购买
Subscription & Recurring Billing Manager for Odoo (Community)
Enterprise-style subscriptions for Odoo Community — recurring plans, proration, trials, dunning & self-service portal, built & installed by ECOSIRE.
$299.00USD
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
核心功能
subscription.plan model defining recurring price, billing interval (daily/weekly/monthly/quarterly/annual), trial length, and linked product/tax
subscription.subscription lifecycle state machine (draft, trial, active, past-due, paused, cancelled) with @api.depends computed MRR, next-invoice-date, and trial-days-remaining fields
Free-trial handling with automatic conversion to paid billing on trial expiry and configurable card-required-on-signup
True line-item proration on upgrades, downgrades, and plan switches — credits unused time and bills the new plan pro rata mid-cycle
Add-on and metered-quantity management layered on top of the base plan without recreating the subscription
Nightly ir.cron automated action that generates account.move invoices for all due subscriptions and posts them per your accounting rules
Automatic charging of saved payment tokens where a payment provider is connected, with success/failure handling
Configurable dunning sequence: smart retry schedule, escalating QWeb reminder emails, and automatic past-due/churn transitions
Churn-risk alerts and a subscriptions dashboard (kanban pipeline + list views) surfacing MRR, active count, and at-risk accounts
Customer self-service portal (website/portal controllers) to view subscriptions, download invoices, update payment method, upgrade, pause, or cancel
ir.model.access.csv access rights plus multi-company record rules isolating portal users to their own data and staff to their company
QWeb-rendered subscription invoices and renewal/dunning email templates matched to your branding
XML-RPC / JSON-RPC endpoints to create, read, and manage subscriptions from your website, app, or external tools
Pause/resume and scheduled cancellation with correct proration and reactivation behaviour
Renewal and end-of-term reminder emails via automated actions to reduce involuntary churn
Community-safe implementation with zero Enterprise-only module dependencies, compatible with Odoo 17, 18, and 19
关于此产品
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.
为什么选择 Subscription & Recurring Billing Manager for Odoo (Community)
subscription.plan model defining recurring price, billing interval (daily/weekly/monthly/quarterly/annual), trial length, and linked product/tax
subscription.subscription lifecycle state machine (draft, trial, active, past-due, paused, cancelled) with @api.depends computed MRR, next-invoice-date, and trial-days-remaining fields
Free-trial handling with automatic conversion to paid billing on trial expiry and configurable card-required-on-signup
True line-item proration on upgrades, downgrades, and plan switches — credits unused time and bills the new plan pro rata mid-cycle
Add-on and metered-quantity management layered on top of the base plan without recreating the subscription
Nightly ir.cron automated action that generates account.move invoices for all due subscriptions and posts them per your accounting rules
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.
你得到什么
- Complete, commented module source (models, XML/OWL views, controllers, QWeb templates, __manifest__.py) installed on your Odoo Community 17/18/19 database and handed over to you
- Configured subscription plans, trial rules, billing intervals, and dunning/retry schedule mapped to your actual pricing
- ir.cron jobs, security (ir.model.access.csv + record rules), and payment-provider wiring set up and verified in your environment
- Branded QWeb invoice and email templates (renewal, dunning, trial-ending) styled to your company
- Admin & operations documentation: how plans, proration, dunning, and the customer portal work, plus a config reference
- XML-RPC / JSON-RPC integration guide with example calls for creating and managing subscriptions externally
- Live training session (recorded) for your billing/finance team plus a portal walkthrough for support staff
- A post-go-live support window with bug fixes and configuration adjustments, plus documented paths for future enhancements
这是给谁的
SaaS & Digital Product Founder on Odoo Community
Runs a subscription business but is stuck on Community to control costs. Needs real recurring billing, trials, and proration without paying for Enterprise, and wants to own the code rather than rent a SaaS billing tool.
Finance / Billing Operations Manager
Currently reconstructs recurring invoices by hand or via fragile cron scripts. Wants automated invoice generation, reliable dunning on failed payments, and a clean MRR/churn view so month-end stops being a manual scramble.
Odoo Partner / Internal ERP Lead
Delivering Odoo to a client (or their own org) on Community and needs a maintainable, security-correct subscription module that respects multi-company record rules and exposes an RPC surface — without forking Enterprise code or reinventing the billing engine.
安装概述
从ECOSIRE下载
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Subscription & Recurring Billing Manager for Odoo (Community) 模块 ZIP。
上传至Odoo
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中（或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传）。
安装模块
激活开发者模式，打开应用程序，单击更新应用程序列表，搜索 Subscription & Recurring Billing Manager for Odoo (Community)，然后按安装。
配置设置
打开新菜单，粘贴您的 ECOSIRE 许可证密钥，连接任何外部凭据（Shopify、Amazon、Stripe 等），然后保存。
验证并上线
运行内置连接测试，同步前 10 条记录，并安排定期 cron。如果出现任何问题，请联系支持人员。
Subscription & Recurring Billing Manager for Odoo (Community) 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Recurring plans, trials & proration on Odoo Community | Purpose-built subscription.plan / subscription.subscription models with trials and true line-item proration | Possible but you design and maintain the entire billing engine yourself | Varies by author; proration and trial depth often limited or partial | |
| Automated invoicing & payment charging | Nightly ir.cron generates account.move invoices and charges saved tokens where a provider is connected | You must write and test the cron, invoice, and charging logic | 部分支持 | |
| Dunning, smart retry & churn handling | Configurable retry schedule, escalating QWeb emails, and automatic past-due/churn transitions with alerts | Build the retry and reminder engine from scratch | 部分支持 | |
| Customer self-service subscription portal | Website/portal controllers to view, upgrade, pause, cancel, and update payment method | Portal controllers and templates hand-built and secured yourself | 部分支持 | |
| Security: access rights & multi-company record rules | ir.model.access.csv plus record rules isolating portal users and companies, verified in your env | Correct only if you get every access rule and record rule right | 部分支持 | |
| Source ownership, fit & handover | Full commented source built to your billing rules, installed and handed over — you own it | You own it but carry all build risk and timeline | Author-owned; you adapt your process to the module and depend on their roadmap | |
| Delivery model | Build-to-order: scoped, built, installed & supported in 2-4 weeks | Internal project — timeline and cost depend entirely on your team | Instant download, then self-configure and self-support | |
| XML-RPC / JSON-RPC integration for external systems | Documented RPC surface with example calls delivered in the handover | You expose and document the API yourself | 部分支持 |
关于Subscription & Recurring Billing Manager for Odoo (Community)的常见问题
How long until the module is live, and what's the process after I buy?
This is a build-to-order module, not an instant download. After purchase we run a short scoping call to capture your plans, trial rules, proration policy, and dunning schedule, then build and install the module directly on your Odoo Community database. Typical delivery is 2-4 weeks depending on how many plans and integrations are involved; we confirm a firm timeline after scoping and keep you updated through build and UAT before go-live.
What support and updates do I get after go-live?
You receive a post-launch support window covering bug fixes and configuration adjustments so the module behaves correctly on your live data. Because we hand over the full, commented source, you own it outright — nothing is locked behind a subscription of ours. Beyond the included window we offer ongoing support and enhancement retainers, and we handle compatibility work when you upgrade across Odoo 17, 18, and 19.
Does this work on Odoo Community, and does it need Enterprise?
Yes — the entire point is to bring Enterprise-style subscriptions to Community. The module is built with no Enterprise-only dependencies, relying only on core Community modules (sale, account, website/portal). It runs on Odoo Community 17, 18, and 19. If you later move to Enterprise, the module continues to work alongside it.
How does proration work when a customer upgrades or downgrades mid-cycle?
On any plan change the module calculates true line-item proration: it credits the unused portion of the current period and bills the new plan pro rata from the change date, rather than cancelling and recreating the subscription. The resulting adjustment posts as account.move lines so your accounting stays accurate and auditable.
Can I automate charging and connect my payment provider?
Yes. A nightly ir.cron job generates invoices for all due subscriptions, and where a supported payment provider is connected it charges the customer's saved token automatically, then routes failures into the dunning/retry sequence. We wire up your provider during the build. If you invoice manually (e.g. bank transfer), the same engine generates and sends invoices on schedule without auto-charging.
Can external systems create and manage subscriptions?
Yes. We expose a documented XML-RPC / JSON-RPC surface so your marketing site, mobile app, or external billing tools can create subscriptions, change plans, and read status programmatically. You get an integration guide with example calls as part of the handover.
相关模块
申请报价
Subscription & Recurring Billing Manager for Odoo (Community)
Enterprise-style subscriptions for Odoo Community — recurring plans, proration, trials, dunning & self-service portal, built & installed by ECOSIRE.
- subscription.plan model defining recurring price, billing interval (daily/weekly/monthly/quarterly/annual), trial length, and linked product/tax
- subscription.subscription lifecycle state machine (draft, trial, active, past-due, paused, cancelled) with @api.depends computed MRR, next-invoice-date, and trial-days-remaining fields
- Free-trial handling with automatic conversion to paid billing on trial expiry and configurable card-required-on-signup
- True line-item proration on upgrades, downgrades, and plan switches — credits unused time and bills the new plan pro rata mid-cycle