Store setup & configuration
Complete Shopware 6 setup — sales channels, tax, shipping, payment and B2B rules configured correctly from day one.
// Shopware · Development
Custom Shopware 6 stores engineered around your catalogue, pricing and workflows — fast, maintainable and ready for growth.
// What you get
Complete Shopware 6 setup — sales channels, tax, shipping, payment and B2B rules configured correctly from day one.
Upgrade-safe plugins that add exactly the features your business needs, following Shopware standards.
Branded, responsive, conversion-optimised storefronts built on the Shopware theme system.
Shopware as a backend with a React or Vue front-end via the Store API for maximum speed.
Connect Shopware with your ERP, warehouse and accounting so data flows once and stays in sync.
Fast load times, clean SEO URLs and structured data so the shop ranks and converts.
// Why it matters
Codewerk Solutions is a Shopware 6 development agency for B2B and industry. We build complete stores, custom plugins, themes and headless storefronts, and we integrate Shopware with the ERP, payment, shipping and accounting systems you already run. Every project starts with your real process and a fixed estimate, and every line of code is written to be clean, documented and upgrade-safe.
Because we also handle maintenance, updates, performance and SEO, your Shopware 6 shop keeps performing long after launch — not just on go-live day. Whether you're launching your first store, replatforming from Shopware 5, or scaling an existing B2B shop, we build the foundation for successful, growing online sales.
// In detail
What we actually do under the hood — so you can judge the work, not just the promise.
Shopware 6 runs on PHP 8.2+, Symfony and Twig, with a Vue.js administration and MySQL/MariaDB behind it. We extend it the way the platform intends — plugins, apps and app scripts — and never patch the core, so your shop stays updatable. Everything lives in your Git repository with a README that lets another developer set it up in an afternoon.
We agree a performance budget before the first line of code: LCP under 2.5s on the product page, TTFB under 300ms with a warm cache. That means HTTP caching, indexed queries, no N+1 loops in listings, lazy-loaded media in modern formats, and Elasticsearch once the catalogue justifies it.
Clean SEO URL templates, canonical tags, controlled faceted navigation so filter combinations do not burn your crawl budget, product structured data with price, availability and SKU, an XML sitemap and hreflang for multi-language shops. Core Web Vitals are treated as a ranking and a conversion factor, not a report.
// Process
Weekly staging previews, no surprises in month three.
Your process, systems and pricing rules mapped. Scope and budget range in writing.
Data model, integrations and wireframes approved before production code exists.
Weekly staging deploys you can click, with a written changelog.
ERP, payment and shipping connected through a queued middleware with an audit log.
Functional tests, load check with real data volumes, security pass, user acceptance.
Scripted go-live with rollback, then two weeks of close monitoring.
// FAQ
A focused B2B store is typically 3–5 months from kickoff to go-live, including ERP integration. A simple catalogue without integrations can be live in 6–8 weeks. You get a range after the discovery call and a fixed estimate after the concept phase.
Both. Self-hosted (on-premise or your own cloud) gives you plugins, full source access and control over your data. Shopware Cloud is simpler to operate but allows apps only. We recommend based on how much custom logic you need — not on what is easier for us.
Yes — that is core business for us. We connect shop, ERP, warehouse and accounting over REST, CSV/XML or a dedicated middleware service, with queued jobs, retries and an audit log so you can always see what was sent where and when.
Start by assuming the free Community edition, because it is a complete shop and everything we build works on it. You move to a paid edition when you need something Shopware only ships there — the B2B features around quotes, order approvals and employee accounts are the usual reason. Do not buy a licence tier for a feature list; buy it for one feature you can name.
Partly. Price rules per customer group, scale prices and rule-based surcharges are standard and cover a surprising number of B2B cases. Where it stops is the contract price your ERP calculates per customer and article — that has to come from the ERP through an interface, not be maintained twice. Bring us your price logic early; it shapes the architecture more than the catalogue does.
Less time than you fear, but not zero. Realistically: one person who is allowed to decide, a few hours a week to answer questions and click through the weekly staging build, and someone from your ERP side reachable during the integration phase. Projects that run late are almost never blocked on code — they are blocked waiting for a decision nobody is allowed to make.
If you sell a manageable catalogue at list prices and want to stop thinking about servers, Shopify is the honest answer and you should not hire us. Shopware earns its extra complexity where the logic is yours: customer-specific pricing out of an ERP, approval workflows, unit and packaging rules — a shop that bends to your process instead of the other way round.
Send a short brief — we reply within one business day.