SaaS Subscription Automation for MEP Emart on Odoo 14 Community

Project at a glance

A subscription lifecycle for a multi-database Odoo SaaS (online recurring plans on Stripe and offline annual plans, automated database activation and expiry, renewals and reminders, plan upgrades and billing-interval changes, customer self-service and a central subscription-health dashboard) built entirely on the Community edition.

Client

MEP Emart

Industry

Technology & SaaS

Platform

Odoo 14 Community

Duration

3-4 months

Services

Odoo Development, Odoo Customization, Odoo Integration, Odoo Community, Business Automation, Odoo Finance & Accounting, Odoo Sales & CRM

The challenge

Customer subscriptions, database expiry dates and payments were tracked by hand across an Odoo 14 Community SaaS platform, creating administrative load and missed renewals. Online recurring and offline annual subscriptions both had to be supported.

Working through a similar challenge? Talk to an Odoo expert

The solution

Designed a subscription-management workflow for SaaS plans: Stripe recurring billing, offline subscription handling with bank-transfer and cheque records, automated database activation and expiration, renewal and payment reminders, plan upgrade and interval changes, payment history, customer self-service in the portal and centralised dashboards for monitoring every customer database.

How we built it

• Designed a subscription management workflow for SaaS plans.
• Automated recurring online subscriptions using Stripe.
• Implemented offline subscription management for annual plans.
• Developed automated database activation and expiration workflows.
• Built subscription renewal and payment reminder automation.
• Implemented plan upgrade and payment interval change functionality.
• Created centralized dashboards for subscription monitoring.
• Developed payment history and expiration tracking.
• Automated email notifications for renewals and expirations.
• Configured customer self-service subscription management.
• Performed testing, deployment, and production support.

Integrations

• Stripe
• Odoo Website & customer portal
• Email (SMTP)

How these are built and where they fail: Stripe payments in Odoo.

What changed

• Recurring billing and renewals automated
• Manual tracking of database expiry eliminated
• Customers upgrade plans and change billing intervals themselves
• Central dashboards and payment history across all SaaS databases
• Enterprise-style subscription capabilities on Odoo 14 Community

What made this project different

• Built entirely on Odoo 14 Community Edition, delivering SaaS subscription capabilities typically associated with Enterprise solutions.
• Unified management of both online recurring subscriptions and offline annual subscriptions.
• Automated database provisioning and expiration based on subscription status.
• Flexible support for multiple subscription plans and billing frequencies.
• Centralized monitoring of customer subscriptions across multiple SaaS databases.
• Scalable architecture designed for growing SaaS businesses.

Technology

• Odoo 14 Community
• Python
• PostgreSQL

Team

The expertise on the project, not personal profiles.

• Odoo Solution Architect
• Odoo Backend Developer
• Functional Consultant
• QA Engineer
• Project Manager

Questions