Skip to content

Home · Case studies · Eden PIM

Case study · PIM development · Product data automation

Eden PIM: product data that builds itself from rules, not from people

Eden Technology had more product data than its workflows could carry. Bintime built a PIM tool that automates those workflows, absorbs supplier content from Vox66, and constructs titles and specifications from the attributes themselves.

6
People on the Bintime team
5 yrs
Partnership period, 2018–2024
15K+
Customers served by the client
3
Automation layers: workflows, content, titles

About the client

A Barcelona reseller with a catalogue growing faster than its processes

Eden Technology sells to consumers from Barcelona and serves more than 15,000 customers. Product data arrives from several directions — its own ERP, supplier feeds and a dedicated content provider — and all of it has to end up on the storefront in one consistent voice.

The PIM engagement started in 2018 and ran for five years. It sits alongside two other Bintime projects for the same client: the ERP with its channels module, and later the B2C webshop that consumes this product data.

  • E-commerce
  • B2C e-commerce
  • Retail
  • PIM
Industry
E-commerce · B2C · Retail
Location
Barcelona, Spain
Partnership period
2018 – 2024
Team size
6 people

Services

  • PIM tool development
  • DevOps
  • QA / QC
  • Technical documentation

Expertise delivered

  • Successful product launch
  • Continuous delivery
  • Business process automation
  • Technical support

Technologies

  • PHP
  • JavaScript
  • MongoDB
  • RabbitMQ
  • Redis
  • Elastic
Visit the client's site →

Business challenges

Three problems, all of them made of product data

Eden approached Bintime to manage a large volume of product data — and quickly it became clear that volume was only the first layer.

Data overload and workflow complexity

Eden needed a PIM system to automate complex workflows and streamline product management, rather than a place to store the same manual process in a nicer interface.

Customised content integration from the content provider

Client-specific content from Vox66 had to be integrated seamlessly. That required a tailored PIM capable of accommodating diverse content formats while maintaining accuracy.

Demand for dynamic product titles

Titles and specifications had to be generated automatically from product content and title rules, so every product name is constructed consistently and uniquely.

Approach

Scrum, and rules instead of manual entry

Through the development lifecycles the whole team embraced an agile approach, implementing Scrum to keep project management efficient. That allowed iterative development, clear and transparent communication, and adaptability throughout the project — so changes were absorbed rather than escalated.

The design principle behind the tool itself: anything a person types twice becomes a rule. Specification and title construction, supplier content normalisation and workflow steps were all moved into configuration the client controls.

Delivery model

Six-person team covering PIM development, DevOps, QA/QC and technical documentation, working in Scrum iterations with the client setting direction.

  1. 01

    Model the attributes first. The attribute structure decides what can later be automated, so it was designed before any workflow was built on top of it.

  2. 02

    Normalise supplier content on the way in. Vox66 content is mapped into Eden’s own structure at ingest, so accuracy is checked once rather than per channel.

  3. 03

    Rules as a product feature. Title and specification rules live in the PIM, editable by the client, not hard-coded in a release.

  4. 04

    Iterative releases in Scrum. Sprint by sprint, with transparent communication and room to change direction as the catalogue grew.

  5. 05

    Documented and tested as delivered. QA/QC and technical documentation were part of the team, not a phase at the end.

Value delivered

What the PIM does that people used to do

01

Data management automation

Automated product data workflows streamlined operational efficiency, reducing manual effort and making data management accurate and consistent instead of dependent on who touched it last.

02

Client-customised content integration

Content from the Vox66 provider is tailored for Eden, with product specification rules and title rules automating the construction of titles and specifications from designated product attributes.

03

Content constructor for the online store

A user-friendly tool to construct and customise product content dynamically, based on predefined rules and an evolving marketing strategy rather than a fixed template.

What contributed to success

Four things that made the difference

KPI focus

The project kept a meticulous focus on KPIs — defining them, tracking them and hitting them — across five years of releases.

Transparent collaboration

Communication went beyond technical solutions into strategic initiatives and insights that moved the project forward.

Clear direction

The client’s clear direction and oversight were pivotal in achieving seamless integration and a fluid working partnership.

Growth-focused roadmap

A growth-focused web app roadmap kept effort aligned with Eden’s objectives and positioned for continuous expansion.

Expanding cooperation

Where the project stands now

The current functionality is a fully realised solution. The work that continues is refinement: making the tool more user-friendly and more closely tailored to how Eden actually works, release after release.

A PIM is never finished in the sense a website is — the catalogue, the suppliers and the channels keep changing, and the rules have to keep up.

FAQ

Questions we get about PIM projects

When does a retailer need a PIM instead of a spreadsheet?

When the volume of product data and the number of steps around it stop fitting in one person’s head, and manual handling starts producing inconsistency rather than saving time.

What are product title and specification rules?

Rules that build a title or specification automatically from designated attributes, so names stay unique and consistent across the catalogue instead of drifting between similar products.

How is third-party content integrated?

Content from Vox66 is normalised into Eden’s own attribute structure at ingest. The PIM accommodates diverse formats while keeping accuracy, so supplier data is not stored as a permanent exception.

What is a content constructor?

A tool inside the PIM for assembling product content from predefined rules, so content can follow marketing strategy without a developer shipping a change each time.

How long did the engagement run?

2018 to 2024: five years with a six-person team, delivered in Scrum iterations, with continuous delivery and refinement after the product was complete.

Do you build custom PIMs or configure existing ones?

Both. Eden needed a tool tailored to its own ERP and its content provider, so a custom PIM was the right answer. Where a product platform fits, we work with Gepard PIM instead.

Start a conversation

Drowning in product data?

Tell us how product content reaches your channels today. We come back with a data model, an automation plan and a team shape.

  • Reply within 24 hours from someone who can scope it
  • Reference calls with existing clients, where they agree
  • NDA signed before any detail is shared

Talk about a PIM project

We reply within one business day.

Reply within 24 hours · NDA on request