Online store launch checklist, in the order that matters
A store can look finished and still be unable to take money. The ordered checks before you go public, including the one nearly everyone skips.
The short version
- Order the launch by waiting time and by money: payment verification and the domain first, design last.
- One real payment pushed through live checkout and then refunded tests seven separate failure points for the price of one processing fee.
- A finished store is not a launch. Nothing on a technical checklist produces visitors, which is the more common reason launch day is quiet.
You can have a store that looks finished and still have a store that cannot take money. That is the usual shape of a bad launch: the site goes live, a handful of people arrive, one tries to buy, something fails quietly, and you find out two weeks later while wondering why the traffic never converted.
This online store launch checklist is ordered, and the order is the point. Later steps assume earlier ones are true, so working out of sequence means doing the same work twice. Anything that touches money comes before anything that touches design, because a plain store that takes payments is worth more than a beautiful one that drops them.
One step matters more than all the others: putting a single real payment through your own checkout with your own card, and then refunding it. Almost nobody does this. It is the difference between launching and only appearing to launch.
Phase 1 — the two steps with waiting time attached
Start here, because these two are the only steps you cannot compress by working harder the night before.
Get your payment account approved. Processors verify businesses before releasing live mode, and verification takes as long as it takes. They may want identity documents, a bank account in the business name, or a description of what you sell, and some categories are declined outright. Learning that two days before launch is a launch postponed; learning it three weeks before is an afternoon of paperwork.
What goes wrong: people build the entire store in test mode, assume live mode is a toggle, and discover on launch morning that the account is "pending review."
Buy the domain and let DNS settle. Domain changes propagate on their own schedule. Point it early, confirm it resolves, and confirm the certificate is valid so the address bar shows a lock. If you are still weighing whether to bother, that question has its own answer: you want the domain before you tell anybody the address.
What goes wrong: launching on a platform subdomain, then moving to a real domain a month later and losing the few links and bookmarks you had earned.
Phase 2 — the catalog, as a buyer sees it
Only now is it worth loading products properly, because prices and variants are what the money steps test.
- Every product has a price that is correct in the currency you will actually charge. Not the currency you built in.
- Every variant exists and is buyable. Size, color, bundle. Click into each one and confirm it adds to the cart.
- Stock counts are real. If you do not track stock, say so deliberately rather than leaving a field at zero, because zero usually means unbuyable.
- Every product has at least one image that is not a placeholder, all the same shape, so the grid does not look broken.
- Shipping weight or dimensions are filled in if your rates depend on them. Blank weights are the classic cause of a $0 or absurd shipping quote.
What goes wrong: a tool generates the catalog, the copy reads well, and nobody clicks through to the third variant of the fourth product, which has no price. An AI that writes product pages and on-page SEO — which is what mAutomate's AI Storefront Studio does — removes the typing, not the checking. Nothing goes live until you approve it, and approving it means looking.
Phase 3 — the money path, end to end
This is the phase people skip, and the only one where skipping is fatal.
The one real payment
Switch to live mode. Buy something from your own store, with a real card, at the real price. Then go into the dashboard and refund it.
Not a test-mode order. Not a 100%-off coupon. A real charge for real money that you give back to yourself. It costs one processing fee, the cheapest insurance you will buy all year.
Here is what that one transaction checks that nothing else does:
| What the test payment proves | How it fails otherwise |
|---|---|
| Live keys are installed, not test keys | Checkout "succeeds" and no money ever arrives |
| The charge reaches your bank account | Payouts are held pending bank verification |
| The order appears in your dashboard | Orders exist at the processor and nowhere you look |
| The customer gets a confirmation email | Buyers assume the order failed and dispute it |
| You get a notification of the sale | First order sits unshipped for days |
| Tax and shipping are added correctly | You eat the difference on every order |
| A refund actually works | Your first refund request becomes a chargeback |
Seven failure modes, one purchase. The refund half matters on its own: refunds use a different permission and sometimes a different balance, and the first time you discover you cannot issue one is usually while an angry customer waits.
The rest of the money path
- Confirm the price on the product page, in the cart, and on the final charge is the same number.
- Test checkout on a phone, on cellular data, not at your desk.
- Abandon a cart deliberately and see what the store does.
- If you have a launch discount code, use it once and check it cannot be stacked with itself.
Phase 4 — shipping, before you promise anything
Publish the three things a buyer needs: where you ship, what it costs, how long it takes.
Then test the quote. Put an order through to the farthest place you will ship and confirm the rate is neither zero nor nonsense. Weigh one packed parcel on a kitchen scale instead of guessing — the guess is always low, and the difference comes out of your margin on every order.
What goes wrong: flat-rate shipping set from a guess, then a month of orders going to the far end of the country at a loss.
Phase 5 — the pages that decide whether you look real
A first-time buyer who has never heard of you is hunting for reasons to trust you, and the reasons are boring pages:
- Contact — a real email address that reaches a mailbox you read. Business email belongs in day-to-day operations, not on a wish list.
- Returns and refunds — in plain words, with a number of days. "Contact us for returns" reads as "we will argue."
- Shipping — the same three facts as above, in one place.
- About — one honest paragraph about who makes this. It converts better than a mission statement.
- Privacy — required in most places if you collect an email address, which you do.
What goes wrong: the store is beautiful and anonymous, and the shopper searches your name, finds nothing, and closes the tab.
Phase 6 — the technical pass
Fast, mechanical, one sitting:
- Open the store on a phone and complete a purchase.
- Click every link in the header, footer and navigation; fix the dead ones.
- Check page titles are distinct and readable in search results, not "Home" and "Product."
- Visit a URL that does not exist and confirm the 404 page offers a way back.
- Send yourself the order confirmation and check it does not land in spam.
- Confirm analytics records visits, including your test visit.
- Search your own store for a product name and confirm the result appears.
Phase 7 — launch day, which is mostly staffing
Pick a weekday morning, not a Friday night. Be available for the first few hours. Watch the first order all the way to the carrier instead of celebrating and going to bed. Reply to the first customer email within the hour: the first five customers are the ones who tell other people.
What a launch checklist cannot do for you
It cannot produce buyers. Everything above makes a store that works for the people who arrive, and arranges nothing about whether anybody arrives. A finished store with no audience is the most common outcome in this business, and it feels like a technical failure while being nothing of the kind.
So do the checklist, then do the harder half. Build a small list before you open so launch day is not silent — pre-launch marketing is the version of that work that fits in a few weeks. After you open, getting the first ten customers is its own project, and those ten are mostly people you contact directly rather than people who find you.
The whole sequence, in one table
| Order | Step | Breaks if skipped |
|---|---|---|
| 1 | Payment account verified | Launch slips by days or weeks |
| 2 | Domain pointed, certificate valid | Links and trust go to the wrong address |
| 3 | Catalog: prices, variants, stock, images | Products that cannot be bought |
| 4 | One real payment, then refunded | Silent checkout failure for everyone |
| 5 | Shipping rates tested to the far edge | A margin loss on every order |
| 6 | Contact, returns, shipping, about, privacy | Shoppers decide you are not real |
| 7 | Mobile, links, titles, 404, email, analytics | Avoidable small leaks everywhere |
| 8 | Launch-day cover for the first orders | A slow first reply to your first customer |
If you only have one hour before you go public, spend it on step 4.
mAutomate plans start at $29 a month for Launch, and every plan includes a 14-day free trial with no card required, so the whole sequence above can be worked through before you pay anything. The pricing page lists what each plan adds; get started is where the store itself begins.
Questions people ask
What should I check before launching an online store?
Work in order: payment account verified, domain and certificate live, catalog prices and variants correct, one real payment pushed through checkout and refunded, shipping rates tested, the contact, returns, shipping and about pages published, then a mobile and links pass. The money path comes before design, because a plain store that takes payments beats a beautiful one that drops them.
Why should I make a real purchase from my own store?
A single live order, refunded afterwards, is the only test that proves live keys are installed, the charge reaches your bank, the order appears in your dashboard, the confirmation email arrives, tax and shipping calculate correctly and refunds work. It costs one processing fee and rules out seven separate silent failures.
How long does it take to launch an online store?
The build is often a few days; the waiting is what sets the date. Payment account verification can take days and occasionally longer, domain and certificate changes propagate on their own schedule, and stock has to arrive. Start those three in the first week and the rest fits around them.
Do I need a custom domain before I launch?
Point a domain before you tell anyone the address, otherwise the links, bookmarks and search results you earn belong to a platform subdomain you later leave. On mAutomate, custom domains begin on the Grow plan at $79 a month, while the Launch plan at $29 runs on a platform address.
- Launching
- Checklists
- Payments
Ready to start your store?
Let the AI build, market, and run it — you ship the product.
Get started free