Skip to content
Cost Guide

How Much Does It Cost to Build an E-Commerce Web App?

A custom e-commerce web app — product catalog, cart, checkout, order management — runs €5,500–20,000 with a solo developer. Agencies quote €35,000–100,000. Shopify covers simple storefronts; custom builds make sense when you need non-standard logic.

Last updated: April 2026

Cost comparison
Agency

€35k€100k

EUR typical range

Timeline: 1231 weeks

Senior Freelancer

€10k€36k

EUR typical range

Timeline: 820 weeks

Senior quality · Balkans ratesDusko Licanin

€6k€20k

EUR typical range

Timeline: 614 weeks

What's included in base scope
  • 01Product catalog with categories, variants, and images
  • 02Shopping cart and checkout with Stripe or payment gateway
  • 03Order confirmation emails and basic order history
  • 04Admin panel for product and order management
  • 05Responsive storefront deployable to Vercel
What drives the cost
  • Catalog complexity — variants, bundles, digital goods, and subscription products each add scope
  • Checkout customisation — multi-step forms, shipping calculators, and tax logic vary significantly by region
  • Inventory management — real-time stock tracking across multiple warehouses or channels
  • Order operations — fulfillment workflows, returns, and partial refunds are often underestimated
What's not in base scope
  • ERP or warehouse management system integration
  • Multi-currency and multi-language storefronts
  • Affiliate or referral program
  • Mobile app (iOS/Android)
In detail

What actually moves the price inside the €5,500–20,000 range

The gap between €5,500 and €20,000 is mostly checkout and catalog logic, not page count. A flat catalog with simple products, one currency, and standard Stripe Checkout sits near the floor. The price climbs when products carry variants, bundles, or subscription billing, and when checkout has to calculate region-specific tax and shipping at run time.

The quietest cost driver is order operations — the admin side buyers rarely demo before signing off. Returns, partial refunds, fulfillment status, and stock decrements on sale are real workflows with edge cases, and they account for a large slice of the upper range. A rough split:

  • Storefront + cart + Stripe Checkout — entry-level scope, near the low end
  • Variants, bundles, or subscriptions — each is a distinct chunk of work
  • Tax/shipping rules + multi-warehouse stock — pushes toward the high end
  • Returns, partial refunds, fulfillment states — the part most quotes underestimate

Scoping to the low end vs what pushes it high

To land near €5,500–8,000, keep the first build narrow: one currency, one region's tax rule, standard variants, Stripe Checkout instead of a custom multi-step form, and a lean admin that covers products plus order status. Ship that, sell through it, then add scope against real data.

What pushes a build toward €20,000 is usually decided before any code is written: subscription or custom-pricing logic, multi-warehouse inventory, heavy returns/refunds workflows, and a checkout that reconfigures by region. None of those are wrong to want — they just belong in a later phase once the core store is earning.

The single biggest saving is honest scope. A pizza-ordering flow I built for Pizzeria Bestek (React + Supabase) stayed cheap precisely because the ordering logic was custom but tightly bounded — no speculative features carried into v1. If a feature isn't tied to a real order or a real customer request, it's a phase-two line item, not a launch blocker.

Costs buyers forget

The build quote isn't the whole bill. Recurring costs that don't appear in a fixed price:

  • Payment fees — Stripe takes roughly 1.5–3.4% + a fixed fee per transaction. On real volume this dwarfs hosting.
  • Hosting — a storefront on Vercel is low-cost or free at small scale, but a managed database, email sending, and image/CDN bandwidth add monthly cost as traffic grows.
  • Third-party / SaaS fees — transactional email, tax calculation, search, and analytics are usually per-seat or usage-priced subscriptions.
  • App-store cut — only relevant if you later add a native iOS/Android app (excluded here). Apple and Google take 15–30% of in-app purchases; web checkout avoids that entirely, which is one reason a web app is the cheaper starting point.
  • Maintenance — dependency updates, payment-API changes, and bug fixes are ongoing. Budget for it as a small monthly retainer or a block of hours, not a one-time line.

Fixed-scope vs hourly, and a realistic timeline

For a first e-commerce build, fixed-scope is the right structure. The feature set is knowable up front — catalog, cart, Stripe checkout, admin — so the risk of an open-ended hourly meter falls on no one. You know the number before work starts. Hourly fits better after launch, for iterative changes where the next feature depends on what real customers do.

Realistic timeline is 6–14 weeks. A focused storefront with standard checkout lands around the low end; subscriptions, multi-warehouse stock, and region-specific tax/checkout push toward 14. Working solo is leaner than an agency on a build this size — no hand-offs between separate design, frontend, and backend teams, and one person holding the full picture.

Proof that this scope ships solo: BookBed, a booking SaaS I built on Flutter + Firebase + Stripe with bidirectional iCal sync, and Callidus, a clinic SaaS on React + Firebase — both Stripe-backed products with the same catalog-checkout-admin shape an e-commerce app needs. Per the build note, if your needs are under ~500 SKUs with standard checkout, a well-configured Shopify often beats a custom build; the custom path pays off when the logic is non-standard, and that's exactly what I scope precisely.

Related
Common questions

How much does it cost to build a E-Commerce Web App?

A E-Commerce Web App costs €6k€20k with a senior solo developer. Agencies typically quote €35k€100k for equivalent scope. The gap is overhead, not quality.

How long does it take to build a E-Commerce Web App?

A E-Commerce Web App takes 614 weeks with a senior solo developer using AI-augmented workflows. Agency timelines run longer due to discovery phases, hand-offs, and approval gates.

What is included in a E-Commerce Web App build?

  • Product catalog with categories, variants, and images
  • Shopping cart and checkout with Stripe or payment gateway
  • Order confirmation emails and basic order history
  • Admin panel for product and order management

What factors drive E-Commerce Web App development cost?

  • 01Catalog complexity — variants, bundles, digital goods, and subscription products each add scope
  • 02Checkout customisation — multi-step forms, shipping calculators, and tax logic vary significantly by region
  • 03Inventory management — real-time stock tracking across multiple warehouses or channels
Working with Dusko

For most e-commerce needs under 500 SKUs with standard checkout, a well-configured Shopify is a better investment than a custom build. When you have non-standard logic — custom pricing rules, subscription models, embedded ordering — that's where a custom build pays off and I can scope it precisely.