Our review of StoreBuilt’s gifting guidance keeps returning to the handover between the buyer and the person receiving the present. A polished gift-card product page is only part of that handover. The recipient fields, date wording and two email journeys must agree, especially when the buyer is trying to preserve a surprise.
For UK ecommerce teams, Shopify gift-card recipient fields can remove the need for a customer to forward a code manually. However, the storefront should explain what happens after payment without promising a precise delivery moment the implementation cannot guarantee. This guide focuses on setup and launch checks; examples are illustrative and do not describe measured client outcomes.
In this guide
- Define the gifting promise before editing the theme
- Confirm native theme support
- Write date wording that matches the service
- Review both notification roles
- Make error handling understandable
- Walk through an illustrative birthday purchase
- Build a controlled launch matrix
- Prepare support before seasonal traffic arrives
- Review the complete product page
- StoreBuilt point of view
Define the gifting promise before editing the theme
Decide which choices the customer needs: buying for themselves, sending immediately to another person or scheduling a future date. Write a short description of each journey in ordinary language. Keep the buyer’s email and recipient’s email clearly distinct. A field labelled only “Email” is ambiguous when the page contains both purchase and gifting details.
Explain whether the product is digital and whether a physical item will arrive. Keep denomination, recipient information and the delivery explanation close enough that mobile shoppers can review them together. Avoid burying essential timing information in a general FAQ. Customers choosing a birthday or anniversary present need the expectation before adding the card to their basket.
Confirm native theme support
Shopify documents recipient email, optional name, message and send-on date fields in supported themes. The relevant option is associated with the gift-card product’s buy-buttons block. Check the active template and theme version rather than assuming that any Online Store theme exposes the same setting. See the official recipient-field guide.
Preview the actual gift-card product while making the change. A default product template may also serve ordinary merchandise, so check that the recipient controls appear only where intended. If the setting is absent, establish support with the theme developer. Adding visually similar custom fields is not enough unless the submitted data connects correctly to the gift-card process.
| Decision | Customer-facing wording to clarify | Implementation check |
|---|---|---|
| Buyer keeps the card | Gift card is for the purchaser | No unintended recipient requirement |
| Gift sent now | Explain who receives which message | Both controlled mailboxes |
| Future delivery | Explain the date and timing expectation | Saved date and timezone context |
| Personal message | Describe optional content clearly | Long text and special characters |
| Mobile purchase | Make the recipient address reviewable | Field labels, keyboard and errors |
Write date wording that matches the service
Shopify describes scheduled emails as arriving approximately between 4 am and 10 am in the purchasing customer’s timezone. That is not a promise of midnight delivery in the recipient’s location. Use wording that reflects the documented window, and avoid a countdown implying second-by-second dispatch. Keep any additional app behaviour separate from the native feature explanation.
For a UK buyer sending to someone overseas, the chosen date can be interpreted differently by each person. Include a short plain-language note near the date field and test how the date is represented in the order evidence available to support. If a business needs exact-time delivery, treat that as an additional requirement to investigate rather than an assumption about the native form.
Review both notification roles
The recipient’s message and the purchaser’s receipt have different jobs. One provides the gift experience and access information; the other confirms the purchase handover. Use two mailboxes controlled by the business when testing so both perspectives can be inspected. Do not rely on a single template preview as proof that the correct recipient receives the expected content.
Existing notification customisations need careful comparison before changes. Back up the current versions, including each supported language, and check that the recipient fields survive the design. A blanket reset can remove useful branding and wording. If you preserve custom templates, verify the functional content as well as spacing, typography and mobile readability.
Contact StoreBuilt to review the gift-card page, recipient data and notification templates as one journey.
Make error handling understandable
Check what happens when the recipient email is missing, malformed or mistyped into a plausible address. Format validation cannot establish that a person owns the mailbox. Give the buyer a clear opportunity to review the address and avoid styling that hides its final characters on mobile. Never imply that an accepted form field proves successful delivery.
Test optional fields independently. A blank recipient name should not produce an awkward greeting if the implementation treats it as optional. A long message should wrap without covering the card details. Include apostrophes, line breaks and ordinary non-English characters in a controlled test. These small checks reflect real gifting behaviour more accurately than testing only a short name and “Happy birthday”.
Walk through an illustrative birthday purchase
Imagine a UK homeware customer buying a gift card for a relative abroad. They select a future date, add a personal message and enter the relative’s address. The store’s previous wording says “arrives at midnight”, but the native delivery process is based on a documented window in the purchaser’s timezone. The risk begins in the promise, even when the software works as designed.
A better release clarifies the timing beside the date field, makes the recipient address easy to review and confirms both notification roles in testing. Support receives a short explanation of which records to inspect if the buyer later asks about delivery. This scenario illustrates a preventable expectation mismatch; it is not a claim that StoreBuilt has delivered a specific client result.
Build a controlled launch matrix
Before any test purchase, agree the store’s approved payment-testing method and who is allowed to create, refund or disable test cards. Keep test identities separate from customer records. If the environment cannot reproduce the full scheduled-send lifecycle safely, record that limitation and complete a controlled live check before promoting a time-sensitive gifting promise.
| Scenario | Evidence to keep | Acceptance question |
|---|---|---|
| Purchase for self | Product form and buyer notification | Is the self-purchase route clear? |
| Immediate recipient gift | Buyer and recipient messages | Did each role receive the intended content? |
| Future date | Saved schedule and eventual delivery | Does behaviour match the promise? |
| Optional fields blank | Rendered email | Is the wording still natural? |
| Long message on mobile | Narrow-screen email view | Is essential content readable? |
| Alternate language | Form and notification language | Are all functional fields preserved? |
Prepare support before seasonal traffic arrives
Create a brief internal checklist for a wrong address, a date question and a missing message. Start by verifying the requester and inspecting the order and gift-card record. Avoid asking customers to post complete card codes in public messages or screenshots. Keep access information within the store’s established support process.
Shopify’s gift-card management guidance is the reference for inspecting and managing records. For a delivery incident after purchase, our separate gift-card email troubleshooting guide follows the missing-message investigation. Separating setup from incident response helps staff choose the appropriate workflow instead of repeatedly changing the theme.
Review the complete product page
The recipient form should fit the product’s hierarchy rather than compete with a long promotional introduction. Keep the amount, delivery method, key conditions and purchase control legible on mobile. Check keyboard navigation and visible field errors. Where the theme requires custom implementation, our Shopify store development service can scope the form and notifications together.
Measure customer questions and completion behaviour after release, but do not attribute every change in gift-card sales to the new form. Seasonal demand and campaign activity can dominate the numbers. The immediate evidence is whether the journey works and customers understand it; commercial impact requires a longer and more comparable observation period.
StoreBuilt point of view
A gift-card flow succeeds when both people understand what happens next. Precise field labels, honest scheduling language and tested notifications matter more than decorative complexity. Build the promise around verified behaviour, then make that promise easy to see before purchase.
Contact StoreBuilt to prepare a gifting journey that your customers and support team can rely on.