Gartenhaus is a leading online platform for home and garden projects. They currently offer more than 50,000 products across 9 different European markets.
However, their eCommerce processes were too reliant on their shop system. This was a problem for several reasons:
These technical hurdles had the potential to severely hamper the medium- to long-term growth of their business so we proposed a project to decouple their shop system from their business data.
We wanted to help Gartenhaus move from a shop-centric approach to a data-centric approach.
Practically, this meant moving a lot of the core data out of the shop system and into more specialized systems, such as different tools for managing product inventory, sales orders and customer data. At the center, we added a middleware layer that facilitates data exchange between these multiple constituent systems.
The middleware layer consists of several “Data Hubs” that store different data types (such as sales orders and product entries). We also created independent definitions for how this data should be structured. This approach ensures that Gartenhaus’s “business objects” aren’t shaped by any software vendor’s view of the world and makes it easier to swap out different systems as the company grows.
We created and integrated three Data Hubs (1. Product Data Hub, 2. Sales Order Data Hub, 3. Customer Data Hub) which enabled Gartenhaus to integrate with new systems and 3rd party tools in a fraction of the usual time.
In addition with the implementation of the Data Hubs we also built the foundation for a simplified migration of a future shop system.
Want to learn more? Contact stephan.schulze@project-a.com