Workflows only you have
Approval stages, calculation logic, discount rules or sign-off paths that come out of your business rather than a manual.
Custom plugin development.
When the standard and the store fall short, we build the extension. As a self-contained plugin that installs and uninstalls cleanly.
When it pays off
When the store has nothing for it.
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.
Connecting your systems
Links to ERP, PIM, CRM or accounting. Import, export, reconciliation - with a log, so it stays traceable when something looks odd.
Gaps in the standard
Sometimes only a small thing is missing in one place. A lean plugin then beats rebuilding the theme.
Your own methods
Payment methods or shipping rules with no ready-made extension available.
How we build
Encapsulated so it cannot drag the shop down.
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.
No changes to Shopware code
We hook in through events, decorators and subscribers. A Shopware update affects the plugin, not the other way round.
Configurable separately
Settings can be set per sales channel so one client does not inherit another one configuration.
As snippets
Whatever customers read in the shop lives as a snippet and can be changed without a developer. That covers German and English.
Cleanly gone
Removal tidies up after itself. What data stays is your decision, not an accident.
What comes with it
A plugin without a manual is half finished.
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.
A manual, not guesswork
Every plugin comes with instructions explaining what the settings do and what to do when something jams.
Configurable without code
Settings belong in the administration, not in a config file on the server.
The code is yours
You get the sources. There is no dependency tying you to us.
Also after launch
Shopware keeps moving. On request we maintain the plugin across version jumps.
How it runs
Understand first, then build.
The most expensive extensions come from starting to write code too early.
What should come out of it
We talk about the goal, not the solution. It often turns out there is a simpler route.
Scope and effort
You get a written estimate of what will be built and what it costs before effort is spent.
With interim versions
You do not see the plugin only at the end, you can steer along the way.
Installed and explained
Installation, manual and a walkthrough for the people who will use it.
Discuss a requirementTell us what is missing. We will say whether something already exists or a custom extension is worth building.
Request a plugin