Membership Program

What It Is

A membership program defines one context in which a person or organization can hold membership. An association might offer national membership alongside a chapter-specific program. Each has its own recognizable reference, intended owners and connection to organizational units. Staff create the program before its types and packages so those records have a membership context to belong to.

The program is broader than a sellable offering. It collects choices shared by several classifications or packages: unit binding, numbering context, exclusivity, grace and continuity. Its membership types describe classifications within that context. A package then selects the program and one classification when describing what a purchase grants. This separation lets an annual and a lifetime offering share a membership context without becoming the same offering.

What It Is Not

A program is not the member’s individual holding or its effective terms. Those records belong to membership administration. It is not a chapter record, even when a chapter supplies the identity of a holding. Nor does it own prices or checkout configuration. Its Commerce settings describe inputs and references used elsewhere.

How It Is Used

Administrators establish programs when shaping the association’s membership model. They choose the owner category and unit relationship, then configure types and offerings. Readers consult the program to understand the context behind a package. Later calendar changes can affect interpretation of existing members because those settings are read live. A binding change deserves particular review: existing affiliation settings can survive the change even though the new binding no longer uses them in the same way.

Its Facets

Eligible owners. Owner categories distinguish people from organizational holdings.

Connection to units. Identity binding and affiliation binding answer different membership questions.

Affiliation requirements. Counts and primary choices guide the permitted unit connections.

Mutual exclusion. Groups restrict overlapping holdings where the consumer enforces them.

Membership numbers. Number scope describes the sequence or owner number used.

Calendar allowances. Grace and continuity are distinct time allowances.

Sales context. Ordering profiles and cancellation treatment reach Commerce without duplicating its checkout record.

Classifications. Types carry benefit and flow-down choices as facets of the program.

Undelivered choices. Some switches remain stored preparation rather than effective controls.

How It Relates

The hierarchy supplies the unit categories used for binding and affiliation requirements. Packages refer to a classification from the program and provide offering-specific terms. The term lifecycle reads grace, continuity and benefit inputs. Membership operations consume identity, owner, numbering and exclusivity settings, while Commerce interprets the program’s selling context.

What It Could Become

The product should define safe transitions between unit bindings and settle the stored grace-benefit and competing-holding switches. It should also decide whether membership numbers must be unique across programs, rather than assuming that separate numbering scopes guarantee that outcome. Clear consumer behavior would make these settings dependable choices for administrators.