Klaviyo expiry properties
Two Klaviyo profile properties, shopwaive_expiry_date and shopwaive_expiry_amount, and the date-triggered flow that reminds customers before their points expire
On a store that uses Shopwaive's balance expiry engine, Klaviyo balance sync also writes two profile properties about points that are due to expire. A Klaviyo flow that is triggered by the date can remind each customer before the points are gone.
The two properties
shopwaive_expiry_date
Date
2026-10-15T00:00:00Z
The time at which the customer's soonest points expire, as a UTC timestamp.
shopwaive_expiry_amount
Number
120
The points that expire in the 24 hours from that time. It is shown the same way as shopwaive_balance, and it is never more than shopwaive_balance.
One expiry at a time. The properties describe the soonest expiry only. When those points expire or are spent, both properties move to the date and the amount that follow.
Removed when nothing is due. A customer who has nothing due to expire has neither property.
Spending lowers the amount. Points that are spent are taken from the points that expire soonest, so the amount usually goes down when the customer redeems.
Read-only. Treat both properties as read-only in Klaviyo, as you do
shopwaive_balance.
On a Balance store the amount is money to two decimals. This page says points.
The date is a time, not a day
shopwaive_expiry_date holds a time of day in UTC. 2026-10-15T00:00:00Z means that the points expire at that instant: midnight UTC, at the start of 15 October.
What that means for a customer depends on where the customer is:
3 hours ahead of UTC
3:00 AM on 15 October
14 October
UTC
Midnight, at the start of 15 October
14 October
5 hours behind UTC
7:00 PM on 14 October
13 October
So:
Do not write that the points expire "on" the date. A customer reads that as the end of that day, and the points go earlier, at the time in the table.
Write the message for your customers' time zone. Where the instant falls in the early hours of the date, as in the first row, "use your points before 15 October" is right. Where it falls on the evening before, name an earlier day or show the time.
Start the flow at least 1 day before the date, and earlier where the instant falls on the evening before.
Build the reminder flow
In Klaviyo, open Flows, click Create flow, and choose Build your own. Choose the trigger Date property and pick
shopwaive_expiry_date. Klaviyo offers a date property once at least one profile carries it.Choose to start the flow before the date, and set the number of days, for example 7. Any number from 1 works.
For how often the flow repeats, choose Should not repeat.
In the trigger settings, set Re-entry criteria to Allow re-entry after a time period, for example 7 days. Klaviyo reschedules a customer whose date changes, and this setting limits how often one customer can enter the flow.
Write the message. Show the amount with
{{ person.shopwaive_expiry_amount }}and the date with{{ person.shopwaive_expiry_date }}.Add a second message nearer the date, for example 1 day before. Klaviyo puts a customer whose date is already less than 7 days away into the flow at the matching point, so that customer skips a message timed 7 days before and gets the one nearer the date.
Keep the messages in Draft until Preview & test shows what you expect, then set them to Live.
A sentence to start from:
The date reaches your template as a UTC timestamp, which is not a form to show a customer. Format it in the template, and check in Preview & test which day it shows for a customer whose date you know. Klaviyo lists its date filters in Date personalization in templates reference.
Klaviyo's own pages on this flow:
How to create a segment- or list-triggered flow, which describes Re-entry criteria for every flow type, and says that the setting is still reaching some accounts
What Klaviyo does with the date
These points come from Klaviyo's pages, linked above.
Klaviyo checks all profiles daily, and whenever a date is added, updated or deleted.
When it triggers the flow, Klaviyo ignores the time of day in the property. It works out the day on which a customer enters from the customer's own time zone, or from your account's when the profile has none. So "1 day before" a date of 15 October enters on 14 October.
When a customer's date changes, Klaviyo reschedules that customer for the new date.
Klaviyo schedules customers only for messages that are set to Live or Manual, and its check runs a full day ahead. A customer whose date is less than a full day after you set the flow live can be missed.
Good to know
Later points can go without a message. The properties describe one expiry at a time. If a customer has points that expire a few days after the first ones, and your flow starts more days ahead than that, the later points do not get a message of their own.
Very small amounts are not reported. An expiring amount below the smallest amount your store shows, such as less than half a point, is skipped, and the properties describe the expiry after it.
Rounding. The balance and the expiring amount are each rounded to what your store shows. On a Loyalty and Rewards store they can differ by one point from the sum you expect.
If balance sync is paused or disconnected, the two properties stay on your profiles as they were, and Klaviyo goes on using the dates. Set the flow to Draft first, or ask Shopwaive support to remove the properties.
After the points have expired. To message customers once their points are gone, see Shopwaive: Balance Expired.
Questions? Send us a message in the in-app chat or email support@shopwaive.com.
Last updated