Skip to content
← Blog

Technical · 8 min read

What agencies should expect from white label Shopify development

What a good white label Shopify partner delivers: scope, store ownership, apps, review and handoff, plus the questions to ask before you hire one.

November 11, 2026

What agencies should expect from white label Shopify development

Key takeaways

  • The store should live in your client’s own Shopify account, with your partner working through staff or collaborator access that ends at launch.
  • A good partner works from your design direction and your scope document, and you review the build before the client sees it.
  • Apps are recurring subscriptions: the client pays, and the partner installs and configures the ones you choose.
  • Ask about ownership, apps, review, handoff and contact with your clients before you hire anyone.

If you sell websites and a client asks for a Shopify store, you have three options: build it yourself, hire a freelancer for the job, or work with a white label partner who builds under your name. This article is for the third case. It covers what white label Shopify development should look like when it works, what to hold a partner to, and where it is the wrong choice.

What white label Shopify development actually means

In a white label arrangement, you own the client relationship, the design direction and the price. The partner does the build and stays invisible. Your client sees your name, your emails and your review process.

That arrangement only works if the boundaries are clear. A good white label Shopify partner does not contact your client, does not pitch them other services, and is happy to sign an NDA. It also says what it does not do. We are a small owner-led studio, and we do not run SEO, ads or social, so we do not pretend to be a full-service shop behind you.

Scope: what the partner builds and what you keep

The cleanest split is that you provide the design direction and the brief, and the partner turns them into a working theme. If you are comparing partners, check how they treat design. Some work from a template and adjust it. Others code the theme from your design direction. That choice affects flexibility, speed and what the client can edit later, and custom theme vs template is worth reading before you decide.

Whichever route you take, settle the scope in writing before work starts. Page count is a poor guide. The catalogue, the distinct templates, the apps and the content drive the effort, as covered in how agencies scope a Shopify build. A good brief also helps; see how to brief a white label web build.

Laptop screen displaying a group of people on a video call
A short call with the partner to walk through the design direction and scope document saves rounds of revision later.

Ownership: whose store is it?

This is the most important question to ask, so ask it first. The store should be created in your client’s own Shopify account, not in yours and not in the partner’s. The partner then works through staff or collaborator access, and that access ends at launch.

The reasons are practical:

  • The client owns their products, orders, customers and billing from day one.
  • Nothing has to be transferred at the end, which is where handoffs tend to go wrong.
  • If you ever stop working with the client, or the partner, the store is unaffected.

Shopify’s documentation on themes is a good starting point for understanding what a theme is and what lives in the store versus in the code.

Watch out: If a partner proposes to build in their own account and “move it over later”, ask exactly how that move works and what breaks. Building in the client’s account from the start avoids the question.

Apps: who pays and who installs

Apps are the cost agencies forget to mention. Most are monthly subscriptions set by the app’s developer, and the price can change. Our position is simple: the client pays for apps on their own account, and we install and configure the ones you choose. We do not push a favourite set of tools, and you are never locked into something we picked.

Put every app in the proposal with what it does and a pointer to its current listing on the Shopify App Store. Shopify also documents how app billing works from the developer side, which helps you understand why prices and plans change. The full reasoning is in Shopify apps: what they cost and who pays.

Process: how a sensible build runs

Details vary between studios, but the shape should be familiar:

Stage What happens Who is involved
Brief and scope Design direction, catalogue notes, app list and exclusions are written down You, with the partner asking questions
Access Client creates the store and grants staff or collaborator access Client, then partner
Build Theme is coded, sections and templates set up, apps installed Partner
Your review You test the store before the client sees it and send consolidated feedback You
Client review and launch You present to the client; launch happens in their account You and the client
Handoff Access ends and documentation goes to you Partner

The step that matters most for your reputation is the fourth one. You should see the store, click through it on a phone, and test checkout before your client does. If a partner wants to show your client the work directly, that is a signal to ask more questions.

Woman working on a laptop in a light-filled living room
Most store owners judge a build on the product page and checkout, so those are worth testing first.

Handoff: what you should receive

At launch, the partner’s access to the store ends. What stays with you is the working store, a clear list of the apps installed and what each one does, and enough notes that someone else could pick up the theme. A Shopify Liquid theme handoff checklist gives you a list to hold the partner to. If your client’s team will edit content themselves, check that the theme uses sections they can rearrange in the theme editor, rather than values buried in code. For general guidance on how a handoff should work across platforms, see our page on white label website handoff.

When white label Shopify is not the right call

Being honest about this saves everyone time.

  • The store is very simple. A handful of products may be well served by a well-chosen template with light changes. A custom theme is not always worth it.
  • The catalogue is large or unusual. Complex bundles, subscriptions, B2B pricing or heavy integrations can take a project beyond a standard build. Those need a scoped conversation, not a quick quote.
  • The client needs something Shopify handles poorly. Sometimes another platform is the better fit. Our piece on WooCommerce vs Shopify covers how to decide, and we also offer white label WooCommerce development.
  • You want one in-house person to own everything. If you already have a capable developer, outsourcing may add overhead rather than remove it.
  • You need a large team. A small studio is a different thing from a large one; small studio or big team lays out the trade-offs.

Questions to ask before you hire a partner

  1. Where does the store live, and who holds the account?
  2. How do you work: from my design direction, or from your own template?
  3. Who pays for apps, and who installs and configures them?
  4. Do I review the build before my client sees it?
  5. Do you ever contact my clients?
  6. What do I receive at handoff, and when does your access end?
  7. How do you handle a request that is outside the agreed scope?
  8. Will you sign an NDA?

Good answers are specific. Vague ones usually mean the process is not defined yet.

Working with us

Our white label Shopify work is custom-coded themes, built from your design direction in the client’s own Shopify account. The price is $1,199 per store, flat, with apps billed to the client. Larger or unusual stores are quoted per project before work starts. You can read more about white label Shopify development, the white label Shopify agency arrangement and how we work with partner agencies. If you serve a specific kind of agency, we also have pages for marketing agencies and design studios. Before the first build, the product page checklist is a useful thing to share with your own team.

Next step

Take one upcoming Shopify project, write down its catalogue, templates and likely apps, and send it over through the contact page. We will tell you honestly whether it fits, whether a template would serve the client better, and what would need quoting separately. You can read how a project runs from start to finish on how we work.

Frequently asked questions

Does the client have to know a partner is involved?
No. That is up to you. We never contact your clients, and an NDA is available if you want it in writing.
Why should the store be in the client's account?
Because the client owns it from the first day, billing and orders included, and nothing needs to be transferred at the end. Access for the partner ends at launch.
Who pays for Shopify apps?
The client, on their own account. We install and configure the apps you choose, but we do not hold the subscriptions.
Is a custom theme always better than a template?
No. A template can be the right answer for a small, simple store. A custom theme makes more sense when the design needs flexibility that a template would fight against.

Sources and further reading

  1. Shopify themes documentation — an overview of what a theme is and how it is built
  2. Theme architecture — how templates, sections and assets fit together
  3. Theme sections — what clients can edit in the theme editor
  4. Theme performance best practices — guidance on keeping stores fast, including third-party scripts
  5. Liquid reference — the template language Shopify themes use
  6. App billing — how app charges work, and why plans and prices can change
  7. Shopify App Store — check each app’s current listing and pricing

Ready to talk?

Looking for a white label web partner you can actually rely on?