Case Study · F.O.C.U.S.

We don't build shops. We build systems that generate revenue.

Replatforming Handelskönig GmbH from JTL-Shop to Shopware 6 — delivered with the nuonic F.O.C.U.S. framework: from fact analysis to continuous scaling. Because go-live is not a success. It is where responsibility begins.
Handelskönig e-commerce on Shopware 6
FFacts

Reality over assumptions

OObjectives

Clarity before speed

CConstraints

The truth about systems

UExecution

Build, don't discuss

SScaling

Growth is a system

Project at a glance
Client
Handelskönig GmbH
Industry
Retail / Construction & Trade Supplies
Platform
Shopware 6
ERP
JTL-Wawi (JTL-Connector)
Payment
PayPal, Amazon Pay, RatePay
Go-Live
October 2024
Status
Scaling phase (ongoing)
Shopware 6JTL-ConnectorCI/CD PipelineLoyalty SystemTrusted ShopsSEO MigrationKlaviyo
F

Facts— Reality over assumptions

The existing JTL-Shop was limiting growth: restricted frontend flexibility, labor-intensive content maintenance, limited extensibility. The system audit made visible where time and conversion were being lost — and where the technical scaling limits lay. The consequence: the move to Shopware 6 as a planned Shopware migration instead of a risky big bang.

O

Objectives— Impact over features

Not "we need a new shop", but measurable goals: a platform that grows with the business, seamless JTL-Wawi integration without data breaks, preservation of the established SEO substance, and a deployment process that enables continuous releases instead of preventing them.

C

Constraints— Making limits visible

The critical conditions were named before implementation, not discovered during it: JTL-Wawi as the fixed ERP, ongoing business operations without interruption, full migration of customers, orders, and loyalty points with continuous number ranges, plus a URL structure grown over years that could not be allowed to break.

Decision formula met

Measurable impact, the client's readiness to decide, clear ownership on both sides. Only then does a project start at nuonic.

~10 months
From facts to go-live
106 work items
In the execution phase
98 %
Completed at go-live
0 breaks
In data, SEO & operations

Execution & Scaling

Go-live was the starting point — not the goal.

U

Execution— Build, don't discuss

No concept loops, but a production-ready system from our Shopware development:

  • Custom theme: Header, navigation (desktop & off-canvas mobile), product listing, product detail page, cart, and checkout to the client's CI.
  • JTL-Wawi integration: Sync of products, customers, orders, and stock levels via the JTL-Connector.
  • Data migration: Customers, orders, loyalty points, and reviews fully migrated — number ranges continuous.
  • Plugin stack: Loyalty system, PayPal, Amazon Pay, Trusted Shops, comparison list, blog, and custom CMS elements for experience worlds.
  • Automate everything: Stage/production environments with an automated deployment pipeline, monitoring, alerting & logging from day one.

Go-live in October 2024 — on schedule, during live operations.

S

Scaling— Growth is a system, not luck

Since go-live, the continuous optimization cycle has been running — Shopware support & maintenance with a fixed release rhythm instead of ad-hoc firefighting:

  • 40+ releases through the automated pipeline — planned, tested, documented.
  • Shopware 6.6 → 6.7 as a major update without downtime, including theme and plugin adjustments.
  • Proactive compliance: GPSR, BFSG preparation, and EEA-compliant conversion tracking — implemented before they became a risk.
  • Growth stack: Klaviyo (flows, back-in-stock, product feed), Trusted Shops widgets, server-side tracking.
  • Performance & conversion: Image formats, CDN, availability and delivery-time logic, checkout optimization — prioritized by data.

Impact over activity

Nearly 290 work items since go-live are not busywork — they are proof that an actively operated shop is a living system. Responsibility doesn't end at go-live. It begins there.

Scaling in numbers
Timeframe
Since Oct. 2024 (ongoing)
Total work items
≈ 290
Releases
40+ deployments
Shopware versions
6.6 → 6.7.x
Compliance
GPSR, BFSG, EEA tracking
Model
Maintenance with a fixed release cycle
Release ManagementShopware 6.7GPSRBFSGKlaviyoServer-Side TrackingPerformance
The roles in the project

Four roles, from facts to scaling.

Responsibility across the full cycle — operationally tied to the phases, with no handoffs into the void.

Strategist

  • Goals & prioritization

Architect

  • System design & integrations

Builder

  • Delivery & quality

Operator

  • Operations & growth
I had imagined the complete migration of our shop to Shopware 6 to be far more nerve-wracking. nuonic ran the project so methodically — from the development environment through data migration and the JTL connection all the way to go-live — that we could focus on day-to-day business instead of putting out fires. The new theme, the checkout, and the entire plugin landscape – AmazonPay, PayPal, Trusted Shops, our loyalty system – ran smoothly from day one. But what truly won us over is the time afterwards: releases arrive in a reliable rhythm, bugs are fixed quickly and traceably, and with Shopware updates or security patches nuonic reaches out proactively before things become critical. Even on mandatory topics like the Digital Product Passport, the team thinks ahead instead of just ticking boxes. For us, this is no longer a mere agency relationship, but a true technical partner.
Katja Thal - Handelskönig GmbH · on working with nuonic
Contact

Want systems instead of projects? Let's talk about impact.

nuonic Digital GmbH & Co. KG · Munich & Hamburg
Benedikt Rillox and Alex Jank, the founders of nuonic Digital