Membership & Association Management

ECOSIRE builds a purpose-made Frappe app — its own membership_association app installed on your bench — that turns ERPNext into a complete association management system while keeping accounting, payments, and reporting native. We model the domain properly with custom DocTypes: Membership Tier (fee, billing frequency, entitlements, eligibility), Member Profile (extending the core Member with photo, category, join date, standing), Dues Schedule, Committee, and Committee Assignment. Membership status is a controlled lifecycle — Prospect → Active → Grace → Lapsed → Reinstated — enforced through hooks.py document events (on_submit, on_update, validate) and Server Scripts so a member can never land in an inconsistent state.

Recurring dues and renewals are driven by ERPNext's native Subscription and Sales Invoice engine, wired to your payment gateway, so revenue posts to the correct income accounts and shows up in standard financial reports with zero double entry. Scheduler Events (registered as scheduler_events in hooks.py) run nightly to flag upcoming expirations, send staged renewal reminders via ERPNext Notifications, move unpaid members into grace and then lapsed, and generate the next billing cycle. ID cards and certificates are produced from Print Formats (Jinja + HTML/CSS) with QR codes that resolve to a whitelisted verification method, and Client Scripts add the in-form actions staff use daily — "Renew", "Issue Card", "Assign to Committee".

The member-facing side is a self-service portal built on Frappe's web framework and Portal Pages: members log in to update their profile, download invoices and receipts, renew online, register for events, and browse a permission-scoped member directory. Everything is governed by ERPNext's role and permission model — we ship dedicated Role Profiles (Member, Chapter Admin, Membership Officer) with row-level permission rules so members see only their own records and officers see only their chapter. A whitelisted REST/Frappe API surface lets you integrate the association data with a public website, mobile app, or email platform.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, confirm your tiers, dues cadence, committee structure, and portal requirements in a written specification, then build against it. Typical delivery is 2–4 weeks from confirmed scope depending on complexity. You get the installable app source code for your ERPNext version (v15 or v16), a UAT pass on a staging bench with a documented rollback plan, deployment to production, training for your team, and a post-go-live support window. The full git repository is handed to you at the end — you own it.