Migration without downtime
Old shop, living catalogue. A big bang over the weekend is not a plan.
E-commerce - Shopware
Shopware that sells.
Shops for DACH and international clients - catalogue, checkout and ERP connections that hold up day to day. No theme polishing without operations.
B2C
B2B
Migration
Plugins
ERP
Where Shopware fits
Retailers and manufacturers who sell across Europe - and whose shop is more than a display window.
B2B complexity
Price tiers, customer groups, quotes - standard themes tear at this point.
Plugin sprawl
Twelve extensions, three of them dead. We clear up before we build further.
ERP & fulfilment
Stock, tracking, invoices. The shop must not be the only source of truth.
What we deliver in Shopware
Storefront, checkout, integrations - and someone for the time after.
Setups & migrations
Shopware 6, data transfer, 301 redirects, payments. Live in slices.
Plugins & themes
Only what the business needs. Custom code where plugins lie.
Integrations
ERP, PIM, payment, shipping. Queues and monitoring included.
Operations
Updates, performance, peak checks. Optional SLA through maintenance.
Approach: sales before feature lists
We start with checkout and stock - not with animations. Whatever keeps revenue running comes first.
- Clarify catalogue, payments, shipping and tax
- Plugin inventory: keep, replace, remove
- Staging with real data, then a cutover plan
- Aftercare after go-live, then regular operations
Typical environment
Shopware 6, custom plugins, a Vue storefront only when it pays off. Often Bitrix or WordPress alongside for content.
How a shop project runs
From the product range to the first real order.
Range & flows
Catalogue depth, checkout, returns. What the shop must never get wrong.
Build
Theme and plugin scope, integrations, test data.
Harden
Performance, payments in staging, permissions, SEO migration.
Live & keep running
Cutover, monitoring, support through the first peak week.
What retailers rely on
Revenue must not turn into a demo.
No fake go-live
Payments and stock are tested - or we do not go live.
European market reality
Tax, parcel stations, payment on invoice: we know the market, no US defaults.
Ongoing care
Updates and incidents after launch - not “good luck”.
Example setup (illustrative)
Step by step move of a shop to Shopware 6: catalogue and customers first, checkout in the second slice, ERP sync through a queue. Goal: no gap in orders, measurably shorter load time in the listing.
Frequently asked questions
Questions from real shop kick-offs.
Shopware or Bitrix?
B2C/B2B with an ecosystem around it: usually Shopware. An existing Bitrix landscape or a close link to CRM: look at Bitrix first. We compare honestly.
Shopware 5 to 6?
Yes, as a project with a data and plugin plan. Not as an “update click”.
Headless?
Only if your channels and your team can carry it. Otherwise storefront first.
Can you build plugins only?
Yes. Or clean up the existing ones. Both are real work.
Who hosts it?
Your hosting provider or cloud. We deliver deployment and checks.
How do we start?
Discovery plus a migration outline with a fixed scope.
More stacks
Related technologies we often use alongside.
Time to switch the shop live?
Catalogue size, target shop and time frame are enough for a first proposal.