# Can an online shop be a static website?

URL: https://ergostrat.com/en/website-build/static-online-shop.html
Language: [Български](https://ergostrat.com/website-build/static-online-shop.html) · [English](https://ergostrat.com/en/website-build/static-online-shop.html) · [Français](https://ergostrat.com/fr/website-build/static-online-shop.html) · [Deutsch](https://ergostrat.com/de/website-build/static-online-shop.html)

Yes. The pages can be static while a separate service handles the cart, checkout and orders. That means the shop still depends on working software, accounts and connections. Choose the arrangement from the way you manage products and fulfil orders, rather than from a promise of “no moving parts”.

## What are the ways to add commerce?

An embedded store is one option. Ecwid documents adding a store, categories or product buttons to an existing website. The catalogue and selling tools belong to the connected service; the page containing the embed is not the whole operating shop.

Another option is to connect a cart to your own page layout, as with Snipcart. The storefront and commerce functions can be separate, but someone must own the integration. These are examples of approaches, not the only tools or architectures available.

Write down where products, prices, stock, orders and customer information are managed. Include who can change them and what happens when a connection fails. A static page does not remove those responsibilities or establish that updates can never break a checkout.

## Where do hosted payment links fit?

Stripe Payment Links offers a hosted payment route and an embeddable buy button. It is another option to evaluate; do not treat a payment link and an entire shop as the same deliverable.

Check the actual buying journey: selecting products and quantities, reaching payment, receiving confirmation, recording the order and handing it to fulfilment. Ask what provides each step. If the chosen integration needs additional development, include it in the proposal rather than assuming a button settles the whole process.

“Static” describes the pages, not every system involved in a transaction. Hosted checkout, inventory and order handling still run somewhere. A useful comparison identifies those dependencies and the person responsible for keeping the connection working.

## Who will manage the catalogue?

Start with the person doing the work. How often do products and stock change? Are there variants, price lists, delivery rules or connections to another system? Ask that person to demonstrate an ordinary update during acceptance, using the tools they will actually keep.

Our website-build scope suits a few to a few hundred products with a clear catalogue and one decision-maker. We do not build systems for thousands of items. That is our service boundary, not a universal technical limit of static storefronts: Snipcart, for example, advertises unlimited products.

- Record the catalogue, variants and update frequency before choosing an approach.
- Specify the source of stock and the route from paid order to fulfilment.
- Keep service and payment accounts in the agreed ownership arrangement.
- Test a normal order, an unsuccessful payment and the agreed cancellation or recovery path.
- Name the owner of maintenance, monitoring and any changes to connected services.

Do not equate static pages with the absence of passwords or maintenance. The editing workflow and commerce providers can still have accounts, permissions and updates. Agree the actual work and support scope rather than relying on the architecture’s label.

## Questions

### Will you build a shop for a small catalogue?

That fits our service scope: a few to a few hundred products, provided the catalogue and operating needs are clear. Confirm the particular requirements before the build. Product count is one input, not proof that every integration is included.

### What if the catalogue grows into the thousands?

Tell us about that plan before the approach is chosen. It is outside our stated website-build scope. Assess the catalogue workflow and commerce system needed for that scale; do not infer that static pages themselves impose the same limit on every implementation.

### What does the cart charge on each order?

Snipcart publishes a 2% charge plus payment-gateway fees, with a minimum monthly fee replacing the percentage for lower monthly sales. Billing is in USD; check current terms and currency exposure. Add service, processor and operating costs when comparing the full arrangement.

## Sources

- [Ecwid: adding a store to an existing website](https://support.ecwid.com/hc/en-us/articles/115004678945-Ecwid-for-any-website)
- [Snipcart: pricing, minimum and included products](https://snipcart.com/pricing)
- [Stripe: Payment Links](https://docs.stripe.com/payment-links)

## Related reading

- [How much does a website cost?](https://ergostrat.com/en/website-build/website-cost.html)
- [Do you need an accessibility statement?](https://ergostrat.com/en/website-build/accessibility-statement.html)

## Tell us your product count before we choose the approach

A website build can include a cart for a catalogue of up to a few hundred products; the specific integration and its price are in the proposal. Write to us with how many products you have and how you update stock.

[Ask about a new website](mailto:contact@ergostrat.com?subject=Website%20build%20question%20after%20Static%20Online%20Shop%20article)