Skip to content

Seasonal Campaigns and Promotions

GadgetSphere runs a four-week festive campaign across all 22 branches and the GSO storefront: RM 50 off any smartphone over RM 1,500, a monthly voucher for GOLD members, birthday points, and double points on accessories that expire at the end of the quarter. Every piece is a record you can create today; the pieces the old page described that do not exist are listed at the end.

1. The festive voucher

In Voucher Management create voucher FEST50:

  • Voucher Type DISCOUNT, Quantity Type DYNAMIC (a serial is generated when claimed) or FIXED with 5,000 tickets; Status ACTIVE; Voucher Limit Per Customer 1; Daily Limit if you want to cap redemptions per day.
  • Event Period and Redemption Period covering the four weeks.
  • Treatment Value → For All: Price Source transaction amount, Operator SUBTRACT, Value 50, Min Spend 1,500.
  • Apply Rules → Doc Hdr: Event Date Range, Redemption Date Range, Branch (all 22); Single Line: Item Category = smartphones.
  • Website Link to the GSO storefront so the cart accepts the code.

At the counter the cashier scans or keys the serial; POS General checks the voucher’s rules and limits and rejects it with the reasons on its troubleshooting table. Redemption does not check the date range itself — run the voucher expiry-checking call after the campaign so leftover tickets go EXPIRED.

2. A monthly voucher for GOLD members

A Recurring Voucher with a recurrence rule (monthly on the 1st), type DISCOUNT, quantity FIXED, and a Member Class rule = GOLD. RECURRING_COUPON_CREATION_PROCESSOR creates that month’s voucher when it runs; schedule it once a day in the Scheduler — the processor’s own description warns that running it more than once a day duplicates the vouchers.

3. Birthday points

Create a schedule for MEMBER_BIRTHDAY_GIFT_PROCESSOR with gift type POINTS, point currency GSPTS, point amount 500, points_validity_in_months 3, member_class_guids = GOLD, and the e-mail fields if you want a message sent. The processor can alternatively assign vouchers (vouchers_to_assign). It adds the points on the birthday or month according to its check frequency; there is no “birthday multiplier” on purchases.

4. Double points on accessories, expiring at quarter end

Add a second price set to the default price book: Single Line rule Item Category = accessories, Doc Hdr Valid Date Range = the campaign dates (absolute), POINT treatment Operator MULTIPLY, Value 2, Validity Period (Days) = the days left to quarter end. Every accessory line earns a lot whose date_end is that date; the scheduled elimination processor writes an EXPIRY line and zeroes the lot when it passes. A separate GSFEST point currency is only worth creating if you want a separate balance the customer can see; it expires the same way — per lot, never by a “hard delete on end date”.

Watching it

  • Membership Admin → each member’s Point Transaction and Points Expiry tabs.
  • Sales Report → Voucher Redemption (by voucher code, company, date redeemed).
  • Voucher Management → Ticket Management counts (generated, assigned, redeemed) and the CSV export.
  • MEMBERSHIP_POINTS_EXPIRY_REMINDER_PROCESSOR e-mails members whose lots are about to expire, if scheduled.

What the old page had and the product does not

A “temporary currency” type with a hard expiry and an exclusive catalogue; multiplier campaigns configured in a Campaigns screen, stacking with tier multipliers; category-specific multipliers that “override the campaign base”; multi-location and omnichannel bonuses; social-media and review earning; a daily lucky-draw spin; purchase-threshold gift tiers; a redemption-bonus percentage; tier-based flash-sale discounts with caps; hourly lightning deals with stock counters; a scheduled communication engine. None has a screen or a processor. What you have is voucher rules, price-set rules, and three job processors on a schedule you create.