Skip to content
Member Labels

Member Labels

A label is a tag you put on a loyalty member: joined at the Penang launch, prefers e-mail, opted out of SMS, bought a laptop in the last year. A member can carry as many as you like.

This page creates labels and, just as importantly, tells you what they cannot do.

Labels versus classes, in one line

A class changes what the system does. A label is for you.

  • Member class — the tier. Price rules and commission schemes read it. One per member.
  • Member label — a segment. Nothing in pricing reads it. Any number per member.
A price-set rule on Member Label does not work. It is one of the rule types BigLedger’s pricing calculator does not evaluate — it treats the rule as satisfied, which means the price set applies to everybody rather than to the labelled members. If a distinction has to change a price, make it a class.

What labels are good for: choosing who goes into a campaign, recording a preference, marking a cohort, and filtering your member list.

Meet GadgetSphere

GadgetSphere Sdn Bhd labels members by how they joined (IN-STORE, ONLINE, EVENT), by contact preference (PREF-EMAIL, PREF-SMS, NO-MARKETING), and by interest (GAMING, PHOTOGRAPHY). None of those changes a price; all of them decide who hears about what.

Before you start

Decide your label lists first. A label belongs to a label list — the grouping — and a label created inside a list carries that list’s code. Getting the lists right before you create fifty labels saves re-doing them. See member label lists.

For GadgetSphere that is three lists: Join channel, Contact preference, Interests.

Step 1: Create the labels

Membership Admin > Member Label > +

Three fields: Label Code, Label Name (required) and the Label List it belongs to.

Keep codes short and readable — they appear in the member-upload CSV and in your own exports.

Step 2: Put labels on members

A member > Labels tab

Link a label; unlink it when it no longer applies. There is no limit.

For an existing list of members, the Upload Membership CSV carries three label columns. The labels must already exist by code — a row naming a label that is not there fails validation, and the Checking tab tells you which.

Step 3: Use them

Labels earn their keep in two places:

  • Filtering the member listing and the membership report, so a campaign goes to the right people.
  • Recording a preference you are obliged to honourNO-MARKETING is worth more than a spreadsheet somewhere, because it lives on the member record where the person working the list will see it.

If you find yourself wanting a label to change a price or a commission, stop: that is a class.

What success looks like

Two minutes:

  1. Open a member and add a label on the Labels tab. It saves.
  2. Go to the Member Listing and filter by that label. The member comes back.
  3. Check that none of your price sets is relying on a Member Label rule — if one is, rebuild it on Member Class.

Common mistakes

What goes wrongWhat you seeThe fix
A price rule built on a labelIt applies to everybodyUse Member Class for anything that changes a price
Creating labels before the listsLabels in the wrong grouping, hard to tidyCreate the label lists first
Uploading members with labels that do not existRows fail validationCreate labels by code first
Using labels as tiersThe tiers do nothing at the tillTiers are classes
Fifty ungrouped labelsNobody can find the right oneGroup them into label lists, deliberately
Marketing preferences kept outside BigLedgerSomebody mails an opted-out customerPut the preference on the member as a label

Related documentation

Last updated on