Skip to content

Related Applets

Membership leans on more of BigLedger than its own six applets: the till, the price book and the Scheduler decide much of what a member earns and when it expires. This page is for whoever sets the programme up or chases a cause that sits in one of them. It lists what the Membership module owns, what each applet records, and what the module borrows from other modules. Which applets belong to the module is an editorial judgement — the product holds no module↔applet relationship.

Applets in this module

One further registry row assigned to this module is a subsidiary’s product and is not documented here.

What each applet records

AppletWhat it records
Membership AdminMembers (card number, member ID, referral code, class, verification status, join / start / end date or lifetime, suspensions), member classes (tiers — a manual assignment), labels and label lists (segments), point currencies and point-to-money rates, manual point adjustments, the per-member point transaction and expiry views, CSV uploads of members and point transactions, the Membership Report and a log of who changed what, from which device. Master data: no document, no posting
Commission SchemeThe rules (which documents qualify — branch, company, document type, date, customer type, member class, sales-agent category, items) and treatments (how much per level) for sales commission and for membership points; Sales Groups; tiered Pricing Models. A scheme’s Membership Points treatment is the scheduled points source; its MLM commission type is what makes a referral tree pay
Voucher Management Applet V2Vouchers (SETTLEMENT, DISCOUNT, REWARDS or PRODUCT; FIXED, DYNAMIC, IMPORT or INVENTORY quantity), their tickets (serial numbers with assignment, validity, cancellation and redeemable status), rules (document-header and line rules), treatments, website links for the storefront, recurring vouchers on a recurrence rule, ticket imports and scanned events. Master data: no posting
Voucher ManagementThe earlier build of the same applet — Voucher, Ticket and Scanned Event only. Both registry rows are active and both point their documentation at the V2 page; which bundle each row installs is pending a registry check
MLM Admin AppletReferral programs, their participants (members enrolled in a program, each with an invite key and QR link), the lineage (one upline→downline edge per row, level computed 1…10), invitations sent through a contact-centre channel and accepted through a registration endpoint, and entity contacts — named people under a customer who are not yet members
OCR Cash BillThe receipt-to-points pipeline: a member’s photographed third-party bill, the text-extraction result, merchant and line matching, and the price book that turns matched lines into point transactions

Applets it depends on, owned elsewhere

AppletOwnerWhy the module needs it
POS GeneralPoint of SaleWhere members are looked up and created at the counter, where bill lines get their point amounts from the default price book, and where points and vouchers are redeemed as settlement or discount lines
Sales Invoice (Internal), Sales Order (Internal)SalesThe other document types a company can name in its member-point configuration; the default is a FINAL sales order
Customer MaintenanceCoreThe customer entity a member may be linked to; its Membership tab shows plan and points; credit control lives here, not in any membership applet
Doc Item MaintenanceCoreThe MEMBER_POINT_DISCOUNT item for redemptions, the item on every manual adjustment, the COUPON item type whose stock in and out reflects voucher tickets, the MEMBERSHIP item type
PricebookCorePrice sets with Member Class rules and discount, sales-price or POINT treatments — the only place an earning rate lives, and the price book the OCR processor evaluates
OrganisationCoreCompanies and branches every member, adjustment and permission target is scoped to; the company member-point configuration, which has no screen
CP Commerce AdminE-CommerceStorefront sign-up that creates members, the default class and per-class spending limit, voucher and commission-scheme links per website, the membership points and voucher steps at checkout, the points counter widget
Sales ReportSalesThe Voucher Redemption report. Its member-reward-redemption route is off the menu and shows sales rows, not points; points earned and redeemed come from the API’s transaction-lines query — see Reports
Sales CommissionSalesThe cycle and posting run that turn an MLM or sales-agent scheme into money, and the scheduled run that turns a scheme’s points treatment into point transactions
SchedulerPlatform tool (no module)Every membership job runs only if scheduled here: points expiry elimination, birthday gifts, MLM invitation sending and lineage insertion, entity linking. Three do less than their names say: the expiry reminder processor runs the expiry and e-mails nobody; the zero-balance status processor acts only on a point currency coded ACCESS; the recurring voucher run creates no vouchers today (see Points expiry and Voucher Management)
Unified Contact CenterDigital CRMThe endpoints an MLM program sends invitations through; an agent can merge a conversation’s contact with a membership card

What is not an applet

Two pages under the membership folder — Membership Points Currency and Membership Program — described screens of Membership Admin as if they were applets of their own. They are not registry rows; point currencies are the PTS CCY Module inside Membership Admin, and the prerequisites the “program” page listed are on that applet’s Before you can use it section.

When the cause of a wrong balance is in one of these applets, start from the symptom on Membership points and vouchers — troubleshooting.