Member Type records store the types of membership offered by your association
Products are used to store data on any good or service sold. For example, Products are used for Dues but there is nothing physical which is actually sold. Products may represent a physical tangible object or something more abstract such as the benefits of membership with your organization. All Products are linked to a Price List Item that stores the cost of the Product
Dues Products act as a link between Dues Options and Products in the Product Catalog. There may be multiple Dues Products for any given Dues Option so that you may easily divide the funds which your association receives according to the amounts of the various Dues Products
Each contact may have one active membership record for each type of membership. This is important so that each contact can hold many types of membership, such as a realtor and an affiliate membership and have dues generated for both membership types. This also allows for an individual to keep one type of membership current and let the other one lapse if he or she so chooses
The attributes help you find commonalities and differences among that type of entity. There are different types of attributes so that you are not always entering text into fields
There are three basic types: manual, Order Paid, and Query based
Entities are defined as record types. For example, you have the contact entity to represent a person, the account entity to represent a company, and so on and so forth
There should be one Dues Schedule for each member type. You may still allow for multiple Dues Options within the Dues Schedule
You should create views that show you the types of records which you work with the most and the most relevant information for your particular job duties
Dues Proration records are used to define the proration schedule for the selected product for new members. The system will automatically generate the Dues Proration records for a Dues Product with a Daily, Weekly, Monthly, or Quarterly pricing strategy. Dues Proration records must be manually created for a Dues Product with a tabular or custom pricing strategy. Dues Proration records should never be created for a Dues Product with pricing strategy of None