How long does it take to build an online shop?

"How long will it take?" is usually the second question after "how much will it cost?" It's a reasonable thing to want to know - but the honest answer is that it depends heavily on factors the client controls, not just the designer.

This guide gives you realistic timelines, explains what the stages of a build actually are, and identifies the things that cause projects to run long - most of which can be anticipated and avoided.

Realistic timelines

Here's what to expect from different types of build:

These are working timelines from brief to live launch - assuming content arrives on time. Add 2-4 weeks to any of these if product photography or copywriting still needs to be done when the build starts.

What actually happens during a build

Understanding the stages helps you understand what's happening when - and what you need to be doing at each point.

Discovery and brief (1-2 weeks) - The designer asks questions. You supply answers. What products are you selling? What do you need the checkout to do? Are there delivery rules? What existing branding assets do you have? This stage is often underestimated in how much it shapes everything that follows.

Design (2-4 weeks) - Visual design work: how the shop looks. Homepage, product listing pages, product detail pages, basket and checkout. You'll see designs for approval before any coding starts. Revisions at this stage are easy. Revisions after coding has started are expensive.

Build (2-5 weeks) - The design is coded up. The shop platform is configured. The admin panel is set up. Product import structures are established. Payment gateway integration is tested. This is the part that's largely invisible to the client - the work is happening in the background.

Content population (1-3 weeks) - Products, descriptions, images, and prices are added to the shop. This is often done partly by the designer and partly by the client. How long it takes depends entirely on how many products there are and how well-prepared the content is.

Testing and launch (1 week) - Test purchases, browser testing, mobile checks, link checking, payment gateway live testing. Then launch.

What actually delays projects

In 29 years of building shops, the most common causes of projects running over time are:

Content not being ready. The single biggest cause of delay. A designer can build the shell of a shop in a few weeks. They can't populate it with products that don't exist yet, write descriptions that haven't been written, or use photography that hasn't been taken. If your product images and copy aren't ready when the build starts, the project will wait for them.

Slow feedback on designs. Design approval typically has a window - the designer needs a response within a certain number of working days to keep the project on schedule. A client who takes three weeks to respond to a design review moves themselves back in the queue.

Scope changes mid-build. "Can we also add a gift wrapping option?" is a reasonable request - but adding it after the checkout has already been built means rebuilding part of the checkout. Changes of scope during a build are one of the most reliable ways to extend a timeline and increase a cost.

Third-party delays. Payment gateway applications, courier API access, and domain transfers all involve third parties who have their own timelines. Stripe approval is usually fast. Some courier integrations take longer. These are worth starting early.

What the client needs to do

A build project is a collaboration. The client's responsibilities typically include:

• Supplying brand assets: logo files, colour references, font preferences
• Providing product content: names, descriptions, prices, variants, images
• Reviewing and approving designs within agreed timeframes
• Setting up or providing access to payment gateway accounts (Stripe, PayPal)
• Providing any copy needed for non-product pages: about, delivery, returns
• Making launch decisions: go-live date, announcement plans

None of this is particularly onerous - but it does require active engagement from the client throughout. Projects stall when clients disappear for two weeks in the middle of a build.

Platform vs bespoke: the time trade-off

A platform-based shop can be live faster. This is a genuine advantage of Shopify and WooCommerce for businesses that need to launch quickly - testing a product idea, responding to a seasonal opportunity, or simply not having the time for a longer project right now.

The trade-off is that "live faster" doesn't mean "better sooner." A shop built on a template in two weeks will look and behave like a shop built on a template in two weeks. The speed comes from not doing custom design work - which means accepting the design limitations of whatever template you chose.

A bespoke build takes longer because more work is being done. The result is a shop that's actually designed for your business rather than adapted from someone else's starting point.

Planning around a launch date

If you have a specific launch date in mind - a product launch, a trade show, a seasonal peak - tell your designer at the briefing stage, not two weeks before you want to go live. A realistic build requires realistic lead time.

Working backwards from a fixed launch date: allow 8-10 weeks for a standard bespoke build, and add time if your content isn't ready when you start. A designer who can see a fixed deadline early can plan their workload around it. One told at the last minute can't.