An ecommerce storefront served from the edge

A conventional shop builds every page on demand. Someone arrives, the application boots, queries the database for the product, the price, the stock and the reviews, renders HTML, and sends it. Do that a thousand times a minute and the database becomes the ceiling on your business.

Almost none of that work produces a different answer per visitor. The product name, the description, the images and the category are identical for everyone. Rebuilding them per person is effort spent arriving back where you started.

Publish once, serve from the edge

Qwikr publishes your storefront as static files to a CDN. A visitor in Manchester is served from a node near Manchester with no application and no database in the path. There is no origin to overwhelm, because there is no origin doing work.

The parts that genuinely differ per visitor — cart, live stock, checkout — are fetched by the page rather than blocking it. The shop appears immediately and the live data arrives a moment later, which is the reverse of the usual arrangement where nothing appears until everything is ready.

The purge is the part everyone forgets

Uploading a changed file to a CDN’s storage updates the origin, not the edge. Without an explicit purge, the cached copy keeps being served — for up to thirty days. A stock change that never reaches the edge is a shop confidently selling things it does not have, and it is the single most common way a static storefront embarrasses its owner.

So the purge is part of publishing rather than a step someone has to remember.

Honest about the trade-offs

Static is not free of cost, and anyone who says otherwise has not run one. Publishing takes time, so a catalogue change is not instantaneous the way a database-backed page is. Anything genuinely personalised has to be fetched client-side, which is more moving parts. And preview matters more, because publishing is a deliberate act rather than a side effect of saving.

What you get in return is a shop that does not get slower as it gets busier.

You may not want one at all

A good number of merchants arrive already running Shopify or WooCommerce with no intention of moving. For them, generating a storefront is not a feature — it is publishing a shop nobody will visit.

So it is switchable. Nominate Shopify or WooCommerce as your primary storefront and Qwikr stops publishing one, while marketplace sync, stock and operations carry on unchanged. That is usually the reason those merchants are here.