The Shopware gap: why German clubs build differently

The pitch is ready. The agency has the track record for it: a polished Shopify app for jersey personalization, a case study built on Premier League numbers, a monthly price. Tobias, the club's e-commerce lead, listens for a while. Then he says one sentence, and the deck stops being relevant.

"We run on Shopware."

Tobias is invented, and so is the agency. Their meeting is still no corner case, because the platform question is real and countable. The question that costs the club money starts after the supporter clicks "add to cart". And there, Shopware looks exactly like Shopify.

We stay with Tobias and follow him behind the cart. It starts with what a search finds.

Four vendors, one platform

Search for jersey-personalization software, and the Shopify App Store dominates. Four examples:

• FlocApp, from the agency WEBQAM, costs $89 a month and $139 on the Expert plan, Shopify only, according to its App Store listing.
• Zakeke, a horizontal product customizer, charges $69.90 to $299.90 a month plus 1.9% down to 1.5% per product sold, per its listing in the same store.
• Kickflip's pricing page lists $59 a month plus up to 1.95% per custom product sold, for Shopify, WooCommerce and Wix.
• 3DReal is jersey-specific: free up to 20 3D products, then $499 a year, also for WordPress, Magento and Wix.

Shopware appears in none of the four. What these models cost a club is in the pricing comparison.

For Tobias, this catalog is close to useless. How many clubs sit where he sits can be counted.

Five Shopware shops, all German

An audit dated July 18, 2026 read the source code of 244 club shops in the top two tiers of seven countries. A platform is recognizable by its markers and the addresses a page loads from. For 22 of the 36 German shops it stayed undetermined.

In Germany 4 of the 36 shops ran on Shopify and 5 on Shopware. Shopware appeared in Germany only, in none of the other six countries.

A pitch that assumes Shopify fits 4 of the 14 German shops whose platform could be determined.

In Switzerland it runs the other way. Of twelve Swiss shops we read on August 6, 2026, ten serve Shopify, among them Young Boys and FC Basel. Two run on WooCommerce: Lausanne-Sport and FC Sion through a kit supplier's team shop. Shopware was in none.

The July 18 audit shows the same picture: in the top two Swiss leagues, 11 of the 22 shops ran on Shopify.

Two countries, two platforms. So what does a club like Tobias's do when the catalog offers nothing?

Clubs have their configurator built

It has one built. Two such builds are public.

The Mannheim agency Neon One describes a Shopware 6 shop in its case study on SV Waldhof Mannheim 07. The club's previous software fell away at short notice. The case study states the new solution had to be in place a little over four weeks from project start, in time for the season start. In a second step the agency added a jersey configurator to that shop, with player selection and live preview.

For Rhein-Neckar Löwen the same agency moved shop and configurator to Shopware 6, in a stated three months, for the 2024/25 sales start. Its case study on the Löwen describes the later work as regular sprints that allow changes without costly relaunches.

None of that is a wrong decision. A club that needs a shop before the season takes the agency that builds it. But one project per club keeps every later change with whoever built it.

Buy or build works through that trade-off. Tobias asks a simpler question first: what does the platform itself give a club?

The name field exists, the release does not

The answer sits in a store Tobias already knows. Shopware lists an extension called "Custom Products" there, €30 a month, for Shopware 5.2.0 to 5.7.20. There is no successor, because the functionality already ships inside Shopware 6. It belongs there to the Professional Edition, says a vendor reply in the reviews of the same Shopware Store page.

On August 6, 2026 the store lists 86 extensions for the word "Konfigurator", among them a product configurator from neonlines GmbH at €65 a month. "Trikot", "Beflockung" and "jersey" each return zero.

Eighty-six extensions for configurators, none for a jersey.

Football-specific starts outside the store, where Neon One sells its own Shopware 6 plugin on a product page.

A generic personalization field is not enough for a jersey, and clubs pay a second time for the difference. How clubs handle that sits in the club-shop audit; the Swiss free-text case in free text for 30 francs.

Read this as a Shopware problem, and Belgium is the counter-example. According to its own case study, WEBQAM rebuilt Standard de Liège's online presence on Shopify and plugged in its own app FlocApp for the jersey personalization.

So a name field is ready-made on either platform. What stays hard is everything after: reviewing an uncertain name, releasing one binding version, giving the printer something it can prove it worked from. As of August 6, 2026, no case in this research documents a public solution.

Three questions, three separate answers. The first is already sitting in the cart of Tobias's shop.

Uncertain names wait for a person

A supporter types a name that is not clear-cut. The shop knows two ways. One lets the name through and produces a misprint somebody pays for later. The other rejects on sight and loses an order that was fine.

kit.ink takes a third. An uncertain name or number is held for a human decision, not rejected outright. The order stays alive. While it is held, no production system can read it.

The reviewer sees the jersey itself, the value, the rule that fired, its severity and the channel. The queue shows how long each case has waited. Without a stated reason there is no decision.

The decision is remembered. When the same text comes back for that club, an earlier rejection is put up at once. An earlier approval is recorded but never releases anything on its own. Nothing enters a live list automatically, because a person always confirms.

A rule does not go live on a hunch either. It first runs quietly and shows what it would flag. A person switches it on afterwards, with the measured numbers in hand. Before a word is allowed through, kit.ink replays it against the past 30 days of decisions and shows which holds it would have lifted.

The check covers text only: names, numbers, free text. Rendered shapes, images and competition logos are a different problem, which checked, not blocked works through. kit.ink curates the rules, not the club.

The second question arrives days later, when the order moves into production.

The order stays fixed until printing

Time passes between cart and press: a shirt ordered in June can go into production in August. In that window the catalog moves on. A player transfers, a kit series gets a new version. Resolve the order only at print time, and production prints today's catalog, not the choice made back then.

So when a supporter adds the shirt to the cart, kit.ink pins the exact jersey edition, the prints, the size and the images and fonts it uses. The fixed order stays as it was, even as the catalog moves on.

A production system can retrieve a personalization only once its state allows it. Every attempt is recorded, allowed and refused alike. A file a shop downloaded earlier, though, sits outside that gate.

One timeline per personalization shows every state change, every refused attempt and every system that read it. It is for Tobias and the club office, not the supporter.

At release the print documents are produced: the print artwork per decorated view at true size and a dimensioned drawing in millimeters. With them come an A4 print instruction in the club's language and a machine-readable sidecar with checksums. Those checksums prove later which version was printed from.

The package has its limit too. It is kit.ink's own format, and the form a press wants it in stays between the club and its printer.

Which leaves the question Tobias's meeting started with: Shopware or Shopify.

One call instead of one project

The shop links a personalization to an order through one call with the club's own credentials. The response states a per-line outcome, so one held line never blocks the others.

That is an interface, not a build-in for one platform. For Shopify there is an app a shop connects with a single code. For other shop systems, Shopware included, there is no ready-made extension in a store. The configurator sits as a block on the product page, and the shop side builds the connection. For Tobias that means development work at the shop, not a click in a directory.

The part that used to cost agency time stays in the club office instead. Club staff set up seasons, jerseys, colorways, size runs, prints, guide lines and squad lists in German, English and French. Setting up the 3D model and connecting the shop are done with kit.ink.

The configurator shows exactly what the catalog holds: the fields, the lengths, the characters and the places the club set.

The chain behind the cart stays the same: the same review, the same release, the same history. What sits in front stays with the shop system. And suddenly Tobias's sentence sounds different.

The gap sits behind the cart

Back to the pitch. Tobias's sentence is correct: the club runs on Shopware, and half the vendor catalog drops out.

Only the platform does not decide whether an uncertain back number gets checked. Nor whether one version counts as released. Nor whether the printer can prove it worked from that version. Those questions stay open, on every platform and in both countries, until a club asks them of its own workflow.

So Tobias's next question to any pitch does not start with the platform. The Shopware gap is not a gap in the shop system. It starts behind the cart.

---

kit.ink supplies the design, the checks, the complete history and the print documents. Nothing else. Checkout, payment, refunds, customer communication and the print partner stay where they are.

Anyone weighing a jersey-personalization setup for a German or Swiss club, on any platform, can find a short, no-pressure conversation about that workflow here.

All cited pages were accessed on August 6, 2026, the kit supplier's team shop on September 22, 2026.