Custom Shopware plugin development.

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.

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.

Your processes

Workflows only you have

Approval stages, calculation logic, discount rules or sign-off paths that come out of your business rather than a manual.

Interfaces

Connecting your systems

Links to ERP, PIM, CRM or accounting. Import, export, reconciliation - with a log, so it stays traceable when something looks odd.

Missing pieces

Gaps in the standard

Sometimes only a small thing is missing in one place. A lean plugin then beats rebuilding the theme.

Payment and shipping

Your own methods

Payment methods or shipping rules with no ready-made extension available.

From our own development

We do not only build plugins on request.

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.

Payment

Custom payment methods

With ALBIS Leasing the leasing application runs right in the checkout, including status checks in the background.

Data

Large admin modules

PIM for Shopware is a module of its own in the administration, with bulk editing, import and export.

Loyalty

Custom logic in the checkout

The Loyalty Program calculates points, tiers and rewards across orders.

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.

The core stays 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.

Sales channels

Configurable separately

Settings can be set per sales channel so one client does not inherit another one configuration.

Texts

As snippets

Whatever customers read in the shop lives as a snippet and can be changed without a developer. That covers German and English.

Uninstalling

Cleanly gone

Removal tidies up after itself. What data stays is your decision, not an accident.

Technology

Built with what Shopware provides.

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.

Foundation

PHP and Symfony

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.

Administration

Admin modules

Dedicated areas in the Shopware administration, with lists, forms and permissions per user role.

Shop

Storefront

Twig templates and JavaScript that fit into the existing theme. Texts are available as snippets.

Background

Scheduled work

Imports, synchronisation and mails run through scheduled tasks and the message queue, so the shop stays fast in the foreground.

Integration

API and interfaces

Custom endpoints in Store API and Admin API as well as connections to external systems via REST, with logging and retries on errors.

Rules

Rule Builder and Flow Builder

Where it fits, we provide custom conditions and actions so you can put processes together yourself.

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.

Documentation

A manual, not guesswork

Every plugin comes with instructions explaining what the settings do and what to do when something jams.

Admin interface

Configurable without code

Settings belong in the administration, not in a config file on the server.

Handover

The code is yours

You get the sources. There is no dependency tying you to us.

Ongoing work

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.

1 - Conversation

What should come out of it

We talk about the goal, not the solution. It often turns out there is a simpler route.

2 - Concept

Scope and effort

You get a written estimate of what will be built and what it costs before effort is spent.

3 - Build

With interim versions

You do not see the plugin only at the end, you can steer along the way.

4 - Handover

Installed and explained

Installation, manual and a walkthrough for the people who will use it.

Effort

What makes plugin development expensive or cheap.

A number without requirements would be a guess. These four points drive the effort the most. Before we start you receive a written estimate.

Scope

One spot or a whole process

An addition in one place is built quickly. A process across product page, cart, checkout and administration takes considerably more.

Interfaces

External systems

Every connection brings its own rules, error cases and test data. Good documentation on the other side saves the most.

Interface

Settings or a module

A few settings are done quickly. A module of its own with lists and editing is a project in itself.

Versions

One or several lines

If the plugin should run on Shopware 6.6 and 6.7, we plan for that from the start because the lines differ technically.

Frequently asked questions

Frequently asked questions about Shopware plugin development

Cost, duration, versions and what happens after handover.

What does it cost to develop a Shopware plugin?

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.

How long does development take?

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.

Which Shopware versions do you develop for?

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.

Will the plugin survive a Shopware update?

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.

Do I own the source code?

Yes. You receive the sources and are not tied to us. The plugin also comes with a manual and an introduction.

Can you adapt an existing plugin?

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.

What is better: a plugin or a theme change?

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.

Do you also develop for Shopware 5?

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.

Discuss a requirementTell us what is missing. We will say whether something already exists or a custom extension is worth building.
Request a plugin