How long does a Shopify store rebuild take?

Timeline quotes for the same store range from two weeks to six months, which tells you the quote reflects the vendor’s process more than the work. Here are the real bands and what moves a project inside them.

The honest bands

A landing page: about a week. One template, one purpose, tracking included. If a vendor quotes a month for a landing page, you’re paying for their queue, not the work.

A facelift: quoted with the scope, usually shorter than a build. Custom cards, homepage merchandising, reviews surfaced, speed work. It ships fast because nothing replatforms: every change stages on a copy of the live theme, and the store keeps selling through the whole project.

A small-catalog custom rebuild: two to four weeks. Theme, catalog architecture, page templates, imagery, tracking. That’s the window I publish for a small catalog on my Shopify storefronts page. Most of my builds launch in two to three weeks, and four is the honest ceiling for a small catalog with imagery gaps. The dated example is Emma Grace Home: a custom build of 150-plus products, imagery included, that opened in April 2026 less than a month after kickoff.

A large catalog or a platform migration: longer, and priced differently. Thousands of SKUs with real specification data, a redirect map protecting existing rankings, or part-number and fitment search. That work runs up to $20,000, with bigger migrations quoted after the audit, and it doesn’t compress into a month. Any vendor who says it does hasn’t done one.

The agency version: longer, for structural reasons. An agency timeline carries coordination: a project manager, a designer, a developer, and QA passing the work between them, with meetings at each handoff.

Project	Typical window	What sets it
Landing page	About a week	One template, tracking included
Facelift	Quoted with the scope, usually shorter than a build	Staged on a copy of the live theme
Custom build, most stores	2 to 3 weeks	One person holds theme, catalog, imagery and tracking
Custom build, small catalog with imagery gaps	Up to 4 weeks	Imagery production
Large catalog or platform migration, Plus included	Quoted after the audit	SKU count, redirect map, apps and integrations

Where the calendar goes

On a multi-person build, most of the calendar is waiting. Imagery is a scheduling problem before it’s a production problem: product ships out to be shot, comes back, and the edited files have to arrive before anyone can build the collection pages that display them. Design waits on imagery. Development waits on design. Coordination waits on everyone and reports on the waiting. Very little of that timeline is work. Most of it’s queue.

When one person holds the theme, the catalog structure, the imagery, and the tracking, those workstreams run in parallel instead of in sequence. That’s where the two to three weeks comes from. The work stops waiting on handoffs.

A cutover week, start to finish

On a site migration I ran, I rebuilt the site and moved its ad account onto it in the same week. It wasn’t a Shopify store, but the shape of the calendar is the same one I use on Shopify.

Before anything was built, I inventoried 533 legacy URLs, 348 of them blog posts. After cutover I sampled 40 redirect rules against the live domain, and 40 of 40 were correct. Rollback stayed one record change away the whole time. The site and ads cutover case study has the full record.

The inventory is why the cutover fit in a week. The URLs were mapped before the build started, so launch week was checking, not discovering.

What the timeline should include

A build isn’t done when it looks done. The closing stretch of a real timeline holds the work that invisible-until-launch projects skip: conversion tracking wired into the new templates and validated end to end, redirects mapped, page speed measured on a phone over cellular, and a staged launch where the old store keeps selling until the moment of cutover.

A quote that beats these windows by skipping those is quoting a different, worse project. The tracking rebuild alone is a $2,500 engagement when bought on its own, which is a useful way to price the omission.

What stretches a timeline

Four things, in order of how often I see them.

Catalog size. 700 products is a different project than 70. Collection architecture, filtering, and variant handling all scale with the count.

Imagery gaps. If half the SKUs have one bare supplier photo, producing catalog imagery becomes its own workstream. It’s why I run an in-house render pipeline, so imagery doesn’t sit in a queue waiting on studio bookings.

Approval lag. The single biggest variable nobody quotes. A founder who reviews in a day keeps a build on pace. A committee that reviews in two weeks can double the calendar by itself, and no vendor can absorb that from their side.

App surgery. Subscriptions, bundles, B2B pricing, ERP feeds. Each integration adds build and testing time, and testing is the half that gets underestimated.

On Shopify Plus, the work that stretches a calendar is checkout apps, B2B pricing and ERP feeds, so a Plus rebuild gets quoted after the audit, the same as a migration.

Why my timelines read short

The build runs through a system: a written playbook for every repeatable step, templates and checks accumulated across every build before yours, and one senior operator instead of four people passing work between them.

Fewer handoffs is most of the answer. The same person doing the theme also wires the tracking, so the two workstreams never wait on each other. The rest is scope discipline: a build with a defined end date has a defined scope, and I’d rather say no to a feature in week one than discover it in week five.

The question to ask any vendor

Ask what happens in week one.

A builder with a working system starts building in week one. A process-heavy shop spends weeks one through three on discovery decks. Both can produce a good store. Only one of them does it this quarter.

Then ask what happens in the last week, because that’s where tracking, redirects, and the speed check either live or don’t. Timelines and pricing for my builds are published on my custom Shopify storefront page, and the risk checklist for the cutover itself is at redesign without losing sales.

When to bring me in

Bring me in when paid traffic lands but doesn’t buy, when the theme fights your catalog, or when you’re weighing a rebuild and need to know if a facelift would do.

I'm Conner Crowe, and I write every audit myself. Send the free audit request with your store URL and add me as a read-only user on the ad account, and within 24 hours of access you'll have a written read on where the store loses paid traffic and what to fix first. No call needed, and nothing in your account or store changes.

Get a free ads audit →

Home or furniture store? The catalog audit reads the public store, so there’s nothing to grant. Request the free catalog audit