PinkCube Selected a PIM Before Leaving Magento 1

PinkCube selected a PIM while the shop was still Magento 1. The print and promotional webshop had to get off that release, and the catalogue had to live somewhere that can feed more than one channel. PIMvendors ran the selection. With the team, they chose an implementation partner that matches how PinkCube works.

Client

PinkCube is a fast-growing webshop for print and promotional products. The range runs to thousands of customizable items, delivery is fast, and the customers are both B2B and B2C. The company is investing in the digital setup so the shop can keep up with that range.

The challenge

The shop was Magento 1, and that application had become a monolith. Catalogue, storefront and channel feeds sat in one place, and the setup was inflexible once the range and the channels grew. PinkCube needed the product data to be manageable, a connection to more than one sales channel, and room to add tools beside the shop. The PIM choice decides whether the next architecture is a set of separate systems or another application that has to do every job.

The approach

PIMvendors ran the full selection. They mapped the applications, wrote down the integrations the PIM had to meet, and defined the capabilities with the PinkCube team: what the shop needs now, and what has to stay possible when another channel or tool is added. The advice was independent, so the vendors on the list were there because they fit the map. The implementation partner was selected against that same map, for this setup and this way of working.

The result

The PIM is in place. Product information is managed in one place and sent out to the channels, so the shop is no longer the only system that holds the catalogue. Magento 1 carries less of that job, and another tool can be added beside the PIM. That is the base for a larger webshop. The trade-off was pace. Leaving Magento 1 was urgent, and a rushed swap would have copied the monolith into a new logo. Mapping the integrations first is what kept the selection from becoming that swap.

If your shop is still Magento 1, map the integrations before you pick the PIM, and pick the implementation partner against that same map. Magento and a PIM explains why the product record sits outside the shop. How to select a PIM is the comparison PinkCube ran from the integration map, with the advice kept independent of the vendors on the list. The commerce stack shows which system owns the catalogue, the shop and the channels. The PIM implementation guide covers the partner build that sits next to a selection like this one.