
Creating a coupon for your own store? Start here.
Write the customer promise first
Imagine a small notebook promotion. Write one sentence explaining which purchase you want to encourage and what the customer should receive. Then prepare an internal brief: who the offer is for, which purchase it targets, when to share it, and what cost you are prepared to accept. This is our suggested planning method, not a list of mandatory platform fields.
Ask someone else to read the brief without an explanation from its author. If they interpret the offer differently, fix the wording first. Settings should not become a retrospective explanation for why a shopper supposedly misunderstood an advertisement. A clear brief also helps the person answering customer questions later.
Setup
On staging, enable coupons: WooCommerce / Settings / General. Open Marketing / Coupons / Add new coupon: code, type, amount, restrictions, limits, expiry; save with Publish.
On staging, check the expected discount and rejection when a restriction is broken.
Check shipping as a separate rule
A coupon's Allow free shipping setting needs a corresponding Free shipping method in the relevant zone. That method can require a coupon, a minimum spend or a combination. A separate checkbox determines whether the threshold is assessed before or after the discount.
A hypothetical calculation: 3000 minus 300 is 2700. A threshold of 2900 is reached before the reduction but not afterwards. This is arithmetic, not a live offer. Compare the selected rule with the customer promise; code acceptance alone does not explain shipping.
A staging copy still needs care
WooCommerce warns that test orders can send emails and enter analytics; integrations may not distinguish them from real orders. Its documentation recommends testing on staging and using the payment gateway's test mode. Understand the connected services before testing instead of relying on the word test.
Its separate conflict guide recommends a backup and isolated theme/plugin checks. If the result differs from expectations, investigate suspected components one at a time on staging. Do not transfer a diagnostic process that disables components to a live store serving customers.
We suggest ending preparation with a short internal decision: who approves the customer promise, who answers questions, and who handles disputed cases. This assigns responsibility; it is not a WooCommerce feature. One screenshot cannot capture that decision. The next colleague needs an intelligible record of what was agreed.
Release the settings separately to production before distribution. Documentation was read on 21 October 2026; we did not configure a real store, place orders or make payments.