Workflows only you have
Approval stages, calculation logic, discount rules or sign-off paths that come out of your business rather than a manual.
When the standard and the store fall short, we develop the plugin for your Shopware 6 shop. As a self-contained extension that installs and uninstalls cleanly.
Before building something new we check whether it already exists. An existing plugin is almost always cheaper than a custom build. Only when nothing fits does this get interesting.
Approval stages, calculation logic, discount rules or sign-off paths that come out of your business rather than a manual.
Links to ERP, PIM, CRM or accounting. Import, export, reconciliation - with a log, so it stays traceable when something looks odd.
Sometimes only a small thing is missing in one place. A lean plugin then beats rebuilding the theme.
Payment methods or shipping rules with no ready-made extension available.
More than 30 plugins for Shopware 6 are ours and run in shops every day. What we learned about updates, sales channels and support goes into every custom project. Dominic Steiner has worked in e-commerce since 2007, almost ten of those years at shopware AG.
With ALBIS Leasing the leasing application runs right in the checkout, including status checks in the background.
PIM for Shopware is a module of its own in the administration, with bulk editing, import and export.
AI Product Search and AI Product Advisor connect the shop to external interfaces.
Sticky Add to Cart and Variant Preselection change product page and listing without touching the theme.
The Plugin Update Manager and the Database Cleanup work with backups, logs and scheduled tasks.
The Loyalty Program calculates points, tiers and rewards across orders.
A plugin should install and uninstall without leaving traces. That is not a given, and it is the main reason we build separate extensions instead of touching the core.
We hook in through events, decorators and subscribers. A Shopware update affects the plugin, not the other way round.
Settings can be set per sales channel so one client does not inherit another one configuration.
Whatever customers read in the shop lives as a snippet and can be changed without a developer. That covers German and English.
Removal tidies up after itself. What data stays is your decision, not an accident.
A Shopware plugin consists of several parts that have to fit together. We use the ways Shopware 6 offers for this instead of adding special solutions next to them.
Business logic as services, hooked in through events, subscribers and decorators. Data lives in its own tables and is read and written through the Data Abstraction Layer.
Dedicated areas in the Shopware administration, with lists, forms and permissions per user role.
Twig templates and JavaScript that fit into the existing theme. Texts are available as snippets.
Imports, synchronisation and mails run through scheduled tasks and the message queue, so the shop stays fast in the foreground.
Custom endpoints in Store API and Admin API as well as connections to external systems via REST, with logging and retries on errors.
Where it fits, we provide custom conditions and actions so you can put processes together yourself.
We do not just deliver code. What belongs to an extension is visible in our own plugins, and the same bar applies to commissioned work.
Every plugin comes with instructions explaining what the settings do and what to do when something jams.
Settings belong in the administration, not in a config file on the server.
You get the sources. There is no dependency tying you to us.
Shopware keeps moving. On request we maintain the plugin across version jumps.
The most expensive extensions come from starting to write code too early.
We talk about the goal, not the solution. It often turns out there is a simpler route.
You get a written estimate of what will be built and what it costs before effort is spent.
You do not see the plugin only at the end, you can steer along the way.
Installation, manual and a walkthrough for the people who will use it.
A number without requirements would be a guess. These four points drive the effort the most. Before we start you receive a written estimate.
An addition in one place is built quickly. A process across product page, cart, checkout and administration takes considerably more.
Every connection brings its own rules, error cases and test data. Good documentation on the other side saves the most.
A few settings are done quickly. A module of its own with lists and editing is a project in itself.
If the plugin should run on Shopware 6.6 and 6.7, we plan for that from the start because the lines differ technically.
Cost, duration, versions and what happens after handover.
That depends on the scope, mainly on interfaces, the interface in the administration and the number of Shopware lines. Before we start you receive a written estimate of what will be built and what it costs. First we check whether a ready-made plugin already exists, because that is almost always cheaper.
A small addition in one place is finished quickly. An interface that synchronises in both directions or a module of its own in the administration takes considerably longer. We state the time frame in the concept, and you see interim versions along the way.
For Shopware 6, usually for the line your shop runs on. If the plugin should cover several lines, for example 6.6 and 6.7, we plan for that from the start.
We do not change Shopware code but hook in through events, subscribers and decorators. Small updates within a line therefore usually work without changes. When moving to a new line, a plugin has to be checked and usually adapted. We take care of that on request.
Yes. You receive the sources and are not tied to us. The plugin also comes with a manual and an introduction.
Yes, if the source code is available and the licence allows changes. Often a small extension of its own next to it is the cleaner solution, because vendor updates then overwrite nothing.
As soon as logic, data or settings are involved, a plugin. It can be installed, updated and removed separately. Pure design belongs in the theme, which is what our template development is for.
We continue to look after existing Shopware 5 shops. For larger new features we recommend moving to Shopware 6, and our migration from Shopware 5 to 6 helps with that.