
A PIM system: one source for product data, and what IT has to arrange
A PIM system (product information management) keeps the description, attributes and images of every item in one place and feeds them to the webshop, the shelf labels and the marketplaces. Choosing the software is the easy part. The work is in deciding which system owns which field, and in the integrations that make that hold.
A PIM system manages the product information a customer reads: descriptions, attributes, images, translations. Price and stock usually stay in the ERP.
Agree which system owns each field before connecting anything. Two systems that both think they own the description will overwrite each other.
We do not select, sell or implement PIM software. We handle the IT around it: integrations, accounts, backup and the devices the data ends up on.
What a PIM system does, and what it does not
A PIM system is where product information gets enriched: the title, the long description, the technical attributes, dimensions, images and translations. It takes the bare item data from the ERP or from suppliers, lets people complete and check it, and delivers the result to every channel that needs it.
That makes it different from the systems around it, and the confusion is where most selection time goes:
- The ERP remains the source for item number, purchasing, price and stock. A PIM that starts managing prices becomes a second ERP.
- A DAM (digital asset management) holds images and video at full size. Some PIM products include it; with a large media library it is a system of its own.
- The webshop displays the information but should not own it. Copy written in the webshop has to be written again for every other channel.
When you need one
Not every business with a webshop needs a PIM. With a few hundred items and one channel, a well-configured shop platform or the ERP itself is often enough. The tipping point is rarely the number of products and almost always the number of places where the same information must be right.
- The same product is described differently everywhere. Webshop, shelf label and marketplace show different text or dimensions, and nobody knows which is correct.
- Supplier data arrives as spreadsheets and is retyped by hand, once per channel.
- A new channel or language takes weeks, because the copy is scattered and has to be found first.
One owner per field, before you integrate
This is the most important decision in the whole project, and it is not a software decision. List every product field and note which system is the source, which systems only read it, and who may change it.
- Item number and barcode: from the ERP. The GTIN behind the barcode comes from the manufacturer or, for an own brand, from your own GS1 number range.
- Price: from the ERP or pricing system; the PIM reads it at most.
- Stock: from the ERP or warehouse system, never from the PIM.
- Description, attributes, images, translations: in the PIM, and only written there.
Leave a field off the list and it goes wrong as soon as two systems both update it: the last one to write wins, and that changes by the day.
The integrations: webshop, shelf label, till, marketplace
A PIM only pays off once the channels are connected. Each integration raises four questions, and they belong in the design rather than in the first incident.
- Push or pull. Does the PIM send changes to the channel, or does the channel fetch them? That decides where an error becomes visible.
- How often. On every change, hourly or once a night. A shelf label updated overnight shows yesterday’s text all day.
- What happens with an empty or invalid field. Is the item held back with an alert to someone, or does it go live with a blank description?
- Who notices when it stops. A broken integration rarely raises an error on the side you are looking at. Monitor it, with an alert that reaches a person.
In the store, shelf labels add the network: the label platform talks to the pricing system and the labels to their base station. How that works in a branch is on our page about electronic shelf labels.
Clean the data before you migrate
The biggest trap is moving today’s mess into tomorrow’s system. A PIM with duplicate items, three spellings of the same size and attributes in a free-text field is just a more expensive spreadsheet.
- Fix the data model first: which product families exist and which attributes each one requires, with fixed values where possible.
- Start with one category and one channel, and get it fully working before the rest follows.
- Deduplicate and normalise before import, not after. Units, sizes and colours in one spelling.
- Keep the old system readable until every channel demonstrably reads from the new one.
Access, backup and who administers it
Almost every PIM is now bought as SaaS, and it is tempting to assume the vendor takes care of everything. The vendor takes care of the platform. Who gets in, what is retained and what you take with you when you leave are yours to arrange.
- Accounts through your own identity. Connect it to Microsoft 365 or another central sign-in, so a leaver or an external agency loses access the same day.
- Roles and an approval step. The person who writes copy is not necessarily the one who publishes it. A change that reaches every channel at once deserves a second pair of eyes.
- Your own export. Ask how to export the full catalogue with images, in what format, and test it once. The vendor’s backup is there for their outage, not for your mistake or your exit.
- One business owner. Someone inside the organisation who owns the data model. Without that person the number of attributes grows until nobody knows them.
What to ask the vendor
- Which standard connectors exist for our webshop, ERP and label platform, and who maintains them when one of those systems is updated?
- What does the API look like, what are its limits, and what happens to a change while the integration is unreachable?
- Where are the data and images stored, and is there a data processing agreement for any personal data, such as staff accounts?
- How do we export everything when we leave, and how long does it take?
- Who does the implementation: the vendor, a partner, or do they expect us to?
How a PIM fits into a wider e-commerce architecture, with webshop, payments and order flow, is covered on our page about IT for e-commerce.
Where our work stops
What we do. We handle the IT around a PIM system: accounts and sign-in through your own identity, the network and device side of the channels the data ends up on (shelf labels, tills, scanners), monitoring of integrations we manage, and the export as part of your backup arrangements. On site, our own local engineers do this too, in every country.
What we do not do. We do not sell or implement PIM software and we do not choose a product for you. The platform belongs to a third party and the product data is yours: we do not write product copy and we do not set prices. The data model and the integrations inside the PIM itself are configured by the vendor or their implementation partner.
Questions we get about this
The five that come up most often.
What is a PIM system?
A PIM system (product information management) is software in which you manage product information in one place: descriptions, attributes, images and translations. It feeds that information to the webshop, shelf labels, marketplaces and print. Price and stock usually remain in the ERP.
What is the difference between PIM and ERP?
The ERP runs the business around an item: purchasing, stock, price and invoicing. The PIM manages what a customer reads about the item. They work together: the ERP supplies the item, the PIM enriches it, and for each field it is agreed which of the two is the source.
Do I need a PIM if I already have a webshop?
Not always. With one channel and a manageable range, the webshop is often enough. A PIM pays off once the same product information has to be right in several places, such as webshop, shelf label and marketplace, or in several languages.
What does IT need to arrange for a PIM?
Which system owns each field, the integrations with webshop, ERP and other channels, monitoring of those integrations, and accounts through central sign-in. Add your own export of the catalogue and one business owner for the data model.
Do you implement PIM software?
No. We do not sell or implement PIM software and we do not choose a product for you; that is done by the vendor or their implementation partner. We handle the IT around it: accounts, backup, and the network and devices the product data ends up on, such as shelf labels and tills.
Further reading
Where product data ends up.
Shall we sort out the integrations around it?
Tell us which channels need your product data and which systems are in place today. We will say what has to be arranged on the IT side; the choice of product stays with you.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.