Skip to content

Redemption Notifications

A customer who pays with a gift card walks away without knowing what is left on it. Redemption notifications close that gap: every time a card is used, the card holder gets an email, a text message, or both, with the date, the amount taken off, the balance remaining and — for in-store purchases — the branch where it happened.

This is what a bank does after a card payment, and customers expect the same from a gift card. It also cuts down "how much is left on my card?" enquiries, and the depletion message is a natural moment to bring someone back.

The person who bought the card as a present can be told as well: see Who gets notified.

From the home page, open the Customer notifications card and click Configure notifications, then open the Redemption notifications tab. (The page's other tabs are Unused balance reminders and Loyalty emails.)

The tab holds the policy — whether notifications are on, when they go out, who gets them, on which channels, and through what. Each message is edited on a page of its own, where a preview and a test send travel with it, and the delivery log has a page of its own too.

Redemption notification settings


Turning notifications on

Notifications are off until you click Enable at the top of the tab, and the switch is per store. Click Save in the save bar to apply it.

Turning them on subscribes Gift Card Hero to your store's payment events so it hears about a redemption the moment it happens — at the till as well as online. Turning them off unsubscribes again; nothing is sent and nothing is recorded.

Redemptions made in Gift Hero POS, the web app for non-Shopify registers, don't send notifications.


When to send

Under When to notify, two triggers — both are ticked by default, and you can use either or both:

  • On every redemption — a message after each redemption, whatever the balance. One message per gift card used on an order: paying with two cards sends two.
  • When the balance reaches zero — a "your card is now fully used" message, sent even when the first option is off.

With both on, a redemption that empties the card sends one message per channel, not two — the depletion wording replaces the ordinary one.

With only the second option on, customers hear from you once, at the end. That suits stores where cards are typically spent over many small purchases and a message per coffee would be noise.

You cannot save the settings with the feature on and neither trigger selected: that would subscribe to the events and then discard every one of them.


Including the branch

Include the store location (ticked by default) adds the branch to the message.

The location is the Shopify POS location the sale was made on, or the branch your till app reports when it redeems cards through the REST API. It is absent on online orders. When there is no location, the row is left out of the message rather than shown empty — nothing to configure for online-only stores.

For multi-branch retailers this is usually the most useful line in the email: it tells the card holder where the money went, which is what makes an unexpected charge recognisable.


Who gets notified

By default only the card holder is told. Who gets notified has a section of its own on the tab, and lets you change that:

  • Card holder (the default) — the person the card belongs to. A store that never touches the setting works exactly as before.
  • Purchaser — the customer who bought the card, instead of the card holder.
  • Both — the card holder and the purchaser each get a message of their own.

This is for the shopper who gives a gift card and wants to know it was used. With Purchaser or Both they hear about every spend — a partial one included — with the amount used and the balance left.

The purchaser follows the same rules as the card holder: the triggers under When to send and the channels under Channels. To hear about every spend, keep On every redemption ticked; with only When the balance reaches zero on, the purchaser hears once, at the end.

The choice takes effect from the next redemption after you click Save. A redemption that is already being delivered keeps the choice it started with.

The built-in email and text are written to the card holder

The built-in email speaks to the card holder: "Your gift card ending in 4242 was just used", and "You can use the remaining balance on your next order". The built-in text is shorter, but says nothing about who spent the card, so a purchaser cannot tell it is about the gift they gave.

Gift Card Hero does not change the built-in wording when you choose Purchaser or Both. Edit the email and the text first, as shown in Wording the message for the purchaser, then save the setting. If the email goes through Klaviyo, the Flow needs a purchaser branch instead — see Klaviyo.

Who counts as the card holder

The person the card was sent to — or, failing that, the customer it is assigned to, then Gift Card Hero's own records of the card, and last the customer on the order the card paid for. How the card holder is found has the full order.

Who counts as the purchaser

The customer on the order the card was bought in. That works for both kinds of card:

  • A Shopify gift card product — the order is read from the card.
  • A card Gift Card Hero issues itself, for example when you sell gift cards through regular products — the order comes from Gift Card Hero's delivery schedule.

The purchaser's email address and phone number are the customer's, or the order's own when the customer has none. The address a gift was sent to belongs to the card holder, never to the purchaser.

Gift Card Hero reads the purchaser's contact details from Shopify only while Purchaser or Both is selected. A redemption recorded while Card holder was selected carries none, so if you switch afterwards the purchaser is looked up when the message is sent — through the order the card was bought in, when Gift Card Hero knows it. Where it does not, there is no purchaser, as under When there is no purchaser.

When there is no purchaser

Some cards have none: a card issued by hand in Shopify admin, one sold at the till without a customer attached, or an imported one.

  • With Purchaser, the message goes to the card holder instead.
  • With Both, only the card holder's message is sent.

Either way the delivery log says so on the purchaser's line.

The same fallback works per channel. A purchaser with an email address but no phone number gets the email, and with Purchaser the text goes to the card holder.

With Both

Each redemption sends two separate messages per channel: one to the card holder and one to the purchaser, each rendered from your template with the matching audience (see below). With SMS on, that is two texts, and your gateway bills each.

When the card holder and the purchaser have the same email address — or, for texts, the same phone number — only one message is sent, and the log says why.

Text messages

Texts follow the same rule as email. With Purchaser, the text goes to the purchaser's phone number, and to the card holder's when the purchaser has none. With Both, each gets their own.

Email and text are decided separately, so the email can reach the purchaser while the text falls back to the card holder.

Wording the message for the purchaser

Three variables tell one message from another:

  • {{ audience }} — who this message is addressed to: purchaser or holder. A message that fell back to the card holder, because the card has no purchaser, is holder.
  • {{ holder.first_name }}, {{ holder.last_name }} and {{ holder.email }} — the card holder, as far as Gift Card Hero knows. They are filled on every message, the card holder's own included, and are empty when not known — so give them a fallback with default.
  • {{ customer.first_name }} and the other customer variables — the person the message is addressed to. On a message to the purchaser, that is the purchaser.

Branch on audience in the subject, the email body and the text. Whatever you put in the {% else %} part is what the card holder reads — including under Purchaser, when a card with no purchaser falls back to the card holder — so keep your card holder wording there.

The subject:

{% if audience == 'purchaser' %}Your gift was used{% else %}Your gift card was used{% endif %}

The email body — a fragment is enough:

{% if audience == 'purchaser' %}
  <p>Hi {{ customer.first_name | default: 'there' }},</p>
  <p>
    {{ holder.first_name | default: 'Your recipient' }} used {{ amount }} from the gift card you gave
    (ending {{ card_last4 }}){% if branch %} at {{ branch }}{% endif %}.
    {% if depleted %}The card is now fully used.{% else %}Balance left: {{ balance }}.{% endif %}
  </p>
{% else %}
  <p>Hi {{ customer.first_name | default: 'there' }},</p>
  <p>
    Your gift card ending in {{ card_last4 }} was just used for {{ amount }}{% if branch %} at {{ branch }}{% endif %}.
    {% if depleted %}There is no balance left on it.{% else %}You have {{ balance }} left.{% endif %}
  </p>
{% endif %}
<p>{{ shop.name }}</p>

The text:

{{ shop.name }}: {% if audience == 'purchaser' %}{{ holder.first_name | default: 'Your recipient' }} used {{ amount }} from the gift card you gave (*{{ card_last4 }}){% if branch %} at {{ branch }}{% endif %}.{% else %}{{ amount }} used from gift card *{{ card_last4 }}{% if branch %} at {{ branch }}{% endif %}.{% endif %} {% if depleted %}The card is now fully used.{% else %}Balance left: {{ balance }}.{% endif %}

Rendered, the text reads, for the purchaser:

Artcaffe: Wanjiru used KSh 1,500.00 from the gift card you gave (*4242) at Westlands. Balance left: KSh 3,500.00.

That is about 110 to 120 characters with typical values, so it fits one 160-character segment. A first name or branch with a character outside the basic Latin set — "Zoë", for instance — switches the whole message to the 70-character limit; see The SMS template. The editor's preview shows the cost of your own wording as you type.

Klaviyo

When the email goes through Klaviyo, your template is not used, so there is nothing to word in Gift Card Hero. The Gift Card Redeemed event carries audience (holder or purchaser) and the card holder's holder_first_name, holder_last_name and holder_email, when known. It is attached to the profile of the person the message is addressed to — for the purchaser's message, the purchaser.

A Flow can filter on audience: use a trigger filter, or a conditional split inside the Flow, to send the purchaser their own wording. A Flow with no condition on audience runs for every event, so once the purchaser is notified it would send them the card holder's email.

With Both, Gift Card Hero sends two events per redemption, one for each person. The full property list is in Integrations.


Channels

Under Channels, tick the ones the notification goes out on — Email, SMS, or both. Email is ticked by default. Each is delivered on its own: a card with an email address but no phone number still gets the email, and a text that the gateway refuses does not hold up the email.

SMS can be ticked once an SMS provider is connected in Settings → Integrations — see Integrations. The row names the provider and the sender ID the texts arrive from. Text messages go out on your own gateway account and are billed to you by the gateway per message; the SMS editor shows what each message will cost.

You cannot save the settings with the feature on and neither channel ticked.

Delivery method

Under Email, choose the pipe that carries it:

  • Gift Card Hero email — the default. We render the email template and send it from our mail server. Nothing to set up, but the email does not come from your own domain.
  • Your mail server (SMTP) — the same email, sent through your own mail server, so it arrives from your domain. Selectable once you add a server in Settings → Integrations.
  • Klaviyo — instead of sending anything itself, Gift Card Hero sends a Gift Card Redeemed event to Klaviyo and a Flow you build there sends the email. The email template is not used in this mode, and until that Flow exists your customers receive nothing. Once Klaviyo is selected, a Send a test event link appears under it: it opens a small form that pushes a sample event with every property filled, so you can build the Flow against it — see Integrations.

Each notification picks its own pipe. Reminders and redemption emails can go out through different ones — Settings → Integrations only holds the credentials. See Integrations for setup.

If the delivery method you chose is not usable when a message goes out — Klaviyo disconnected, or the mail server settings incomplete — the email is sent through Gift Card Hero email instead.

The SMS has no delivery method to choose: it always goes through the provider connected in Integrations.


Messages

The Messages section shows each message in one line — the email's subject, the SMS as the customer reads it, whether each is the built-in version or yours, and how it goes out (or why it is not going out: the channel is off, Klaviyo sends it, no gateway is connected). Edit template on each row opens its editor.

Every editor shows, under its title, through what the message leaves, with a Change link to where that is chosen. On the right it lists the variables and says whether you are on the built-in message or your own; Reset to built-in puts ours back.

The email template

Leave the template as the built-in one and customers get ours, which already covers both the ordinary and the depletion wording. It is written to the card holder: if you notify the purchaser too, see Who gets notified. Edit it and yours is used instead — including, from then on, in place of any improvements we make to the built-in one. A field cleared to empty is read as "use the built-in one".

Available variables:

Variable What it holds
{{ amount }} Amount taken off the card, in your store's currency format
{{ balance }} Balance remaining after this redemption
{{ date }} When the redemption happened
{{ branch }} Store location, empty for online orders
{{ card_last4 }} Last four characters of the gift card code
{{ order_name }} The order the card paid for, for example #1001
{{ depleted }} True when this redemption emptied the card
{{ customer.first_name }} First name of the person the message is addressed to, when known — the card holder, or the purchaser on a message to them
{{ audience }} Who the message is addressed to: holder or purchaser
{{ holder.first_name }} The card holder's first name, when known — filled on every message, including those to the purchaser
{{ holder.last_name }} The card holder's last name, when known
{{ holder.email }} The card holder's email address, when known
{{ shop.name }} Your store name

{{ customer.last_name }}, {{ customer.email }} and {{ customer.phone }} are filled in too when known, and describe the same person as customer.first_name. Wording the message for the purchaser shows how to use audience and the holder variables. The body can be a full HTML document or just a fragment. Templates can use only these variables and the basic store details (shop.name, shop.email, shop.domain, shop.currency); the {% include %} and {% render %} tags are not available.

Wrap anything that may be absent so the email reads correctly either way:

{% if branch %}Used at {{ branch }}.{% endif %}

{% if depleted %}
  Your card is now fully used.
{% else %}
  You have {{ balance }} left.
{% endif %}

Redemption email editor

Preview renders the template against sample figures, exactly as the customer would see it. Send test email opens a small form with the address to send to, prefilled with your store's contact email; the test goes out through the same pipe the real notification uses, so it also proves your SMTP settings deliver. The subject is marked [Test]. You can send up to 20 test messages an hour per store, across all the editors.

The SMS template

The editor ("Redemption SMS") lists {{ amount }}, {{ balance }}, {{ date }}, {{ branch }}, {{ card_last4 }}, {{ depleted }} and {{ shop.name }}; the other variables of the email, such as {{ order_name }}, {{ customer.first_name }}, {{ audience }} and {{ holder.first_name }}, work as well. The same rule applies as for the email: leave it as the built-in text and you get ours, edit it and yours is used. A text can be up to 2,000 characters before rendering.

The built-in text is one message long and reads, for an ordinary redemption:

Artcaffe: KSh 1,500.00 used from gift card *4242 at Westlands. Balance left: KSh 3,500.00.

and, when the card is emptied:

Artcaffe: KSh 1,500.00 used from gift card *4242 at Westlands. The card is now fully used.

Under the editor, the preview shows the message as the customer will read it — both the ordinary and the depletion wording — and how many messages each one costs, updated as you type. A text is billed per segment: 160 characters for plain text, 70 once it contains a character outside the basic Latin set (an emoji, a curly quote, some accented letters), so a small edit can double the cost of every message. A longer text is split into segments of 153 characters (67 with such characters). The counter is computed on the rendered text, not on the template, so the tags themselves do not count.

Send test SMS (disabled until an SMS provider is connected) opens a small form for the number to send to. The test is rendered against sample figures and sent through your gateway — so it also proves the gateway delivers, and shows you the message on a real phone. A local number is read as one on the gateway's country. One real message is sent and billed.


Delivery log

The Delivery log section on the tab sums up the last seven days — how many redemptions were sent, failed and not sent — and names the most recent one. View delivery log opens the full log on its own page.

The log lists every redemption picked up and what became of each message. The columns are Date, Gift card, Redeemed, Balance left, Branch and one column each for Email and SMS — who it went to and how it ended. A redemption made through the REST API shows "REST API" and its reference under the branch. Search by the card's last characters, an email address, a phone number or an order name; narrow by status, by channel, and by period (the last 7, 30 or 90 days, or all time). Click a card to open it in Shopify.

Delivery log

Statuses, per channel:

  • Sending — the message is still being delivered.
  • Sent — the message went out.
  • Failed — the send was rejected. Hover the badge for the reason; a wrong SMTP password, a rejected address and an unregistered SMS sender ID all show up here. A failed channel is retried a few times on its own — the other channel is not sent again.
  • Not sent — the redemption was recorded but this channel deliberately did not go, with the reason next to it. Most often "no email address (or phone number) is known for this gift card", or a card that still has a balance in a store that only sends depletion notifications.

A channel that is not ticked shows a dash.

Under the address or number the log names where it came from — "sent to, per the gift card", "assigned to, per the gift card", "from the gift card record", "from the delivery schedule", "from the order customer" or, when the message went to the purchaser, "purchaser". This is what separates "nothing was sent" from "it went to the wrong person": a card whose recipient was never recorded falls back to the customer on the order it paid for, and this line is what shows you that.

Purchaser lines

When the purchaser has a message of their own, or was skipped, a second line labelled Purchaser appears under the channel. It shows the purchaser's address or number (a dash when none is known), a status and, when something kept the message from going, the reason.

The line above it is the main message: the card holder's, except with Purchaser, where it is the purchaser's. With Purchaser, the second line appears only when the message had to go to the card holder instead.

Reasons you may see on the purchaser's line, printed under the status:

  • "No purchaser is known for this gift card — it was issued without an order, or the order has no customer" — the card has no purchaser. With Both, only the card holder was told.
  • "No email address is known for the purchaser", or the same for a phone number — with Both, the purchaser is known but has no address on this channel, so only the card holder was told.
  • "No email address is known for the purchaser — sent to the card holder instead", or the same for a phone number — with Purchaser, the card has no purchaser or the purchaser has no address on this channel, and the message went to the card holder. The main line shows where it went.
  • "The purchaser is the card holder — one message sent" — with Both, the two share an address, so a single message went out.
  • "Could not look up who bought the card" — the message to the purchaser is Failed, because Gift Card Hero could not reach Shopify to find the order. With Both it is on the purchaser's line; with Purchaser it is on the main line, since that is the purchaser's message. This is not treated as "no purchaser": the message is retried on its own and is not redirected to the card holder in the meantime.

With Purchaser, if the card holder could not be reached either, the first two wordings above appear without "sent to the card holder instead" — nothing went out on that channel.

A Not sent purchaser line never changes the outcome of the redemption: if the card holder's message went out, the redemption counts as sent. A Failed one does — the redemption counts as failed and is retried, and only the message that failed is sent again. One that already went out is not repeated.

Search finds a redemption by the purchaser's email address or phone number as well. The status filter, combined with a channel, also looks at the purchaser's message, so choosing SMS and Failed finds a failed purchaser text too.

A message without the balance

Gift Card Hero reads the card the moment it is spent. Now and then Shopify does not answer in time — usually because the store is making a lot of requests at once. The card is then read again just before the message goes out, and the log says "The card could not be read when it was spent" under the balance; if Shopify still does not answer, the redemption shows Failed with "Could not read the gift card" and is retried. The later reading supplies the balance, so a card spent again in between can show a little less than this purchase left. With Force gift cards to be onetime on, the card has been emptied by then — as it may already be when Shopify answers on a second try a moment later — so the balance is Unknown and the message goes without it: the built-in email and text leave the balance out, and the Klaviyo event has no balance. To do the same in your own template, wrap the balance in {% if balance != blank %}…{% endif %}.


How the card holder is found

The card holder is found like this, in order:

  1. The gift card's recipient in Shopify — the person the card was sent to, set on the card itself, so it works for cards issued from the Shopify admin or a till.
  2. The customer the card is assigned to in Shopify — also read from the card.
  3. The gift card record in Gift Card Hero — the address the card was delivered to (email only; the record holds no phone number).
  4. The delivery schedule — for cards queued for a future send.
  5. The customer on the order the card paid for — the last resort, and the person who placed that order, who is not necessarily the card holder. (The order the card was bought in belongs to the purchaser — see Who counts as the purchaser.) For the phone number this also looks at the number typed at checkout.

The email and the phone number are looked up separately, each down this list, so they can come from different places — the email from the gift card, the number from the order — and the log says which.

If nothing yields an address or a number, that channel is logged as not sent. Assigning a recipient with a phone number to the card in Shopify fixes it for every future redemption of that card.

This is the person the holder template variables describe. The purchaser is found differently — see Who counts as the purchaser.


Notes

  • Refunds, voids and failed payments are ignored — only a successful payment from a gift card sends anything.
  • Test-mode orders never produce a customer message.
  • A repeated event from Shopify does not send a second message; each redemption is notified about at most once per channel and per person — with Both, the card holder and the purchaser each get one.
  • These are transactional messages about a customer's own card, not marketing, so the marketing consent filter that applies to reminders does not apply here.
  • Gift Card Hero has no SMS provider of its own: if the SMS channel is on and the provider has since been removed in Integrations, the text is logged as not sent and the email still goes.