You have a strategy, but the horsepower is missing on the road? I translate complex requirements into clean, maintainable code. No hacks, no should-be-fine attitude — engineering at senior level.
I do not do everything. In return, I do these four things properly — with a real senior background instead of clicked-together plugins.
Custom features that fit your processes exactly. No bloated store plugins, but lean, performant code — following Shopware standards, cleanly tested, documented.
Connecting Shopware to ERP (Pickware, Plenty, JTL), PIM or third-party systems. Robust, fault-tolerant and with clean logging — not the thing that gives up at the first edge case.
Your shop is slow? I clean up under the bonnet, fix N+1 queries and optimise the database layer. With profiling, not with gut feeling.
No dull data copy, but a clean re-architecture of your processes in the modern Shopware core. With a plan, risk analysis and phased approach — not a big bang.
Which model fits depends on the project — not on the sales pitch. Here are the three I work with.
When the scope is fixed — new plugin build, interface, clearly defined feature. You know in advance what it costs.
When the path becomes clear as you walk it — refactoring, architecture support, acute performance topics. Billed weekly.
When you need ongoing capacity — architecture support, code reviews, roadmap sparring. Monthly quota, plannable.
Four phases. No waterfalls, no theory — the process that works in practice for Shopware projects.
We define interfaces, data models and risks. You get a spec that any senior developer could work with — not just me.
Clean code following Shopware standards (Symfony-based). Weekly demo branches, code reviews, everything traceable in Git.
CI/CD processes that make sure nothing blows up on release. Staging first, rollback plan always included.
Tideways & Sentry on board. We see errors before the customer notices them — and I am reachable in case something does start smoking.
No logo wall. Here is the honest list — what I touch daily and what you can rely on.
No marketing speak. Three cases where I got hands-on — with what happened technically and what came out at the bottom line.
Migration · API architectureMigration from a monolithic in-house solution to Shopware 6. Construction of a highly secure API layer between Shopware, telemedicine services and the ERP. Focus on strict data integrity and an architecture that withstands the requirements for sensitive patient data (GDPR/audit).
Performance · InfrastructureComplete overhaul of the hosting strategy for maximum performance. Implementation of Redis caching, RabbitMQ queues for asynchronous ERP processes and media offloading via S3/ImgProxy. The result: a system that today scales to 4× the load — at a quarter of the original server costs.
Technological realignment as lead developer for the switch from Shopware 5 to 6. Construction of a scalable infrastructure with Redis and RabbitMQ as well as the design and implementation of a specialised interface for connecting resellers for the B2C market. Stable operation despite complex logistics requirements.
Tell me briefly what you have in mind — plugin, integration, migration or something between the lines. We check technical feasibility, I name the model and budget. Takes 30 minutes.