Skip to main content
Updated Oct 19, 2026
Zu Wei
18 min read
9 views

When Does a Customer's Voucher Expire?

What Is This?

Pixalink uses three different expiry dates across the reward system. They live on three different things: the reward itself, the voucher code you upload, and the voucher your customer claims. Each one controls something different — this article explains which date does what, and what to put in the Expired At column when you upload third-party voucher codes.

How It Works

Pixalink rewards come in two flavours. Most rewards run without a voucher pool — Pixalink just hands out a fresh voucher to each customer. Third-party rewards (Shopify, WooCommerce, partner promo codes) run with a voucher pool that you upload upfront. Both flows are below.

Flow 1 — Standard reward (no voucher pool)

This is how about 7 out of 10 rewards work. The merchant sets the rules. The customer claims. Pixalink creates a fresh voucher on the spot.

The standard voucher: setup, claim, use The standard voucher: setup, claim, use. Setup time (you do this once). Merchant to Reward: Set End Date and Custom Valid Days. Claim time (per customer). Customer to Reward: Claim the reward. Reward to Customer Voucher: Pixalink calculates Expired At from the reward's rules. Customer Voucher to Customer: Voucher delivered. Use time (before Expired At). Customer to Customer Voucher: Redeem at outlet. The standard voucher: setup, claim, use Setup time (you do this once) Merchant Reward Set End Date and Custom Valid Days Claim time (per customer) Customer Reward Claim the reward Reward Customer Voucher Pixalink calculates Expired At from the reward's rules Customer Voucher Customer Voucher delivered Use time (before Expired At) Customer Customer Voucher Redeem at outlet

Flow 2 — Third-party voucher reward (with voucher pool)

This is for partner promo codes. The merchant uploads a pool of pre-made codes. When the customer claims, Pixalink picks one from the pool — but still calculates the customer's Expired At from the reward's rules, not from the pool code's date.

Partner codes: setup, claim, use Partner codes: setup, claim, use. Setup time (you do this once). Merchant to Reward: Set End Date and Custom Valid Days. Merchant to Voucher Pool: Upload 3rd-party codes (Expired At per code, optional). Claim time (per customer). Customer to Voucher Pool: Claim a code. Voucher Pool to Reward: Read the rules (pool code's Expired At ignored). Reward to Customer Voucher: Pixalink calculates fresh Expired At. Customer Voucher to Customer: Voucher delivered with the partner code. Use time (before Expired At). Customer to Customer Voucher: Redeem the partner code. Partner codes: setup, claim, use Setup time (you do this once) Merchant Reward Set End Date and Custom Valid Days Merchant Voucher Pool Upload 3rd-party codes (Expired At per code, optional) Claim time (per customer) Customer Voucher Pool Claim a code Voucher Pool Reward Read the rules (pool code's Expired At ignored) Reward Customer Voucher Pixalink calculates fresh Expired At Customer Voucher Customer Voucher delivered with the partner code Use time (before Expired At) Customer Customer Voucher Redeem the partner code

The key difference: in Flow 2, the pool code carries its own Expired At, but Pixalink ignores it when creating the customer's voucher — it always recalculates from the reward's rules.

How the voucher’s expiry is calculated How the voucher’s expiry is calculated. Customer claims a code to Custom Valid Days toggle on?. Custom Valid Days toggle on? to Use the reward's End Date: No. Custom Valid Days toggle on? to Reward has an End Date?: Yes. Reward has an End Date? to Use today + Valid Days: No. Reward has an End Date? to Which is earlier?: Yes. Which is earlier? to Use today + Valid Days: today + Valid Days. Which is earlier? to Use the reward's End Date: End Date. Use the reward's End Date to Set time to 23:59:59. Use today + Valid Days to Set time to 23:59:59. Set time to 23:59:59 to Save as Customer Voucher Expired At. How the voucher’s expiry is calculated Customer claims a code Check 1 Custom Valid Days toggle on? No Use the reward's End Date Set time to 23:59:59 Save as Customer Voucher Expired At Yes Continue at check 2 Reward has an End Date? Check 2 Reward has an End Date? No Use today + Valid Days Set time to 23:59:59 Save as Customer Voucher Expired At Yes Continue at check 3 Which is earlier? Check 3 Which is earlier? today + Valid Days Use today + Valid Days Set time to 23:59:59 Save as Customer Voucher Expired At End Date Use the reward's End Date Set time to 23:59:59 Save as Customer Voucher Expired At

Layer 1 — The Reward (your campaign)

The reward is the campaign itself. It has two date settings, no "Expired At" of its own:

  • End Date — when the whole campaign closes.
  • Valid Days — only used if you turn on the Custom Valid Days toggle. When on, it sets how many days each customer gets to use their voucher after claiming.

If the Custom Valid Days toggle is off, Valid Days is ignored — even if a number is saved.

Layer 2 — The Voucher Code (your uploaded pool)

When you upload a list of third-party codes (Shopify, WooCommerce, partner codes), each code sits in a pool waiting to be claimed.

Each code can have its own Expired At, but this field is optional — it's only there for third-party uploads. If you leave the column blank, Pixalink fills it in for you using the reward's rules. If you do set it, the code stops being claimable after that date, even if nobody has used it.

Layer 3 — The Customer's Voucher (what they hold)

When a customer claims a code, Pixalink calculates the voucher's Expired At fresh. It does not copy the pool code's date. Here's how it works, step by step:

  1. Start with the reward's End Date.
  2. Is the Custom Valid Days toggle on? If no, stop — the voucher expires on End Date.
  3. If yes, also calculate today + Valid Days. Use whichever date comes first (the earlier one wins).
  4. Always set the time to the end of that day (23:59:59).

If the reward has no End Date but Custom Valid Days is on, the voucher just gets today + Valid Days.

Real-Life Examples

Pixalink rewards use one of three expiry setups. We've ranked them from most common to least common based on how merchants actually set up their rewards.

Most common: Rolling expiry (no End Date)

Around 7 out of 10 rewards work this way — evergreen rewards like welcome gifts, birthday treats, and tier perks.

Aishah runs a cafe in Bangsar. She sets up a welcome reward with no End Date and Custom Valid Days 30. Every new customer's clock starts when they claim:

  • Wei Lin signs up 5 December → his voucher expires 4 January.
  • Siti signs up 28 December → hers expires 27 January.

There's no campaign close date — the reward just keeps running.

Common: Fixed campaign (End Date only)

About 1 in 4 rewards work this way — short campaigns where everyone gets the same deadline.

Ahmad runs a bakery and launches a Hari Raya promotion with End Date 30 April and Custom Valid Days off. Every customer who claims, no matter when, gets the same expiry:

  • Priya claims 10 April → expires 30 April.
  • Farah claims 29 April → also expires 30 April.

Simple and predictable for time-bound events.

Less common: Capped campaign (End Date + Valid Days)

Only about 3 out of 100 rewards use both — usually third-party voucher campaigns where the merchant wants a usage window inside a fixed campaign.

Wei Lin runs a bubble tea chain. He uploads 500 partner promo codes with End Date 31 December and Custom Valid Days 14:

  • Aishah claims 5 December → her voucher expires 19 December (5 Dec + 14 days).
  • Siti claims 27 December → hers expires 31 December (the campaign end caps it).

What to Set When Uploading Third-Party Vouchers

The Expired At column in the upload CSV is optional. You have two choices:

  • Leave it blank (recommended for most cases) — Pixalink uses the reward's rules to fill it in.
  • Type the campaign End Date — keeps every code claimable until the campaign closes.

If your partner's codes truly expire earlier (for example, "these only work until 15 December"), use that date instead.

Good to Know

  • The customer's voucher expiry is locked in at claim time — editing the reward later doesn't change it.
  • The pool code's Expired At is never copied to the customer's voucher (except for one case below).
  • If you pre-assign a code to a customer during import by adding their phone number to the CSV, that customer's voucher does copy the pool code's Expired At directly.
  • Customer vouchers always expire at the end of the day (23:59:59).
  • Codes that expire while still in the pool are ignored — no customer ever sees them.

Need Help?

If you're not sure what date to put on your voucher upload, contact the Pixalink support team — they can check your reward setup with you.

What's Next?

Was this article helpful?

Thank you for your feedback!

0 found this helpful 0 did not

Search