Almost every distributor and small manufacturer we visit has one, in some shape: the single giant file "products_final_v27.xlsx", the one the webshop, the Allegro listings, the B2B price list and the quote for the customer all feed off. Until the day it stops working.
The symptoms are always the same. A sales rep sends a customer a quote with last year's price because they copied it from an old version. A product shows "out of stock" on the website while the warehouse has 200 pieces — nobody moved the flag. A customer gets a drill described as "120 mm long" and finds 150 mm in the box, because Allegro got updated and WooCommerce didn't. Three people spend half the week gluing an Excel, photos from Dropbox and Word descriptions into something you can load into three different sales channels. Each of them does it slightly differently.
This isn't a problem another spreadsheet will fix. This is a problem a PIM — Product Information Management — is built for.
What a PIM actually does (and doesn't)
A PIM is the single place where you keep product information: name, description, technical parameters, photos, documents, translations, variants, logistics data. From that one place, the PIM pushes consistent data to every channel: your WooCommerce shop, Shopify, Allegro, price comparison feeds, PDF price lists, print catalogs, B2B portal.
Watch out for three misunderstandings:
- A PIM is not an ERP. The ERP manages stock levels, purchase prices, sales documents. The PIM manages how a product looks and reads on the outside. These two systems complement each other; they don't replace each other.
- A PIM is not a DAM. A DAM (Digital Asset Management) is a media library — high-resolution photos, video, PDFs. A PIM can have a simple DAM built in, but it's not the same tool.
- A PIM is not an e-commerce platform. A PIM doesn't sell. It feeds the channels that do.
If you have 200 products, a single coherent spec sheet from the manufacturer and you sell through one shop — a PIM will do nothing for you. If you have 3,000 products, several sales channels and two languages of description — without a PIM, you're losing control.
Signals it's time for a PIM
You don't need a survey to figure this out. Five honest answers are enough:
- Does the sales rep sending an offer always know which price and which description is "the current one"?
- Are the product photos in one place, or scattered across Dropbox, someone's laptop and an old NAS from 2018?
- How many hours a week do three people waste re-pasting the same data into different systems?
- When the manufacturer changes a spec, how many places do you need to fix by hand?
- How many "description doesn't match the product" complaints did you get last quarter?
If one of the answers embarrasses you — that's the signal.
A simple stack for SMEs
The PIM market has long been a theater in which enterprise vendors try to sell SMEs a €100k rollout. You don't need that. In a 15–50 person trade or distribution business, three variants work:
- Akeneo Community Edition — open source, self-hosted. Rollout in 3-6 months, integration and configuration cost 40-120k PLN. Works well from 2,000 to 50,000 products. Requires your own server or hosting.
- Cloud PIM (Pimcore, Plytix, Sales Layer) — SaaS, 500-2,500 PLN per month depending on product count and users. Faster rollout (6-12 weeks) but less flexible for unusual integrations.
- A DIY "mini-PIM" on top of the ERP + a custom overlay — only works when you have fewer than 1,000 products and one or two sales channels. Below that scale it's often cheaper than a licensed PIM.
There's no single right answer. The choice depends on how many products you have, how many people touch them and whether you sell on Allegro (which has quirks not every PIM knows about).
What it looks like at a real client
An 18-person distributor of automotive accessories from Greater Poland was running a catalog of 8,200 products in a single Excel file, synced once a week to Allegro, two WooCommerce shops and a B2B portal for workshops. Three people spent a combined 22 hours a week updating descriptions, prices, photos and technical data. Even so, every month a dozen or so complaints came in about the description not matching what was actually in the box.
The rollout took four months. The choice fell on Akeneo Community, integrated with Comarch Optima (stock levels and purchase prices as the source of truth), Allegro API (listings synced hourly) and WooCommerce (every 15 minutes). Photos live in Akeneo's built-in DAM; German and Czech translations were added as a second and third language layer.
Six months later: catalog work dropped from 22 to 6 hours a week, "description doesn't match the product" complaints fell from a dozen a month to 1-2 a quarter, and sales reps stopped sending quotes with year-old prices because the price list is generated live from the PIM. The third person, who had mostly hammered away at Excel before, moved to customer service.
It's not a miracle transformation. It's simply order.
Common rollout mistakes
PIM rollouts fail in a few very repeatable ways:
- Loading dirty data "as-is." If your Excel has three variants of the same product and four spellings of the same brand, the PIM won't fix that. Someone who sits down and cleans it up will. A week of data cleanup before migration is not wasted time.
- Too rich a product model at launch. Don't define 80 attributes if in practice the shop uses 12. You can always add. It's harder to dig out of a swamp.
- No defined source of truth. Who owns the price — ERP or PIM? Who owns the description — the supplier or you? Without an answer, you'll have two "truths" within two weeks.
- Ignoring the people. The three people who used to maintain the Excel by hand are the product experts in your company. Bring them into the project from day one — otherwise they'll go back to Excel within a month.
What it really costs and when it pays back
Honest ranges for a Polish SME:
- Setup and integrations: 40-150k PLN (Akeneo CE) or 20-60k PLN (SaaS PIM).
- License or hosting: 0 PLN (Akeneo CE, beyond the server bill) or 6-30k PLN per year (SaaS).
- Maintenance and small changes: 5-15k PLN per year.
Payback shows up when the saved people-hours × their rates + fewer complaints + shorter time-to-market for a new product outweigh those figures. At the distributor in the example, that took about 8 months. At a smaller company (1,500 products, one channel) it probably wouldn't pay back at all — and the honest answer there is a better Excel, not a PIM.
If you're not sure whether your business is already "past Excel" — half an hour of conversation is usually enough to settle it.
A PIM doesn't sell. But without a PIM your sales team is selling a version of the product that doesn't exist anymore.