Building a one-product Shopify store

A one-product store isn't a small version of a normal store. The whole structure inverts: there's no browsing, no collections that matter, no navigation problem to solve. The homepage is the product page, and every design decision follows from that.

The homepage is the product page

Don't build a homepage that links to a product page. Build one page that does both: proposition, product, evidence, purchase — with the buy option repeated as the visitor scrolls.

A structure that works:

1. Above the fold — what it is, who it's for, the product image, price, and add to cart. All of it, without scrolling.
2. The problem it solves, in the customer's words.
3. How it works — three steps or three features, not twelve.
4. Proof — reviews, numbers, press, photographs of it in use.
5. The detail — specifications, materials, dimensions, what's in the box.
6. Objections — delivery, returns, guarantee, compatibility.
7. FAQ — the actual questions from your support inbox.
8. A final buy block.

Repeat the add-to-cart at least three times down that page. On mobile, a sticky buy bar after the first screen.

What to do about navigation

Almost nothing. A one-product store with a nine-item menu looks like it's hiding something. Keep it to what's genuinely needed — contact, FAQ, policies — usually in the footer rather than a header menu.

There's no collection structure to design, which removes the decision that normally ages worst. Spend that effort on the product page instead.

Variants still matter

One product rarely means one variant. Size, colour, bundle quantity, subscription versus one-off — all of these are variant decisions, and on a single-product store they carry the entire merchandising load.

Two things to get right:

• Bundle pricing shown as a saving. "3 for £45 — save £15" outperforms three separate quantity options.
• The default selection. Whatever is preselected is what most people buy. Choose it deliberately.

Product page anatomy covers the rest.

Where the conversion work is

With one product there's nowhere to hide, which is useful — the funnel is short enough to actually reason about.

• Page speed matters more, because there's a single page carrying everything. A heavy hero video is the whole first impression and the whole LCP problem — the performance checklist.
• The FAQ is a conversion tool, not a support page. Write it from real questions.
• Reviews near the buy block, not at the bottom.
• The returns promise stated in one line, near the price — policy pages.

More generally, conversion design.

The technical setup is simpler

Genuinely less to do than a normal build:

• One product to photograph properly. Do it well — you have no catalogue to hide behind.
• Simple shipping: usually one or two zones and a flat rate.
• No import, no filtering, no collection pages.
• A theme can be heavily simplified — most of its templates are unused.

Which means the budget concentrates on the one page and the photography, which is exactly where it should be.

When you add a second product

Plan for it, lightly. The common trap is a store so hard-coded to one product that adding a second means a rebuild.

Build the page as proper sections rather than one bespoke template, keep the product data structured, and the transition to a small catalogue later is a day rather than a project.

What doesn't work

• A generic homepage that makes people click through to the product. You've added a step and lost half of them.
• Fake scarcity. On a one-product store it's the only thing on the page and it reads as exactly what it is.
• A long brand story before the product. People arrived because of an ad about the product.

One product removes every structural decision and leaves you with only the hard one: is this page convincing? There's nothing else to blame.