Points Redemption Strategies

A GadgetSphere member with 12,000 GSPTS (RM 120 at 100 points = RM 1) buys an ultraportable laptop for RM 3,499 at GS-PEN-01. There are three ways the points, or a voucher, can reduce what they pay. Each is a different line on the cash bill, and the ledger sees each differently. This page is the worked example, for whoever decides how members may spend; the mechanism behind each road is on Reward Types.

1. Points as a settlement line

The cashier picks the member points settlement button in POS General. The panel converts points to cash through the PTS to CCY rate, up to the points settlement method’s limit — an amount, or a percentage of the bill — and never more than the balance is worth; the customer pays the rest by card. The till’s cap is the only check: the server does not re-check a points settlement at FINAL, because it is a payment line. Only the points-discount line is checked against the member’s stored balance (Reward Types sets the two buttons side by side).

The REDEEM transaction line, and the draw-down of the member’s lots (the soonest-ending unexpired lot first, one contra row per lot), follow only if the company’s member-point configuration names the cash bill and its posting status. It defaults to a FINAL sales order. Left at the default, the till takes the points as payment and nothing ever deducts them — the member keeps the balance they just spent. Finalise one redemption on a test member before go-live and check that a REDEEM line appears on their Point Transaction tab.

Ledger: the cash bill posts its full revenue; the points settlement is one of the bill’s settlement-method lines and posts the way the cash bill’s settlement lines post — to the account of the cashbook named on the points settlement method (Reward Types → Points sets out where each button lands). That is the cash bill’s posting, not the module’s.

2. Points as a discount line

If the branch is configured with a Points Discount Item Code (POS_DEFAULT_POINTS_DISCOUNT_GUID, a MEMBER_POINT_DISCOUNT item from Doc Item Maintenance), the redemption becomes a negative line on the bill using that item. Revenue is reduced by RM 120; the customer pays RM 3,379. This path converts at a fixed 100 points to RM 1, in steps of 100, whatever your PTS to CCY rate says — it matches here only because GadgetSphere’s rate is also 100 to 1. The same REDEEM transaction line is written, under the same configuration condition.

Ledger: revenue is lower by the discount, posted to the discount item’s GL code. Again the cash bill’s posting.

3. A voucher

A SETTLEMENT voucher from Voucher Management (face value RM 100, a FIXED quantity of tickets, a Member Class rule) is redeemed by scanning the ticket serial: it must sit on a settlement-method line of the bill; a PRODUCT voucher must sit on a product line. At FINAL the server marks the ticket redeemed and records the bill, branch and location on it, and the ticket’s history shows Redeemed against the bill. Unless the voucher allows anonymous use, only a ticket assigned to the bill’s customer is marked — a member’s ticket redeemed on a bill made out to a walk-in customer stays unredeemed. Nothing moves a ticket to EXPIRED; that takes the voucher expiry-checking call. Redeeming a ticket writes no membership point line.

Ledger: the voucher line is a settlement line of the bill and posts as the bill’s settlement lines post. The redemption job itself writes ticket fields only — no voucher-liability or breakage journal. If you sell vouchers, the liability is a journal somebody books.

What the member pays on each road

On the RM 3,499 laptop, with 12,000 GSPTS worth RM 120 at GadgetSphere’s rate:

Road	What the bill shows	The member pays the rest	What the membership records write
1. Points settlement	A RM 120 payment line beside the card, if the settlement method’s limit allows that much	RM 3,379 by card	A `REDEEM` line, only where the cash bill is the configured awarding document and the follow-on points job runs for your tenant
2. Points-discount line	A RM 120 negative line on the discount item, posted to that item’s GL code (or the company’s default sales code if it has none)	RM 3,379	The same `REDEEM` line, under the same condition
3. RM 100 voucher	A RM 100 settlement line carrying the ticket serial	RM 3,399	No point line; the ticket is marked redeemed after FINAL, if it is assigned to the bill’s customer (or the voucher allows anonymous use) and inside its redeemable dates, where the redemption step runs for your tenant

The cost of each road to the business, and who carries it, is on Reward Types → What each one costs.

What the membership tables record

Event	Row written
Earning	A `REWARD` transaction line, one per document line with a point amount; a lot with a start and an end date
Redemption (1 or 2)	A `REDEEM` line, drawn against the lots it consumed; the running balance updated by the queued rebuild — provided the cash bill is the configured awarding document
Void of the bill	Nothing is reversed: the redeemed points are not returned. Post a Point Adjustment on the member to give them back
Expiry	An `EXPIRY` line and the lot zeroed, by the scheduled elimination processor

None of these rows carries an amount signum, and journal posting has no rule for them. A points balance is not a liability account in BigLedger. If Finance wants to carry one, it is a manual journal from the current-balance API each month-end.

Online

On a CP Commerce storefront the checkout widget can enable membership points and cash vouchers; the cart order earns points through the same document-type and status rule, run by the CP Commerce member-points processor, and the storefront shows the balance with the Membership Points Counter widget (CP Commerce Admin). Two differences from the till: the storefront job writes its lines as adjustments (ADJ) valid until 31 December 9999, so online points never expire whatever the price book’s validity says; and it skips the order altogether when the company’s scheduled point-assignment days is set to 0, because it is the same code that runs a company’s delayed award (Membership in Depth).

What the old page had and the product does not

A rewards catalogue with point prices and separate rewards inventory; “smart redemption suggestions” and minimum-purchase tiers; partner rewards (cinema, streaming, dining, hotel) with a partner API; charitable donations with tax receipts and leaderboards; gift-voucher generation from points with a 12-digit code and a member wallet at the counter (the one points-for-voucher path is a storefront’s Buy Now, in Membership in Depth); a built-in 50 %-of-transaction rule (a percentage cap is a setting on the points settlement method, above); burn-rate analytics.

The only redemption paths are the three above, and the only limits are the points settlement method’s limit, the stored-balance check at FINAL on a points-discount line, and, for a voucher, its Daily Limit on a free gift the till adds by itself (Voucher Rewards says what not to rely on).