Swain-Tech Studio websites for small businesses and independent creatives

A Shop, or a Way to Get Paid

"I need a website with a shop" is often said when the actual requirement is "I need people to be able to pay me."

Those are very different projects. A shop is the heaviest, most ongoing thing you can attach to a website. Taking payment can be a link. For service businesses that need to connect labour time with pricing, this page is a useful reference point.

What a shop actually commits you to

Not the build — the operation, which is permanent.

Product photography, for everything, redone as stock changes. The largest hidden cost of selling online.

Stock accuracy, forever, or you are refunding people.

Shipping — weights, boxes, rates, and the queue at the post office. For an independent reference beyond this site, Stripe is a useful place to compare approaches.

Returns, and a policy, and the arguments.

Tax, which varies by what you sell and where the buyer is.

Failed payments and disputes.

All of it real, all of it recurring, and none of it visible in a quote for building the site. If you sell forty products at volume, this is your business and it is worth owning. If you sell four things occasionally, it is a large amount of machinery for a small amount of money.

The lighter options

Four, in rough order of effort.

A payment link. Your payment processor generates a link or a button for a fixed amount. Put it on a page, send it in an email, print the QR code. No cart, no stock, no shipping logic. Ideal for deposits, a handful of fixed-price items, a class, a commission stage.

An invoice. Underrated. For anything negotiated or made to order, an invoice with a pay-now link is the whole system, and it produces better records than a shop.

A booking or scheduling tool that takes payment. For services and appointments this is the actual requirement, and it is not a shop.

A single embedded checkout for a small range. A handful of products with a buy button each, hosted by the payment provider. Some stock handling, no store to maintain.

Each of these can be added to an existing site in an afternoon, and none creates ongoing work beyond fulfilling what people bought.

When you do need a real shop

More than roughly twenty products, where browsing and searching matter.

Stock that must be tracked because running out has consequences.

Variants — sizes, colours, options — which get unmanageable without a proper catalogue.

Shipping that varies by weight, destination or item.

Repeat customers with accounts and order history.

Discounts, bundles or subscriptions.

If several of those apply, use a shop platform and let it handle the parts that change constantly. Custom work here is rarely justified — payments, tax and fraud are solved problems you do not want to own.

The middle answer people miss

Sell online without a shop: a catalogue plus a way to pay.

Show what you have, with prices and good photographs. Let people order by message, phone or a form, and send a payment link. You get discoverability, price transparency and orders, without stock sync, shipping rules or returns automation.

For makers, commission work, food producers with changing availability and anyone selling fewer than about twenty things, this is frequently better than a store — and it converts well, because a short human exchange before payment closes sales that a checkout would lose.

Starting small and growing

The sequence that works:

Start with a payment link. Find out whether anyone buys.

Add a catalogue if enquiries start arriving about specific items.

Add checkout when handling orders by hand becomes the bottleneck.

Add a full shop when the catalogue and stock genuinely need managing.

Most people start at step four, on the assumption that a shop is what a website with sales means. Then they maintain a store for four products, and the maintenance outlasts the enthusiasm.

Building the shop before you know what sells means paying for it twice — once to build, once to keep alive until it is used.

The short version