How ILFD Group Centralised Multi-Channel Product Data with OneSila

The main goal for us was efficiency and consistency across all listings. We had multiple team members each responsible for different platforms and marketplaces, and because we aim to maintain consistent product content and brand tone everywhere, we effectively had 5–6 people inputting the same data into 5–6 separate systems. This was repetitive and not the best use of resources. On top of that, it introduced risk. If someone was off or unavailable, their platform would simply fall behind. New products wouldn’t go live everywhere at the same time, which directly impacts visibility and sales.

We chose OneSila because they demonstrated an understanding that our catalogue and internal processes weren’t standard. Rather than forcing a rigid structure onto us, they were willing to adapt and work with the complexity. Sascha and David gave us confidence early on. They understood what we were trying to achieve and didn’t shy away from the challenges involved in getting there. That willingness to engage with the reality of our setup was a key factor in the decision.

Previously, when new product lines came in, each team member would list them independently on their respective platform. As a result, product content could vary between platforms, some listings were incomplete or inconsistent, and products could be missed entirely on certain channels.

OneSila has centralised everything. We now manage product data in one place and distribute it across all platforms from there. This has standardised content across all channels, removed duplication of effort, and reduced reliance on individual team members for specific platforms. It’s also been a significant time saver, which has allowed us to redirect effort into growth areas rather than admin.

Yes. Before, there was a noticeable discrepancy between marketplaces because listings were managed separately. Now, pushing products across multiple channels is straightforward. If a product exists in OneSila, getting it live on additional marketplaces is a simple process. This has allowed us to maintain a much more complete and aligned catalogue across platforms like Amazon and eBay.

There’s still some initial setup involved, as expected, but once that’s in place, scaling to a new channel is quick and efficient. What used to feel like a separate project for each marketplace is now more of an extension of the same workflow.

Previously, we relied heavily on spreadsheets. Each category had its own format and required fields, so the time to list products varied significantly. There were also frequent issues like upload errors, missing required fields, and rework after failed submissions. This meant delays were common, and getting products live wasn’t always predictable.

Now everything is managed within OneSila. Required fields are clearly defined and visible, which makes the process much more intuitive even for new team members. These can also be customised so that non-required fields can be made required, which allows us to define the level of data we want and make listings more content-rich. If there’s an issue, it’s flagged immediately in the system, and corrections can be made quickly without restarting the entire process.

The biggest gain is control and predictability. We can get products live faster and with fewer errors. That time saving is already being reinvested into handling a higher volume of SKUs, expanding into additional marketplaces, and supporting broader growth initiatives.

Inconsistent product information across platforms was the biggest issue. Different descriptions, missing details, and mismatched data created a poor customer experience, internal confusion, and a diluted brand image.

Absolutely. We now need fewer people managing listings because the process is more efficient and less fragmented. Those resources have been reallocated to other parts of the business, and we’re now able to focus on expansion rather than maintenance.

Yes. That’s probably one of the biggest outcomes of implementing OneSila. We now have a structured product data model, a centralised system, and a repeatable workflow.