Build a single product website that sells one thing well

Why one product earns its own site

A marketplace listing gives your product a title, a few images and a box of bullet points squeezed between a competitor's ads. A general shop gives it a grid tile. Neither leaves room for the things that actually sell a considered purchase: how it was made, what it looks like in a real kitchen or on a real wrist, what it's like after six months, and what happens if it arrives damaged.

A dedicated site also gives you an address you can print on the box, say on a podcast and put in an Instagram bio. When the product is the brand (a single knife, a standing desk converter, a board game, a tool you invented) that address matters more than a shop with one item on its shelf.

The page, top to bottom

Most single-item sites that work follow roughly the same order, because it matches the order of a buyer's doubts.

1. Name, one-line purpose and the price. Put the price near the top. Hiding it until the end reads as a trick, and people scroll to find it anyway.
2. The hero photo. The product on its own, well lit, at the size people expect it to be. Then a second photo in use.
3. Three to five reasons it's different. Specific: "forged from one piece of 1.4116 steel", not "premium quality".
4. Details and dimensions. Size, weight, materials, what's in the box, care instructions. A short table works better than a paragraph.
5. Gallery. Close-ups of the parts people worry about: joins, seams, the underside, the charging port.
6. Questions. Delivery times, returns, warranty, compatibility. These are the questions you otherwise answer by email.
7. The buy button, again. Repeat it after the questions, with the price beside it.

Photos carry most of the weight

With one product, there's nowhere to hide a weak photo. Shoot it against a plain background for the hero, then in context, then in detail. Keep the lighting and angle consistent so the gallery reads as one set. A short video of the product being used can answer more questions than a paragraph of copy; host it on YouTube or Vimeo and link to it, because these pages can't play video.

A designed product page uses library photos in its own sections; your photos can show only as entries in a CMS collection (variants or uses, say) whose image field holds the address of a photo you host, so for a page built around your product shots, ask for an app build. Uploaded files are used by app builds: they're checked by their first bytes (so a renamed file of the wrong type is refused) and stored under your account, and the model looks at them when it lays out the app, so it can put the in-use shot beside the paragraph about using it. Video files also play only inside app builds, not on a designed product page. Write the alt text for each image as a description of what's shown, not a keyword.

Taking payment without a cart

A cart exists to collect several items before checkout. With one item it's an extra step that loses buyers. Instead, point the buy button straight at a checkout link from your own payment provider. On Anticode you can use a link from Stripe Payment Links, PayPal, Gumroad, Lemon Squeezy, Shopify or Whop. Your provider hosts the checkout, collects the card details, applies tax rules you've set there, and sends the receipt.

If you later offer the product in two colours or sizes, let the checkout handle it: an Anticode account has one payment link, opened by every buy button, so use a provider checkout with options or a short product list. Read more in add a buy button to a website and the Stripe Payment Links integration.

How Anticode builds it

Describe the product in a sentence or two: what it is, who it's for, and how it should feel. The Architect asks up to three questions that change the page, such as whether you'll ship internationally or which photo should lead, then shows a short plan before anything is built. The design engine lays out a landing page with the payment must-have, held to one of seven design systems. A kitchen tool might suit Editorial; a piece of outdoor kit, Organic; a tech accessory, Technical or Swiss. One action colour is used for the buy buttons, so they stand out from everything else on the page.

The published page is plain HTML and CSS with no scripts, which keeps it fast on a phone and means there's no tracking code on the product page. Page views per day and where they came from are in the dashboard, counted without cookies.

What this setup won't do

• No stock count. Anticode doesn't track inventory, so it can't show "3 left" or stop selling at zero. Manage that in your payment provider (Shopify and some others can cap quantities) and update the page when you sell out.
• No shipping or tax calculation on the page. Your checkout provider handles both, if you set them up there.
• No on-site checkout. Payment always happens on your provider's checkout page, not inside the site.
• No order management. Orders, refunds and receipts live in your payment provider's dashboard.

If you expect to add a second and third product soon, a product catalogue site or a full online store build may be the better starting point.

Questions people ask

Is a single product website better than selling on a marketplace?

It's different rather than better. A marketplace brings buyers who are already searching there; your own site gives you the whole page, your own address and the customer relationship. Many sellers run both and link the site from the packaging.

Can I sell more than one size or colour?

Yes, but the choice happens at checkout. Your account has one payment link, so point it at a provider checkout or product list that offers the variants. There's no variant picker that changes the price on the page itself.

Does Anticode take a cut of sales?

The payment link belongs to your own provider account, so payments go straight to that provider. Their fees are set by them.