Member Setup
This section is for whoever keys or imports members, and for whoever decides what a member record holds. A member is a card with a card number, an optional link to a customer entity, one class, any number of labels and a point balance per currency. Everything in this section is maintained in the Membership Admin applet.
| Page | What it covers |
|---|---|
| Member Classes | The one tier a member holds; assigned by hand, never by the backend |
| Member Labels | Tags a member can hold several of; grouped in label lists |
| Member Creation | The member form, the card-number rule, and how a member gets its customer entity |
| Bulk Import | The Upload Membership and Upload Member Point Transaction CSVs |
Order. Classes and labels first, because the member form and the CSV refer to them by code. Then the card-number rule. Then members.
One member, one class. A membership header is one record with one class; a person who holds two cards is two member records, and nothing joins their balances (Merge two cards for one person, in this order). The previous version of this section described one membership holding several balances; BigLedger has no umbrella membership that joins several cards or their balances, so each card stays a member record of its own.
The jobs, step by step. The task guides for these records are Member Classes, Member Label Lists, Member Labels and Registering a Loyalty Member, in the order above.