Shopware training works when it is split by role: content, formats, costs and a plan for UK retailers.
Shopware training pays off when it is split by role. The person who maintains products needs different content than the person who handles orders or builds campaigns. One day for everyone together achieves little. Three short sessions per role achieve more.
Most teams need five topics: the administration and search, products with variants and properties, orders and returns, Shopping Experiences, and the Rule Builder and Flow Builder. Add a clean permission concept so nobody changes settings by accident.
Shopware Academy certifications are aimed mainly at developers and architects. For daily work in the store, the documentation, training on your own system and practised workflows matter more. If you have your store run in the shop subscription, you do not need to learn the technology, updates and hosting yourself.
This article is for managing directors, e-commerce leads and team leads who are introducing a Shopware store or want to bring a grown team to a common level. You will learn which content each role needs, which formats exist, what they cost and what a plan for the first 30 days looks like.
Many training sessions follow the menu of the administration. The trainer clicks through every area from top to bottom, and after four hours everyone has seen everything once. Two weeks later nobody remembers how to create a variant with its own price. That is not the team’s fault. It is the structure.
People remember workflows they carry out themselves and need again soon. Good training therefore starts with the tasks of your daily work: creating a new product with six sizes, booking a partial return, building a campaign page for a sale. Only then comes the question of where that sits in the menu.
Before you book anything, check which of these problems you want to solve. For the first, half a day on your own system is enough. For the second, you need documented workflows and a backup person. For the third, a refresher helps that looks at the functions added since the last update. How the versions follow each other is covered in the article on Shopware updates and versions.
Divide your team into roles before you define content. In small stores one person covers several roles. The split still helps because it shows what is really needed.
| Role | Must be confident with | Only needs to know about |
|---|---|---|
| Product maintenance | Products, variants, properties, media, categories, import and export | Custom fields, dynamic product groups |
| Order handling and service | Orders, status changes, returns, credit notes, customer accounts | Flow Builder, email templates |
| Marketing and content | Shopping Experiences, promotions and discounts, SEO fields, newsletter recipients | Rule Builder, sales channels |
| Store management | Rule Builder, shipping and payment, users and permissions, reports | Extensions, updates, hosting |
| In-house tech or agency | Extensions, updates, interfaces, theme, troubleshooting | An overview of all business workflows |
The middle column is your curriculum. The right column only needs a 20-minute overview. That keeps the training short, and each person practises only what they need next week.
Suppose a retailer for outdoor clothing has four people working on the store: one for products, one for orders, one for marketing and the owner. This is a made-up example, not a client project. Instead of one shared day, the owner plans four sessions of 90 minutes each. Product maintenance practises variants and the CSV import. Service practises returns and partial credit notes. Marketing builds a landing page. The owner sets up roles and learns how shipping rules apply. In the end each person has invested 90 minutes instead of eight hours.
A small shared part is still worth it. It takes about 45 minutes and creates a common language.
If your team does not know Shopware at all yet, the overview What is Shopware? helps beforehand. It explains editions, terms and structure without technical language.
Product maintenance is where most mistakes and most manual work happen. Practice pays off fastest here.
Shopware generates variants from properties such as size and colour. Variants inherit values from the main product until someone removes the inheritance on a field. That is powerful, but also a source of errors. If you enter the price on 40 variants one by one, you later have 40 places to maintain. So practise three cases: generating variants, setting a different price for a single variant and restoring the inheritance.
Custom fields store information that Shopware does not know by default, for example a care instruction or a flag for freight goods. They are grouped in sets and assigned to areas such as products or categories. According to the documentation, the technical name of a set cannot be changed later. So define names cleanly once. For a custom field to appear in the store, a template change is needed. The team should know that a filled field is not automatically visible.
From about a hundred products, importing by CSV is worth it. The documentation gives clear rules: files in UTF-8, semicolon as separator, prices with a decimal point instead of a comma. An import can create and change data, but not remove it. Before the real run there is a test run that shows errors without writing anything. Faulty rows end up in a separate file for correction. Product maintenance should play through exactly this process once from start to finish. The details are in the article on the Shopware CSV import.
These three tools set Shopware apart from simple site builders. They are also the part teams most often leave to the agency, although they could operate it themselves.
With Shopping Experiences, marketing builds home pages, category pages and landing pages from blocks. Important for the training: the difference between layout and assignment. A layout is a template. Only the assignment to a category or a product makes it visible. If you change an assigned layout, you change every page that uses it. So practise duplicating before rebuilding.
The Rule Builder defines conditions: free shipping from 50 euros, purchase on invoice only for existing customers, a discount only for one customer group. A rule is built once and used in several places. The team must understand that a changed rule takes effect everywhere it is attached. A flag such as freight goods can be created as a custom field and queried in a rule. That is how product maintenance and shipping logic work together.
The Flow Builder automates processes after an event, such as an email after an order status change or a tag on the customer account after the first purchase. For service, being able to read the existing flows is enough. Store management should be able to build a simple flow. Which functions are included in which plan is shown in the overview of Shopware costs.
Plan more time for this block than for product maintenance. The operation is explained quickly. Thinking in rules and events needs examples from your own business.
Training without a permission concept is half done. In many stores everyone works with administrator rights because that was fastest at the start. Then someone deletes a shipping method by accident, and nobody knows who it was.
Shopware manages users and roles under Settings, System, Users and permissions. A role bundles rights for areas of the administration. Per area there are the levels view, edit, create and delete. The levels build on each other: edit includes view, create includes edit. On top come additional permissions, for example for clearing the cache, import and export or managing extensions. Administrators have all rights and are not assigned roles.
Each person gets a personal account. Shared logins save no time and make it impossible to trace changes. For external systems there are integrations with their own key. According to the documentation, the secret key is shown only once. The permission concept also covers how customer data is handled. What applies legally is summarized in the article on data protection in the online shop.
There are four ways to build Shopware knowledge. Most teams combine two of them.
| Format | Strength | Weakness | Fits |
|---|---|---|---|
| Official documentation | Free, current, available in English and German | Does not know your store and your extensions | Looking things up, single questions |
| Shopware Academy and learning paths | Structured, self-paced, with an exam | Focus on development and architecture | Developers, technical project leads |
| Workshop on your own system | Practices real workflows with real data and extensions | Costs money and needs preparation | Business teams after launch or relaunch |
| Internal handover | Cheap, close to daily work | Also passes on mistakes and detours | Onboarding new colleagues |
The documentation is divided into sections such as getting started, features, configuration, extensions, and tutorials and FAQs. It is the best source for the question of how a function is meant to work. It does not answer how your store was set up. A workshop on your own system closes exactly this gap.
United Kingdom: For UK shops, three topics belong in the training. First, VAT with the standard rate of 20%, the reduced rate of 5% and the zero rate of 0%, practised on your own range. Second, the handling of customer data under UK GDPR, which fits well with the permission concept. Third, shipping to the EU, where shipping rules and customs information need their own exercise. The prices in this article are in euros.
The Shopware Academy is the official learning offer from the vendor. The learning paths live in the Shopware Community Hub and are designed for self-study, with modules, exercises and practical scenarios.
In November 2026 the certification page lists nine certifications: Backend Developer, Backend Developer Intermediate, Frontend Developer, Frontend Developer Intermediate, App Developer, DevOps Engineer, PaaS Specialist, PaaS Native Specialist and Solution Architect. These are profiles for development, operations and architecture. We did not find a dedicated certificate for daily store maintenance there.
For merchants this means: the Academy is the right place if you train your own developers or want to check the qualification of a service provider. It is not made for product maintenance, service and marketing. What to look for in an agency’s certificates is covered in the article Finding a Shopware agency. If you want to hire developers yourself, the article Hiring Shopware developers helps.
There are no fixed list prices for training on your own system. The price depends on preparation, duration and the number of roles. So calculate with effort instead of a flat figure.
The following numbers are assumptions for your own maths, not a price list. Insert your own hourly rate.
That is 13 hours. At an assumed hourly rate of 120 euros, this comes to 1,560 euros net. Add your team’s working time: four people with 90 minutes of training and 30 minutes of questions each make 8 hours. A shared training day for the same four people ties up 32 hours and usually delivers less.
The need for training drops when technology and operations are not on your side. In the solution25 shop subscription, our team builds and runs the store. According to the current page, the Scale package costs 299 euros per month and the Pro package 499 euros per month, each with a 24-month minimum term and no setup fee. Enterprise is available on request. Scale includes, among other things, 200 products created by us, the setup of payment and shipping, go-live and an introduction, hosting in Germany, security and plugin updates, daily backups and support by ticket or email. Pro includes up to 500 products with variants, a dedicated contact person, a monthly report and phone support.
To be fair: even in the subscription you maintain products and process orders yourself. So you still need the training for product maintenance and service. You do not need to learn updates, hosting and extensions.
A plan with fixed dates beats every good intention. It can look like this:
The step with the self-written guides looks minor, but it is the most important one. Whoever writes down a workflow notices where they are still unsure. And the next new colleague finds a guide that fits your store.
Plan a one-hour refresher twice a year. Shopware releases new versions regularly, and with each one details in the administration change. Combine the refresher with the update: what is new, what affects us, who has to do something differently?
For a business team, 45 minutes of shared basics and 90 minutes per role are usually enough, plus a question session after a few weeks. Full training days are rarely necessary.
The Shopware Academy offers learning paths and certifications. The nine certifications we found in November 2026 are aimed at developers, operations and architects. For daily work in the store, the documentation and training on your own system are the better route.
According to the English Academy page, 999 US dollars per year excluding VAT. It applies to one user and includes one exam attempt per certification per year. Check the current price in the Shopware Account before booking.
Online works well if every person clicks for themselves on their own computer and the group stays small. On site is worth it when several roles work together on one process, for example returns between warehouse and service.
No. You operate product maintenance, orders, Shopping Experiences, the Rule Builder and the Flow Builder without code. You need programming for your own extensions, theme changes and interfaces.
solution25 is a Shopware Platinum Partner from Bremen, Germany, and has worked with Shopware since 2017. We train teams on their own system: split by role, with your products, your extensions and your workflows. In a short call beforehand we clarify who needs to know what, and we say openly when one hour of introduction is enough.
If you are unsure where your team stands, write to us via the contact page. If the store is already running and daily work keeps getting stuck, Shopware support is often the faster route than training. And if you want to hand over technology and operations completely, take a look at the shop subscription.

Henrik Schäfer is a TÜV-certified data protection officer and handles privacy and compliance topics in ecommerce projects at solution25. He helps merchants put privacy requirements into practice without losing sight of conversion. Get in touch
Responsible for content and updates: Henrik Schäfer. Last updated: November 2026. Next content review: February 2027.