Shopware, from plugin to platform

Yes. We start with a paid review of code, database, plugins and hosting, and give you a written report with risks and a prioritised plan before any development begins.

Clearly scoped work is quoted as a fixed price. Continuous development runs on a monthly retainer with a transparent hour report. We tell you which one fits.

You do, from the first commit. It lives in your Git repository with documentation that lets another team take over.

If you are already on Shopware 5 and the shop earns money, stay on Shopware 5 until a concrete reason appears — a plugin vendor dropping support, an ERP project, a PHP deadline. If you are starting from nothing, Shopware 6. Nobody should migrate because a version number sounds old. Tell us your reason and we will tell you whether it is a real one.

Anything we say before seeing your shop is guesswork. As an illustration: a single plugin sits in the low four figures, a full B2B store with ERP integration in the mid five figures. What moves the number is never the design — it is how many exceptions live in your pricing, your catalogue and your order process. We quote after the review, not before.

Often yes, and if you have someone who knows Symfony, let them. Shopware is a normal PHP framework underneath. Hire an agency when the work is spiky rather than constant, when you need a second opinion on an architecture decision, or when one person leaving would stop your shop. For a steady stream of small changes, in-house is usually cheaper than we are.

A core hack is a change made directly in Shopware's own code instead of in a plugin. It works on the day it is written and then quietly blocks every update afterwards, because the next release overwrites it or collides with it. Most shops that describe themselves as unupdatable are simply full of them. Cleaning that up is normal work for us. Adding more is not.