Services
Shopware work that lasts
I work as a single developer on Shopware 6 projects — no team in between, no ticket ping-pong. You talk to the person writing the code.
Extensions & integrations
Features Shopware does not ship — built as a proper plugin, not a theme hack.
When a requirement cannot be expressed in the standard, it becomes an extension. It lives in its own plugin, hooks into Shopware's official extension points, and therefore survives the next update. Four of my extensions grew out of exactly this kind of client work and are in the Shopware Store today.
What you get
- An extension as a standalone plugin, configurable from the administration
- Integration with CRM, ERP, PIM or automation services through their APIs
- Flow Builder actions so your team can rewire processes without a developer
- Background processing for large data volumes instead of browser timeouts
- Changelog, upgrade path and migrations for existing installations
A good fit when
- A requirement can only be met through workarounds in the standard
- A third-party system needs shop data without manual exports
- Existing customisations live in the theme and break with every update
Upgrades & migrations
From 6.4 to 6.7 without the store standing still for three days.
Shopware upgrades rarely fail because of the core. They fail because of extensions and custom work. So every upgrade starts with an inventory: what is installed, what of it is compatible, what can be replaced and what gets dropped. Then the upgrade runs on a copy first, never on production.
What you get
- An inventory of every extension and customisation with its compatibility state
- A staging environment cloned from production for the trial run
- The upgrade itself, including database migrations
- Adjustment of custom extensions to changed interfaces
- An acceptance checklist for your team and a rollback plan
A good fit when
- The store runs on a version that no longer receives security updates
- An extension you need only exists for a newer Shopware version
- An earlier upgrade attempt was abandoned midway
Custom store features
Configurators, B2B logic, and a search that finds things despite typos.
Some assortments do not fit a product grid. Cut-to-size ordering, tiered prices per customer group, order processes with approval steps — these are requirements no off-the-shelf extension covers. I build them as part of the store rather than as a separate island beside it.
What you get
- Product configurators with pricing by dimension, material and quantity
- B2B features such as customer group pricing, approvals and quote flows
- Search rollout with OpenSearch, including typo tolerance and filters
- Shipping and pricing logic that goes beyond the built-in rules
- Custom reports and exports for adjacent systems
A good fit when
- Products are priced by size, weight or material thickness
- The store serves business customers with different prices and processes
- The default search fails to find items that demonstrably exist
Operations & maintenance
Servers, updates, and the phone call when something fails at night.
A store is not finished at launch. I run servers, keep Shopware and its extensions current, and am reachable when something breaks. That includes the unpleasant part: cleaning up after a security incident and making sure it does not happen again.
What you get
- Setup and operation of servers for Shopware, including hardening
- Regular updates of Shopware, extensions and system packages
- Automated deployments instead of copying files over FTP
- Backups, restore tests and monitoring
- Analysis and clean-up after security incidents
A good fit when
- Nobody feels responsible when the store is unreachable
- Updates keep getting postponed because nobody knows what will break
- After an incident the store needs to come back cleanly and verifiably
Let us talk about your project
An extension, an upgrade, or a store that has become slow: describe the situation briefly and you will get an honest assessment.