Placing Shopify + AI developers, see open talent

Shopify

What a Shopify Build Actually Includes, Phase by Phase

Two honest quotes for the same store can differ fourfold. The gap is almost never the design. Here is what each phase really contains.

Karan PambharFounder & CEO, Code Elevator
Published ·Updated ·5 min read
Trusted Experts
Contents

Two Shopify quotes for the same store can differ by a factor of four, and both can be honest.

The gap is almost never the design. It is what each quote assumes about data, integrations, and who does the fiddly parts nobody enjoys. This is what the phases actually contain, so you can read a proposal and see what has been left out of it.

Phase 1: Decisions, before any design

The questions that decide your budget get answered here. Skipping this phase is the main reason builds go over, because the answers arrive anyway, just later and more expensively.

  • How many products, and how many options on each? Shopify limits how many variants a single product can have. Large catalogues with many options sometimes need a different data model, and that is a structural decision, not a detail to sort out later.
  • Where does product data live now? A clean spreadsheet is an afternoon. An old system with inconsistent fields and no usable export is a project in its own right.
  • What has to talk to what? Accounting, warehouse, ERP, email, subscriptions, loyalty. Each one is real work and each one can fail independently.
  • Which countries, currencies and tax rules? Selling into the EU and the US from one store has genuine consequences for pricing display, tax collection and checkout.
  • Who is the decision maker? One named person who can approve things. Builds with a committee take longer and cost more, every time.

If a proposal goes straight to design without answering these, the number in it is a guess wearing a suit.

Phase 2: Design that survives contact with real products

Design for Shopify is mostly about templates, not the home page. The home page gets the attention. The product page makes the money.

The thing to insist on is that designs are shown with your actual products, including the awkward ones. The item with a nine word name. The one with three photos when everything else has eight. The one that is out of stock. The one with a name in a language that uses longer words than English.

Designs that only work with ideal content break in week one, and the fix always costs more than doing it properly would have.

The templates that matter more than people expect

  • Collection pages with filters. This is how most people actually browse, and it is usually designed last.
  • Search results. Visitors who search convert far better than those who do not. An ugly search page is a real loss.
  • Empty and error states. No results, out of stock, payment declined. These get skipped and then land on customers at the worst moment.

Phase 3: Build

This is theme development, and modern Shopify themes are built from sections you can rearrange yourself in the editor. That matters more than it sounds.

A theme built as flexible sections means you can add a banner or reorder a landing page later without paying anybody. A theme built as fixed pages means calling a developer for every small change, forever. Ask which one you are getting, and ask to see the editor before you accept the work.

Custom fields, called metafields, are the other thing worth asking about. They are how you attach structured information to products: care instructions, ingredients, size charts, delivery notes. Without them that content gets shoved into the description as loose text, where nothing else in the store can use it, filter on it, or display it consistently.

Phase 4: Data migration, where the time actually goes

This is the phase most quotes underestimate and most delays come from.

Products are the easy part. The hard parts are customer accounts, order history, and the URLs of your existing pages. Get URLs wrong and every link into your store, from Google and from every site that ever mentioned you, lands on an error page. The ranking goes with it.

Ask directly: who is writing the map from old URLs to new ones, and when is it tested? If the answer is vague, that vagueness is your risk, and it is the most expensive risk in the whole project.

Things that do not migrate cleanly and should be discussed early

  • Customer passwords. They generally cannot move between platforms. Customers will need to reset, so plan the email that tells them.
  • Product reviews. Often tied to whichever app held them, and moving them is a separate job.
  • Discount and gift card codes. Balances and expiry dates need deliberate handling.
  • Subscriptions. The hardest of the lot. If you have them, raise it in the first conversation, not the last.

Phase 5: Launch and the fortnight after

Launch day is not the end of the work, and a build that treats it that way leaves you alone at the worst possible moment.

Real orders behave differently from test orders. Customers use address formats nobody tried, pay with cards issued in countries nobody tested, and find the one product with a missing weight within the first hour. Two weeks of active support after launch is the difference between a bumpy fortnight and a bad quarter.

Ask what the support arrangement is for those two weeks, and what response time you get. A build with no post-launch cover is not finished, it is abandoned.

What you should own when it is over

Worth writing into the contract, because it is easy to discover far too late that you own less than you assumed.

  • The Shopify store, on your own account, with your own billing.
  • The theme code, in a repository you control.
  • Any custom app built for you, including its source code.
  • Domain and DNS access.
  • Written notes on the integrations and why they are configured as they are.

If any of that sits with the agency rather than with you, you are not a client. You are a tenant, and your rent is whatever they decide it is next year.

The question worth asking before you sign

Ask any agency to show you a store they built two years ago that the client has been running without them ever since.

It is a much harder question than a portfolio, and the answer tells you whether they build things people can own or things people must keep paying for. Both are real business models. You should know which one you are buying.

We work this way on our own Shopify development projects, and everything above is written into the engagement rather than left as an assumption.

If you have a proposal in hand and want a second opinion on what it leaves out, send it over. We will read it and tell you what we would ask, even if you go with them. Ask us to read your Shopify quote.

Hire for this

Need this built right? Hire a vetted Shopify Developers, matched in 48 hours.

Hire Shopify Developers
Karan Pambhar
Founder & CEO, Code Elevator

Founder and CEO of Code Elevator, working with clients on Shopify and ecommerce builds and on MLM platform software. Based in Dubai, UAE.

More from Karan
Before you decide

Four clients, on camera.

Client video

Why he brought his development work to Code Elevator.

MikePlays here
Keep reading

One useful piece a month, no more than that.

What we learned building and hiring for this work. No newsletter filler.

Get started

Reading about it is step one. Building it is step two.

Hire a pre-vetted engineer who has shipped work like this before. Matched within 48 hours.

We reply within an hour during our working day in India and the UAE.

Chat with our team