How to scope a Shopify build

Decide the theme approach first

The single biggest cost driver is how you're building the storefront:

• Configured theme, a premium or free theme adjusted to the brand. Fastest and cheapest,

with limits on layout freedom.

• Customised theme, a theme extended with bespoke sections and features. The common

middle ground.

• Fully custom, a bespoke theme (or headless, see [what goes in a headless commerce

spec](/guides/what-goes-in-a-headless-commerce-spec)). Most control, most cost.

Name the approach explicitly in the scope. "A Shopify store" can mean any of these, and the gap between them is thousands of pounds.

Scope the apps, and their monthly cost

Shopify's app ecosystem fills gaps the core platform leaves: subscriptions, advanced filtering, loyalty, reviews, bundles, upsells. Two things to get right in the scope:

• Which apps are needed for the required features, and whether each needs configuration or

custom work to fit.

• Ongoing app costs. Many apps carry a monthly fee that the client pays indefinitely.

Make these visible in the scope so they aren't a nasty surprise after launch, and so it's clear they're the client's recurring cost, not yours to absorb.

Product data and migration

Migration is where Shopify projects quietly overrun. Scope it deliberately:

• Catalogue size and structure, number of products, variants, options, and how clean the

source data is.

• Where it's coming from, an export, another platform, a spreadsheet, or manual entry.
• What's included, images, SEO metadata, redirects from old URLs, customer records, order

history.

• Who does the data cleanup, you or the client. This assumption alone decides whether

migration is a day or a fortnight.

Know Shopify's boundaries

Scope around the platform's real constraints, not an idealised version of it:

• Checkout customisation is limited on standard plans; deep checkout changes generally

need Shopify Plus and checkout extensions. Don't promise bespoke checkout flows without confirming the plan.

• Some B2B, multi-currency and multi-store needs point to Shopify Plus. Establish the plan

before you quote features that depend on it.

• Complex catalogue logic sometimes hits variant and option limits that shape the design.

Writing these boundaries into the scope as explicit assumptions is what prevents a mid-build "but we assumed…" dispute.

Write the exclusions down

Most Shopify scope creep comes from things everyone assumed but nobody wrote: content population, product photography, copywriting, third-party app fees, post-launch support, and ongoing SEO. State clearly what's in and what's out, against the section it affects, so the line is unambiguous later.

Turn the checklist into a reusable scope

You'll scope your third Shopify build much like your first, so capture the pattern once. In ScopeDeck, a Shopify Scope Type pre-shapes the right sections, and reusable snippets let you save a fully-formed "Shopify migration" or "subscription setup" block, quote wording, spec detail, task seeds and default hours, to drop into the next store. Scope the build once properly, and every Shopify project after gets faster and more consistent. Agencies doing this at volume can see the fit on the Shopify agencies page.