Static export instead of a webshop: when the shop is physical, the cart is the problem
A boutique with a physical store doesn't need a webshop — it needs a conversion path into the store. We dropped cart, checkout and inventory sync — and shipped a faster, cheaper, more robust product.
A second-hand fashion shop in Odžaci. Premium selection, curated vintage pieces, loyal regulars, a physical storefront. The brief: "We need a webshop."
We said no. Or rather, not yet.
What the client actually needed
Pushing deeper into the conversation, what she actually wanted was visibility. Customers find the shop through Instagram, then scroll the posts, then call or drop in. The problem wasn't "we sell too little online." The problem was "new visitors don't find us."
A webshop doesn't solve that. Webshops aren't for discovery, they're for transaction. Discovery comes through SEO, social, referrals. And a typical headless-commerce stack costs:
- Shopify plan: ~€30/month
- Custom theme maintenance or agency lock-in
- Inventory sync between backend, POS and online — for one-off vintage pieces, essentially unsolvable
- Tax complexity (shipping, returns, EU-OSS)
- Onboarding friction: training the owner
For a second-hand boutique selling unique pieces, that's negative value.
What we built instead
Case 07 — a brand site, not a shop:
- Next.js +
next export→ 100 % static HTML tree - Framer Motion for microinteractions that carry the premium-selection feel
- 6 category cards with curated highlights — no inventory sync
- Contact form + phone buttons as the primary CTA
- Address + map + opening hours front and center
Delivery: nginx serves straight from the /out tree. No Node runtime in production. Hosting cost effectively zero (server slot on the existing client infrastructure).
What we won
- Sub-second first paint on rural-network mobile in Vojvodina.
- Zero maintenance. No plugin updates, no theme migration, no PCI compliance.
- Content edits take minutes: category text → markdown file →
next export→ done. - SEO score stable-high — no hydration overhead, no JS render block.
- Phone-CTA conversion clearly measurable — visitors call directly, call-to-visit rate is visible.
When the webshop is still right
This decision is context-dependent, not a dogma:
- Inventory > 500 SKUs with replenishment → webshop makes sense, inventory sync scales.
- Standard ship-able stock → webshop makes sense, the cart pays off via cross-sell.
- Discovery comes via paid ads → webshop makes sense, the cart is the conversion endpoint.
For our client: none of these. Discovery through local social, inventory unique-piece driven, shipping not the core business. The webshop would have been a cost line with no counter-value.
The meta-lesson
Before every SMB project ask: where does revenue happen today? If the answer is "at the door," build a door-opening site, not a cart.
Webshops are expensive because they solve many problems. If you don't have those problems, you pay the price without the counter-value.