The Gift Card Flow Nobody Tests Until December
Test the gift card flow like a stranger in a hurry: can they find it from search and the footer, choose an amount without fighting preset buttons, send it to a recipient with a scheduled date, and get a confirmation that states what happens next. Most friction hides in denomination design, delivery expectations, and an unconfirmed recipient email address.
Gift card buyers are your least loyal visitors and your most time pressed. Many will never buy anything else from you. They arrive in December, on a phone, with a birthday or a holiday deadline, and the flow they meet was designed as an afterthought and tested by nobody.
That neglect is expensive in a specific way. A failed gift card purchase is rarely retried later. The occasion passes, the buyer picks a marketplace card instead, and the store loses both the sale and the new shopper the recipient would have been.
Denominations and the custom amount trap
Preset amounts should bracket your typical order value, with one option near the average basket so the card actually covers a purchase with shipping. A card that falls 8 dollars short of a normal order plus delivery teaches the recipient that your store costs extra to use.
If you offer a custom amount, respect it. Minimums and maximums should be stated before the buyer types, not announced as an error after. And keep the amount step to one decision. Every extra upsell panel between amount and payment is a tax on a buyer who has already decided.
Delivery timing is the product
The buyer is purchasing a date as much as a balance. Say plainly whether the card arrives by email immediately, whether a future send date can be scheduled, and what the recipient sees. A printable option matters for the buyer who wants something to hand over, and its absence sends people to the comments of your help page.
The recipient email field deserves a confirmation entry or at least a review step with the address in large type. A typo in that field is a total loss that surfaces on the occasion day, which is the worst customer service conversation in retail. Prevention here is one extra input and thirty seconds of design attention.
After purchase, silence is a bug
Send the buyer a confirmation that states the amount, the recipient, the scheduled date, and how to fix a mistake. Send the recipient a message that looks like it comes from a store, not a payment processor, with the balance and a direct path to shop.
Then test redemption as the recipient, on a phone, with a real code, including what happens when the order total is under the balance and whether the remaining balance is visible afterward. Gift card programs fail at redemption more often than at purchase, and the recipient's first visit decides whether the card created a customer or a story.
Related reading
Related reading: Setting a Free Shipping Threshold: The AOV Math Most Stores Skip, Cart Drawer or Cart Page? The Answer Splits by Who Is Buying, and Shopify Search and Discovery Filters: Setting Up Filters Shoppers Actually Use.
Frequently asked questions
Should gift cards be sold in preset amounts or custom amounts?
Offer both. Presets speed up the common purchase and should bracket your typical order total including shipping. A custom amount with clearly stated minimums and maximums serves buyers with a specific budget or occasion.
Why ask buyers to confirm the recipient email address?
Because a single typo delivers the card to the wrong inbox or to nobody, and the failure is discovered on the occasion day. A confirmation field or a clear review step costs seconds and prevents the most damaging gift card error.
Can gift card delivery be scheduled for a future date?
On platforms like Shopify, scheduled sending depends on the app or setup you use. If you offer it, state the send date in the buyer confirmation. If you do not, say the card is delivered immediately so buyers can plan around it.
What should a gift card confirmation email include?
The amount, the recipient address, the delivery timing, and a route to correct mistakes, plus a code or link the buyer can keep. Silence after payment is what turns a normal purchase into a support ticket.