← All articles

Blog

How to Set Up Subscription Plans and Auto-Renewals in Odoo

A practical guide to setting up subscription plans, billing cycles, and automatic renewals in Odoo — pricing, payment automation, and dunning for failed payments.

3 min read
  • mid
  • odoo

The promise of subscription software is that billing runs itself — customers are charged on schedule, renewals happen automatically, and you stop manually invoicing. But that only works if you set up your plans, payment automation, and failed-payment handling deliberately. Here is how to configure Odoo Subscriptions so it genuinely runs on autopilot.

Define your subscription plans

Start with the plans you offer. A plan defines what the customer gets, the price, and the billing frequency. Decide your structure:

  • Billing frequency — monthly, quarterly, annually. Many businesses offer monthly and a discounted annual option.
  • Tiers — if you have different levels (basic, pro, enterprise), set up a plan for each.
  • What is included — the products or services tied to each plan.

Keep your plan structure as simple as your business allows. A clear set of plans is easier for customers to choose and for you to manage than a sprawling matrix of options.

Set pricing and billing cycles

Configure each plan’s price and cycle. For Indonesian businesses, price in IDR and decide your billing dates — many subscription businesses bill on the customer’s signup anniversary, others on a fixed monthly date. Be clear about what happens on the first cycle (full charge, prorated, or a trial). Get these rules right at setup, because they drive every future invoice.

Connect payment automation

This is what makes renewals truly automatic. Connect a payment method so that, when a subscription renews, payment is taken without the customer having to do anything. For Indonesian subscribers, this means integrating a gateway that supports the payment methods they use — cards for automatic charging, and being realistic that some Indonesian customers prefer manual transfer or e-wallet, which affects how “automatic” renewal can be.

A practical reality: card-on-file auto-charging is smoothest, but is less universal in Indonesia than in some markets. Plan for a mix — auto-charge where you can, and a smooth renewal-payment prompt (with a payment link) where you cannot.

Configure auto-renewal

Decide and configure how subscriptions renew:

  • Auto-renew — the subscription continues and bills automatically each cycle until cancelled. Best for ongoing services where continuity is expected.
  • Manual renewal — the customer is prompted to renew. More friction, but appropriate where you want explicit re-commitment.

Most subscription businesses auto-renew, because it maximises retention (customers stay unless they actively leave). Be transparent with customers that it auto-renews, and make cancelling straightforward — both for trust and increasingly for fairness expectations.

Handle failed payments (dunning)

This is the step people forget, and it directly costs revenue. When an automatic payment fails — an expired card, insufficient funds — you need a process to recover it rather than silently losing the customer. Set up dunning:

  • Retry the payment automatically after a few days.
  • Notify the customer that their payment failed, with a link to update it or pay.
  • Escalate through reminders before suspending or cancelling.

A good dunning process recovers a meaningful share of failed payments that would otherwise become involuntary churn — customers who wanted to stay but whose payment quietly failed. For Indonesian businesses where manual-transfer renewals are common, clear renewal reminders (including via WhatsApp) are part of this.

Test the full cycle before going live

Before relying on it, run a test subscription through a full cycle — signup, first bill, renewal, and a deliberately failed payment to confirm dunning works. Confirm invoices post correctly to accounting and payments reconcile. Discovering that renewals do not charge, or that failed payments vanish silently, is far better in testing than with real subscribers.

Watch the metrics

Once running, watch your MRR, churn, and failed-payment recovery. These tell you whether the automation is healthy. A creeping involuntary-churn number, for instance, points to a dunning problem worth fixing.

Set up well, subscription billing genuinely runs itself and protects revenue through proper dunning. If you want help configuring your plans, payment automation, and a dunning process that fits Indonesian payment realities, we are glad to work through it with you in a free, one-hour conversation.