ShopifyProduct Thinking6 min readTurning a blank store into a first sale
A setup checklist that treats an empty store as a sequence, not a form.
- The surface
- The merchant admin after signup: the home screen setup guide, the product editor, the theme picker, and the payments and shipping settings that gate going live.
- What the user wants
- I want to sell something online without hiring anyone, and I want to know which of the hundred things in this admin actually has to happen before I can take money.
The setup guide on the home screen
A new store opens on an ordered checklist of tasks such as adding a product, customising the theme, and setting up payments, each collapsible into a short explanation and a single button.
progressive disclosure: Showing the few controls most people need, and keeping the rest one step away.
A commerce admin has more settings than any new merchant can hold in their head. Showing one ordered list hides the rest until it matters, so the merchant makes one decision at a time. The ordering also carries an opinion about what matters first, which is a product decision disguised as UI.
Add your first product
The product editor asks for a title, description, media and price, and leaves inventory, variants, SEO and metafields further down the page with sensible values already filled in.
Defaults as decisions
Every field left blank is a question the merchant has to answer before they can proceed. Prefilling the long tail means a merchant who knows nothing about SKU conventions still ends up with a valid product. The defaults encode Shopify's judgement about what a reasonable store looks like.
Picking a theme
New stores start on a free default theme that is already populated with the merchant's own products, and the theme editor edits live sections with a preview beside the controls.
Seeded empty state: What a screen shows before there is any content in it.
A blank storefront gives a merchant nothing to react to, and reacting is easier than creating. Putting their real product into a working layout collapses the gap between setup and something that looks like a shop. The preview turns an abstract settings change into a visible consequence.
Payments
Shopify offers its own payment processing as the first and most prominent option, with third party gateways listed underneath, and the setup flow collects business and bank details in stages rather than one long form.
House option as the path of least resistance
Choosing a payment gateway is the one setup step where a non technical merchant is least equipped to evaluate options. Putting a first party option at the top removes a comparison the merchant did not want to do. It is also the part of the business Shopify most wants attached, which is why the placement is not neutral.
The test order
Merchants can place a test order using a test mode before the store is live, which produces a real looking order in the admin without moving money.
Rehearsal before commitment
The scariest moment in setting up a store is not knowing whether checkout actually works. A test order lets the merchant see the whole loop, including the confirmation email and the order record, before a stranger does. Confidence built here is what makes them willing to send traffic.
Removing the password page
A development store sits behind a password page, and going live is a single explicit action that removes it. The admin shows the store's status plainly.
One clear commitment point
Scattering the launch across many settings leaves merchants unsure whether they are live. Compressing it into one toggle makes the state legible and reversible. It also gives the setup guide a real finish line, which is what makes the checklist feel completable.
A checklist is a statement of priorities
What not to copy
- The setup guide implies that finishing the checklist produces a working business. It produces a working store. Nothing in the flow asks where traffic will come from, which is the actual constraint for almost every new merchant, and the cheerful completion state papers over that.
- App recommendations appear throughout the admin, styled like platform features rather than paid third party software. A merchant who cannot yet tell the difference can accumulate several monthly subscriptions before making a single sale.
- Transaction fees for using an external gateway are documented but surface late, after a merchant has already chosen and configured one. Pricing that penalises a choice should be visible at the moment of choosing, not in the settings page afterwards.
- Theme customisation invites weeks of work on a storefront nobody is visiting yet. The admin has no counterweight nudging merchants toward the first customer conversation instead of the tenth font change.
The takeaway
An onboarding checklist is a strategy document. The order you put the tasks in tells the user what you believe matters, so be honest about whether it also tells them the truth.
Finished the teardown? Bank it and the day counts toward your run.
Where the principles come from
- The Design of Everyday Things, Don Norman
- Nudge: Improving Decisions About Health, Wealth, and Happiness, Richard H. Thaler and Cass R. Sunstein
- Progressive Disclosure, Nielsen Norman Group
Written from public behaviour of the product, not from inside it. Interfaces change often, so treat the flow described here as of the time of writing and check the live product before quoting it.