White label Shopify means a partner builds the Shopify project and your agency sells it under its own brand: your name on the proposal, the contract and the invoice, someone else’s hands on the code. White label Shopify development pays when requests arrive faster than you can hire and you stay the person the client trusts. It stops paying when access, ownership or the paperwork is vague.
We are noprob agency, and this guide is for small agencies, web agencies and performance agencies that get Shopify requests and do not want to hire for them. Two rules for reading it. The facts come from Shopify’s own pages, linked next to each one. Commercial practice (what to write down, how to price, what to tell the client) has no official source, so we write it as our opinion and mark it: “in our view” or “we recommend”.
What does white label Shopify development mean?
It means the work is done by one company and sold under the brand of another. That is our definition, and it is a commercial one: we found no official definition that covers web agencies. Shopify’s Partner Program Agreement does not use the words “white label” at all, and neither do its brand guidelines.
What Shopify does have is rules on subcontracting, and those are the ones that matter. Under the Partner Program Agreement, a partner stays responsible for its employees, agents and subcontractors even when it subcontracts, and may access a merchant’s store only for work the merchant has authorized. A partner also cannot present itself as Shopify or misrepresent its affiliation. The store side works the same way: under Shopify’s Terms of Service a store has a single Store Owner, and that owner is responsible for the employees, agents and subcontractors working on it.
Offers of white label web development or white label web design services cover many kinds of sites. On Shopify the work happens inside the client’s own store, in the client’s own account, so access and ownership follow Shopify’s procedures. The next sections cover them.
When does white label Shopify make sense for an agency, and when does it not?
In our view it makes sense when you own the client relationship and the project has an edge: a start, an end and a scope you can write on one page. This section is opinion. The Shopify facts come in the sections after it.
It tends to work when:
- Shopify requests reach you now and then, not every week, and a developer hired for them would sit idle between projects.
- The client pays you for strategy, ads, content or design, and the build is one step of a bigger relationship.
- The project has a fixed scope and calendar. A migration is the clearest example: the platform changes, the store stays the same. Our Shopify migration service is built that way, and our guide to migrating to Shopify shows the steps.
It tends not to work when:
- Shopify is the core of what you sell and you want the skill in house.
- The scope is open ended and changes every week, so someone in your team has to answer on the spot.
- You have not tested the builder on a small job first.
- The client already knows and trusts the builder more than you.
Our rule: resell what you can describe in one sentence with a date. Refer what you cannot. And if you prefer not to resell at all, you can point out the store and let the partner handle the rest.
How does a builder get access to a client’s Shopify store?
Through a collaborator account that the client approves, not through a shared login. Shopify’s page on working on client stores recommends the collaborator account and says a partner cannot ask for or use the merchant’s credentials. A staff account, created by the merchant, is the fallback when the collaborator account is not enough.
The steps, from the collaboration documentation:
- The partner requests access from the Dev Dashboard with the store’s myshopify URL, the merchant’s 4-digit request code and the permissions it wants. If the partner already has an app installed on the store, the code is not needed.
- The merchant finds the code in Settings, Users, Security. Generating a new code invalidates the previous ones.
- The Store Owner, or a staff member with the admin role, approves. The merchant decides which areas are open and grants only the permissions needed (collaborator accounts).
Details that save you a message to the client:
- Collaborators do not use up the store’s user limit and have no POS access.
- Access expires after 90 days without a login, and the partner must turn on two-factor authentication.
- A store can have at most 2 pending requests.
| Access | Who creates it | What Shopify says |
|---|---|---|
| Collaborator account | The builder requests it, the client approves | Recommended; the client sets the permissions |
| Staff account | The client creates it | Fallback when the collaborator account is not enough |
| Shared login | Not an option | A partner cannot ask for or use the merchant’s credentials |
We recommend asking for the narrowest permissions the job needs, writing them in the contract and removing the access on the day the project ends.
Does the client see who really builds the store?
Partly: the client can see details about the builder inside their own Shopify admin. According to the page on working on client stores, Shopify shows the merchant data about the partner that asks for access: how long the account has existed, a band for its active collaborations, and the country of registration and of the request. And when a collaborator is removed, the name stays visible in the activity log and in order histories (collaborator accounts).
In our view the honest move is to say it before it happens. Put one line in the proposal that a build partner works under your responsibility, and the access request will not surprise anyone. We recommend this over hoping nobody looks: the client owns the store and can read its logs.
How does the store get transferred to the client?
If the builder creates the store, it does so as a client transfer store inside the builder’s organization and hands it to the client at launch. That is the route described in Shopify’s page on client transfer stores. A development store cannot be transferred to a client or converted to a production store, so it is the wrong tool for a store that will go live.
What the documentation on transfers says, in order:
- Before the transfer the store takes no real transactions and runs no custom or draft apps.
- Shopify Payments (even in test mode), Balance, Credit and Capital must be turned off first, or the transfer fails.
- The partner starts the transfer from the Dev Dashboard with the client’s email. The client accepts the invitation and chooses a plan.
- A pending transfer expires after seven days. Until then it can be resent or canceled.
- The partner’s company entity is never transferred: the client receives a new entity in their own organization.
When the client already owns the store, the direction flips. A partner working through a collaborator account cannot transfer ownership: the merchant has to start it, and ownership cannot go to a collaborator account. The merchant can pass it to an existing user from Settings, Users, or to someone outside from Settings, General, with acceptance by email (changing or transferring ownership). The previous owner keeps the permissions on the store and loses those at organization level, so review them right after.
Who earns Shopify’s partner compensation on a white label project?
The partner that built the store and transferred it to the merchant. Shopify’s Partner Program is an open, performance-based agency partner program, aimed mainly at agencies, consultancies and system integrators that offer services to merchants (program FAQ). On the earnings page, revenue share goes to whoever built and transferred the store, it is not split between agencies on the same store and it stays tied to the original billing store. Commission on stores you build comes only from transferring a client transfer store to the merchant (managing client stores). Payouts remain at Shopify’s discretion and the amounts can change (how to earn).
In our view this belongs in the contract, not in a footnote. Decide before day one who builds the store, from which Partner account, and who receives the compensation. And do not build your price counting on it: Shopify can change the amounts.
What should you put in writing before the first white label project?
Put in writing who works for whom, what “done” means, how access starts and ends, who owns the code and what happens when someone does not pay. This is our recommendation, not a legal template. Shopify and a few other sources give hints on some of the points, linked below.
- Who contracts with whom. You contract with the client and the builder works for you. It matters because the Partner Program Agreement keeps the partner responsible for its subcontractors.
- Scope, calendar and acceptance. What is included, the dates and what counts as accepted.
- Access. A collaborator account, the permissions listed one by one, no shared logins and the day the access is removed.
- Store and transfer. Which account creates the store, who is the Store Owner at go-live and when the transfer happens.
- Code ownership. Who owns what is built, and from when. Do not assume it: write the assignment down.
- Confidentiality. The Partner Program Agreement lets confidential information go to subcontractors who need it, if they are bound by confidentiality at least as strict.
- Customer data. If the store sells to people in the EU, the European Data Protection Board’s guidelines on controllers and processors say a processor cannot engage another one without the controller’s written authorization.
- Payment and non-payment. Under the Agreement it is up to the partner working for a merchant to have an agreement with remedies for non-payment, and Shopify does not step into those disputes.
- Contact with the client. Who talks to the client, and whether the builder may approach them directly after the project, for a fixed period or never.
- Support after launch. Who answers, how fast and who pays for fixes.
None of this is legal advice. Have a lawyer or consultant who knows your market review the contract before you sign the first one.
How do you make a real margin on white label Shopify development?
A real margin is what is left after the builder’s price and after you have paid yourself for the time you spend selling, managing and answering the client. In our view agencies lose margin on the second part more than on the first.
| Line | What it is | We recommend |
|---|---|---|
| Builder’s price | What you pay the build partner, fixed in writing | Quote the client only after you have it |
| Your management time | Briefing, calls, reviews and client messages | Price it as a line, not as a favor |
| Risk buffer | Delays, a change of mind, a late payment from the client | Keep part of the price for it |
| Margin | What stays after the three lines above | Judge it per project, not per hour |
Three rules we recommend:
- Sell a fixed price on a fixed scope. Margin disappears in open scope, one small request at a time.
- Never resell below your costs to win a client. A discount you cannot afford becomes a late project.
- Talk about margin with the builder before the first quote. A good partner tells you what the job costs and when it will be done.
Shopify’s own compensation (previous sections) is a possible extra, not a base for the price. Nothing in this guide promises a result: your margin depends on what you charge and what you deliver. To see how a finished migration reads from the client’s side, open the Nazzi case study. Your client will ask the questions in how to choose a Shopify migration agency, so it helps to have the answers.
How does noprob agency work with agencies?
Your agency resells the Shopify migration under its own brand and we carry it out, or you point out a store to us. In both cases you earn from €1,000 per project. That is our agency partner program.
We are enrolled in the Shopify Partner Program. What we build for your client is the Shopify Launch Sprint: a Shopify migration in 14 days with our Custom AI System, go-live between day 15 and 30, 90 days of support, 4 written guarantees and a public price by company revenue in 4 installments.
Frequently asked questions
What is white label Shopify development?
White label Shopify development is when one company builds a Shopify store or migration and another agency sells it under its own brand. The client contracts with the agency, the builder works for the agency and the store stays the client’s.
Does Shopify allow white label work?
Shopify’s Partner Program Agreement does not mention white label. It keeps the partner responsible for its subcontractors and allows access to a merchant’s store only for work the merchant authorizes. Read it, and ask a consultant if you are unsure.
How does a white label partner access my client’s Shopify store?
Through a collaborator account. The partner requests access from the Dev Dashboard with the store’s myshopify URL and the client’s 4-digit code, and the client approves and sets the permissions. Sharing the client’s login is not an option.
How is the store transferred to the client?
The builder creates a client transfer store in its own organization and transfers it from the Dev Dashboard to the client’s email. The client accepts and chooses a plan. Shopify Payments, Balance, Credit and Capital must be off first, and a pending transfer expires after seven days.
When does white label Shopify development pay for an agency?
In our view, when you own the client relationship, requests arrive faster than you can hire and the project has a fixed scope and calendar. The margin is what is left after the builder’s price and your own management time, so quote only after you have the builder’s price in writing.
What should a white label agreement include?
We recommend putting in writing who contracts with whom, scope and acceptance, access and its end date, the store transfer, code ownership, confidentiality, customer data, payment terms, contact with the client and support. It is not legal advice: have a consultant review it.
The Shopify Launch Sprint moves your store to Shopify in 14 days with our Custom AI System: a fixed calendar, a public price and 4 written guarantees.
Antonio Manitta
Founder & eCommerce Manager at NoProb Agency
For over 7 years I have helped fashion, supplements, and DTC brands scale their eCommerce. I work in long-term partnership with three brands at a time, building stable systems that compound.
About NoProb →
