top of page
Oct 23
5 min read

Updated: Nov 8

Klaviyo Dynamic Coupon Codes: Setup, Timing and Checkout QA

A real coupon repair: Ouidad

In the Ouidad project, the October 2026 record identifies a numeric-field issue in the coupon setup. The field was corrected on 24 October. On 27 October, the client accepted using different codes in the form and welcome email.

The useful proof is a specific repair and an agreed handoff. It does not establish that the discount was the winning offer or caused a revenue increase. For your own release, test the submitted form, stored values, delivered email, eligible basket and redemption behavior together. Our monitoring guide separates a passed launch check from ongoing account health.


By Trayan Hristov · Thrivelia · Reviewed October 2026


Thrivelia guide: Klaviyo Dynamic Coupon Codes: Setup, Timing and Checkout QA

Klaviyo dynamic coupon codes give individual recipients their own discount code. For Shopify, you can create the coupon in Klaviyo, define the offer and insert it into a message. The operational work is making sure the customer receives a valid code, understands its conditions and can redeem it at checkout.


Start with the offer and customer journey. Then check generation, expiry, reminders and competing promotions. A correctly rendered code can still be the wrong incentive for that customer.


Choose unique or static codes deliberately


A static code is shared across recipients. A dynamic code is assigned individually. Klaviyo's coupon overview distinguishes those options and explains that uploading codes does not create discounts in your store: the codes must already work in the commerce system.


Unique does not mean impossible to share. A customer can forward a code. Equally, static does not mean unlimited: Shopify supports usage limits and customer eligibility. Decide how the offer should behave rather than treating the label as the complete rule.


Define the Shopify discount before writing the message


Use Klaviyo's Shopify coupon setup to create the coupon. Give it a recognisable internal name and optional prefix, then set the discount type, applicable products or collections, minimum purchase, activation and expiry. Use the exact coupon name when inserting its template tag.


Write a short offer brief covering who qualifies, what is excluded, when the incentive ends and who owns changes. Include margin after the discount, product cost, fulfilment and any shipping subsidy. A larger basket is not automatically a more profitable order.


Keep subscription offers separate. Klaviyo's Shopify-generated coupon guide limits these codes to nonrecurring orders; do not assume they work on subscription purchases. Confirm the subscription platform's supported setup before promising that benefit.


Prepare campaigns and flows differently


Use

Supply decision

Timing check

Campaign

Generate sufficient codes before scheduling.

Allow for audience growth before send time.

Shopify flow

Codes are generated automatically as needed.

Review generation, retries and skips.

Uploaded-code flow

Replenish the available codes yourself.

Check store validity as well as Klaviyo availability.


Klaviyo's SMS coupon guidance distinguishes prepared campaign supply from automatic generation for supported flow integrations. For campaigns, leave a buffer for new eligible recipients. A send-time audience can outgrow a batch that was sufficient when you scheduled it.


Assign an owner to check supply before large sends and review the first live flow entrants. An automated journey still needs someone watching whether the promised offer reaches customers.


Make the deadline match the actual validity


The Shopify coupon guide allows relative days/hours expiry for flows, while campaigns offer one-year or specific-date expiry. Relative expiry includes an additional 24-hour grace period; a specific expiry date does not. Klaviyo and Shopify also display dates using different timezone conventions.


Check the actual generated discount and checkout behaviour before writing an exact deadline. Do not assume that a four-hour setting means redemption stops four hours after receipt. Put the conditions in clear customer language and keep the reminder schedule inside the tested window.


Treat each channel and template as its own build


Use the editor's coupon insertion option, or the tag {% coupon_code 'WELCOME10' %} with your exact coupon name. SMS and MMS support one dynamic coupon per message; the SMS auto-responder does not support unique coupons. Leave room for the real code length when checking message segments.


In email, hiding a coupon block does not reliably prevent code assignment. Klaviyo warns that hidden blocks can still consume codes. Avoid placing several offer tags in a template and assuming recipients consume only the visible one.


For forms, put a unique coupon on the success step and require the relevant email or phone field. Klaviyo's form guidance supports a static fallback for unique coupons. Create that fallback in Shopify first and check its discount rules. This form feature is not a universal fallback for campaign and flow messages.


Use a real checkout test, not just a preview


An in-app preview can show a PREVIEW placeholder. A preview sent to an inbox or phone can use an available real code, according to Klaviyo's preview guidance. For relative-expiry flow coupons, use a controlled profile through the flow and inspect recipient activity rather than treating a placeholder as success.


  1. Receive the message on a controlled profile. Confirm the code, offer copy and destination agree.

  2. Build an eligible basket, then test the wrong product, a below-minimum basket and an excluded customer where relevant.

  3. Redeem the code and try it again. Check what a later reminder displays after redemption and after expiry.

  4. Test the offer alongside a live automatic discount and another code. Inspect the final payable amount.

  5. Place an order during the journey. Confirm the remaining recovery or incentive reminders make sense.

  6. Test email and SMS for the same person, plus a second profile. Record code reuse, message overlap and actual delivery outcomes.


Use the right Shopify auto-apply link for the event. A checkout-recovery URL is not interchangeable with a browse-event product URL. Test the received button, its query parameters and the final checkout; a working link does not override discount eligibility.


Separate generation failures from rejected discounts


If the message was not delivered, inspect recipient activity, the exact coupon name and available supply. Shopify flow generation can retry, then skip if it fails or the retry window ends. Uploaded-code shortages also need attention. Do not assume Klaviyo silently sends the promotion without its code.


If the message arrived but checkout rejects the code, check activation, expiry, eligible products, minimum spend and prior redemption. Review Shopify's combination settings on the relevant discounts. An existing discount is not automatically the explanation: some combinations are supported and others are not.


Document what support should offer when a genuine customer encounters a failure. Avoid improvising an unrestricted replacement code that changes the economics of the original promotion.


Coordinate reminders around one customer decision


Consider a fictional homeware retailer offering a first-order incentive on selected full-price products. Its welcome email and SMS should describe one coherent offer. A simultaneous cart reminder should not introduce a larger discount simply because the customer entered another journey.


Reuse the intended coupon for a reminder and test the received code. The same unexpired code can appear again; showing it again does not reset redemption. Recheck whether the customer has purchased before sending another purchase incentive. Our Klaviyo flow guide explains the surrounding entry, exclusions and QA work.


Measure redemptions, discount cost, contribution and subsequent purchasing alongside message-attributed revenue. Where volume permits, compare an incentive with a relevant alternative or holdout. Redemption alone cannot establish that the discount created an additional purchase.


Frequently asked questions


Are Klaviyo dynamic coupon codes single-use?


Shopify-generated unique codes are single-use, but can still be shared before redemption. Uploaded codes follow the redemption rules in the store system. Test those rules rather than assuming the upload makes a code single-use.


Why does my preview show the coupon name instead of a working code?


In-app previews use a placeholder. Test with an available real code and a controlled recipient. A correctly styled placeholder proves neither discount validity nor checkout behaviour.


Will every message automatically fall back to a static code?


No. The form builder supports a configured static fallback. Treat campaign and flow shortages separately, and inspect skips or retries instead of expecting that form behaviour everywhere.


If incentives are scattered across overlapping journeys, explore our flow rebuild project or Klaviyo agency support. We can help define the offer rules, customer journey and launch checks together.

 
 
 

Recent Posts

See All

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page