Create coupons in WordPress under Marketing → Coupons → Add coupon. Set a code, a discount type (percentage, fixed cart discount, or fixed product discount), an amount, and usage restrictions. If a coupon isn't applying at checkout, the fix is almost always in the restriction tabs, not the server: check Usage restriction for minimum/maximum spend, excluded sale items, and product/category rules, and check Usage limits for per-coupon or per-customer caps that may already be exhausted.
Coupons and caching
Coupon fields live on the cart and checkout pages, and those pages are dynamic by nature. See how we make your site fast for how caching is handled on Flashcloud generally, and WooCommerce hosting for the stack behind it. If a coupon still looks like it isn't taking effect, clear the customer's session first (log out and back in, or test in a private browser window) before assuming it's a cache problem. Product and category pages are cached normally, so a sale badge or price change on those pages can take a short moment to show for a returning visitor, but it never affects what happens at checkout.
Common reasons a coupon won't apply
- Expired or scheduled: check the
Coupon expiry datefield. - Excluded from sale items: if a product is already on sale and the coupon has "Exclude sale items" checked, it won't stack.
- Individual use only: if this is enabled, the coupon fails silently when another coupon is already in the cart.
- Minimum spend not met: WooCommerce shows a notice for this, but customers often miss it above the fold.
- Email restrictions: coupons scoped to specific customer emails will reject anyone else's code entry.
- A caching or minification plugin conflict: this is rare on Flashcloud because we don't ask you to run extra caching plugins on top of what's already pre-configured, but if you've added a third-party optimizer, temporarily disable it to rule out a JS conflict on the coupon field.
Performance during sales
Coupon codes tend to cluster around sales events, and sales events mean traffic spikes. Redis object cache is provisioned on every WordPress hosting account and helps the store handle the extra load. For the broader picture on running a store under load, see running a WooCommerce store, which covers what stays cached, what doesn't, and why testing changes on a staging copy first matters more for a store than for a blog.
Testing coupon changes safely
If you're changing coupon logic with a plugin, adjusting tax class behavior tied to a coupon, or testing a new bulk-discount extension, do it on a staging copy of the site rather than live. Push to live only after a full test order confirms the discount, tax, and total all come out right.
When to contact support
If a coupon isn't applying because of something server-side, caching behavior that doesn't match what's described above, PHP errors in your logs, or a database issue, open a ticket from the portal's Support section. You can check logs and server details yourself via accessing cPanel first if you want to narrow it down. Tickets go to a real person, not a bot.