How much does a custom ecommerce website cost?

The catalog, B2B features, integrations and any migration from an existing platform account for most of it. Once discovery has mapped those, you get one fixed figure. If a hosted platform would serve you better, that is what we will recommend.

Should we build a custom store or stay on Shopify?

Stay if the platform does what you need with a few apps. Build when the platform is what limits you: pricing it cannot express, B2B workflows, or an ERP it cannot sync with properly. A headless setup on top of a platform is sometimes the middle ground, and discovery is where that gets decided.

Can you connect the store to our ERP, inventory and CRM?

Yes. Orders, stock and customers move between the store and those systems automatically, so nothing is re-keyed. The connection method depends on what each system exposes, which we establish in discovery.

Will we lose search rankings when we replatform?

Not if the move is planned. We map every old URL to its new one, keep structured data and page content in place, and check the redirects before launch. A short dip while search engines recrawl is common; a lasting loss usually means redirects were skipped.

What is headless commerce, and do we need it?

Headless means the storefront is a separate application that talks to the commerce engine through an API. It gives full control over design and speed, and it adds a system to maintain. It is worth it when the storefront has to do things a theme cannot.

How long does a custom ecommerce build take?

Count on one to three weeks of discovery. The first production release usually follows eight to sixteen weeks after that; the size of the catalog, the integrations and any data coming from another platform decide where in that window it lands.

Which payment providers can you integrate?

Any provider with a documented API. We use Stripe most where it serves the market, and connect regional providers when the countries you sell in call for them.

Who maintains the store after launch?

We can, on a monthly agreement you can end with 30 days’ notice. The code and accounts are yours, and the runbook is written so your team or another one can take over.

Build · E-commerce

Custom ecommerce website development, from storefront to ERP

We design and build the storefront, the checkout and the systems behind them, connected to your payments, inventory, ERP and CRM so that orders never have to be re-entered by hand.

Get a written scope See how we work

A written scope and a fixed budget before any work is billed.

When a custom store is the right call, and when it is not

A hosted platform such as Shopify is the right answer for many stores, and we will say so when it is. A custom build earns its cost when the platform is what limits you: pricing rules it cannot express, B2B accounts and quotes, a catalog that does not fit its product model, or an operation that runs on an ERP the platform cannot talk to properly.

We build the store around how your customers buy and how your warehouse ships. The storefront and the checkout are designed together with the order handling behind them, and the connections to payments, inventory and your ERP are part of the first scope.

Speed and search are planned before the first commit. Every build has a Core Web Vitals budget, and a store that moves from another platform keeps its URLs, its redirects and its structured data, so rankings carry over. For connections that reach beyond the store, see API and ERP integration.

Why people get in touch

Sound familiar?

Orders are typed into the ERP by hand

The store and the ERP do not sync, so someone re-keys every order and stock levels are only right on the morning after.

The platform cannot express how you sell

Customer-specific prices, B2B quotes, bundles or approval steps need a pile of plugins, and each update breaks one of them.

The store is slow on the phones your customers use

The theme and its apps load more script than content, and the checkout loses people on a mid-range phone over a weak connection.

Moving platforms feels riskier than staying

Years of URLs and rankings, customer accounts and order history make a replatform look like a bet on the whole business.

One store, end to end

The storefront customers see and the systems that turn a click into a shipped order.

Storefront and product design

Catalog, product pages and a checkout shaped around how your customers buy, validated as a prototype before it is built.

Catalog
Product pages
Checkout

Commerce engineering

Cart, payments and order handling built to your rules: customer pricing, B2B accounts, bundles and approvals.

Cart
Payments
Orders

Integrations

Payments, inventory, ERP and CRM connected to the store, so an order moves through the business without anyone re-keying it.

ERP
Inventory
CRM

Performance and search

Core Web Vitals budgets and technical SEO planned before the first commit, including redirects and structured data for a store that is moving.

Core Web Vitals
Technical SEO

Built to be owned

What you keep at the end

Everything below is yours from the first commit, under your own accounts wherever possible. Nothing in it is licensed from us, and nothing can only be maintained by us.

tree

your-company/

docs/requirements.mdThe written scope and the fixed budget for the store.
storefront/The store, its checkout and its admin screens.
integrations/The payment, inventory and ERP connections, with their logs.
seo/redirects.csvEvery old URL mapped to its new one, for a store moving platforms.
docs/runbook.mdDeploys, rollbacks and what to do when a sync fails.

How the work runs

Four stages, and what
each one hands you

Every stage ends in something you can review and keep, including the stages that come before any code is written.

scope

Discovery and requirements analysis

We map the real problem before any code is written: stakeholders, constraints, existing systems, and what success means in measurable terms.

requirements.md
scope + fixed budget
risk register

design

Design and architecture

Interface flows and system architecture designed together, so what we specify is what we can build and scale.

clickable prototype
system diagram
data model

build

Build, with a weekly demo

Short delivery cycles with visible progress. You review working software throughout, not a finished system revealed on launch day.

staging deploy / cycle
test suite + CI
weekly demo

operate

Launch, then operations

We deploy the system, monitor it, and hand over the runbook. We then continue to operate it under a monthly agreement you can end with 30 days’ notice.

production infra
runbook + handover docs
monitoring + alerts

Terms

Terms we put in writing
before work begins

The figures we commit to on every engagement. Your project gets its own dated plan on top of them.

Week

048121620

Inquiry: 1 business dayA reply from someone who has read the brief.
Discovery: 1 to 3 weeksEnds in a written scope and a fixed budget.
Weekly review: Every weekThe work as it stands, on a link you can open yourself.
First release: 8 to 16 weeksTypical time from the end of discovery to production.
Operations: 30 days’ noticeMonitoring and iteration under a monthly agreement.

Illustrative. Every project receives its own dated plan before work begins.

Pricing

What a custom ecommerce website costs

A custom store gets the same treatment as any build here: discovery ends in a written scope, and that scope has one price. If a hosted platform would serve you better for less, that is where you will hear it.

01The catalog: how many products, variants and pricing rules it carries
02B2B needs such as customer accounts, quotes and approvals
03How many systems the store connects to, and how open their APIs are
04Migration from an existing platform: products, customers, orders and URLs
05Payment providers and the countries you sell in
06Who runs the store after launch

Stack

What we build it with

Tools with long support horizons and large talent pools, so the system stays maintainable by any capable team, not only ours.

Next.js

Server-rendered storefront pages that load fast and are easy for search engines to read.

Stripe

Card payments and subscriptions where the market suits it; other providers connect through their APIs.

PostgreSQL

Orders, customers and inventory in one database you own.

Vercel

Every change on its own preview link, reviewed before it reaches the live store.

Questions buyers ask us

The ones that come up most in first conversations about this service.

Something not covered here?
Email us at hello@kodfabrika.com.

Ask a question

Services

Related services

All services

Existing systemsAPI and ERP integrationConnect new software to your CRM, ERP, payments and internal tools.DesignUI/UX designUser journeys, a clickable prototype and user testing, before any code is written.Existing systemsLegacy modernizationMove the system that holds you back to a current stack, without stopping operations.

Built to last.
Started this week.

Tell us what you’re building. You’ll receive a written scope, a defined budget, and a delivery plan. Not a proposal deck.

Get a written scope hello@kodfabrika.com