Skip to main content

Hi everyone

I’ve gone through related threads but haven’t found a workable solution.

I have a post-purchase flow that sends a unique single-use coupon with a 90-day expiry. The issue is that if a customer places a second order without redeeming the first code, the flow sends the same code again (since it’s still valid), and the email repeats the original static expiration date from the first send. This creates confusion about the actual expiry.

I considered using show/hide logic based on redemption status, but as far as I can tell there’s no way in Klaviyo to check whether the code was actually redeemed.

Has anyone implemented a reliable workaround or a different strategic approach to avoid resending the same code and expiration date?

Thanks,
Irene

Hi ​@Woodhope,

That’s a good question. As of right now, it’s unfortunately not possible to accomplish this, because no events are sent from most integrations (Shopify, BigCommerce, Magento, ect) that let Klaviyo know that a coupon has been redeemed. I definitely understand that this is limiting, and it would be really useful to have this feature, so you could build filters based on this. I’m happy to reach out to our product team and recommend that we implement this in the future.