Most DTC brands going into a Shopify rebuild have a vague sense of “it’ll take a couple months” and not much else. That vagueness is where budgets balloon and launch dates slip, not because the work is unpredictable, but because nobody set concrete expectations for what happens in which week and what the brand is actually responsible for delivering along the way.
Here’s what a real Shopify rebuild timeline looks like for a DTC brand doing a full custom theme build, not a template swap, based on how this actually plays out over 8 to 12 weeks.
Weeks 1-2: Discovery and Strategy
This is the phase most brands want to skip and the one that determines whether everything after it goes smoothly. A real discovery phase covers three things: a technical audit of the current store (what’s actually driving revenue, what’s broken, what app dependencies exist), a competitive and customer-experience audit (where the current site loses people, what competitors are doing better), and a content and asset inventory (what photography, copy, and brand assets actually exist versus what needs to be created).
The brand’s job in these two weeks: get decision-makers in the room for the kickoff and audit review, and start pulling together brand assets (logo files, product photography, past campaign creative) that the design team will need. Brands that show up to week 3 without their assets organized are the single most common cause of a slipped week 3.
Weeks 3-4: Information Architecture and Wireframes
Before any visual design happens, the site’s structure gets mapped: navigation, collection hierarchy, product page structure, and the customer journey from landing page to checkout. This is wireframe-level, black and white boxes, not colors and fonts. Skipping this and jumping straight to visual design is how brands end up with a beautiful homepage and a confusing, poorly converting collection page structure underneath it.
This phase also finalizes the technical scope: which apps will be integrated (Klaviyo, subscription platforms, reviews, loyalty), which of those need custom integration work versus a standard install, and what the checkout customization requirements are given the brand’s current Shopify plan.
Weeks 4-6: Visual Design
Homepage, collection page, product page, and cart/checkout experience get designed as a system, not as isolated pages. This typically means one full concept round, one round of revisions based on stakeholder feedback, and a final design approval before development starts. Brands that try to compress this into a single round of feedback usually pay for it later in development change orders.
The most common point of friction here isn’t the design itself, it’s indecisive or fragmented feedback from multiple stakeholders with different opinions. Naming a single decision-maker for design approval before this phase starts saves real time.
Weeks 6-9: Development
This is where the custom Shopify theme actually gets built: Liquid templating, app integrations, page speed optimization, and responsive behavior across devices. For a fully custom theme (not a modified purchased template), this is typically the longest single phase.
Midway through development, a staging link should go live so the brand can review functional pages in a real browser, not just static design files. This is also when app integrations get tested individually, Klaviyo forms firing correctly, subscription logic working as expected, reviews displaying properly, before they’re all tested together.
Weeks 9-10: QA and Content Migration
Every page gets tested across devices and browsers. Product data, collections, and existing customer accounts get migrated from the old store structure. This phase also includes 301 redirect mapping, every old URL needs to point to its new equivalent, or the brand loses existing SEO equity and breaks any bookmarked or linked pages from email campaigns, ads, and backlinks.
This is the phase most frequently rushed when a launch date is slipping, and it’s the one that causes the most visible problems post-launch: broken redirects, missing products, checkout bugs that only show up on a specific device or browser.
Weeks 10-12: Launch and Post-Launch
Launch itself should happen during the brand’s lowest-traffic window, not mid-campaign or during a planned promotion. Analytics and tracking (GA4, Meta Pixel, any attribution tools) get verified as firing correctly before traffic starts flowing, not after. A brand that launches without confirming tracking is working loses the ability to measure the new site’s actual performance against the old one.
The two weeks after launch matter more than most brands expect: monitoring for edge-case bugs that only appear under real traffic and real customer behavior, and being available to fix them fast rather than treating launch as the finish line.
What most timelines get wrong
Two assumptions consistently blow up a Shopify rebuild schedule. The first is assuming feedback rounds will be fast; a single stakeholder taking a week to respond to a design round adds a week to the entire project, not just that phase. The second is assuming content (photography, copywriting, product data) will be ready when development needs it; content production should start in week 1, in parallel with design, not after design is approved.
A realistic budget for this kind of rebuild also needs to include a buffer for scope additions. Almost every rebuild surfaces something in week 6 or 7 that wasn’t in the original scope, a subscription flow that needs more customization than expected, a product configurator that wasn’t fully specified upfront. Budgeting a 10-15% contingency for this is more honest than pretending it won’t happen.
Written by David Herskowitz, Founder and Creative Director of Splash Creative, a senior-led Shopify design agency working with DTC brands in New Jersey and New York. Splash builds fully custom Shopify themes, not modified templates, with strategy and copywriting included. Projects start at $20,000. Talk to David about your rebuild timeline.
