How do you test gift card emails and PDF vouchers across devices and email clients? Follow the complete delivery path—from the purchase event and scheduled sending to inbox rendering, PDF access, and redemption—using real orders, inboxes, phones, computers, and printed vouchers.
Define the expected gift card delivery flow
Document what happens after a customer purchases a gift card. The flow depends on the plugin configuration, payment method, order status, recipient details, and selected delivery option. A paid order does not necessarily create and send a voucher at the same moment.
Identify the event that creates the voucher and the event that releases its email. Before reviewing the message layout, verify the purchase events that trigger gift card delivery, including successful payments, failed payments, retried transactions, and manual order-status changes.
For every scenario, record the intended recipient, delivery time, subject line, message content, voucher format, and administrative record. The flow may include a recipient email, a buyer confirmation, additional administrative recipients, a PDF attachment, or a secure download link.
Also define what must not happen. Failed or cancelled payments must not release usable value unless the store is intentionally configured that way. Refreshing an order page, repeating a payment callback, saving the order, or rerunning a background task must not create duplicate vouchers.
Use a staging environment with production-like email and scheduling settings. Isolate the inboxes, payment methods, analytics, and integrations so QA orders do not affect customers or live reporting.
Create an email-client and device matrix
An email preview can reveal obvious layout errors, but it cannot demonstrate inbox placement, attachment handling, mobile access, or behavior in real applications. Use separate inboxes and open purchase-triggered messages on the clients and devices included in the matrix.
Cover at least these dimensions:
- Mailbox providers: Gmail, Outlook or Hotmail, Yahoo Mail, and providers important to the store’s market.
- Desktop access: browser-based webmail and relevant native applications.
- Mobile access: iPhone Mail, Gmail for Android, Outlook mobile, and applications visible in analytics or support requests.
- Delivery format: a PDF attachment, a PDF download link, or both.
- Customer type: guest buyer, registered customer, buyer sending to another person, and buyer sending to their own address.
- Network conditions: broadband, mobile data, and a slower connection for large files or externally hosted images.
Use a separate mailbox for every provider instead of forwarding one message between accounts. Forwarding can alter sender information, headers, HTML, links, and attachments, producing a result that differs from the original voucher email.
Open at least one message with external images disabled. The voucher value, instructions, recipient information, and primary action must remain understandable when remotely hosted graphics are blocked.
Check immediate, delayed, and scheduled delivery
Cover every delivery mode enabled in the store. This commonly includes immediate sending and may include an interval-based delay, a fixed date, or a date selected by the customer.
Flexible PDF Coupons PRO – Advanced Sending extends Flexible PDF Coupons PRO with delayed and scheduled gift card delivery. It is not a standalone mailing tool: it requires the parent plugin and uses the voucher and order data generated by the WooCommerce purchase flow.
Immediate delivery
Place a qualifying order and record the payment time, voucher creation time, email generation time, and inbox receipt time. Define an acceptable delivery window so support staff know when a delay requires investigation.
Repeat the process with each supported payment method and order-status trigger. The voucher must not leave the store while the order remains unpaid, on hold, failed, or cancelled unless that workflow has been deliberately configured.
Interval-based delay
During QA, configure a short interval. In Flexible PDF Coupons PRO – Advanced Sending, the delay is calculated from the purchase time; the order still needs to satisfy the configured conditions before the message can be released. Base the expected timestamp on that rule rather than on a later manual status change.
Move an order to the required status after its calculated delivery time and record the resulting behavior. This edge case belongs in the support procedure because it may require an immediate queue run or a controlled resend.
Fixed-date and customer-selected delivery
Schedule messages shortly before and after midnight in the store’s timezone. Include a weekend, month boundary, leap day when relevant, and daylight-saving transition. Compare the customer’s selected date with the order data and scheduled action.
WooCommerce scheduled actions are available under WooCommerce status tools. Because standard WordPress scheduling depends on cron execution and site activity, low-traffic environments can release queued messages later than expected. Use production-like cron settings when measuring delivery timing.
For setup details, review delayed gift card email delivery and scheduling WooCommerce gift card delivery. Then evaluate the recipient’s result with an actual order.
Duplicate-delivery protection
Repeat actions that could invoke delivery more than once: retry a payment, move an order status back and forth, resend an email, rerun a scheduled action, and restore a failed background job. The recipient must not receive unexpected duplicate messages or multiple active codes.
If resending is available to support staff, establish whether it reuses the original voucher or creates a replacement. The procedure must prevent accidental duplication or invalidation of the customer’s balance.
Review sender, subject, and recipient details
Every message needs a recognizable sender name and an address associated with the store’s domain. Review the From name, From address, Reply-to address, and reply behavior. SPF, DKIM, and DMARC records also need to align with the service sending the message.
Delivery checks go beyond seeing whether a message eventually appears. Inspect the main inbox, spam or junk folder, promotions tabs, quarantine notices, and security warnings. Record each provider separately.
Read the subject line with real dynamic data. It must remain clear with long recipient names, personalized content, and a lengthy store name. Do not expose a complete redeemable code in the subject because lock screens and notification previews may display it.
Compare the recipient address in the purchase form, order record, email headers, and voucher content. Include separate buyer and recipient addresses, additional recipients where available, and addresses entered with accidental whitespace. A message sent successfully to the wrong person is still a critical delivery failure.
For template and personalization options, see customizing gift card emails with Flexible PDF Coupons PRO – Advanced Sending. After a template change, use another purchase-triggered message because preview data may hide missing or incorrectly mapped fields.
Inspect rendering on desktop and mobile
Open every delivered message rather than judging it from the inbox preview. The complete voucher email needs to remain readable without zooming, horizontal scrolling, or copying its content into another application.
Review the header, logo, greeting, personalized message, voucher value, redemption instructions, validity information, and footer. Buttons need comfortable tap targets on phones, while text links must remain visible if an email client removes button styling.
Include narrow screens, increased system font sizes, dark mode, and remote-image blocking. Essential information cannot depend exclusively on a background image or low-contrast graphic. If the email contains both a button and a plain link, both need to open the same voucher.
Open links while signed out of the store. A gift recipient may not have a customer account and cannot be unexpectedly redirected to login unless authentication is an intentional part of the flow. Also open a copied link in another browser and on another device.
If a plain-text version is available, inspect it independently. It needs a meaningful subject, recipient information, redemption instructions, validity details, and an accessible voucher link where required.
Validate PDF attachments and download links
PDF voucher QA covers both the file and its business data. Open the PDF from each email client, download it, save it under the supplied filename, and print it from mobile and desktop devices. Different clients expose attachments through different interfaces, so opening only the server-generated file does not reproduce the customer experience.
Compare the voucher with its order
Match every PDF with its source order and corresponding WooCommerce coupon or voucher record. Review these fields when they are enabled in the template:
- The unique voucher or coupon code.
- The monetary value or configured benefit.
- The recipient’s name and email address.
- The buyer’s name and personalized message.
- The issue date, expiration date, and validity conditions.
- The store branding and redemption instructions.
- The website address, contact details, and applicable restrictions.
Generate at least two vouchers with different values and recipients, then compare them side by side. This exposes cached files, reused content, incorrect dynamic fields, and cases in which one customer receives another customer’s voucher.
If the PDF contains a QR code or barcode, scan it from a phone screen and from a printed copy. The encoded value needs to match the visible code and lead to the intended redemption process.
Check attachments and linked downloads separately
For attachments, make sure the PDF is present, has a sensible filename, opens without corruption, and is not a zero-byte file. Note the full message size and repeat the process after adding high-resolution branding assets.
For linked vouchers, open the link immediately, after the expected waiting period, in a private browser window, and on another device. Record whether it expires, requires authentication, or permits repeated downloads. Customer instructions must describe the actual behavior.
Protect against browser caching by opening vouchers from two orders in the same session and then in separate private sessions. Creating a later order must never cause an earlier link to display the wrong voucher.
Review PDF usability and accessibility
Important text needs to remain selectable, copyable, enlargeable, and interpretable by assistive technology. A design that stores all instructions in one image prevents many assistive tools from extracting and reading the content.
Review reading order, text contrast, font size, descriptive links, and the visual separation of the code from surrounding content. When custom typography is used, inspect font embedding and special characters. See custom fonts in WooCommerce PDF coupons for template-specific configuration guidance.
Finally, apply a delivered code to a controlled order to confirm that delivered voucher codes redeem correctly. Delivery QA is incomplete if the PDF contains a code that is inactive, expired, missing, or connected to the wrong value.
Use long names, special characters, and multilingual content
Dynamic fields often look correct with short English sample data and fail with longer or more diverse customer input. Prepare realistic edge cases such as:
- A long recipient name containing several words.
- A hyphenated surname and an apostrophe.
- Accented Latin characters and supported non-Latin writing systems.
- A personalized message spanning several lines.
- Quotation marks, ampersands, currency symbols, and punctuation.
- A long store name, product label, or validity description.
- Right-to-left content when the store supports a right-to-left language.
Follow the data from the product page and cart through the order, email subject, message body, and PDF. Characters cannot turn into empty boxes, question marks, HTML entities, or unexpected markup.
Pay particular attention to line wrapping and PDF page breaks. Long messages cannot cover the voucher code, branding, validity date, or redemption instructions. If a template has a character limit, enforce it on the customer-facing form instead of silently truncating content during generation.
For multilingual stores, use the language selected during purchase and inspect what the recipient receives. Include translated dates, currency formats, decimal separators, headings, PDF instructions, and fallback fonts.
Document resend and recovery procedures
Create a response for bounced, delayed, blocked, deleted, and incorrectly addressed messages. The procedure needs to distinguish message generation, handoff to the mail service, inbox delivery, and access to the voucher.
WooCommerce email records can show whether a message was sent, failed, disabled, or skipped. A successful handoff does not prove that the recipient’s provider placed it in the inbox, so compare store records with SMTP or email-service logs when available.
For delayed messages, inspect the scheduled action before resending. Record whether it is pending, completed, failed, or overdue. Otherwise, a manual resend may be followed minutes later by the original scheduled email.
Define who may resend a voucher, how recipient ownership is established, whether the same PDF is reused, and when the original code is disabled. Include a safe way to correct an email address without creating another balance.
Prepare customer-facing wording for checking junk folders, recognizing the sender, requesting a controlled resend, downloading the PDF again, and reporting a code that appears to have been used. Keep internal security and administrative steps out of customer instructions.
Complete the delivery sign-off checklist
Run final sign-off with new orders and clean inboxes. Record the order number, scenario, expected result, actual result, delivery timestamp, client, device, and supporting screenshots.
- Establish that the configured payment or order event creates exactly one voucher.
- Cover every immediate, interval-based, fixed-date, and customer-selected delivery mode enabled in the store.
- Check timing around midnight, weekends, month boundaries, and daylight-saving changes.
- Review the From name, domain-based address, Reply-to behavior, subject, and recipient.
- Record inbox placement in Gmail, Outlook, and other relevant accounts.
- Open the email in required desktop, webmail, Android, and iPhone clients.
- Read the message with remote images disabled, on a narrow screen, and with increased text size.
- Open, download, save, and print the PDF on mobile and desktop devices.
- Match the code, value, recipient, message, validity details, restrictions, and branding with the order.
- Use long names, special characters, multiline messages, and supported languages.
- Repeat triggers, retries, resends, and scheduled jobs without creating uncontrolled duplicates.
- Redeem a delivered code and compare its balance and restrictions with the voucher.
- Simulate a failed or delayed email and complete the documented recovery process.
- Review email logs, scheduled actions, order notes, and mail-provider records.
- Obtain approval from the people responsible for store operations and customer support.
Treat a missing voucher, incorrect value, wrong recipient, exposed customer data, unusable code, inaccessible download, duplicate balance, or unreliable scheduled delivery as a launch-blocking defect. Cosmetic spacing can receive a lower priority only when it does not obscure instructions or hinder voucher use.
Key conclusions
- Use purchase-triggered messages in real inboxes instead of relying on previews.
- Evaluate scheduled delivery against the store timezone and background-task queue.
- Match every email and PDF with the correct order and recipient.
- Open attachments and download links on desktop and mobile devices.
- Use challenging names, messages, characters, and languages to expose template defects.
- Look for duplicate delivery after payment retries, status changes, resends, and recovered scheduled actions.
- Prepare a controlled recovery process before customers report missing messages.
Summary
Reliable WooCommerce gift cards require more than generating a code or sending a preview. Complete QA follows the real purchase trigger through sender authentication, inbox placement, client rendering, PDF access, scheduled delivery, duplicate protection, recovery, and redemption.
Keep an auditable record of every scenario and expected outcome. You can also review the Flexible Coupons category when planning the configuration covered by the delivery matrix. Approve the campaign only when the intended recipient can receive, understand, save, print, and use the correct voucher without assistance.
Frequently asked questions
Which email clients are most important for gift card QA?
Start with Gmail, Outlook, iPhone Mail, Gmail for Android, and any provider that appears frequently in store analytics or support tickets. Use separate original deliveries rather than forwarded copies.
Can an email preview replace a real gift card order?
No. A preview can reveal layout issues, but it does not reproduce purchase data, voucher generation, scheduling, sender authentication, inbox placement, or attachment handling.
How do I check a scheduled WooCommerce gift card?
Place an order with a near-future delivery time, compare the stored time with the store timezone, inspect the corresponding scheduled action, and record the actual inbox receipt time. Include midnight and daylight-saving edge cases.
Why must a QR code be scanned from both a screen and paper?
Screen brightness, display scaling, print quality, contrast, and physical size can affect scanning. A code that works on a monitor may fail on a customer’s phone or printed voucher.
What is the difference between resending and replacing a voucher?
Resending delivers the existing voucher again. Replacing creates a new code and normally requires the original value to be disabled. Support procedures need to state which action is used to avoid duplicate balances.
Send gift cards at the right time
Add delayed and scheduled delivery to Flexible PDF Coupons PRO.
Flexible PDF Coupons PRO – Advanced Sending lets stores offer immediate delivery, a configured delay, or a customer-selected delivery date while keeping voucher data connected to the WooCommerce order.
