What UK retailers own of their domain, data, design, code and licences when an agency builds the shop or they use it on a subscription.
You own your data, the content you created yourself and your domain, provided you are registered as its holder. For the design and custom code, you only have the rights your contract grants you. Under German copyright law, which this article describes, copyright itself cannot be transferred. An agency can only grant you usage rights: non-exclusive or exclusive, limited or unlimited. If the contract says nothing specific, the purpose of the contract decides. And people usually only argue about that purpose once things have already gone wrong.
The shop platform never belongs to you. You use it under a licence. Shopware 6 is freely available as software under the MIT licence. Above €1 million in gross merchandise volume per year, Shopware’s fair usage policy requires a paid plan. Shopify is a rented platform: your shop runs there as long as you pay. You can take your data with you, not the shop as a whole.
With a shop subscription, the clause on the end of the term decides everything. With shop25, the shop subscription from solution25 starting at €299 per month plus VAT, the usage rights to the shop pass to you after the minimum term of 24 months, according to the shop25 offer page.
This article is for managing directors, e-commerce managers and founders who want to know what they will own before signing an agency or subscription contract. You get an overview of every building block of an online shop, the legal basics, four exit scenarios and a contract checklist. The legal parts refer to German law and the EU General Data Protection Regulation (GDPR). This article is not legal advice. Have a specific contract reviewed by a lawyer in your jurisdiction.
“The shop is mine” is a sentence we often hear in first conversations. It sounds clear, but it is not. An online shop is not a single thing. It is a bundle of building blocks, each governed by different rules. Three terms help bring order to this.
In everyday language we say ownership when we can freely dispose of something. Legally, the word fits an online shop only to a limited extent. Under German law, ownership in the strict sense applies to physical things, such as a server. Code, design and copy are works, and customer data is information about people. Different rules apply to these building blocks.
A usage right is permission to use someone else’s work in a certain way. Whoever creates the design or code remains its author. You, as the client, receive usage rights, and their scope is set out in the contract or follows from the purpose of the contract. This is the building block that causes the most disputes when you switch agencies.
A licence is contractual permission to use something, usually granted by the maker of a piece of software: Shopware, a plugin vendor, Shopify, a theme developer. Every licence has a licensee. Who that is determines whether you can keep using the software after switching agencies.
| Building block | Who typically owns it | What matters |
|---|---|---|
| Domain | The registered domain holder | Who is registered with the registry |
| Customer data and orders | You are responsible for them as the merchant | Access, export format, return at the end of the contract |
| Product data, copy, images | Whoever created them or holds the rights | Usage rights to agency content and stock photos |
| Design | The author, you receive usage rights | Scope and duration of the usage rights |
| Custom code | The author, you receive usage rights | Right to modify and handover of the source code |
| Shop platform | The vendor | Licence model and plan |
| Plugins, apps, themes | The vendor | Who the licensee is and whether the licence can be transferred |
| Hosting and accounts | The respective contracting party | In whose name contracts and logins are held |
If you want to decide freely about your shop in the end, you need to secure each of these building blocks separately. The following sections go through them one by one.
For customer data, the situation is clearer than for code and design. The GDPR distinguishes two roles. The controller is whoever determines the purposes and means of processing personal data (Art. 4(7) GDPR). The processor is whoever processes data on behalf of the controller (Art. 4(8) GDPR).
In an online shop, you as the merchant are the controller. You decide which data you collect at checkout, what you use it for and how long you keep it. The agency and hosting provider that run the shop for you are usually processors. This requires a data processing agreement that sets out, among other things, the subject matter, duration, nature and purpose of the processing (Art. 28(3) GDPR).
Art. 28(3)(g) GDPR requires the processor, at the end of the services, to delete or return all personal data at the choice of the controller, unless the law requires storage. So you have leverage to get your customer data back. But the regulation does not say in which format, how quickly or at what cost. That is exactly what belongs in your contract.
Keep statutory retention requirements for accounting records in mind. Clarify with your tax advisor which data you must keep and for how long before you shut down an old shop.
With Shopware on your own or a rented server, you have direct database access with the right login. A full database dump then takes minutes. Shopify offers no database access. You export through the admin as CSV or read data through the API. Both work, the routes are just different. On Shopify, plan extra steps for images, metafields and app data.
Product data you maintained yourself belongs to you. That also applies on rented platforms. Shopify states in its terms of service that it does not claim ownership of the materials merchants upload. Shopify does, however, take a licence to operate its services. That is common and necessary so your shop can be displayed at all.
Things get more difficult with content that others created for you.
Category copy, guides and product descriptions written by an agency can be works protected by copyright. You then need usage rights. Without a clear rule, the purpose of the contract usually covers use in the shop. Whether you may also use the same copy on marketplaces, in a catalogue or in a second shop remains open.
The same applies to photos. If the agency hires a photographer, the chain of rights must be intact: from the photographer to the agency and from the agency to you. Ask specifically whether the photos may also be used on Amazon, on social media, in ads and in print.
Stock photos are tied to the licensee. If the agency licensed an image with its own account, you may not be allowed to keep using it after a switch. Manufacturer images are subject to your supplier’s terms. If you want to work cleanly, keep a simple list: image, source, licensee, permitted use.
Hypothetical example: A merchant has the agency create 300 category texts and 1,200 product photos. The contract only says “creation of an online shop.” Three years later, the merchant switches agencies and wants to use the content for an Amazon presence. Whether that is allowed now depends on how the purpose of the contract is interpreted. One sentence in the contract would have prevented the question entirely.
Design and custom code are the building blocks where the word “own” is most misleading. The German Copyright Act (Urheberrechtsgesetz, UrhG) regulates this clearly, but differently from what many clients expect. The following explains the principles of German law. It is not legal advice and does not replace a review of your contract. If your contract is governed by another country’s law, different rules may apply.
Under Section 29(1) UrhG, copyright cannot be transferred, except by inheritance. Even if you paid for the development in full, the developer or designer remains the author. What can be transferred are usage rights. Section 29(2) UrhG refers to Section 31 UrhG for this.
Section 31(1) UrhG allows usage rights to be granted for individual or all types of use, as a non-exclusive or exclusive right, and limited in territory, time or content. The difference between the two forms is crucial for merchants:
Section 31(5) UrhG is particularly important. If the types of use are not individually named in the contract, the scope of the rights is determined by the purpose of the contract that both parties had in mind. When in doubt, you only receive the rights you need for the agreed purpose. A contract for the “creation of an online shop” certainly covers running the shop. Whether it also allows another agency to rework the code, or allows you to use the design in a second shop, is open.
Sections 69a and following UrhG apply to computer programs. Programs are protected in any form, including preparatory design material (Section 69a(1)). The ideas and principles behind them are not protected, including those behind interfaces (Section 69a(2)). Under Section 69c UrhG, anyone who reproduces, modifies, distributes or makes the program publicly available needs the consent of the rights holder. For you, this means: if another agency is to develop a custom plugin further later on, you need the right to modify it. Without that right, the source code is of limited use to you.
An agency works with its own building blocks: a base theme, libraries, modules it uses for many clients. It is fair that it only grants a non-exclusive usage right to those. Otherwise it could no longer use its own work. The clean solution separates two kinds of code:
A usage right without access to the source code does you little good. Agree that the code is kept in a repository you can access, or that it is handed over in full at the latest when the contract ends. This includes short technical documentation and the login details for all services the code uses.
The legal rules described here are German law. UK copyright law has its own rules. If your contract is governed by the law of England and Wales or Scotland, have it reviewed by a UK solicitor. In the UK, the UK GDPR applies, which largely mirrors the EU rules on controllers and processors described above. Prices in this article are net. In the UK, VAT is 20 % at the standard rate, with reduced rates of 5 % and 0 % for certain goods. If you ship to the EU, customs and VAT rules apply to those orders, and your shop has to handle them correctly. Those settings and integrations are part of what you should own and be able to take with you.
The software your shop runs on belongs to the vendor. You use it under a licence. For the question “who owns your online shop?”, what matters is not who owns the software, but in whose name the licences are held and whether you can keep running the shop without the agency.
According to its official GitHub repository, Shopware 6 is free and released under the MIT licence. The MIT licence is very permissive: you may use, modify and distribute the software. Shopware also offers paid plans. According to its German pricing page, these are Rise from €600 per month, Evolve from €2,400 per month and Beyond on individual quotation, each plus VAT. Under the fair usage policy, you need a paid plan if the shops linked to your account generate more than €1 million in gross merchandise volume in the preceding 365 days. According to Shopware, you can continue to use the Community Edition software independently.
The critical point with Shopware is the Shopware Account. Your shop, its licence domain and all licences for extensions are registered there. According to the Shopware documentation, an entire shop or individual licences can be transferred to another account through a licence transfer wizard. Shopware’s sales team reviews the request, no transfer is possible with a negative balance, and invoices already issued remain with the previous holder. If your agency bought plugins in its own account, you will need its cooperation when you switch.
Our recommendation: create the shop in your own Shopware Account and buy extensions there. The agency works with its own login. What extensions cost is explained in our article on Shopware costs.
WooCommerce is a licence-free plugin for WordPress. Paid extensions have their own licences with their own terms. The same applies here: buy licences in your company’s name, not the agency’s.
Shopify is software as a service. You rent the platform, and Shopify takes care of hosting, security and updates. Under its terms of service, the shop owner is whoever signs up for the service. If you sign up on behalf of your employer, your employer becomes the shop owner. Make sure your company, not the agency, opens the shop. Agencies then work with their own logins.
According to the terms of service, a theme from the Shopify Theme Store is licensed for one shop only. Apps are subscriptions tied to your shop. You can download your customised theme, but it only runs on Shopify. A later move to Shopware or WooCommerce therefore means a new shop into which you migrate your data. That is not a flaw but the other side of the model: in return you get a platform whose technology you do not have to worry about. Which system suits which requirements is compared in our article Shopify or Shopware.
The domain is the building block that is easiest to secure and most often registered incorrectly. Many agencies register domains for clients because it is faster. Sometimes the agency’s name ends up in the holder field.
DENIC, the registry for German .de domains, recognises the registered holder as the domain holder. According to DENIC, that applies even if it was agreed verbally or otherwise that you should actually be the holder. In that case, you have to settle the matter directly with the registered holder. DENIC cannot help. A so-called DISPUTE entry can prevent the domain from being transferred to third parties in the meantime. Registries for other country domains and for .com have their own rules, but the principle is the same everywhere: whoever is registered controls the domain.
A transfer to another provider requires a transfer code, called AuthInfo at DENIC. It goes to the domain holder. If you are not registered, you cannot move your domain to another provider yourself.
So check today who your domain is registered to. The easiest way is to ask your agency directly for written confirmation of who is registered as the holder.
There are two hosting models. Either you sign the contract with the hosting provider yourself and the agency gets access. Or the agency provides hosting as part of its service, as with many subscription models. The second model is convenient but shifts control. Then the contract has to say how the shop moves to another host when the contract ends. You can read more about the models in our article on e-commerce hosting.
The rule of thumb: accounts belong to your company, and the agency gets personal logins with the permissions it needs. Avoid shared passwords by using a password manager. Then you can revoke access easily when you switch, without anything coming to a standstill.
Whether a contract is good shows at the end. The following four scenarios are typical cases and should be read as hypothetical examples. They show how differently a switch of agencies can go, depending on what was agreed beforehand.
Domain, Shopware Account and payment providers are in the merchant’s name. The code is in a repository the merchant can access. The contract grants an exclusive usage right to the custom development, including the right to modify. The switch consists of giving notice, revoking logins and onboarding the new agency. The new agency reads its way into the code instead of rewriting it.
The shop runs on the agency’s server, the plugins were bought in its Shopware Account, the domain is registered to it. The contract says nothing about usage rights. Now the negotiating starts. Sensible steps:
In the worst case, rebuilding is faster than fighting over the old code. You still get your data back.
With a subscription, the agency pre-finances the build and earns it back through the monthly fees. If you want to leave before the minimum term ends, you will usually have to pay the remaining fees or agree on a buyout. What rights you have until then is governed by the contract. You get your data back here too, but not necessarily the shop as a whole.
If shop ownership lies with the merchant, switching agencies on Shopify is easy: remove the old login, set up a new one. Switching platforms, on the other hand, is a new project. Data moves via export and import, theme and apps do not. How such a migration works is described in our article on moving from Shopware to Shopify, from the opposite direction.
Whatever the scenario: document the handover in a record. It should include the database dump, media files, source code, documentation, a list of all licences with their licensees, all logins and the status of the domain. Signed by both sides, with a date.
With a shop subscription, you do not pay a large project price but a fixed monthly fee. The agency carries the risk of the build. That is why it usually keeps the rights to the shop during the minimum term. What happens afterwards is the interesting part. There are three models on the market:
None of these models is bad in itself. What matters is that you know which one you are signing. Our article on renting an online shop calculates when a subscription pays off.
shop25 is the shop subscription from solution25. A team builds the shop on Shopware, WooCommerce or Shopify and keeps running it afterwards, starting at €299 per month plus VAT. There are three packages: Scale, Pro and Enterprise. According to the German-language shop25 offer page:
The last point shows why a close look pays off: some services are tied to the term, others pass to you. Ask for the offer to state specifically which components the usage rights cover and how the handover works. We recommend that with every provider, including us. The Black Week conditions from 23 November are listed on the shop25 page.
You can place this list next to any agency or subscription contract. If a point is missing, ask before you sign.
| Clause | What it should say |
|---|---|
| Usage rights to custom development | Exclusive, unlimited in time and territory, with the right to modify and to pass on to third parties |
| Usage rights to standard components | Non-exclusive, perpetual, with the right to modify for your shop |
| Timing of the transfer of rights | On acceptance, on payment or after the minimum term, clearly stated |
| Design, copy, photos | Use outside the shop too: marketplaces, social media, advertising, print |
| Source code | Repository with your access or complete handover when the contract ends |
| Documentation | Technical documentation of customisations and interfaces |
| Domain | Your company as the domain holder |
| Licences | Shopware Account, plugins, apps and themes in your company’s name |
| Data processing | Agreement under Art. 28 GDPR, with return of data in a named format |
| Data export | Format (e.g. database dump, CSV), deadline and cost |
| Hosting move | Cooperation in moving to another host, with a deadline |
| Term and termination | Minimum term, renewal, notice period, buyout for early exit |
| Handover | Handover record and support during a switch at an hourly rate |
A good contract covers all of this on two pages. If your provider dodges these points, that tells you how the exit will go later. More selection criteria are in our article on finding a Shopware agency.
Not automatically. Under German law, copyright stays with the developer (Section 29 UrhG). You receive usage rights whose scope the contract defines. If it says nothing, the scope follows the purpose of the contract. Agree on usage and modification rights and the handover of the source code explicitly.
As the merchant, you are the controller under the GDPR. The agency or platform processes the data on your behalf. When the contract ends, a processor must delete or return the data at your choice. The format and deadline should be in the contract.
Your data, yes. The shop as a whole, no. Theme and apps only work on Shopify. A switch means rebuilding the shop on Shopware and migrating products, customers and orders.
The registry recognises the registered holder. You have to settle the transfer with the agency. For German .de domains, a DISPUTE entry with DENIC can prevent the domain from being transferred elsewhere in the meantime.
According to the shop25 offer page, the usage rights to the shop pass to you after the minimum term of 24 months ends. Which components this covers in detail is stated in your offer. Ask about it in the consultation.
Project or subscription: before we start, we go through with you which rights, accounts and data are yours and what happens if you switch. In writing, before you sign. If you are looking for a shop at a fixed monthly price, packages and terms are described on the shop25 page of solution25. If you already have a shop and are unsure who the domain, licences and logins are registered to, we can go through it with you in a shop analysis. For anything else, reach us via the contact form.

Besar Bilalli is co-founder and Co-CEO of solution25, the Shopware agency based in Bremen. Before founding the agency in 2017, he and Besnik Bilalli built their own online store without any startup capital and grew it to more than 500 orders a day. Since then, he has guided merchants through Shopware projects, from platform selection to day-to-day operations. He’s happy to answer questions about this article personally: get in touch.
Responsible for content and updates: Besar Bilalli. Last updated: November 2026. Next content review: February 2027.