---
title: "Framily — Shopware 5 maintenance with automated book production"
description: "How nuonic maintains not just Framily's Shopware 5 shop, but the entire production line behind it — every order automatically becomes a personalized children's book. Including stable Shopware 5 support right up to a smooth system change. Delivered with the nuonic F.O.C.U.S. framework."
canonical_url: "https://nuonic.de/en/case-studies/framily-focus"
---

<case-study-hero eyebrow="Case Study · F.O.C.U.S." image="/images/case-studies/framily-hero.png" imageAlt="Framily online shop — configurator for personalized children's books">

Every order a one-off. <span>



</span>



<span className="mono-hl">

Shop maintenance with automated book production.

</span>



<template v-slot:lead="">

How nuonic maintains not just Framily's Shopware 5 shop, but the entire production line behind it: every order automatically becomes a personalized children's book — produced by a fleet of physical Macs running InDesign, delivered as a print PDF to the print shop. A case for our [Shopware support & maintenance](/en/shopware-agency/support) — stable operation of Shopware 5 right up to a smooth system change.

</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":"Framily"},{"label":"Product","value":"Personalized children's books & calendars"},{"label":"Platform","value":"Shopware 5"},{"label":"Production","value":"InDesign automation on a Mac fleet"},{"label":"Markets","value":"DE, AT, CH, FR, IT"},{"label":"Timeframe","value":"Since 2023 (ongoing)"}]" :tags="["Shopware 5","Shopware Support","InDesign Automation","Mac Fleet","Jenkins CI","Adyen & Klarna","GA4 / BigQuery","Smooth System Change"]" label="Project at a glance">



</case-study-facts>

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

Framily sells personalized children's books: name, dedication, characters — every book a one-off. The special part sits behind the shop: every order runs through an automated production line in which InDesign scripts on a fleet of physical Macs generate the individual print PDF. When we took over [maintenance](/en/shopware-agency/support) in 2023, the audit showed: Shopware 5 at end of life, an incompatible payment plugin, a broken CI pipeline — and a production line where every outage meant paid orders weren't produced.

</case-study-section>

<case-study-section letter="O" name="Objectives" subtitle="Impact over features">

The goal was unambiguous: **every paid order gets produced.** In addition:

- **A stable shop** across the revenue-critical Christmas and advent-calendar season.
- **Working payments** with no failures in the checkout.
- **Fast time-to-market** for new book titles.
- **Transparency** whenever something in the chain gets stuck.

</case-study-section>

<case-study-section letter="C" name="Constraints" subtitle="Making limits visible">

The truth about this system: a heterogeneous landscape of Shopware 5, cloud infrastructure, Jenkins CI and physical production Macs that can't simply be "cloudified away". On top of that:

- **Five country shops** (DE/AT/CH/FR/IT) plus partner and cooperation shops.
- **Licensed brand worlds** with approval processes.
- **The pitfalls of personalization itself:** an apostrophe in a child's name can stop an entire production run.

</case-study-section>

<case-study-callout title="Maintenance here means: not only the shop must run — the factory behind it too.">

Whoever doesn't understand the production line can't look after this shop. That's exactly why this is a case for [Shopware support & maintenance](/en/shopware-agency/support) that goes beyond the frontend — all the way to the print shop.

</case-study-callout>

<case-study-stats :stats="[{"value":"1 book","label":"Per order — fully automated"},{"value":"8 Macs","label":"Production fleet maintained"},{"value":"5 countries","label":"Shops in DE, AT, CH, FR, IT"},{"value":"2 systems","label":"Shop & production from one hand"}]">



</case-study-stats>

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

From the cart to the print shop.

</case-study-heading>

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

After the purchase, the real magic begins — without a human stepping in: **order → print-API middleware → Mac fleet (InDesign) → checked print PDF → print shop.** What we repaired and built for it:

- **Payment rescued:** updated the incompatible Adyen plugin and made the client's own Klarna capture plugin compatible with it — payments run reliably again.
- **CI pipeline repaired:** Jenkins fixed, updated, and the deployment flow across the entire Mac fleet restored.
- **Production errors eliminated:** fixed special-character encoding in the InDesign scripts — names with an apostrophe or accent no longer stop a production run.
- **Seasonal business secured:** advent calendars, Christmas designs and discount campaigns live on time across all five country shops.
- **New titles fast to market:** book and configurator deployments standardized via Jenkins.
- **Data made usable:** GA4 conversion tracking completed, BigQuery/Looker dashboards for reports and license accounting.

</case-study-section>

<case-study-testimonial background="gray" name="Jan Kaufhold - Framily GmbH" role="on working with nuonic Digital">

Our collaboration began at a moment when we urgently needed IT help. nuonic took on the task and got up to speed on our Shopware system quickly and with great initiative. Since then they have not only fixed critical technical problems effectively, but also proactively proposed and implemented cost-saving measures across our IT landscape.
Working with nuonic is characterized by very strong technical know-how and very well organized project management. They stand out through a professional way of working, solution orientation and creativity. Their proactive approach and the ownership they take of our topics have impressed us. nuonic is always available and supportive, which makes the collaboration very pleasant.
We recommend nuonic as a reliable IT partner and greatly appreciate their work so far. We look forward to continuing the collaboration.

</case-study-testimonial>

<case-study-callout title="Shopware 5 at end of support? We keep you stable — right up to a clean handover.">

Framily shows it perfectly: a Shopware 5 system at end of life is no reason for panic, but for reliable operation. We kept the existing **Shopware 5 shop** stable and hardened as part of our [Shopware support & maintenance](/en/shopware-agency/support) — payment, security, seasonal business. And when the switch to a new shop system came, the transition on our side ran smoothly: book production kept running right through the system change, and we shut down the Shopware 5 instance in an orderly way — without a single lost order.

</case-study-callout>

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

In 2025 the Mac production line was moved into its own operations project: monitoring via UptimeKuma, clearly defined alerts for stuck orders, S3 file storage — and the switch of all production interfaces to the new shop system during the platform change, including an orderly shutdown of the Shopware 5 instance. **Book production kept running right through the system change — and runs to this day.**

</case-study-section>

<case-study-callout title="Impact over activity">

The production line outlived its shop system — **whoever builds systems instead of projects makes infrastructure platform-independent.**

</case-study-callout>

<case-study-facts :facts="[{"label":"Shop maintenance","value":"Shopware 5, payment, frontend, campaigns"},{"label":"Production","value":"InDesign automation, print API, Mac fleet"},{"label":"Infrastructure","value":"Jenkins CI, deployments, S3, monitoring"},{"label":"Operations","value":"Alerts, order support, book deployments"},{"label":"Transition","value":"Production line connected to the new shop system, SW5 shut down in order"},{"label":"Model","value":"Continuous maintenance since 2023"}]" :tags="["Shopware Support","Payment","Print Automation","Monitoring","Smooth System Change"]" label="Services at a glance">



</case-study-facts>

<focus-roles :roles="[{"title":"Strategist","items":["Prioritization by revenue risk"]},{"title":"Architect","items":["Print process & interfaces"]},{"title":"Builder","items":["Shop, scripts & pipeline"]},{"title":"Operator","items":["Monitoring & production operations"]}]" 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>

<service-contact background="navy" ctaLabel="Let's talk impact →" ctaTo="/en/contact" label="Contact" phone="+49 8141 828197-0">
<template v-slot:heading="">

Your shop is more than a shop? Let's talk about <span className="cta-hl">

impact

</span>

.

</template>

<template v-slot:body="">

nuonic Digital GmbH & Co. KG · Munich & Hamburg

</template>
</service-contact>