How much to charge for an ecommerce website
How much to charge for an ecommerce website comes down to one question: how much money will move through this store, and what does it cost the owner when something breaks? A five-product store for a side business and a store with hundreds of products, variants and wholesale pricing are not the same job, even if the homepages look alike. Price the build on a share of the value the store handles, add lines for the catalog, payments and integrations, and quote a monthly plan. Do not price on pages or hours.
Claude Code makes the storefront fast to build. You can describe a product page and have it working quickly, and adding Stripe payments with Claude Code shows how quickly checkout comes together. That speed is why the pages are the wrong thing to charge for. The slow, risky parts are the product data, the checkout, the connections to shipping and inventory, and who fixes it when an order does not go through on a sale weekend.
Who buys ecommerce websites, and what they are really paying for
The buyer tells you where the value is. Ask how the business sells today before you talk about design.
Common ecommerce buyers and what the store is worth to them
| Buyer | What they need | What it is really worth |
|---|---|---|
| Business moving off marketplaces or social selling | Their own store and checkout | Sales they keep instead of handing a cut to a platform, and customers they own |
| Brand on a store builder that has outgrown it | Custom features the builder cannot do | Sales lost to the limits of the current setup |
| Local or wholesale business | Online ordering, customer accounts, trade pricing | Orders taken without phone calls and manual invoices |
| Creator or course seller | Selling merch or digital products | Revenue from an audience they already have |
The best client is usually the business that is already selling and hitting a wall. They know their numbers, they feel the cost of the current setup every week, and they can tell you what a better store is worth.
The CCC Store Quote
Six parts of an ecommerce website quote
| Part | What it prices | Question to ask the client |
|---|---|---|
| Base build | The storefront and the job it does for the business | How do you sell today, and what is that costing you? |
| Catalog | Products, variants, categories, product data and images | How many products and variants, and where does that data live now? |
| Payments and checkout | Payment provider, taxes, discounts, shipping rates | How do customers pay, where do you ship and what discounts do you run? |
| Integrations | Shipping, inventory, email marketing, accounting, a CRM | What else needs to know when an order comes in? |
| Launch | Domain, moving old orders and customers, redirects, testing real orders | Is there an existing store, and what has to come over? |
| Keep plan | Monthly monitoring, fixes, updates and small changes | Who do you call when checkout stops working? |
Base build. Start with what the store will handle. Ask what they sell in a typical month today and what the current setup costs them in fees, lost sales or manual work. Price the build at a fraction of one year of that value so the client can see it pay for itself.
Catalog. This is where ecommerce quotes go wrong. A handful of simple products is quick. A large catalog with sizes, colors, bundles and messy data in a spreadsheet is days of cleanup before a single page looks right. Ask to see the product data before you quote, and price the cleanup as its own line.
Payments and checkout. Checkout is the part that has to work every time. Price the payment provider setup, tax handling, discount codes and shipping rules separately. If they sell to other countries, ask now, because currencies, taxes and shipping zones add real work.
Integrations. Each outside system is its own line. An order that has to reach a shipping tool, update inventory, add the customer to an email list and land in accounting is four connections, each with its own way to fail. How much to charge for an API integration covers pricing those one at a time.
Launch. Moving from an old store means customers, past orders, product links and search rankings that point at old URLs. Redirects and a test order on the live store are not optional. Price launch on its own so the client sees it is real work.
Ask these before you quote
- Who owns the accounts? The domain, hosting, payment provider and any store platform should be in the client's name, with you given access. Payouts must go to their account, never yours.
- Custom build or a store platform? If a hosted store platform does what they need, building custom may cost them more to run. Say so. Recommending the cheaper path builds more trust than any portfolio piece.
- Who adds products and runs sales after launch? If it is someone on their team, they need an admin they can use without you, and that is part of the build.
- Is there a launch date, like a holiday sale or a product drop? A fixed date with an unclear catalog is a risk you should price.
- What happens to the old store? If there is one, you need its data, its URLs and a plan for the switch-over day.
More questions that prevent a bad quote are in client discovery questions before you quote.
Always quote the Keep plan
A store is never finished. Payment providers update their APIs, plugins and libraries need updates, a shipping rate changes, and the owner wants a new landing page for every sale. If nobody owns that, checkout breaks quietly and the client finds out from a customer who could not pay.
Quote a monthly plan in the original proposal. Say what it covers: checking checkout and orders work, updates and security fixes, hosting if you manage it, and a set amount of small changes. Say what it does not cover: new features and new integrations, which are quoted separately. How to price a maintenance retainer covers the structure.
How to present the ecommerce quote
- Lead with the outcome in their words. One line on what the store does for the business, then the price.
- Itemize it. Base build, catalog, payments and checkout, integrations, launch, then the Keep plan. Itemized quotes get trimmed, not rejected.
- Gate payments on proof. A deposit to start, a payment when a full test order goes through on a staging store, and the final payment once the live store takes a real order. How to structure milestone payments for an AI project covers the schedule.
- Write the scope down. The product count, the payment methods, the integrations and who owns what. How to write a statement of work for an AI project has the template.
And skip hourly. Claude Code makes the build fast, so hourly pricing turns that speed into a pay cut. I covered why in why I stopped charging hourly for AI builds. If the client also wants a sales dashboard or a CRM connected to the store, how much to charge for a dashboard and how much to charge for a CRM cover those lines.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for an ecommerce website?
Price it on the sales the store will handle and the manual work it removes. Charge a fraction of one year of that value for the build, add lines for the catalog, payments, integrations and launch, and quote a monthly plan.
Should I charge more for a large product catalog?
Yes. Product count, variants and the state of the product data drive a lot of the work. Ask to see the data before you quote and price the catalog and any cleanup as their own line.
Should I charge a monthly fee for an ecommerce website?
Yes. Stores need checkout monitoring, updates, security fixes and small changes for sales and new products. A monthly plan covers that work so the store keeps taking orders.
Should I build a custom store or use a store platform?
Use whatever is cheapest to run for what the client actually needs. If a hosted platform covers it, say so. Build custom when they need something the platform cannot do, and price that difference.
Should I charge hourly for an ecommerce website?
No. Claude Code makes the build fast, so hourly pricing punishes you for that speed. Price on the value of what the store handles, with each part itemized.
Last reviewed by Duncan Rogoff on October 16, 2026
