There’s a moment in every store build where the design is done, the products are loaded, and everyone is excited to launch. That’s exactly when mistakes slip through. Order emails go to an old address. Tax is calculated wrongly for one region. The payment gateway is still in test mode, or worse, it’s live but nobody tested a refund.
I’ve launched a lot of WooCommerce stores, and I’ve also been called in after rushed launches went wrong. The difference is almost always a boring, thorough checklist. Here’s mine. It’s long, but every item is on it because something went wrong without it at some point.
Store basics
Start with the foundations in WooCommerce settings.
- Store address and currency. Your address affects tax calculations and some shipping methods. Confirm the currency, decimal places and price format match what customers expect.
- Selling locations. Decide which countries you sell and ship to. Restricting these avoids orders you can’t fulfil.
- Store pages. Confirm the shop, cart, checkout and my account pages are assigned correctly under WooCommerce settings. A missing assignment causes confusing errors.
- Permalinks. Set product URLs to a clean structure before launch. Changing them later means redirects and lost search rankings.
Products
- Every product has a clear title, a proper description, accurate price and good images.
- Variable products have every variation priced and in stock where appropriate. A variation with no price can’t be purchased, and customers rarely tell you; they just leave.
- Stock levels are correct, and you’ve decided whether to allow backorders.
- Weights and dimensions are filled in if shipping rates depend on them.
- SKUs are unique and match your inventory or accounting system.
- Product categories make sense from a customer’s point of view, not just internally.
Spend some time browsing the shop as a stranger would. Look for missing images, duplicate products, odd formatting and prices that end in strange decimals.
Taxes
Tax is where small errors become expensive. The rules differ by country and region, and they change.
- Decide whether prices are entered including or excluding tax, and whether they’re displayed including or excluding tax. Keep it consistent with what’s normal in your market.
- Set up tax rates for every region you sell to, or use a tax automation service.
- Check tax on shipping. In many places, shipping is taxable.
- Place test orders to addresses in different regions and confirm the tax amounts.
If you’re unsure about your obligations, talk to an accountant before launch. Fixing tax mistakes on hundreds of past orders is miserable.
Shipping
- Shipping zones are created for each region, in the right order. WooCommerce matches the first zone that fits, so a broad zone above a specific one will catch orders meant for the specific one.
- Rates are correct for different cart sizes and weights.
- Free shipping thresholds work as intended, including whether coupons count toward the threshold.
- Local pickup, if offered, is clearly explained.
- Shipping classes are assigned to bulky or special items.
Test carts at the edges: just under the free shipping threshold, just over it, a single light item, and a heavy combination.
Payments
This section deserves the most attention.
- Payment gateways are connected to the correct live accounts, not personal or test accounts.
- Test mode has been used to place successful orders, failed payments and refunds.
- Live mode is switched on before launch, and one real low-value order has been placed and refunded.
- Payouts go to the correct bank account.
- Webhooks are configured where the gateway requires them, so order statuses update correctly. A missing webhook can leave paid orders stuck as pending.
- The checkout works with the payment methods customers actually use in your market, including wallets if relevant.
I always place a real order with a real card before launch, then refund it. Test mode catches configuration issues, but only a live transaction proves money will actually arrive.
Checkout experience
- Remove checkout fields you don’t need. Every unnecessary field costs conversions.
- Guest checkout is enabled unless you have a strong reason to require accounts.
- Error messages are clear when a field is missing or a card is declined.
- The checkout works properly on mobile phones, which is where much of your traffic will come from.
- Terms and conditions or privacy checkboxes appear only where legally required, and link to the right pages.
- Coupon codes work, and expired or invalid codes show a helpful message.
Emails
WooCommerce sends a lot of emails: new order notifications to you, order confirmations, processing and completed emails to customers, password resets and more.
- Every email template has your branding, correct colours and logo.
- The “from” name and address are set to something customers recognise.
- Admin notifications go to an inbox someone actually checks.
- Emails are delivered reliably. Default PHP mail often lands in spam or isn’t sent at all. Set up SMTP with a transactional email service and configure the domain’s SPF, DKIM and DMARC records.
- Send yourself every email type and read them on a phone.
Unreliable email is one of the most common post-launch complaints I hear. Customers assume their order failed when they don’t get a confirmation, and they either order twice or contact support.
Legal and trust pages
Requirements depend on where you and your customers are, but most stores need:
- Privacy policy
- Terms and conditions
- Refund and returns policy
- Shipping information
- Contact details and business information
Link them in the footer and at checkout where appropriate. Clear policies also reduce support questions and build trust with first-time buyers. If you sell into regions with strict consumer protection or data rules, get proper advice on the wording.
Performance
A slow store loses sales. Before launch:
- Test product, category, cart and checkout pages on mobile.
- Compress and properly size product images.
- Confirm page caching excludes the cart, checkout and my account pages, and doesn’t cache personal data. This is a classic mistake that can show one customer’s cart to another.
- Enable a persistent object cache if your host supports it.
- Make sure High-Performance Order Storage is enabled if the store is new, and that your plugins support it.
- Remove unused plugins and scripts.
Security
- SSL is active across the whole site, with no mixed content warnings.
- Admin accounts use strong passwords and two-factor authentication.
- Staff accounts use the Shop Manager role, not Administrator, unless they need full access.
- Automatic off-site backups are running, with enough frequency for your order volume.
- A firewall or security service is in place.
- Debug mode is off, and error messages aren’t displayed to visitors.
Analytics and tracking
- Analytics is installed and records purchases as conversions, with order values.
- Ad platform conversion tracking is set up if you’ll run ads.
- Cookie consent is configured to meet the rules in your markets, and tracking respects it.
- Search Console is set up and the sitemap submitted.
Place a test order and confirm it appears correctly in analytics. Getting this right at launch means you have clean data from day one.
Final test orders
Before announcing anything, run through these scenarios end to end:
- A guest buys one simple product with a card.
- A logged-in customer buys several products, including a variation, with a coupon.
- An order to a different tax region.
- A failed payment, to confirm the customer sees a clear message and can retry.
- A refund processed from the WooCommerce order screen, confirmed in the gateway.
- A password reset and account creation.
Check that stock reduced correctly, emails arrived, analytics recorded the sale and the order shows the right status.
After launch
The first week matters. Watch orders closely, check emails are going out, keep an eye on error logs and respond quickly to any customer who reports a problem. Most launch issues show up in the first few days, and catching them early protects both sales and reputation.
Frequently asked questions
How long does it take to prepare a store for launch?
For a small store with a few dozen products, a thorough checklist takes one to two days of testing and fixing. Larger stores with complex tax, shipping or integrations need more. It’s always less time than cleaning up after a bad launch.
Should I launch with a soft opening?
Yes, if you can. Open quietly to friends, existing customers or a small audience first. Real customers find problems that internal testing misses, and it’s easier to fix them before you spend money on marketing.
Which payment gateway is best?
It depends on your country, the payment methods your customers prefer, fees and payout speed. Many stores offer one major card processor plus one popular wallet or local option. Avoid offering too many choices, which can clutter checkout.
Do I need a staging site for my store?
Strongly recommended. After launch, plugin and theme updates should be tested on staging before reaching the live store. A broken checkout costs money every hour it’s down.
Final thoughts
Launching a store is exciting, but the customer’s first order sets the tone for everything that follows. A methodical checklist turns launch day from a gamble into a non-event, which is exactly what you want. Take the extra day, test every path a customer might take, and open your doors with confidence.
