What a Static Website Can and Can't Do: Shops, Bookings, Logins

Static websites are fast, cheap to host and very hard to hack. So why not use them for everything, including an online shop? Because static sites are built for one kind of job, and a shop is a different kind. This guide draws the line plainly. For the background on how static sites work, read static websites: benefits and weaknesses.

Key takeaways

Static sites are ideal for websites that show: services, people, work, articles, contact details.
Forms, bookings, newsletters, maps, videos and reviews all work on a static site.
Selling a few things works when the checkout runs in an external system you own.
Full online shops need a shop system with a database. Taking payments is only a small part of the job.
The test: does your website mainly show, or mainly do? And where does your revenue happen?

What static websites do very well

A static website is a set of finished pages, delivered exactly as they are stored. Every visitor gets the same page, with no database in between. That is a perfect match for any site whose job is to present something:

Company and service pages: what you offer, who you are, how to reach you.
Team, opening hours and locations, with an embedded map.
References, case studies and portfolios.
Blogs, guides and news, which are read far more often than they change.
Landing pages for campaigns, where every second of load time costs enquiries.
Multilingual pages and legal pages.

The everyday features most businesses need work too, each handled by a small service in the background: contact forms, appointment booking (built in or through a tool, see Calendly alternatives), newsletter signup, embedded maps, videos and reviews, and a few buy buttons that send the customer to an external checkout.

In return you get pages that load almost instantly, nothing on the public server to attack (no plugins, no admin login, no database, see WordPress security flaws), very low hosting costs, and a site that stays up when traffic spikes.

The grey zone: selling a little

Many businesses sell something on the side. A static site handles that as long as another system does the actual selling:

A handful of products or vouchers sold through a payment link (for example Stripe Payment Links), a Shopify Buy Button, an Etsy shop or a voucher service.
Events and workshops with tickets sold through a ticketing tool.
Online courses or a member area, for example lessons behind an access code. The lessons and the access check run on a connected course platform, and your website presents the offer and links to it. The check has to happen on a server. A code that only hides content on a static page keeps out nobody who has the direct link.

The rule: the connected system does the actual work. It takes the payment, sends the receipt, tracks what is left, handles refunds or checks who may open a lesson. Your website shows the offer and links to it. Once you want the website itself to do more of that work, you have left the grey zone.

What static websites are not built for

Some websites don't just show things. They work with data that changes every minute and belongs to individual customers. That is the job of an application with a database.

Full online shops

A real online shop is software that handles far more than people expect:

Products with variants. Ten products in four colours and five sizes are already 200 variants, each with its own stock count.
Stock: what is available, what sits in someone's cart, what to reorder.
Prices and discount codes that change often, and sales with start and end dates.
Cart and checkout, with address checks and a choice of payment methods.
Taxes, shipping zones and rates per country. Outside the EU, customs come on top.
Customer accounts with saved addresses and order history.
Order confirmations, invoices, shipping emails, returns and refunds.
Connections to fulfilment, marketplaces and accounting.

A common idea is: "Payments run through PayPal or Stripe, so the website only has to show the products." That doesn't hold up. Payment is the smallest item on that list. Everything else has to live somewhere, and that somewhere is a shop system with a database. Without one, the work ends up in spreadsheets and inboxes, and the mistakes end up with your customers.

There is a legal side too. Selling to consumers online means showing prices including VAT and shipping costs, clear order steps, an order confirmation, and in the EU a 14-day right of withdrawal that your checkout and emails have to explain. Some countries add their own rules. Germany, for example, requires the final order button to say "order with obligation to pay" or similar. Shop systems are maintained to keep up with these rules. A hand-built checkout on a static site is not.

Other jobs that need an application

The same goes for booking engines with live availability (hotel rooms, rental equipment), customer portals, product configurators that calculate prices, and anything built on user logins and user-generated data, such as forums or job boards. A static site can link to each of these. It should not try to be one.

How to decide: two questions

1. Does your website mainly show, or mainly do? If visitors come to learn about you and then call, write or book, your site shows. If they come to log in, configure, order or manage something, it does.

2. Where does your revenue happen? If customers pay in person, by invoice or through a booking, the website supports the sale and static is a great fit. If most revenue goes through an online checkout, the shop is the business. Keep it on Shopify, Shopware or WooCommerce, and add content or landing pages around it only if they help.

What you need	Static website	Better tool
Services, team, references, blog	Ideal	Not needed
Contact form, booking, newsletter	Works well	Not needed
A few products or vouchers	Works, with an external checkout	Payment link, Buy Button, voucher service
Event tickets	Works, with a ticketing tool	Ticketing platform
Online shop with variants and stock	Not the right tool	Shopify, Shopware, WooCommerce
Member area or online courses	Works, with a connected course platform	Course platform with access codes
Live availability, portals, configurators	Not the right tool	A dedicated application

How ShiftPress handles this

ShiftPress is a web agency that works with people and AI. We build and run websites that show: we take over your site or build a new one, host it as a fast static site and keep it up to date with you, with a person checking before anything goes live. Forms, documents and bookings are part of it (see win customers). To sell a few things, we connect an external checkout that you own and run.

We don't build or run full online shops. If your shop is the business, it belongs in a shop system with people who specialise in it, and we would rather say so up front. What we do offer is on the done-for-you page and in our pricing.

Frequently asked questions

Can I sell products on a static website?

Yes, a few, if the checkout lives somewhere else. A static page can show the product and a buy button that hands off to Stripe Payment Links, a Shopify Buy Button, Etsy or a voucher service. That system takes the payment and handles receipts and refunds. Once you need variants, stock, customer accounts or shipping rules, you need a real shop system.

If payments go through PayPal or Stripe, is that enough to run a shop?

No. Payment is the smallest part of a shop. A shop also manages products and variants, stock, prices and discount codes, taxes and shipping per country, customer accounts, order emails, invoices and returns. That work needs a shop system with a database behind it.

I only sell three products. Is that too much for a static website?

Not necessarily. Three products without variants, at a fixed price and with simple shipping, can work well with payment links. It tips when each product comes in sizes or colours, when you need to track stock, or when customers expect an account and order history. Count your variants, not your products.

Can ShiftPress run my Shopify or WooCommerce shop?

No. We build and run websites that show your business, and we connect simple external checkouts for selling a few things. We do not build or run full online shops. If the shop is your business, keep it on Shopify, Shopware or WooCommerce with people who specialise in it.

Can you build the content pages around my existing shop?

Often, yes. Pages about your company, guides, a blog or campaign landing pages can live on a fast static site and link into your shop for the purchase. Whether that is worth it depends on how your shop and domain are set up, so we look at it with you first.

What happens to my shop if I move my website to ShiftPress?

Nothing changes in your shop. It stays in its own system, with its products, orders and customer accounts. Only the pages around it move. If the shop and the website share one domain today, the shop usually gets its own subdomain starting with shop., and old shop links are redirected so nobody lands on an error page.

The bottom line

Static is the best home for websites that show what a business does, and that covers most of them. Selling a few things fits too, as long as the checkout runs somewhere else. A full online shop is software in its own right: give it a shop system, and let the static site do what it does best.

What a static website does well, and what it can't do