Shopware Development for Mid-Market and B2B

It depends mainly on the scope of customisation, the number and complexity of interfaces to ERP, PIM or CRM, B2B logic such as customer groups and approval flows, data migration and the team model. That is why we start with a Discovery phase: afterwards you know the scope, architecture and budget range before development starts. No surprise bills. No hidden fees. Ever.

A single plugin is often ready after a few sprints; a new store or a migration takes correspondingly longer. We fix the timeline after the Discovery phase and work in 14-day sprints, so you see working software every two weeks.

Plugins run inside your Shopware installation and suit deep changes to logic and data model, but need self-hosting or PaaS. Apps talk to Shopware through webhooks and the Admin API, also work with Shopware in the cloud, and can be updated independently of the store. Which one fits depends on your hosting and the size of the change.

Yes. We start with a code and architecture audit: which plugins can be updated, where the core was changed, which dependencies exist. Afterwards you know what stays, what needs rework and in which order.

We develop to the Shopware coding standards, never change the Shopware core and keep customisations inside plugins or apps. Automated tests in the CI/CD pipeline show before every update whether everything still works.

You do. All code, IP and assets created during the engagement are fully transferred to you at project completion. We sign an IP assignment agreement as part of the contract.

Yes. Shopware 5 is no longer developed by the vendor and no longer receives security updates. For GVB-geliMED we did not migrate the store one-to-one but rebuilt it on Shopware 6, with a new concept and new features.

Yes. For HOBA we built a B2B product configurator for Shopware. Typical B2B requirements are customer groups and individual prices, quote and approval flows, quick order and the connection to your ERP.