Launching a WooCommerce Store? These 7 Mistakes Will Sink It Before Day One

Launching a WooCommerce Store? These 7 Mistakes Will Sink It Before Day One

I’ve watched a lot of WooCommerce stores launch over the years. Client stores, friends’ stores, my own stores. And here’s the uncomfortable truth: most of the ones that failed didn’t fail because of the product. They failed because of decisions made in the two weeks around launch day.

The good news? Every one of these mistakes is avoidable, and none of the fixes cost much. Let me walk you through the seven I see over and over again.

Mistake #1: Building the store in public

You buy the domain on Monday. By Tuesday it’s live with a default theme, “Hello World” post, and three products with placeholder descriptions. By Wednesday, Google has crawled it, a few early visitors have seen it, and your brand’s first impression is… that.

Nobody gets a second first impression. Not with customers, and honestly, not with Google either.

The fix takes ten minutes: put a proper maintenance or coming soon page up before you touch anything else. A good one does three jobs at once:

  • It hides the mess, so early visitors see a clean, branded page instead of a half-built store.
  • It returns the right status codes, so search engines treat the site as temporarily under construction rather than broken.
  • It gives you a headline and a sentence of keyword-rich text, so you can start ranking before the store even exists.

And it can collect email addresses, which brings me to mistake number two.

Mistake #2: Launching to an audience of zero

Here’s a question I ask every store owner before launch: “Who are you going to tell?”

The silence is usually the answer.

Your coming soon page should have one job beyond looking good: capturing emails. Every curious visitor during your build phase is a potential day-one customer. I’ve seen stores open with 40 orders in the first week purely because they collected 600 emails during a two-month build. Compare that with launching cold and hoping Google sends someone.

Mistake #3: Testing on fast hosting, launching on cheap hosting

Your store feels quick when you’re the only one on it. Add real product images, a few plugins, and twenty simultaneous visitors, and that $3-a-month hosting plan starts gasping.

Slow stores don’t get complaints. They get silence. People just leave. Load your full catalogue, run speed tests on every page template, and do it before launch while fixing things is still free.

Mistake #4: Treating international customers as an afterthought?

money

This is the big one, and almost everyone gets it wrong.

Picture a shopper in Berlin finding your store. Nice products, fair prices… in dollars. Now she’s doing mental currency maths. Then she’s wondering what her bank will add on top. Then she’s gone.

Card issuers typically add 1 to 3 percent in conversion fees when someone pays in a foreign currency. That’s an invisible surcharge on every international order, and your customer feels it even when she can’t name it.

Before we get to the fix, it helps to know there are two very different things sold under the “currency” label:

Display-only converter True multi-currency
What the customer sees An approximate converted price, often labelled “from approx.” A real, final price in their own currency
What the customer pays Your base currency, plus 1-3% card conversion fees Exactly the price shown, in their currency
Effect on trust Undermines it; charged amount never matches Builds it; no surprises on the statement
Effect on conversions Little to none Higher international conversion rates

You want the right-hand column. WooCommerce ships with exactly one currency, so you need an extension for it. I usually point people to the multi currency plugin for WooCommerce built by Aelia, who’ve been doing WooCommerce internationalisation for over a decade (their switcher sits at 4.9 stars across 90+ reviews, which tells you something).

currency switcher

What it actually does: you pick the currencies you want to accept, visitors choose theirs from a small switcher widget, and the whole store follows. Prices, cart, checkout, the payment itself. The customer pays exactly the number she saw on the product page, and the order records which currency was used so your bookkeeping stays sane.

A few features do the heavy lifting:

  • Geolocation detects a visitor’s country and sets their currency automatically, so that shopper in Berlin sees euros before she’s clicked anything. Her choice is remembered on return visits.
  • Exchange rates update themselves from providers like Open Exchange Rates, or you can set them manually.
  • Fixed prices per currency mean your hero product sells at a clean $99, €95 and £85 instead of $99, €91.37 and £77.82.
  • A base currency per product is handy if you import goods priced in euros but mostly sell in pounds.
  • Payment gateways can be shown or hidden per currency, so customers only see options that actually work for them.

Set this up during the build, behind your maintenance page, and international customers are welcome from minute one instead of month six.

Mistake #5: Writing legal pages after someone asks for them

Privacy policy. Terms. Refund policy. Shipping information. Boring? Completely. Optional? Not even slightly. Payment providers ask for them, ad platforms ask for them, and the first customer dispute will ask for them loudly. Write them while the store is still hidden and you’ll never think about them again.

Mistake #6: Never once buying from your own store

You’d be amazed how many owners launch without ever completing a purchase on their own site.

Before you go live, be your own customer and run through this list:

  • Buy something on desktop, then buy something on your phone.
  • Apply a coupon code and check the totals.
  • If you set up multiple currencies, buy in each one. The product page price, checkout total, charged amount and order record should all agree.
  • Read the confirmation email your customer will receive, in each currency.

Every path a real customer can walk, walk it first.

Mistake #7: Throwing away the maintenance page after launch

Launch day arrives, the curtain comes down, and most owners delete the maintenance plugin like scaffolding they’ll never need again.

Keep it. Every store eventually faces a redesign, a migration or a 2am emergency, and there’s a world of difference between visitors seeing a broken checkout and visitors seeing a calm, branded “back shortly” page that protects both your reputation and your rankings. Thirty seconds to activate, when you need it most.

The seven mistakes at a glance

The mistake The fix
1. Building the store in public Put a maintenance / coming soon page up first
2. Launching to an audience of zero Collect emails on the coming soon page
3. Cheap hosting under real load Speed-test every template with the full catalogue
4. One currency for the whole world Install a multi currency plugin before launch
5. Missing legal pages Write privacy, terms, refunds and shipping early
6. Never testing your own checkout Place test orders on every device and currency
7. Deleting the maintenance plugin Keep it installed as your emergency safety net

Notice the theme? Every mistake comes from doing things in public that should have been done in private, or skipping prep that felt optional until it wasn’t. Build behind a curtain, collect your audience while you build, price for the whole world, test like a customer, and keep your safety net installed.

Do that, and your launch week is spent packing orders. Skip it, and you’ll spend the same week learning these lessons the expensive way.