---
title: "Handelskönig — From JTL-Shop to Shopware 6"
description: "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."
canonical_url: "https://nuonic.de/en/case-studies/handelskoenig-focus"
last_updated: "2026-08-14T18:31:48.447Z"
---

<case-study-hero eyebrow="Case Study · F.O.C.U.S." image="/images/case-studies/handelskoenig-hero.jpg" imageAlt="Handelskönig e-commerce on Shopware 6">

We don't build shops. We build <span>



</span>



<span className="mono-hl">

systems that generate revenue.

</span>



<template v-slot:lead="">

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.

</template>
</case-study-hero>

<case-study-focus-strip :phases="[{"letter":"F","name":"Facts","tagline":"Reality over assumptions"},{"letter":"O","name":"Objectives","tagline":"Clarity before speed"},{"letter":"C","name":"Constraints","tagline":"The truth about systems"},{"letter":"U","name":"Execution","tagline":"Build, don't discuss"},{"letter":"S","name":"Scaling","tagline":"Growth is a system"}]">



</case-study-focus-strip>

<case-study-facts :facts="[{"label":"Client","value":"Handelskönig GmbH"},{"label":"Industry","value":"Retail / Construction & Trade Supplies"},{"label":"Platform","value":"Shopware 6"},{"label":"ERP","value":"JTL-Wawi (JTL-Connector)"},{"label":"Payment","value":"PayPal, Amazon Pay, RatePay"},{"label":"Go-Live","value":"October 2024"},{"label":"Status","value":"Scaling phase (ongoing)"}]" :tags="["Shopware 6","JTL-Connector","CI/CD Pipeline","Loyalty System","Trusted Shops","SEO Migration","Klaviyo"]" label="Project at a glance">



</case-study-facts>

<case-study-section letter="F" name="Facts" subtitle="Reality over assumptions">

The existing JTL-Shop was limiting growth: restricted frontend flexibility, labor-intensive content maintenance, limited extensibility. The [system audit](/en/services/consulting) 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](/en/shopware-agency/migration) instead of a risky big bang.

</case-study-section>

<case-study-section letter="O" name="Objectives" subtitle="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](/en/shopware-agency/seo), and a deployment process that enables continuous releases instead of preventing them.

</case-study-section>

<case-study-section letter="C" name="Constraints" subtitle="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.

</case-study-section>

<case-study-callout title="Decision formula met">

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

</case-study-callout>

<case-study-stats :stats="[{"value":"~10 months","label":"From facts to go-live"},{"value":"106 work items","label":"In the execution phase"},{"value":"98 %","label":"Completed at go-live"},{"value":"0 breaks","label":"In data, SEO & operations"}]">



</case-study-stats>

<case-study-heading eyebrow="Execution & Scaling">

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

</case-study-heading>

<case-study-section letter="U" name="Execution" subtitle="Build, don't discuss">

No concept loops, but a production-ready system from our [Shopware development](/en/shopware-agency/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.

</case-study-section>

<case-study-section letter="S" name="Scaling" subtitle="Growth is a system, not luck">

Since go-live, the continuous optimization cycle has been running — [Shopware support & maintenance](/en/shopware-agency/support) 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.

</case-study-section>

<case-study-callout title="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.**

</case-study-callout>

<case-study-facts :facts="[{"label":"Timeframe","value":"Since Oct. 2024 (ongoing)"},{"label":"Total work items","value":"≈ 290"},{"label":"Releases","value":"40+ deployments"},{"label":"Shopware versions","value":"6.6 → 6.7.x"},{"label":"Compliance","value":"GPSR, BFSG, EEA tracking"},{"label":"Model","value":"Maintenance with a fixed release cycle"}]" :tags="["Release Management","Shopware 6.7","GPSR","BFSG","Klaviyo","Server-Side Tracking","Performance"]" label="Scaling in numbers">



</case-study-facts>

<focus-roles :roles="[{"title":"Strategist","items":["Goals & prioritization"]},{"title":"Architect","items":["System design & integrations"]},{"title":"Builder","items":["Delivery & quality"]},{"title":"Operator","items":["Operations & growth"]}]" label="The roles in the project">
<template v-slot:heading="">

Four roles, from facts to scaling.

</template>

<template v-slot:intro="">

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

</template>
</focus-roles>

<case-study-testimonial background="gray" name="Katja Thal - Handelskönig GmbH" role="on working with nuonic">

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.

</case-study-testimonial>

<service-contact background="navy" ctaLabel="Let's talk impact →" ctaTo="/en/contact" image="/images/team/founders.jpg" imageAlt="Benedikt Rillox and Alex Jank, the founders of nuonic Digital" label="Contact" phone="+49 8141 828197-0">
<template v-slot:heading="">

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

</template>

<template v-slot:body="">

nuonic Digital GmbH & Co. KG · Munich & Hamburg

</template>
</service-contact>