StoreBuilt’s review of Shopify’s ownership documentation starts with a distinction that matters in every handover: an administrator who can edit the store is not necessarily the account that owns it. Our planning checks separate access, ownership and operational responsibility. Giving someone broad permissions does not establish that the formal owner role has moved.
To transfer Shopify store ownership, a UK merchant needs a clear recipient, the right transfer route and a coordinated review of the services surrounding the store. This guide concerns an actual change of owner. If you are only changing agencies while the business retains ownership, an access and documentation handover is usually the more relevant project.
In this guide
- Confirm what is actually changing
- Separate the assets that need their own handover
- Prepare the recipient and transfer window
- Review restrictions and provider dependencies
- Complete the correct ownership route
- An illustrative founder handover
- Verify the store can still operate
- StoreBuilt point of view
Confirm what is actually changing
Start with a short written description of the transition. Is the same business appointing a new owner account, is a store moving to a different business, or is an agency returning a client store? These situations can share technical steps while having different contractual, billing and operational consequences.
Identify the current store owner from the admin and confirm that the person can authenticate. Do not discover on transfer day that the account depends on an unavailable employee’s device or inaccessible mailbox. Use the platform’s supported account-recovery route if access is missing; sharing passwords is not a substitute for resolving ownership.
Shopify’s change and transfer ownership guidance distinguishes an existing-user route from a transfer to someone outside the store. Plus and organisation arrangements can require different handling. Check the applicable flow for the actual account rather than following screenshots from an unrelated store.
Separate the assets that need their own handover
The store owner role is only one item in the business’s control map. The domain registrar, payment providers, email platform, shipping accounts and repositories may all have separate access and billing. List those dependencies before scheduling the transfer so the new owner does not inherit a store whose essential services remain inaccessible.
| Asset or responsibility | Evidence needed | Handover owner |
|---|---|---|
| Shopify owner role | Current owner and intended recipient | Current store owner |
| Domain registration | Registrar access and current contact details | Domain administrator |
| Shopify billing | Approved billing information and outstanding items | Finance lead |
| Payment providers | Required account and payout changes agreed | Authorised payments contact |
| Externally billed apps | Account owner and payment responsibility | App account owner |
| Operational alerts | Correct recipients and escalation route | Ecommerce operations lead |
Do not include passwords or recovery codes in a handover spreadsheet. Record where authorised access is managed and who can grant it. The receiving party should use their own identity and appropriate authentication. A checklist that relies on one shared login may appear convenient but leaves the business unable to explain who controls a critical action.
For a broader agency transition, use our Shopify agency handover guide. Keep the formal owner-role change distinct from repository access, unfinished development work and support responsibilities. That separation makes both projects easier to verify.
Prepare the recipient and transfer window
Confirm the exact recipient email through an agreed channel. A typo here affects a privileged account transition, so review the address deliberately. If using the existing-user route, establish that the recipient has the required user account. For an external transfer, make sure the intended recipient knows to expect the invitation and can complete acceptance.
Choose a window when the current owner, incoming owner and relevant operational contacts are available. Avoid combining the transfer with a theme launch, payment migration and warehouse switch unless the project genuinely requires it. Fewer simultaneous changes make any unexpected symptom easier to investigate.
Agree what happens if the invitation is not accepted or the process stops partway through. Keep the existing support arrangements available until completion is verified. Do not remove the only person who can resolve a billing or domain issue simply because the handover meeting has finished.
Review restrictions and provider dependencies
Check Shopify’s current transfer considerations before committing to a date. Its documentation identifies particular financial-product and account circumstances that can affect transfer eligibility. If the store uses such services, resolve the requirements with Shopify Support before treating the owner change as a routine admin action.
Business details and payout arrangements also deserve a separate review. A sale of the business can require provider checks beyond changing an email address. Follow the relevant provider’s supported process, and have the appropriate finance or legal adviser review responsibilities where needed. This article is an implementation checklist, not legal or financial advice about a business sale.
Create a list of open items with named owners and evidence required for closure. “Payment account checked” is weak evidence if it only means someone can view a dashboard. A better entry describes which account is linked, who is authorised to operate it and what change the provider has confirmed or still requires.
Complete the correct ownership route
For an existing user, Shopify’s documented route begins in Settings > Users and works through the current owner’s role and relevant store. For a new owner outside the business, the documented route begins in Settings > General and sends an invitation. Follow the current prompts and any authentication requests in the actual account.
Record the status after the action. An invitation sent is not an invitation accepted, and a message about a transfer in progress is not proof of completion. Keep those states distinct in the project notes. If the receiving party declines or cannot accept, investigate the reported state rather than repeating the action without understanding it.
After acceptance, verify the owner shown in the admin and the incoming owner’s access. Review any remaining permissions and organisation implications relevant to the store. Keep only the former team’s access that is explicitly needed for the agreed transition period, and record when it will be reviewed again.
An illustrative founder handover
Imagine a UK homeware business where a founder is handing day-to-day ownership control to another authorised company director. The incoming director already works in the admin, but the founder still holds the owner role and receives domain-renewal notices. This is an illustrative scenario, not a reported StoreBuilt client case.
The team confirms the intended owner, checks authentication and reviews billing and notification contacts before making the change. After the role moves, it verifies the recipient’s access and separately updates the domain contact arrangement. No one assumes that the ownership action automatically completed every surrounding account change.
If the same business were merely replacing its development agency, transferring the owner role could be unnecessary. The agency would instead receive or lose the appropriate collaborator access. Defining the transition at the start prevents a permissions task from becoming an avoidable ownership project.
Verify the store can still operate
The incoming owner should complete practical checks that reflect the business’s daily work. Confirm access to orders and settings, the intended notification recipients, the relevant billing surface and the teams responsible for fulfilment. Use existing evidence or authorised test procedures rather than placing unplanned real orders or moving money just to test access.
| Check | Passing evidence | If unresolved |
|---|---|---|
| Owner role | Intended account shown as owner | Keep transfer work open |
| Recipient acceptance | Completed platform status | Follow up through the agreed channel |
| Domain control | Authorised access and contact arrangement | Assign registrar task separately |
| Billing responsibility | Reviewed account details and open charges | Finance owns the exception |
| Operational notifications | Correct destination and test evidence | Fix routing before relying on alerts |
| Former access | Only agreed transition permissions remain | Review with incoming owner |
Capture a short completion record containing the date, store identity, verified owner and outstanding dependencies. Do not write “handover complete” while critical accounts are still awaiting access. The record should allow a future team member to understand what was actually verified without exposing private account information.
StoreBuilt point of view
An ownership transfer succeeds when the incoming business can control and operate the store independently. The button click is a milestone inside that process. Prepare the connected accounts, verify acceptance and close the remaining dependencies with evidence. Our Shopify support service can help organise the technical checks around that transition.