Cart
Surcharges & Discounts
Checks rules from the Rule Builder whenever the cart changes and adds matching surcharges, discounts or products.
Plugin development
Shopware plugin development: exactly the feature your shop is missing.
When neither Shopware itself nor a ready-made plugin fits, I build the missing feature as a custom plugin. For more than ten years I have been developing exclusively for Shopware and have built hundreds of plugins. More than 100 of them are available from digitvision in the Shopware Extension Store.
Check first, then build
Does your idea really need its own plugin?
A custom plugin is not always the right way. Before I develop anything, we go through four levels together. The search often ends sooner than you think.
Simple before complex.
If a setting or a ready-made plugin is enough, I will tell you. A new development is only worth it if it gives you something that does not exist yet.
- 01
Shopware standard
Shopware can do a lot on its own: conditions in the Rule Builder, workflows in the Flow Builder, content with Shopping Experiences. If the standard is enough, I show you the setting, and you need no plugin.
- 02
Ready-made plugin
The Shopware Extension Store has plugins for many tasks. A well-maintained plugin from the store is usually up and running faster than a new development and receives updates from its vendor.
- 03
Customize an existing plugin
If a plugin covers almost everything, I add the missing parts instead of starting from scratch.
Plugin customization - 04
Custom plugin
If none of this fits, I develop a plugin that maps exactly your processes. It only steps in where needed and leaves the rest of Shopware untouched.
Where a plugin steps in
What a plugin can change in Shopware.
A plugin can extend almost any part of your shop. Six of my own plugins show how different that looks.
Product page
Product Bundles
Shows a package of several products with its own price on the product page and makes the saving visible.
Customer account
Returns & Return Labels
Adds return registration to the customer account, also for guests, with a DHL or UPS label.
Flow Builder
DHL Shipment Tracking
Reports DHL shipping events to the Flow Builder, which turns them into emails, status changes or notes for your team.
Administration
DATEV Export
Adds its own export page to the Administration: preview, checks and a finished DATEV posting batch for your tax advisor.
Before Shopware
Firewall & Security Suite
Checks every request before Shopware starts and blocks attackers, scanners and bots.
Process
How your plugin is built.
You don’t need a specification. A description of your process and a real example from your daily shop business are enough to start.
- 1
Understanding the requirement
We go through your process with real examples, including the special cases: guest orders, cancellations, several sales channels or languages.
- 2
Concept
I define where the plugin hooks into Shopware and which settings you get in the Administration. Whatever Shopware can already do, I reuse.
- 3
Development with tests
I develop according to Shopware’s guidelines and back the plugin up with automated tests and static code analysis.
- 4
Go-live and beyond
Before going live, the plugin runs in a copy of your shop. Afterwards I remain your contact, including for the next Shopware update.
Quality
How to recognize a good plugin.
Whether you work with me or not: these four points tell you whether a plugin will still run in two years.
No changes to the core.
A good plugin does not change any Shopware files. It uses the intended ways such as events, decoration and template inheritance, so an update overwrites nothing.
Settings instead of fixed values.
Whatever may change is a setting in the Administration, not hard-coded. Small changes then don’t need a developer.
Tested and checked.
Automated tests and static code analysis find errors before they show up in your shop. For my plugins, both run before every new version.
Ready for updates.
Shopware keeps evolving. A maintained plugin is checked and adapted for new versions before you install the update.
Experience
Hundreds of plugins, since Shopware 4.
I have been developing plugins for Shopware since Shopware 4, first at several former employers for Shopware 4 and 5. Since 2018 I have been publishing my own plugins as digitvision, today more than 100 in the Shopware Extension Store.
On top of that come plugins I developed for individual shops that never went into the store. This experience goes into every new plugin: I know where Shopware leaves room and where a plugin causes trouble during updates.
- Mention XML interfaceData exchange between the shop and the Mention ERP system.
- Automatic DHL trackingDHL shipment tracking right in the shop.
- UPS shipping cost calculationReal-time shipping costs via the UPS interface.
- Save cartSave carts, share them via link and load them again later.
- Set configuratorCustomers put together their own combinations, such as a PC.
- Shipping methods per productBlock shipping methods and set surcharges per country.
Reviews
What shop owners say about my plugins.
The reviews are translated from German.
“Now we have had Digitvision develop a custom extension, which also worked without any problems, and we were able to optimize our workflow even further.”
“For developers there are lots of good entry points and plenty of configuration.”
FAQ
Frequently asked questions.
Your question isn’t listed? Give me a call or send me a short message about what you need.
Does my idea really need its own plugin?
Not always. A lot can be solved with the Rule Builder, the Flow Builder, Shopping Experiences or a ready-made plugin from the store. I check that first and tell you honestly if it works without a new development.
What does the effort for a plugin depend on?
Mainly on how many places in your shop the plugin touches, how many settings it needs, whether an integration is involved and how many special cases there are. After our first conversation I estimate the effort and send you a quote.
Will my plugin still work after a Shopware update?
A plugin that extends Shopware only in the intended ways survives most updates without changes. Before larger version jumps I check it in a copy of your shop and adapt it if necessary.
How do you test a plugin before it goes live?
During development with automated tests and static code analysis, then in a copy of your shop. There I run through every process the plugin touches, from the cart to the finished order.
Can I change the settings myself later?
Yes. Anything you want to change later becomes a setting in the Administration, per sales channel if you like. Only what should never change is fixed in the code.
More services
What else I can help you with.
Contact
Tell me what your shop is missing.
Briefly describe what the plugin should do, ideally with an example from your daily business. You don’t need technical terms. I will get back to you with a first assessment.
+49 (0) 234 97354482info@digitvision.de Eike Brandt-Warneke · Hevener Straße 65 · 44797 Bochum, GermanyHelpful: your shop’s address and Shopware version. Please do not send passwords or customer data.
