---
title: "GHS Shop & Wäscherutsche — Cross-border commerce with Shopware"
description: "Two brands, three destination countries, and fulfillment from Austria and Germany: nuonic migrated GHS Shop and Wäscherutsche from Shopware 5 to 6 and implemented their cross-border order processes."
canonical_url: "https://nuonic.de/en/case-studies/ghs-waescherutsche-focus"
last_updated: "2026-08-24"
---

<case-study-hero eyebrow="Case Study · F.O.C.U.S." image="/images/case-studies/ghs-waescherutsche-hero-gradient-balanced.png" imageAlt="GHS Shop and Wäscherutsche as two sales channels on one Shopware 6 platform">

Selling across borders — implemented cleanly for tax <span>



</span>



<span className="mono-hl">

and operations.

</span>



<template v-slot:lead="">

Two brands, one Shopware instance, two shipping locations, and three destination countries: for GHS Shop and Wäscherutsche, we delivered the migration from Shopware 5 to 6 and translated professionally validated tax requirements into robust order, fulfillment, and document processes.

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

<case-study-focus-strip :phases="[{"letter":"F","name":"Facts","tagline":"Two brands, one system"},{"letter":"O","name":"Objectives","tagline":"Automate with confidence"},{"letter":"C","name":"Constraints","tagline":"The goods flow defines the case"},{"letter":"U","name":"Execution","tagline":"Migration without data loss"},{"letter":"S","name":"Scaling","tagline":"Performance for operations"}]">



</case-study-focus-strip>

<case-study-facts :facts="[{"label":"Client","value":"GHS Shop / Wäscherutsche · Gerold Schmierer"},{"label":"Industry","value":"Technical home systems"},{"label":"Platform","value":"Shopware 5 → Shopware 6.7.x"},{"label":"Architecture","value":"2 sales channels · 1 installation"},{"label":"ERP","value":"Pickware"},{"label":"Markets","value":"Austria · Germany · Switzerland"},{"label":"Fulfillment","value":"Warehouse in AT · drop shipment from DE"},{"label":"Status","value":"Ongoing development as needed"}]" :tags="["Shopware 6.7","Multi-sales-channel","Pickware","Chain transactions","VAT logic","Fulfillment","DATEV","Sendcloud"]" label="At a glance">



</case-study-facts>

<case-study-section letter="F" name="Facts" subtitle="Two brands, one system">

[GHS Shop](https://www.ghs-shop.at/) sells central vacuum systems and accessories, while [Wäscherutsche](https://www.waescherutsche.at/) offers systems for moving laundry conveniently through the home. Both brands are operated by the same company — with separate product catalogs and distinct storefronts, but on the same Shopware instance, the same ERP, and a shared inventory operation.

The existing Shopware 5 setup was technically outdated and suffered from performance problems. The aging platform made development, automation, and reliably secure operations increasingly difficult. The move to Shopware 6 was therefore planned as a complete [Shopware migration](/en/shopware-agency/migration): products, customers, orders, media, reviews, SEO URLs, and documents all had to move while business continued.

</case-study-section>

<case-study-section letter="O" name="Objectives" subtitle="Automate with confidence">

- **Operate two shops efficiently:** separate brands and catalogs as two sales channels on one shared technical foundation.
- **Process cross-border orders reliably:** B2C and B2B sales to Austria, Germany, and Switzerland with robust order and document workflows.
- **Represent the physical goods flow:** control shipping from the Austrian warehouse and drop shipments through a supplier in Germany within one system.
- **Reduce manual work:** use Shopware Flows and Rules, integrate Pickware, and automate repeatable processes.
- **Build for the future:** establish an up-to-date Shopware 6.7 platform with staging, CI/CD, monitoring, logging, and backups.

</case-study-section>

<case-study-section letter="C" name="Constraints" subtitle="The goods flow belongs in the order logic">

The defining complexity was not a single VAT rate. It was the interaction of billing and delivery addresses, B2B or B2C status, VAT ID, shipping location, product, and the party arranging the movement of goods.

In a cross-border chain transaction, several successive supplies correspond to just one movement of goods. That movement can be assigned to only one of the supplies for VAT purposes. The [Austrian Federal Ministry of Finance](https://findok.bmf.gv.at/findok/?execution=e100000s1&segmentId=8fa89aee-67ca-4707-8079-102188753097) explains, among other factors, the relevance of the party arranging transport and the VAT ID used.

The tax assessment itself was supplied by the client and its tax adviser. Our role was to implement the approved requirements unambiguously. When products originate from different shipping locations, the system separates the transaction into independent orders. This keeps the goods flow, order processing, and documents generated in Shopware/Pickware consistent for each delivery.

</case-study-section>

<case-study-callout title="Technical consulting, not tax advice">

nuonic does not assess tax-law matters. We translate rules approved by the client and its tax adviser into **testable Shopware processes, configuration, and custom software**.

</case-study-callout>

<case-study-stats :stats="[{"value":"2","label":"Brands & sales channels"},{"value":"3","label":"Destination countries"},{"value":"2","label":"Shipping locations"},{"value":"~8 months","label":"Relaunch project duration"}]">



</case-study-stats>

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

One big-bang go-live — without disrupting ongoing business.

</case-study-heading>

<case-study-section letter="U" name="Execution" subtitle="Migration, processes, and two storefronts">

After roughly eight months, the new platform went live in a big-bang release in 2024. The client supplied the design and category structure; nuonic implemented both storefronts on ThemeWare and owned the technical concept, development, migration, and launch.

- **Complete data migration:** products, customer data, orders, media, reviews, SEO URLs, and historical documents transferred from Shopware 5 to 6.
- **Two sales channels:** separate catalogs and storefronts, but one installation, one Pickware system, and a shared operational data set.
- **Custom process logic:** a custom plugin plus Shopware configuration for order splitting, adapted VAT ID handling, and custom documents.
- **Integrated commerce stack:** Pickware, product configurator, search, PayPal, DATEV, Sendcloud, and KlickTipp brought together.
- **Quality in live operations:** business acceptance with the client team and documented edge cases in Confluence.
- **Automated operations:** staging, CI/CD pipeline, monitoring, logging, and automated backups from go-live.

</case-study-section>

<case-study-callout title="Complexity lives in each individual case">

The technical challenge is not defined by order volume alone. **Goods flow, shipping location, destination country, customer type, and VAT ID** can trigger a different process for every order — handled reliably on one shared platform.

</case-study-callout>

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

Current software needs a platform that keeps up under load.

</case-study-heading>

<case-study-section letter="S" name="Scaling" subtitle="68 percent better TTFB after the hosting move">

In 2026, nuonic moved both sales channels to its Shopware hosting platform at mittwald. Shopware, the database, OpenSearch, RabbitMQ, workers, and email hosting now run in an environment operated by nuonic on mittwald's managed platform.

The main trigger was sluggish performance in the Shopware admin. We measured the environment reproducibly before and after the migration with our own benchmarking tool. The results are also documented in the [joint mittwald case study](https://www.mittwald.de/cases/e-commerce/68-schnellere-ladezeiten-fuer-shopware-6):

- **Frontend TTFB:** down from an average of 177 ms to 56 ms — 68 percent faster.
- **Throughput under load:** up from around 58 to 176 requests per second — roughly tripled.
- **Scaling:** linear performance instead of an early plateau.
- **Migration:** overnight cutover with less than ten minutes of downtime.
- **Day-to-day impact:** a noticeably faster backend for ongoing shop management.

The platform is kept current on Shopware 6.7.x and developed further as needed. Improved performance also supports the technical SEO foundation, while Flows and Rules make new automations easier than on the former Shopware 5 setup.

</case-study-section>

<case-study-facts :facts="[{"label":"Frontend TTFB","value":"Avg. 177 ms → 56 ms"},{"label":"Throughput","value":"58 rps → 176 rps"},{"label":"Migration downtime","value":"< 10 minutes"},{"label":"Platform operations","value":"nuonic on mittwald Managed Platform"},{"label":"Shopware version","value":"6.7.x · kept current"}]" :tags="["mittwald","Container Hosting","OpenSearch","RabbitMQ","Workers","Performance","Monitoring"]" label="Hosting in numbers">



</case-study-facts>

<focus-roles :roles="[{"title":"Strategist","tagline":"Translate business requirements into executable processes."},{"title":"Architect","tagline":"Organize two brands, locations, and goods flows in one system."},{"title":"Builder","tagline":"Deliver migration, theme, and custom plugin reliably."},{"title":"Operator","tagline":"Own hosting, updates, and long-term development."}]" label="Four roles, one team">
<template v-slot:heading="">

From validated requirements to fast operations.

</template>

<template v-slot:intro="">

The collaboration did not end with the relaunch: since 2024, nuonic has supported GHS Shop and Wäscherutsche through ongoing development, platform operations, and new requirements.

</template>
</focus-roles>

<case-study-testimonial background="gray" name="Gerold Schmierer - GHS Shop / Wäscherutsche" role="on working with nuonic">

By now I know Alex and Ben well, and honestly, I'd rather work with the two of them than with any agency I had before. Together we handled the move from Shopware 5 to 6 – but the best part is that things didn't go quiet afterwards. I run two shops, GHS Shop and Wäscherutsche, with different shipping routes, and I also sell across the border. That's not always straightforward. Whatever I come to them with, the two of them find a way, and in the end it just works.
The hosting move was the same story: well prepared, hardly any downtime, and I still notice the performance today – especially in the backend, things are noticeably faster. To me, they're not service providers – they're two people I can rely on and genuinely enjoy working with.

</case-study-testimonial>

<service-contact background="navy" ctaLabel="Plan a safe migration →" ctaTo="/en/shopware-agency/migration" label="Shopware migration" phone="+49 8141 828197-0">
<template v-slot:heading="">

Complex goods flows in a legacy shop? Let's plan a robust <span className="cta-hl">

migration

</span>

.

</template>

<template v-slot:body="">

nuonic Digital GmbH & Co. KG · Munich & Hamburg

</template>
</service-contact>