WooCommerce "Coupon Does Not Exist"? Causes & Fix

The coupon is sitting right there in your admin, published, in date — and checkout insists it doesn't exist. That contradiction is the clue: WooCommerce isn't reading your coupon list, it's reading a cached answer about it.

Last updated: 16 Jul 2026 · ~6 min read

What this error actually means

Before WooCommerce checks anything about a coupon — dates, limits, restrictions — it has to turn the typed code into a coupon. It looks for a published coupon whose code matches, and caches that lookup. If it comes back with nothing, you get Coupon "CODE" does not exist! and no other checks ever run.

That's worth knowing, because it narrows things down hard. This error means not found — not expired, not used up, not restricted. An expired coupon says it has expired. A coupon at its usage limit says the limit is reached. So if you're seeing "does not exist" while looking straight at the coupon, only two things can be true: the lookup is being answered by a stale cache, or the coupon isn't in the state you think it's in.

The most common causes (most likely first)

1. A persistent object cache is holding a stale "not found" for this codeThe coupon is published and visible in the admin, but checkout denies it. It usually starts right after you create, rename or restore a coupon. The proof is quick: flush the object cache (Redis, Memcached, or your host's object cache panel) and retry — if it works immediately, this was it.
2. The coupon isn't actually publishedLook at the status column in Marketing → Coupons, not just the row. Draft, Pending, Private, Scheduled for a future date, or sitting in the Trash all produce exactly this error — the lookup only matches published coupons. Scheduled is the sneaky one, because it looks finished.
3. The code doesn't match what's storedIt works when you type it by hand but not when you paste it. A trailing space, a non-breaking space, or a curly quote picked up from a Word doc or an email signature makes it a different string. WooCommerce also normalises coupon codes to lower case when they're saved.
4. The coupon exists somewhere elseYou're looking at it in staging, or on a different site in a multisite network, or it didn't survive a partial database restore. Search for the code on the live site specifically, including the Trash, and confirm it's genuinely there.
5. A plugin was generating the coupon and no longer isThe code isn't in Marketing → Coupons at all, yet it used to work. Bulk-generator, subscription and loyalty plugins can register codes on the fly rather than storing them as real coupons — deactivate or break one and every code it supplied vanishes.

Where to look first

• Flush your object cache and retry the code immediately. Redis, Memcached, or whatever your host calls it. Works now? That was cause 1 — and the real question becomes why invalidation isn't firing.
• Open Marketing → Coupons and read the status, not the name. Draft, Scheduled, Private and Trash all read as "does not exist" to checkout (cause 2).
• Retype the code by hand instead of pasting it. If typing works and pasting doesn't, you have an invisible character in the code, not a coupon problem (cause 3).
• Confirm you're looking at the live site, not staging, and not another site in the network — and search the Trash while you're there (cause 4).
• Code not in the coupon list at all? Then it was never a stored coupon — something was generating it. Find which plugin, and check it's active and healthy (cause 5).

How to know you fixed it

Frequently asked