What to have ready before a Shopify store is built

A project stalls on what was never decided: the catalog, shipping, language, and who gets to say yes. Here is the list before you start.

Author: Henry Navntoft, Shopify developer

Most delays in a Shopify project are not the code. They are a catalog that is not finished, a shipping price you will “figure out”, and three people who all think they approve the homepage. You can start the build without that. You cannot finish.

Before the first line

  • A catalog you can sell: names, prices, variants, and images at a quality you will show.
  • Shipping, returns, and the countries you actually ship to. Not “worldwide” as the default.
  • One language and one market first, if you do not already run the others.
  • One person who can say yes to design and copy. Not a committee.

What usually is missing

Payments and shipping apps get chosen as if they were details. They are the store. An inventory or accounting integration that “comes later” means you launch with a manual gap. Write it down before the scope is locked. If you are coming from another platform, that sits under migration. If you are starting clean, it sits under the store build.

A short list beats a long brief nobody read. Ten products that are real are worth more than a spreadsheet of four hundred rows you will not stand behind. The price of the work follows how finished that material is. That is covered in what a Shopify store costs.

About the author

Henry Navntoft. Shopify developer at Globus in Copenhagen. Builds stores, apps, and migrations for Danish and international brands.

Q&A

Can you start while we collect the images?

Yes, on the structure: theme, templates, shipping, and payments. Product pages cannot be finished on images you do not have. Agree which set has to be ready for launch.

Who should approve along the way?

One person. Several approvers is the reliable way to spend two weeks on a button. The others can watch. One says yes.

Do we need every product ready before we start?

You need a set you will stand behind: names, prices, variants, and images. Four hundred empty rows delay more than they help.

Can shipping and payments wait until after launch?

No. That is the store. A store without shipping rules and payments is a catalog page. Settle them before the scope is locked.

More guides

Want us to look at your store?

Tell us what you sell and where it stalls. We’ll say whether it is a theme, an app, or a move.

Get in touch

How to use the list before a build

Most delays are not the code. They are a catalog that is not finished, a shipping price nobody has chosen, and three people who all think they approve the homepage. The guide is that list. You can start the build without it. You cannot finish. Use it internally before you ask for a quote, so the quote does not have to guess those four things.

When you write to us, say what is already settled and what is not. We can scope the theme while the catalog is finished, but we will not put a launch date on something nobody has approved. The contact form is there for that note.

The list belongs with the Shopify store service and with the migration service if you are coming from another platform. Same questions, different start date. Catalog, shipping, language, and one person who can say yes apply in both places.

Name the person who is allowed to say yes. Not a group. One person. If that name does not exist yet, finding it comes before drawing a theme. The guide exists because projects die there, not in Liquid.

Catalog, shipping, language, and approval are the four things we ask about, even when you write about a migration and not a new theme. The list is the same because both projects stall in the same places. Take it to the internal meeting before you ask for a date.

The list is catalog, shipping, language, and one person who may say yes. Those four are there because projects die there, not in Liquid. A catalog that still lives in three spreadsheets cannot have a launch date. A shipping price nobody has chosen cannot be tested in checkout. A language you might want later has to be said now if the theme must support it. And if three people all think they approve the homepage, there is no approval.

Name the person before you ask for a date. Take the list to the internal meeting. You can start a scope while the catalog is finished, but you cannot finish without it. The same is true of a migration: the four questions are the same, the start date is different. When you write to hello@globus-dev.com, say what is already settled and what is not. Then the quote does not have to guess.

The store service and the migration service use the same list. The difference is whether you start from an empty store or from one that already has URLs you cannot afford to lose. Say which of the two it is. The phone, if you would rather call, is +45 51 98 23 45. The studio is in Copenhagen. The guides on cost, themes, and a slow store can wait until those four things have an answer. This list is the one a quote would otherwise have to invent.