Looking for Shopware licence pricing – what the platform itself costs per edition? That's a different question, and this article doesn't answer it. Head to what a Shopware shop costs instead, where we separate licence, project and running costs. This page is about what it costs to have a plugin built for your shop.
Depending on scope, a custom-developed Shopware plugin costs between roughly €990 for a compact feature and several thousand euros for complex solutions with their own configuration interface and integrations. As a rough guide: a plugin with one clearly defined job starts at around €990, one with its own admin interface from about €1,680, and a full-scope plugin with admin interface and an integration from €2,900. Anything beyond that is billed by effort at €79/h. Why the range is so wide – and when the investment pays off – is what we'll look at honestly here.
The short version
- Cost: A compact plugin starts at €990, €1,680 with its own admin interface, €2,900 for a full-scope plugin with admin area and integration. Anything larger by effort.
- Hourly rate: Complex plugins are billed transparently at €79/h.
- Biggest cost driver: Integrations with external systems and the admin interface — not the visible core feature.
- Break-even: A €990 plugin beats a €180/month subscription stack after 6 months, a €60/month subscription after 17. A €2,900 plugin needs a good four years against €60/month.
- Updates: Major versions like 6.6 → 6.7 cost adjustment work — most of all for plugins with their own admin interface.
- Play it through: The configurator on our pricing page shows how scope and price relate.
Why there's no fixed price per plugin
Prices are net in euros, charged from Germany. Plugin budgets depend far more on the feature than on the country you buy in.
"What does a Shopware plugin cost?" is one of the most common questions shop owners ask us. And the short answer is: it depends – but not in a vague way, rather on very concrete, traceable factors.
A plugin is ultimately a piece of software that hooks into your shop at defined points. Whether it just shows a small note on the product page or builds a complete connection to your inventory management system is the same kind of difference as between a flat-pack shelf and a custom-built kitchen. Both are "furniture" – and yet a zero easily separates them in price.
At its core, the price comes down to development effort: the more features, edge cases, interfaces, and integrations, the more hours go into concept, implementation, and testing. That's why we bill transparently by hourly rate – and give you a reliable range beforehand so you know where you stand.
Price ranges by plugin type
To give you a realistic picture, here are our typical entry prices by plugin type. These are guide values from our projects – not a rigid price tag, but honest orientation:
| Plugin type | Example | Price (guide value) |
|---|---|---|
| Compact plugin, one feature | Shipping note based on postal code, custom badge, small checkout tweak | from €990 |
| Plugin with admin interface & configuration | A feature the shop owner can switch on and off themselves in the backend | from €1,680 (€990 base + €690 interface) |
| Full-scope plugin | Several features, with its own admin area and one integration already included | from €2,900 |
| Integration with a third-party system | Connection to inventory management, a shipping provider, or an external system | €1,400 as a building block |
| Complex plugin billed by effort | Multiple interlocking features, extensive logic, store publication | effort × €79/h |
The building blocks can be combined – but watch one point we end up explaining in nearly every first call: as soon as you need an admin interface and an integration together, the "custom plugin" package at €2,900 is cheaper than stacking both onto the €990 compact package (990 + 690 + 1,400 = €3,080). In the custom package both building blocks are already included. You can play it through in the configurator on our pricing page – there you'll see directly how scope and price relate.
What drives the price
Five factors ultimately decide where your plugin lands in that range:
- Scope of features: Every feature that has to be thought through, built, and tested costs time. A single, clearly defined job is considerably cheaper than a bundle of many small special requests.
- Admin interface: If your team should be able to configure the feature themselves in the backend – change values, switch things on and off, maintain rules – it needs its own configuration page. That interface adds around €690, because behind it sit forms, validation, and save logic.
- Integrations: As soon as your plugin has to talk to another system – inventory management, ERP, shipping provider, payment provider – the effort for that connection is added. Third-party interfaces are rarely as cleanly documented as you'd wish – and that effort is exactly what makes integration plugins their own cost block.
- Multilingual support: If you sell in several countries, texts, outputs, and configurations have to be translatable. That's no black magic, but it noticeably increases the testing effort.
- Store review: If you want to offer your plugin in the official Shopware Store, it has to hold up to Shopware's guidelines and code review. That's additional work on quality, documentation, and compatibility – but worth it if you want to market the plugin yourself.
Top tip
The most expensive part of a plugin is rarely what the customer sees. It's the edge cases: what happens with an empty cart, with two languages at once, with an abort in the middle of the process? This is exactly where cleanly built software separates itself from the kind that comes back to bite you in six months.
Break-even against the subscription: worked out per price tier
For many features there are ready-made plugins in the store – often for a monthly or annual fee. Individually that seems harmless. But let's actually run the numbers.
Say you use three subscription plugins at €60/month each. That's €180 a month, so €2,160 a year. Over five years that adds up to €10,800 – and afterwards you own not a single one of them. Cancel, and the features are gone.
- three subscription plugins at €60/month over 5 years
- €10,800
- what you own at the end of it
- €0
Blanket claims like "you're in the black after two years" are nonsense all the same – it depends entirely on which price tier you're weighing against which subscription. The break-even is simple: one-off price divided by monthly fee = months to break even. Here are our price tiers against three realistic subscription levels, rounded up to full months:
| Your own plugin | vs. €30/month | vs. €60/month | vs. €180/month |
|---|---|---|---|
| Compact, €990 | 33 months | 17 months | 6 months |
| Compact + admin interface, €1,680 | 56 months | 28 months | 10 months |
| Custom, €2,900 | 97 months | 49 months | 17 months |
Read the table from right to left and the decision gets easy:
- If you're replacing several expensive subscriptions at once (right-hand column), even a custom plugin pays for itself in about a year and a half – a compact one in half a year.
- If you're replacing a single €60 subscription, the compact plugin is through after roughly a year and a half. A €2,900 plugin, on the other hand, needs a good four years – which is only a good idea when you can't buy the feature that way at all.
- Against a €30 subscription, essentially only the compact tier makes sense. At 97 months – eight years – your shop's business model has probably changed before then.
Important: this math only counts money. Two things come without a price tag and often weigh more in practice – the feature fits your process exactly (instead of at 80%), and the source code belongs to you. If the subscription vendor shuts down or discontinues the plugin, your feature is gone; your own plugin stays.
As a rule of thumb from this table: from around €30–40 in monthly subscription fees with a permanent need, it's worth looking at your own solution – below that practically never, above it almost always.
We've laid out the underlying idea in more detail in our article on having a Shopware plugin developed instead of paying a subscription. And if you want to know what expensive premium subscriptions actually offer and how much of it you could build yourself, take a look at Shopware hidden features and premium plugins. The most common trigger for a custom plugin, by the way, is connecting your own systems – what that looks like concretely is in our post on connecting Shopware to your ERP.
A worked example from practice
To make the numbers tangible, here's a typical scenario we run into often. A shop wants customers to automatically receive a discount code for their next purchase above a certain order value – configurable from the backend, in German and English, with a connection to their existing newsletter service.
Break it down and a traceable picture emerges:
- Core feature (generate and output the code): compact plugin, base from €990.
- Admin interface (set the order value threshold, discount amount, and validity yourself): €690.
- Newsletter service integration (hand codes over automatically): €1,400.
- Multilingual support: €290 for translation and the extra testing effort.
Added up individually that would be €3,370. But because an admin interface and an integration come together here, the "custom plugin" package is the better route: €2,900 with both building blocks included, plus €290 for multilingual support – €3,190 one time. That's exactly how the configurator works it out too.
What does that mean against the subscription alternative? Three or four tools that together do the same thing realistically land at €180 a month. €3,190 divided by €180 is 18 months to break even – from then on you save every month, and the code belongs to you. You get exactly this breakdown from us upfront, so you can decide which building blocks are worth the price to you and which aren't.
What updates cost: the jump from Shopware 6.6 to 6.7
"Paid once, sorted forever" would be a lie, and most quotes stay quiet about exactly this part. Shopware ships major versions with breaking changes – code that worked before doesn't afterwards. For the jump from 6.6 to 6.7 that includes:
- The administration runs fully on Vue 3 (out of compatibility mode, state management moved from Vuex to Pinia). Practical consequence: a plugin with its own admin components effectively needs two editions – one for 6.6, one for 6.7. That's precisely why the admin interface is the most expensive building block not just to build, but to update.
- Payment and shipping methods need a
technicalName. Skip it and you get a placeholder assigned – which catches up with you later. - Symfony and libraries move along with it (DBAL 4 and PHPUnit 11 among others). Deprecated Symfony services fall away, and whoever used them has to rebuild.
- Structures were removed in the storefront, parts of the generic page loading among them. Templates that hung on those run into nothing.
What that means for you hangs on almost exactly one question: how deeply does your plugin hook into Shopware? A compact plugin that outputs a piece of information and has no admin interface of its own usually gets through with small adjustments. As soon as custom admin components, payment methods, or deep template overrides are involved, it turns into real work, which we bill by effort at €79/h.
So, two honest notes. First, "override as little as possible" isn't a developer quirk, it's the direct lever on your update costs. Second, the same effect applies to bought plugins – except there you keep paying rent and additionally wait for the vendor to catch up. In practice it's worth holding off on a major version until the extensions you depend on are actually compatible.
What a Shopware agency charges for a plugin
If you're comparing quotes, you'll find three billing models – and very different numbers for the same job:
- By effort at an hourly rate. Rates vary widely in the market – by size, location, and the provider's overhead. We bill at €79/h. The advantage of this model: you pay exactly for what was done. The drawback: without a solid effort estimate upfront, you don't know what you're heading into. So always ask for a range with an upper and lower bound, not just an hourly rate.
- Fixed price per package. That's our route for everything that can be planned – €990 compact, €2,900 custom, building blocks with clear prices. You know where you stand beforehand.
- Day rates with a minimum booking. Common with larger providers. For a small plugin you quickly pay for a whole day even though it was half of one.
What you should ask about every quote, regardless of price: Do I own the source code? Is documentation included? What does it cost when Shopware releases a new major version? A cheap quote with no answer to the third question isn't a cheap quote.
Running costs: what comes after the purchase
Your own plugin is paid for once – but "once" doesn't mean "maintenance-free forever." There are no licence fees and no extra server costs (the plugin runs along on your existing shop hosting). What remains is the maintenance effort at major versions that we broke down above.
The difference from a subscription is fundamental all the same: with a subscription you pay continuously, whether anything changes or not. With your own plugin you only pay when work actually comes up – and you decide when. If your shop is under a maintenance agreement anyway, those adjustments run along with it; what that looks like is on our Shopware service page.
When your own plugin is NOT worth it
Honest stays honest – and we'll actively advise against it when the math doesn't work out. Your own plugin tends not to be worth it in these cases:
- The feature is standard and changes constantly. Connections to services that frequently rebuild their interfaces (some payment or marketplace providers) are often better off as a subscription – because someone else handles the ongoing maintenance there.
- You only need the feature briefly or as a test. For a time-limited project or a trial, a subscription you can cancel monthly is simply cheaper.
- A store plugin fits 100%. If a ready-made solution genuinely covers your requirement completely and the price is fair, there's no reason to reinvent the wheel. It only gets critical when the one decisive requirement is the one that's missing.
- The savings potential is too small. If you pay €10/month for a plugin and rarely need it, custom development never pays for itself – even the compact package would take over eight years. When in doubt, do the sum from the break-even table before you get in touch.
We do exactly this assessment together with you before we build anything. In our projects we often see customers ultimately choose a leaner solution than they'd originally imagined – because they know the numbers.
How we work
You tell us which feature you're missing or which subscription plugin you want to replace. We look at your shop, estimate the effort honestly, and weigh it against your running costs. Then you get a transparent quote with a clear price range – and an honest recommendation on whether the development is worth it for you or not.
If you want to dig deeper, our service page on custom Shopware plugins covers the process, examples, and our approach.
Are you currently paying for Shopware plugins you could actually own – or missing a feature that doesn't exist off the shelf? Let's take a look together in a free initial assessment and do the actual math. It costs you nothing, and afterwards you'll know exactly where you stand.
Frequently asked questions
What does a custom Shopware plugin cost?
A compact plugin with one clearly defined job starts at around €990. With its own admin interface for configuration you’re looking at around €1,680; a full-scope plugin with admin area and integration starts at €2,900. Anything beyond that we bill by effort at €79/h.
When is a custom plugin worth it instead of a subscription?
Divide the one-off price by the monthly fee. A compact plugin at €990 breaks even against a €60/month subscription after 17 months, and against three subscriptions totalling €180 after just 6. A custom plugin at €2,900 needs a good four years against €60/month — which mainly makes sense when the feature doesn’t exist off the shelf. Rule of thumb: from around €30–40 a month with a permanent need, your own solution is worth a look.
Which factor drives the price of a Shopware plugin the most?
Usually not the visible core feature, but the integration with external systems (€1,400 as a building block) and the admin interface (€690) — behind those sit forms, validation and save logic. On top of that come multilingual support and, if you want to offer the plugin in the Shopware Store, the official code review.
Are there running costs with a custom plugin?
No licence fees and no extra server costs — the plugin runs along on your existing shop hosting. A plugin built to the official standards usually survives smaller Shopware updates without intervention. Major versions bring maintenance effort, which we bill by effort at €79/h. So you only pay when work actually comes up — and you decide when.
What does adapting a plugin to Shopware 6.7 cost?
That depends almost entirely on how deeply the plugin hooks in. Shopware 6.7 is a major version with breaking changes: the administration runs fully on Vue 3 (state management moved from Vuex to Pinia), payment and shipping methods need a technicalName, and the Symfony update drops deprecated services. A compact plugin without its own admin interface usually gets through with small adjustments. Plugins with custom admin components effectively need two editions — one for 6.6, one for 6.7. We look at the code and give you a range before we start.