A Shop That Can Be Updated Again
Our Oxid license ran out and the shop had become too old to upgrade. We rebuilt it on Shopware and redesigned the frontend at the same time. I worked in the product team on the listing and the detail page, and on the service that feeds them with product data.
- Client
- Calida Group Digital GmbH, in-house
- Engagement
- About a year and a half on the replatform project
- Role
- Web Developer, product team
- Year
- 2023 to 2024
- Stack
- Shopware 6, Twig, TypeScript, Nest.js, RabbitMQ, PHP
- changes in the core, so the shop can update
- 0We only extend Shopware with plugins and apps, and nobody patches the core. So we can install a new Shopware version without breaking our own code.
- product feed for the whole shop
- 1Our product system sends the data into Shopware over RabbitMQ. Price, media and stock come in over the same route and in the same format.
- accessibility level on the product pages
- AAAA is the WCAG level most shops have to meet. It covers color contrast, using the whole page with a keyboard, and labels a screen reader can read. We checked the listing, the filters and the detail page.
- Withheld
- Traffic, revenue and conversion numbers · Screens, design files and copy · Contract details with the vendors
Oxid itself was not the biggest issue. Over the years people had patched the core to fix things quickly, and at some point we could not update the shop without breaking those patches. When the license ran out we decided to start over on Shopware instead of patching again. This time mobile first, and set up so we can stay on the newest version.
My part was the product pages. We rebuilt the listing and the detail page for mobile first and added recommendations and cross selling to both. In the backend I connected our product system to Shopware, so the shop gets its product data from one place and in one format.