Memberships within MemberKit have a defined period, type and status. Memberships typically remain active for a single payment period and upon a member renewing a new 'membership' is created. Therefore accumulating in a list of memberships attached to a single profile over time, compared to more basic systems that simply retain a snapshot of a single and current membership type, status and end date.


In order to use memberships in MemberKit, you will need to:


  • Define Membership Statuses
  • (optional) Define Membership Categories
  • (optional) Define Membership Cycles (otherwise, rolling or 'anniversary' type can be used)*
  • (optional) Define Profile Fields (to capture additional user information within Membership join/renew forms)
  • Message templates (to send to uses on first join, renewing, expiring, defined notifications, etc.)
  • Invoice template


* Rolling or 'Anniversary' periods simply start from the date joining (or follow the end date if the same membership type is currently active).



Membership Types


Membership types the overall behaviour including approval process, join and renew forms, pricing structure and notifications to be triggered relating that that membership.


Membership Categories


Membership categories helps to group several membership types. This typically doesn't provide functional benefits, just something to help you organise your membership types.


Membership Status


Memberships status indicates a state of membership at any particular time. For example, active, pending, cancelled, etc.. The status also determines if a member has access to resources and member pricing, or receives follow up notifications to renew or post renewal (ie. if a membership status is defined as 'cancelled', there member typically shouldn't receive follow up notifications to renew).


Membership Periods & Cycles


Each membership type can be specific with varying pricing and pricing periods. Rolling or Anniversary types simply adds a set period to the end of the current expiry date (unless joining or the expiry date has already past, which the current date will be used). Cyclical types allow you to define specific pricing periods, for example 1st January to 31st March, then 1st April to 30th June etc., or recurring periods that can be weekly, monthly, quarterly, semi-annual or annual (for which the start of the billing week or month can also be adjusted).