Clubs, associations, and membership-driven organisations quickly outgrow spreadsheets and disconnected tools the moment they try to track who is a current member, which tier they hold, when their dues lapse, and which activities they have registered for. Odoo's core sale, contacts, and event apps each hold a piece of this, but nothing on the base install models a membership as a first-class object with a renewal cycle, a state machine (draft → active → grace → lapsed → expired), and enforced access to member-only benefits. Teams end up reconciling partner tags, sales orders, and manual reminders by hand, and the picture is never trustworthy at renewal time.

Members Club is a build-to-order Odoo module ECOSIRE designs, builds, installs, and supports for your specific club rules. At its core we add a members.membership model (and supporting members.tier, members.activity / members.activity.registration models) with proper fields.Selection state, @api.depends computes for expiry_date, days_to_renew, and is_active, and @api.constrains guards so a member can't hold two overlapping active memberships in the same tier. Tier pricing and dues flow through native product.product/sale.order so invoicing, taxes, and your chart of accounts stay standard Odoo — no shadow accounting. Renewals, grace-period transitions, and lapse notifications run on scheduled ir.cron jobs plus automated actions (base.automation), so status is always current without anyone remembering to run a report.

Every capability is scoped to your governance model. Security is enforced through ir.model.access.csv groups (member, committee, admin) and ir.rule record rules so, for example, an activity coordinator sees only their own club's registrations while a treasurer sees dues across all tiers — and in a multi-company setup the company_id rules keep chapters separated. The member and back-office experience is delivered with standard views and OWL components (list, kanban by status, form with a smart-button to the member's activity history and invoices), and QWeb reports produce membership cards, renewal notices, and roster/dues PDFs on your letterhead. Where you need self-service — member sign-up, renewals, or activity registration — we can extend the Odoo website/portal controllers, and everything is reachable over the standard XML-RPC/JSON-RPC API for integration with a payment gateway, mailing platform, or door-access system.

Because it is built to order, delivery follows a clear path: a short scoping call to capture your tiers, dues cycles, activity types, and access rules; a fixed written quote; a build on a staging database; UAT with your team; then production install with a rollback plan and handover of the git repository. The module targets Odoo 17.0, 18.0, and 19.0 and works on Community or Enterprise (features that assume Enterprise-only apps are flagged during scoping so there are no surprises). Pricing starts from $249 (indicative, single-company base scope); additional tiers with distinct rules, multi-company or multi-chapter separation, portal self-service, payment-gateway integration, and migration of existing member history increase the quoted scope.