Shopware 6 Development
Custom Shopware 6 stores, plugins, themes and headless setups — built for B2B pricing, workflows and scale.
Learn more →// B2B software engineering
Shopware stores, custom Node.js & React applications, ERP integration and automation — engineered in-house for industry and B2B.
// What we do
From e-commerce to internal tools and integrations — we design, build and maintain systems for the long run.
Custom Shopware 6 stores, plugins, themes and headless setups — built for B2B pricing, workflows and scale.
Learn more →Maintenance for Shopware 5 and clean migrations to Shopware 6 — products, orders, SEO URLs and custom logic intact.
Learn more →Next-generation web apps and single-page shops — fast React front-ends on Node.js APIs, built to your spec.
Learn more →Connect shop, ERP, warehouse and accounting so data flows once and stays in sync — no more double entry.
Learn more →Automate repetitive work — imports, exports, invoicing, notifications and reporting — with reliable scheduled jobs.
Learn more →Bespoke software for your industry — configurators, portals, dashboards and tools built around your process.
Learn more →// Why Codewerk
// How we work
We map your process, systems and goals, and agree on scope and a fixed estimate.
Architecture, data model and UI are designed before a line of production code is written.
We develop in short iterations with staging previews, so you see progress every week.
Go-live, monitoring and ongoing maintenance — we stay on to keep the system healthy.
// About us
For over 12 years we've built software — with a special focus on e-commerce and custom B2B solutions. Codewerk Solutions is a dedicated team of developers and designers, not a one-person shop.
We cover the full stack — Shopware, Node.js, React and design — under one roof, and we work directly with owners and teams in English and German. From the first estimate to long-term support, one team owns what it ships.
// FAQ
Three things, mostly: Shopware 5 and 6 stores, custom Node.js and React applications, and the plumbing between them — ERP, warehouse and accounting integrations plus the scheduled jobs that keep the data in sync. Almost always B2B, almost always for a company that already sells something and has outgrown the system it started on. If you need a brochure site or a marketing campaign, we are the wrong shop.
We do not publish rates, because one sentence — connect our shop to our ERP — can mean two weeks or six months depending on what your ERP lets us near. After a scoping conversation and a look at your systems you get a fixed estimate for a defined scope, in writing, before anything is built. Where the scope is genuinely unclear we say so and quote the analysis first, instead of inventing a number we would later have to defend.
Nobody can answer that from a short brief, and anyone who does is guessing. What actually drives the timeline is rarely on our side: how fast your ERP vendor answers, whether the product data is clean, who is allowed to sign off. We build in short iterations with a staging preview early on, so you watch progress weekly instead of waiting for a reveal. A date gets committed once the scope is fixed and the dependencies are known — not before.
Usually yes — most of our work is inherited code, not greenfield. We start with a paid look at the codebase before quoting anything, because putting a price on a system we have not read is how both sides end up unhappy. Sometimes the honest result is that your shop is fine and needs two days of fixes rather than the rebuild you were budgeting for. We will tell you that, and you are free to take it elsewhere.
You do. The custom code, the repository and the deployment scripts are yours at handover, and we do not park your business on a proprietary platform you have to keep renting from us. What nobody can hand over is the open source underneath: Shopware, Symfony, React and the rest keep their own licences. Get ownership written into the contract anyway — with us or with anyone else. It is the clause that lets you leave.
Five in-house developers. That is enough for a shop, an integration or an internal tool, and not enough for a twelve-month programme with three parallel workstreams — for that, hire a larger agency and do not let us talk you out of it. What the size buys you is that the person answering your email wrote the code. What it costs you is a queue: sometimes we cannot start next week, and we will say so.
// Let's talk
Send a short brief and we'll reply with next steps and a rough estimate — usually within one business day.