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, almost entirely, 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. The one thing that does read it is a commission scheme’s Member Label rule — and see the caution below before you build one.

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.

A commission rule on Member Label matches any member who carries any label. The commission scheme lets you pick labels on the rule, but today the check only asks whether the sale’s member has a label link — not one of the labels you picked. So once you label members at all, a Member Label rule pays on every labelled member’s sale. Until that changes, build commission distinctions on Member Class too.

What labels are good for: recording a preference, marking a cohort, and telling the person who opens a member record something they need to know.

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 on the member record:

Recording a preference you are obliged to honour — NO-MARKETING is worth more than a spreadsheet somewhere, because it lives on the member record where the person working the list will see it.
Marking a cohort — EVENT, GAMING — so whoever opens the member knows how they came to you and what they care about.

What labels will not do for you today: pick out a segment on screen. The Member Listing search has no label filter — it searches by card, member, branch, IC, mobile, member class, dates and delivery address — and the membership report filters by join, end and birth dates only. If a campaign list has to come from a label, plan for that before you rely on it: a segment you need to select by is better carried as a member class, or kept alongside your campaign tool.

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:

Open a member and add a label on the Labels tab. It saves, and the label shows under its label list on that tab. (The tab’s search box reloads the list rather than filtering it — scan the list itself.)
Close the member, open it again, and the label is still there.
Check that none of your price sets or commission schemes is relying on a Member Label rule — if one is, rebuild it on Member Class.

Common mistakes

What goes wrong	What you see	The fix
A price rule built on a label	It applies to everybody	Use Member Class for anything that changes a price
Creating labels before the lists	Labels in the wrong grouping, hard to tidy	Create the label lists first
Uploading members with labels that do not exist	Rows fail validation	Create labels by code first
Using labels as tiers	The tiers do nothing at the till	Tiers are classes
A commission rule on one label	Commission paid on every labelled member’s sale	Build the rule on Member Class
Planning a campaign list around a label	Neither the Member Listing nor the membership report filters by label	Segment you must select by → a class
Fifty ungrouped labels	Nobody can find the right one	Group them into label lists, deliberately
Marketing preferences kept outside BigLedger	Somebody mails an opted-out customer	Put the preference on the member as a label