StoreBuilt checked Shopify’s gift-card management and notification documentation for this guide. The useful distinction is between buying a card, issuing it and delivering it to the intended person. Treating those stages as one email event can lead support staff to resend the wrong message or create unnecessary replacement value.
A Shopify gift card email not received complaint is often urgent: the buyer may be waiting to send a birthday present, while the recipient has nothing to open. UK ecommerce teams need a process that restores the intended experience without exposing the redeemable code or confusing the existing balance.
Contact StoreBuilt to review the gift purchase and recipient journey before your next gifting campaign.
Table of contents
- Ask which message is missing
- Check the order and the existing card
- Respect recipient schedules and timezones
- Use the existing card’s resend path
- Investigate mailbox delivery without repeated guessing
- Test custom notification content separately
- An illustrative birthday-gift investigation
- Build a gifting readiness checklist
- StoreBuilt point of view
Ask which message is missing
Start with the person reporting the problem. Are they the purchaser or the recipient? Ask whether they received an order confirmation, a gift-card message, or a message confirming a future delivery. Do not assume that an email showing the order number also contains everything needed to redeem the gift.
Record the purchase reference and the expected delivery date. A customer saying “I bought it yesterday” does not tell support whether it was scheduled for next week. Likewise, an inbox screenshot from the buyer says little about what the recipient received. Each mailbox belongs to a separate step in the journey.
Keep the questions short and purposeful. Support should not ask for the recipient’s entire inbox or a full gift-card code. The goal is to locate the right merchant record and establish the missing event, not to collect every piece of personal information associated with the purchase.
Check the order and the existing card
Find the order through the merchant’s normal identity-verification process. Review its payment and fulfilment information, then locate the associated gift-card record if one exists. Do not fulfil an unpaid or suspicious order merely to make a message appear; follow the merchant’s order-handling policy.
Shopify’s gift-card notification guidance distinguishes the new gift-card notification from the buyer’s gift-card receipt. It links the new-card message to fulfilment of the gift-card product or sending a created card. That distinction provides a concrete first check when only the order confirmation arrived.
If no card record exists, a resend action is not the next step. Investigate the issue or fulfilment process with the person who owns it. If a record exists, note its status and a limited identifier so colleagues can refer to the same card without copying its full redeemable credentials.
Respect recipient schedules and timezones
A supported recipient form can collect a recipient email, a message and a send date. Check the saved values rather than asking the buyer to reconstruct them from memory. A surprise gift can be spoiled by sending early, even when the support team’s intention is to help.
Shopify describes scheduled delivery timing in its recipient-fields documentation. Use that current guidance and the purchasing customer’s timezone when assessing whether the expected window has passed. Do not promise midnight delivery or an exact minute unless the actual service supports it.
For UK stores selling to overseas buyers, write the relevant date and timezone in the internal note. A buyer abroad may be thinking in local time while support is thinking in London time. Clarifying that difference can prevent an unnecessary replacement or an accidental early disclosure to the recipient.
| Customer report | Check first | Avoid |
|---|---|---|
| Buyer has only an order confirmation | card issue and fulfilment state | assuming all gift messages were sent |
| Recipient has nothing before the chosen date | saved recipient schedule | sending early without resolving intent |
| Recipient email looks incorrect | verified purchase and stored address | disclosing value to a new unverified address |
| Email arrived without useful card content | notification rendering | creating another card immediately |
| Card link opens but payment fails | card status and balance | repeating inbox troubleshooting |
Use the existing card’s resend path
Once the correct card and customer are established, follow Shopify’s supported resend workflow. The gift-card management instructions place this under Products > Gift cards: open the relevant card and select Resend gift card. The record, rather than a guessed order email, should anchor the action.
A resend is different from issuing another card. For a partially used card, the communication relates to its remaining balance. Do not create additional value simply because a recipient cannot locate the original message. A replacement, if needed, requires a separate decision about the existing card and the customer’s entitlement.
Record that the resend was initiated, when it happened and who should receive it. Then ask the customer to confirm receipt through an appropriate support reply. A clicked send button is evidence of an action, not proof that the recipient’s mail system delivered it to the inbox.
Investigate mailbox delivery without repeated guessing
Ask the intended recipient to check spam and any organisational quarantine they can access. Confirm the address through the merchant’s identity process. When a company mailbox is involved, the recipient’s IT administrator may be able to inspect filtering using the approximate send time and sender details.
Avoid issuing repeated resends every few minutes. Delayed messages arriving together can make the customer think several different cards exist. Use one controlled attempt, record the result and move to the next diagnostic question. Repetition adds noise when the underlying address or recipient schedule is wrong.
If reports affect several unrelated customers, compare their timing and purchase paths. A pattern after a notification edit deserves a different investigation from a single misspelled address. Keep the original report intact, then append findings so another support agent can follow the sequence.
Test custom notification content separately
A redesigned gift email needs checks beyond its visual preview. Confirm that the message retains the card access content, remaining-value information where applicable and the intended recipient context. A beautiful image cannot replace the functional part of the notification.
Use controlled test records and mailboxes owned by the business. Inspect the message on desktop and mobile, including an email client that blocks remote images. Essential information should remain understandable without the hero image. Avoid embedding live customer card details in screenshots used for a design review.
When editing a template, keep a copy of the previous version and make one coherent change at a time. If a new layout causes a regression, the team needs a clear restoration path. The separate order notification testing guide provides a broader framework for transactional email QA.
An illustrative birthday-gift investigation
Consider a UK skincare store whose buyer contacts support because a gift has not arrived. The buyer has an order confirmation and assumes the recipient should already have the card. Support initially prepares to issue a replacement of the same value.
The investigation instead checks the saved recipient details and discovers a future send date selected during purchase. The team explains the schedule to the verified buyer and confirms the intended next action before altering delivery. The original card remains the reference for all subsequent support work.
This is a hypothetical operating example, not a reported StoreBuilt client result. It illustrates why the support question should be “which stage has failed?” before it becomes “how do we send another card?” The second question can create financial and customer-service complications if asked too early.
Build a gifting readiness checklist
Before a seasonal promotion, test the paths the shop actually offers: purchase for self, purchase for another recipient and scheduled delivery if enabled. Include the relevant theme and notification versions in the test record. An old successful test does not automatically cover a newly redesigned recipient form.
| Test path | Evidence needed | Responsible role |
|---|---|---|
| Purchase for self | card access reaches controlled buyer | ecommerce owner |
| Recipient purchase | correct person and message | customer-experience owner |
| Scheduled gift | stored date and expected timing | support lead |
| Resend | existing card identified correctly | authorised support agent |
| Mobile email | readable content and working destination | implementation team |
Monitor support contacts by missing stage rather than labelling all of them “email problems”. This makes it easier to see whether the next improvement belongs in the recipient form, the notification design or the support process. It also prevents delivery complaints from being confused with redemption failures.
StoreBuilt point of view
The best gift-card support preserves the customer’s intended gift and the merchant’s existing value record. StoreBuilt would verify the recipient, timing and card state before changing anything. Fast support is useful; fast duplication of value is not a reliable recovery process.
Explore Shopify design and development or Contact StoreBuilt for help testing recipient forms and gift-card notifications.