Ecommerce Website Development Cost: What Moves the Quote

Ecommerce Website Development Cost: What Moves the Quote

You have asked three agencies to quote an online store and the numbers are far enough apart that at least one of them must be answering a different question. Usually all three are. “An ecommerce website” can mean a fifty-product shop with a hosted checkout or a wholesale platform with contract pricing and a live warehouse feed, and quotes rarely say which one they assumed. This article explains what actually moves the number, so you can read any quote you receive and ask the questions the quote skipped.

The six things that move an ecommerce quote

Catalog size and variants come first, but not in the way people expect. Two hundred simple products cost less to set up than forty products that each come in six sizes, eight colors and three materials, with separate stock and images per combination. Variant logic, bundles, configurable products and per-variant pricing are where product data becomes engineering.

Payments and tax are second. A single card processor with one currency is standard. Adding wallets, buy-now-pay-later, B2B invoicing with net terms, multiple currencies, or sales tax across many US states with different rules for shipping and digital goods each adds setup, testing and ongoing maintenance. Shipping rules are third: flat rate is simple, while live carrier rates, free-shipping thresholds by region, oversized items, split shipments and local pickup are each a rule someone has to build and test.

Integrations are fourth and usually the largest single driver. Accounting, ERP, warehouse or 3PL, email marketing, a CRM, a product information system and a marketplace feed are each a connection with its own failure modes. Content is fifth: product descriptions, category copy, size guides and photography do not write themselves. Compliance is sixth: accessibility, privacy and cookie consent, and the age or prescription checks some categories require.

Three store sizes, described by scope

A starter store has up to a few hundred simple products, one payment processor, flat or weight-based shipping, one integration (usually accounting or email) and content you supply. It launches in weeks and its main risk is thin content, not the code.

A growth store carries thousands of products or complex variants, several payment methods, live shipping rates, tax automation, two to four integrations, customer accounts with order history and a content plan that includes product photography. This is the most common project we are asked about and it runs a few months.

A platform store adds business-to-business pricing, an ERP as the source of truth, multiple warehouses or storefronts, marketplace or multi-vendor logic and custom checkout flows. It is a multi-phase engagement and the correct move is almost never to build everything at once. Our decision guide on Shopify versus a custom store covers when a hosted platform, a custom build or a hybrid fits each of these sizes.

What a serious quote contains

It lists the catalog assumptions: how many products, how many variants, who enters the data and in what format. It names the payment methods, the tax approach and the shipping rules it covers. It lists every integration by name and states what data flows in which direction and how often. It says who writes the product copy and who shoots the photos. It states what is out of scope, which is the single best predictor of whether you will receive surprise invoices.

It also covers the period after launch: hosting, monitoring, platform and plugin updates, security patches, and a response time when checkout stops working. And it separates one-time work from recurring costs, so you can see the three-year picture rather than just the launch number. A quote that arrives without a single question about your catalog, your warehouse or your accountant is a guess with a decimal point.

What is missing from a cheap quote

Almost always the same three things. Maintenance is the first: the store is delivered, the invoice is paid, and six months later a platform update breaks the checkout with nobody on call. Ask who fixes it, how fast, and what that costs per month. A store with no maintenance plan is not finished, it is abandoned at launch.

Content is the second. The quote assumes you will supply descriptions for every product, and you will not, because nobody has time to write four hundred of them. Thin or copied descriptions are the most common reason a technically sound store does not sell or rank. Photography is the third. A store launched with supplier images looks like every other store selling the same supplier's products. We cover what a listing actually needs in How Many Product Images a Listing Needs.

There is a fourth, quieter omission: data migration. If you have an existing store, moving products, customers, orders and URLs is a project in itself, with a rehearsal run, a comparison of counts and a redirect map for every old address. A quote that does not mention redirects has not thought about your search rankings, and those rankings are often the most valuable thing the old store owns.

How to compare two bids

Put both quotes in one spreadsheet with a row per item: catalog setup, variants, payments, tax, shipping rules, each integration, content, photography, migration, testing, training, hosting, maintenance. Mark each row included, excluded or unclear. The bid with the most unclear rows is the one that will grow after signing.

Then compare the questions each vendor asked before quoting. The vendor who asked about your ERP, your return rate and who owns product data will usually deliver closer to the quote, because they priced the real project. Finally, ask both for the same reference: a store they built that is still running two years later, and who maintains it. Longevity says more than a launch screenshot.

Where to find actual figures

We do not put amounts in articles because a number without the scope behind it misleads more than it helps. The e-commerce development page publishes our indicative ranges per store size, what moves each one, and what every package includes. If your project is a growth or platform store, the safest first step is a short paid discovery sprint that produces a written scope you can take to any vendor. Tell us what you sell and how it reaches customers, and we will tell you which size you are looking at.

Frequently asked questions

How much does it cost to build an ecommerce website?

It depends on catalog complexity, payment and tax setup, shipping rules, integrations, content and compliance, not on the number of pages. A simple store with supplied content is a project of weeks; a store with complex variants, live shipping, tax automation and several integrations runs months. Our indicative ranges by store size are published on the service page.

Why is my quote so much higher than a Shopify subscription?

Because the subscription covers the platform, not the store. Product setup, variant logic, theme customization, integrations, content, photography, migration and testing are work on top of any platform. A subscription plus apps is the recurring cost; the quote is the one-time work of building a store that fits your business.

What ongoing costs should we expect after launch?

Hosting or platform subscription, app or plugin fees, payment processing, tax automation if you use it, and maintenance: updates, security patches, monitoring and small changes. Plan for content and photography as recurring work too, because a catalog that never changes stops ranking and stops converting.

Should product photography be part of the ecommerce quote?

Yes, or at least a line that says who is responsible for it. Supplier images make your store indistinguishable from competitors selling the same products. Whether the shoot is done in our studio in Serbia, by a local photographer working to our brief, or through remote art direction and retouching, it should be planned with the store, not after it.

How long does ecommerce website development take?

A starter store with supplied content typically launches in a few weeks. A growth store with complex variants, several integrations and a content plan takes a few months. Platform stores with B2B pricing and ERP integration are phased over quarters. Data preparation and content are the usual bottleneck, not the development itself.

Have a question or a project in mind? The first call is free: tell us what you are building and we will tell you honestly what it takes.

Book a free call
All articles