Guide

How do you choose a PIM? 10 questions to ask before the demo

Almost every platform looks good in a demo. What matters is how it would work with your products, your systems and the people who handle the data every day. Ten questions to prepare beforehand.

~ 8 min read

When you start evaluating a PIM, it’s easy to begin with the wrong question:

“Which platform has the most features?”

Demos help, but almost every platform looks good when it’s shown in its ideal scenario.

What you need to find out is how it would work in your real one.

  • With your products
  • With your variants
  • With the systems you already use
  • With the people who work on the data every day
  • And above all with the awkward cases that today force you to open Excel, call a colleague or improvise a manual workaround

That’s why it’s worth preparing a few questions before you ask for a demo.

Not to build an endless list of requirements, but to pin down what the PIM actually needs to solve in your company.

1. What problem are we trying to solve?

It sounds obvious, but it’s the most important point.

“We need a PIM” isn’t a problem yet.

The problem might be:

  • Product information scattered across several files
  • The same updates made by hand, over and over
  • Products published with incomplete data
  • Trouble managing variants and compatibility
  • Translations you can’t be sure are complete
  • Distributors who each need a different file
  • Relying on IT for every single change
  • Taking too long to get a product onto a new channel

The more concrete the problem, the easier it will be to see during the demo whether the platform really solves it.

A question to bring to the demo:

“Let me show you how we handle this process today. How would it change with your PIM?”

3. Can the data model follow the logic of our products?

A demo can look very simple as long as every product has the same fields.

In real life, though, an industrial pump, a spare part and a promotional kit may call for completely different structures.

So it’s worth finding out:

  • How families and categories are handled
  • How attributes change between product types
  • How variants and relationships work
  • How market- or channel-specific fields are handled
  • How easy it is to change the structure over time

The goal isn’t to find a platform “with no limits”.

It’s to work out whether the structure can properly represent the complexity you actually have.

4. Where does the data come from today?

A PIM rarely lives on its own.

Codes, prices or stock levels may come from the ERP. Some specifications may come from a PLM. Images may sit in a DAM. Other data may still live in spreadsheets or internal databases.

Before the demo, sketch out, even very roughly, the path your information follows today.

Then ask how the PIM would fit into that flow.

Useful questions:

  • Which integrations already exist?
  • Which ones need a custom connection?
  • How are imports and updates handled?
  • What happens when a value changes in the source system?
  • How are errors and missing data dealt with?

A nice-looking screen counts for little if every update then needs a manual step across three systems.

See how openlane integrates with your systems

5. Where does the information need to go?

An ecommerce site is only one of many possible destinations.

You might need to feed:

  • Several ecommerce sites
  • Marketplaces
  • Distributors
  • B2B portals
  • Your corporate website
  • Digital catalogs
  • Apps
  • External partners
  • Specific feeds or exports

And each destination may need different fields, languages, images or structures.

A good demo should therefore show not just how data gets in, but how it’s prepared to go out.

A question to bring to the demo:

“If this distributor needs 25 fields in one format and the marketplace needs 40 different ones, how do we serve both destinations from the same product?”

6. Who will work in the PIM, and what do they need to do?

Software choices are often driven mainly by IT, but the people using the PIM every day may be marketing, the product team, sales or external collaborators.

That’s why it helps to list the actual roles. For example:

  • Who creates a product?
  • Who enters the technical data?
  • Who writes the descriptions?
  • Who manages translations?
  • Who approves?
  • Who can change the structure?
  • Do photographers, agencies or translators need to take part?

During the demo, try to look at the product through these people’s eyes, not just the administrator’s.

A useful question:

“How easy is it for this person to do the job they do every day?”

7. How do we know when a product is really ready?

Having data in the PIM doesn’t automatically mean having a complete catalog.

For one product family you might require:

  • 15 technical attributes
  • At least three images
  • A user manual
  • A certification
  • A description in Italian and German

For another family the requirements might be completely different.

So during the demo it’s worth understanding how completeness, checks and validation are handled.

Questions to ask:

  • Can I define different mandatory information for each family?
  • Can I see at a glance what’s missing?
  • Can I track completeness separately by language, market or channel?
  • Can I block or flag the publication of incomplete products?

This is one of the areas where a PIM should stop people having to keep everything in their heads.

See how openlane checks catalog completeness

8. How are images, documents and other media handled?

Product information isn’t just fields and descriptions.

There are images, manuals, certifications, data sheets, videos and other content that must stay attached to the right product.

If the project also covers media management, ask to see in practice:

  • How they’re uploaded and organized
  • How they’re linked to products and variants
  • How versions and approvals are managed
  • How they’re distributed to the various channels
  • Whether there’s a built-in DAM or an external one is connected

Don’t stop at “do you have a DAM?”

Ask to see the workflow you actually need.

Read the guide: what a DAM is and why it belongs alongside your PIM

9. How independent will we be after implementation?

The initial setup can be perfect.

Then, six months on, a new category comes along. A new market needs different attributes. Marketing wants to change a workflow. A new distributor signs up.

At that point the question becomes:

Can we handle these changes ourselves, or do we have to open a ticket every time?

That doesn’t mean IT or your technology partner should never be involved again.

It means knowing which tasks the people in charge of the catalog can handle on their own, and which ones call for technical skills.

Useful questions:

  • Who can add an attribute?
  • Who can change a product family?
  • How easy is it to add a language or a market?
  • Which configurations require development work?
  • Which ones require the vendor to step in?

The answer has a big impact on day-to-day work after go-live.

See how openlane adapts to your company

10. What happens when we grow?

Today you might have two markets and one ecommerce site.

Two years from now you might have five languages, three brands, new distributors and a much bigger catalog.

You don’t need to design for every possible future scenario today.

You do need to know whether the platform can keep pace with reasonable growth without forcing you to rebuild everything.

During the demo, ask what happens when:

  • The number of SKUs grows
  • The number of users grows
  • You add new product families
  • You open a new market
  • You connect another channel
  • Your internal processes change

The question isn’t just “can it do it?” It’s also:

“How much work does it take?”

A good demo should start from your products

There’s a very simple way to make a demo more useful.

Bring with you:

  • 3 to 5 real products
  • One or two files you use today
  • An example of an export a distributor asks for
  • One tricky case
  • One process that takes too much manual work today

And ask them to work on those.

A demo built entirely on the vendor’s data can show you the software well.

A demo built at least partly on your own cases helps you see whether that software can work for you.

Request a demo on your own products

Don’t look for the platform with the most features

When you compare several PIMs, a matrix with hundreds of features can look like the most objective method.

But 150 ticks aren’t necessarily worth more than 100.

One feature that solves an important everyday problem can count for far more than ten you’ll never use.

That’s why it pays to split your requirements into at least three groups:

  1. 01

    Essential

    Without these, the project doesn’t solve the problem you’re starting it for.

  2. 02

    Important

    They add value, but could be introduced in a second phase.

  3. 03

    Nice to have

    They’re interesting, but they shouldn’t drive the decision.

That way the demo stops being a contest between feature lists and becomes a much more concrete test.

The final question: does it really make our work easier?

At the end of the evaluation, go back to where you started.

A PIM should help you bring order to your product data, cut errors and manual work, and make it easier to manage catalog, people and channels as they grow.

If getting there means introducing a structure your team struggles to understand, or a process even more complex than the one you have now, it’s worth pausing.

The right platform isn’t necessarily the one that can do the most.

It’s the one that handles the complexity you need without adding more where you don’t.

Read the guide: how to implement a PIM

Want to see openlane on your own product data?

Book a guided demo and let’s talk about your catalog.

Request a demo