The licence is rarely the biggest number in a PIM budget, and it is the only one most vendors will quote you early. Everything else arrives later. Implementation, integration, getting the data fit to load, training, and the internal time nobody costed. PIM pricing conversations start with a monthly subscription and end somewhere considerably more expensive. This is the version we build with clients before they sign anything.
The seven layers of PIM pricing
A PIM budget has seven cost layers. Six of them get quoted by somebody. The seventh never does.
| Layer | What it covers | Who quotes it | When it lands |
|---|---|---|---|
| 1. Licence | Platform subscription, priced on SKUs, users, locales or channels. | Vendor. | On signature, then every year. |
| 2. Implementation | Data model build, configuration, workflow, roles, testing. | Vendor services or an implementation partner. | Weeks one to twenty. |
| 3. Integration | Connectors to ERP, ecommerce, DAM, marketplaces and print. | Partner plus your own IT. | Mid-project, then permanently. |
| 4. Data preparation | Cleansing, deduplication, attribute mapping, enrichment, imagery. | You, a partner, or an outsourced team. | Before go-live, and it does not stop. |
| 5. Training and change | Role training, documentation, new ways of working. | Partner or internal. | Around go-live. |
| 6. Managed service | Admin, releases, small changes, second line support. | Partner or a new internal hire. | From go-live onwards. |
| 7. Internal time | Your team’s hours, backfill, and the sponsor’s attention. | Nobody. | Throughout. It is the largest hidden number. |
Vendors quote layer one. Implementation partners quote layers two, three and five. Layer four is where budgets break, because it is the layer that depends on the state of data nobody has audited yet.
Layer one: what actually drives the licence
Most PIM vendors price on some combination of four things. SKU or product record count. Named users or editor seats. Locales and languages. Channels or activation destinations.
Which of those four dominates varies by platform, and it matters more than the headline rate. A distributor with 400,000 SKUs and six users has a very different bill from a brand with 4,000 SKUs and sixty users. Read the metric before you read the number. If your catalogue is growing 20 per cent a year, a SKU-metered contract signed at today’s volume will not look clever in year three.
Our own PIM pricing guide puts typical SaaS licence cost at £500 to £5,000 or more per month. Open source deployments swap that for hosting, at roughly £200 to £2,000 per month. The development cost comes on top.
Which PIM vendors publish pricing publicly
We are a partner to all six platforms below. That means we read their pricing pages often. Here is what each one published as at 20 August 2026.
| Vendor | What is published | Source |
|---|---|---|
| Akeneo | Three packages compared. Growth shown as “Starting at $0 Annually” with a free trial, Advanced and Premium both “Call for a quote”. A free open source Community Edition is offered separately. | Akeneo package comparison |
| Plytix | Full public price list. Standard free at 500 SKUs, Pro at 499 per month for 50,000 SKUs, Enterprise on request. Unlimited users on every plan. Add-ons priced openly. | Plytix pricing |
| Sales Layer | Four plans with published user and SKU ceilings, from 5 users and 10,000 SKUs up to 35 users and 200,000 SKUs. Prices themselves are quote-only, in euros or dollars. | Sales Layer pricing |
| Bluestone PIM | No list prices. Usage-based model quoted from your users, SKUs and languages. States contracts are typically three to twelve months. | Bluestone PIM pricing |
| inriver | Four plans named and described (Foundation, Core, Professional, Enterprise). No prices published. States every plan is fully customisable. | inriver plans |
| Bluemeteor | No pricing page. Buyers are routed to a demo or a quote request. | Bluemeteor |
Publishing a price list is a go-to-market choice, not a virtue. Platforms that sell self-serve to smaller catalogues publish, because the buyer needs to qualify themselves in ten seconds. Platforms that sell into complex enterprise estates do not. The deal has ten variables, and a published number would be wrong for almost everyone reading it. Neither approach tells you anything about the quality of the software. We cover all six on our PIM partners pages.
What it does tell you is how much homework you have to do. If two of your shortlist publish and two do not, your comparison is not like for like until you have quotes from all four.
Layer two: implementation
Implementation is the configuration work that turns an empty platform into your platform. Attribute model, category structure, completeness rules, user roles, workflow, validation, import templates, testing.
Four things drive the cost. The number of attributes and categories. The number of channels you publish to. The number of locales. And how much workflow you need. Approval chains are the most expensive thing to configure and the most likely to change later.
Our pricing guide puts SaaS setup and onboarding at roughly £5,000 to £20,000 as a one-off. Open source setup or development runs from £10,000 to well over £100,000, depending on complexity. The gap between those two numbers is not really a gap. It is the difference between configuring a product and building one. We set out what is in scope on our PIM implementation services page.
Layer three: integration
Integration is where the estimate meets your actual systems. A connector to a mainstream ecommerce platform is usually straightforward. A connector to a twenty year old ERP with a custom item master is not, and no vendor can size it from a demo call.
Three questions predict the cost. How many systems, in which direction does data flow, and how often. One-way nightly is cheap. Two-way near real time between PIM, ERP and a marketplace is an engineering project with its own testing cycle.
Budget for the second integration too. Almost nobody stops at one. The second usually lands the year after the project closed, when the budget line has gone. A one-way nightly feed typically runs £3,000 to £10,000. Two-way and near real time, between PIM, ERP and a marketplace, is more often £15,000 to £50,000 per integration.
Layer four: data preparation, where budgets actually break
This is the layer that decides whether the project lands. It is also the one clients most consistently underestimate, because it is invisible until somebody opens the export.
The work is unglamorous. Deduplicating SKUs. Mapping supplier attribute names onto your model. Turning free text into value lists. Fixing units of measure. Sourcing missing images and datasheets. Writing descriptions for the eighty per cent of the catalogue nobody has ever written about.
Two rules from experience. First, audit before you budget. An hour with a category export tells you more about cost than a week of vendor demos. Second, decide what “complete” means per category before anyone starts, or the work has no finish line. This is the work we do as product content enrichment. It is the layer most likely to need a real number rather than a guess. Expect £0.30 to £1.50 per SKU for a simple retail line, £1.50 to £4 for a mid-complexity distributor line, and £4 to £12 for a technical industrial line.
Layer five: training and change
Cheap to buy, expensive to skip. The visible cost is a few days of role-based training and some documentation. The real cost is that a PIM changes who does what.
Category managers who used to email a spreadsheet now have to fill in required fields before saving. Suppliers who used to send a PDF now get rejected. Somebody has to own that conversation, and it is not the implementation partner. Every stalled PIM we have been called into had a working platform and a team still using the spreadsheet. Role-based training and documentation typically runs £3,000 to £15,000. A named change owner for the first six months costs more than all of it, and is the line most often cut.
Layer six: ongoing managed service
After go-live somebody has to run the thing. Platform admin, release testing, new attributes, new channels, user support, and the small changes that arrive weekly for the first six months.
You have three options and they cost differently. Hire someone, which is a salary plus the risk they leave with all the knowledge. Absorb it into an existing team, which is free until it quietly is not. Or buy it as a PIM managed service, priced by hours or by scope. Most often it is a monthly block of hours, typically £1,000 to £5,000 a month depending on catalogue size, channel count and how much change is still landing.
The mistake is assuming the answer is zero because the platform is SaaS. SaaS removes the servers. It does not remove the administration.
Layer seven: the internal cost nobody budgets for
Here is the line that never appears on a quote. Your people.
A mid-sized PIM project pulls in the sponsor, the product data lead, category managers, ecommerce and IT. Workshops, testing and data work, for months. None of that time is backfilled. It is simply absorbed, which means something else does not happen that quarter.
We ask clients to estimate it properly, in days, by role, before the business case goes to the board. A mid-sized programme absorbs 60 to 120 internal days across sponsor, product data lead, category managers, ecommerce and IT. A large one runs past 200. Two things follow. The number gets respect, because it is usually large. And the project gets a real sponsor, because somebody has to defend it.
The number on the other side
Cost only means something against the alternative. Gartner says poor data quality costs organisations at least $12.9 million a year on average, based on its 2020 research. The figure sits on its data quality topic page. That figure covers all enterprise data, not product data specifically, so treat it as direction rather than a line in your business case.
The product-specific version is easier to measure in your own numbers. Rejected marketplace listings. Returns caused by wrong specifications. Time spent answering questions the datasheet should have answered. Those are countable, and they make a better case than any vendor slide.
PIM pricing at three sizes
Our pricing guide sets out three year-one shapes. They are a reasonable sanity check against any quote you receive.
Early stage or smaller catalogue. Around £0 to £10,000 in year one. Free or entry tier platform, light configuration, data prepared internally.
Mid-market and growing. Around £10,000 to £50,000 in year one, plus services. Real configuration, one or two integrations, some outsourced data work.
Enterprise or complex. £50,000 and upwards in year one, plus services. Multiple channels and locales, deep ERP integration, governance, and a managed service from day one.
Those bands cover licence and platform. Services sit on top, and in complex estates services usually exceed the licence. That is normal, and a quote where implementation looks suspiciously cheap against the licence is a quote to question.
When PIM pricing does not add up
We talk clients out of PIM projects reasonably often. Three situations where the numbers do not work.
You have fewer than a few thousand SKUs, one channel and no supplier onboarding problem. A well-run spreadsheet and a tidy ecommerce back end will hold that for a while longer. Our piece on whether you need a PIM covers the threshold honestly.
Your real problem is identity, not content. If systems disagree about which product is which, PIM will hold two rich records for one product.
Nobody internal owns it. A PIM with no owner becomes an expensive read-only copy of the ERP within a year. If you cannot name the person, delay the purchase and fix that first. That is usually the outcome of an honest PIM selection process.
Key takeaways
- The licence is one of seven cost layers and is rarely the largest.
- Read the pricing metric before the price. SKUs, users, locales and channels produce very different bills for the same catalogue.
- Plytix publishes a full price list and Akeneo publishes package comparisons. Sales Layer, Bluestone PIM, inriver and Bluemeteor quote on request.
- Data preparation is the layer that breaks budgets. Audit a category export before you set the number.
- Internal time is the largest unquoted cost. Estimate it in days by role and put it in the business case.
- Services exceeding licence cost is normal in complex estates. An implementation quote that looks cheap against the licence usually is.
Getting a real PIM pricing number for your catalogue
A useful PIM budget takes a look at three things. The state of your product data, the systems it has to talk to, and who will own it afterwards. We can usually give an indicative shape in a single conversation, including telling you if the answer is not yet.
We do this as part of PIM selection, independently of the vendors we partner with. Book a thirty minute discovery call and bring a category export and your integration list.