AI is now part of almost every PIM platform. Most vendors can generate product descriptions, translate content and flag missing attributes. These functions save time, but they do not tell you whether a platform is ready for agentic commerce.
The real test is what happens after AI identifies the work. Can it access live product data, update records, follow business rules and move products through a workflow, or does it stop at a suggestion? This article compares Bluestone PIM, Akeneo, Inriver, Salsify and Pimberly across content generation, data quality, workflow support, Model Context Protocol and external agent access, based on information available in June 2026.
Key Takeaways
- AI content generation alone does not make a PIM agentic.
- MCP lets compatible AI applications connect to product data and tools through a standard protocol.
- Bluestone PIM combines full UI/API parity with read and write MCP coverage across core PIM concepts.
- Akeneo provides broad MCP access in beta, with gaps across media files and workflow execution.
- Inriver, Salsify and Pimberly take narrower approaches centred on data access, internal workflows or AI-assisted product content.
What Does AI In PIM Cover Today?
AI in PIM now covers several types of product data work, but they do not provide the same level of autonomy.
| Type of AI capability | What it does | Typical example |
|---|---|---|
| Content assistance | Generates or edits product content | Writing descriptions from technical attributes |
| Data analysis | Finds gaps, anomalies or inconsistent values | Detecting missing materials or incorrect categories |
| Workflow assistance | Runs an AI task inside a defined process | Translating content during product onboarding |
| Conversational access | Turns natural-language requests into searches or actions | Finding products below a completeness threshold |
| Agentic execution | Reads the situation, selects an action and carries it out | Updating data and triggering publication after validation |
Most current PIM AI functions sit in the first three categories. They save time, but a person still starts the task, reviews the output or moves the product to the next stage.
Agentic execution changes that relationship. The agent receives a goal, works across live product data and performs the operations needed to reach it. Human control remains through permissions, approvals, workflow rules and audit records.
What Makes a PIM Agentic?
An agentic PIM lets AI take part in product data operations rather than limiting it to text generation or recommendations.
For example, an AI assistant may identify products without German descriptions and show the results. An agent can find those products, generate the missing values, write them to the correct market context, check completeness and trigger the next approved workflow step.
This depends on more than the quality of the language model. The PIM needs structured data, machine-callable operations, granular permissions and an interface through which the agent can use those operations.
A useful distinction is:
-
AI-assisted PIM: AI prepares an answer or suggestion for a user.
-
Agentic PIM: AI can act on product data within defined controls.
Why Does MCP Matter for PIM?
MCP, or Model Context Protocol, gives AI applications a standard way to connect to external systems, data and tools.
For a PIM, this can give agents direct access to product records and operations without building a separate custom integration for every AI client. The same MCP server may connect tools such as ChatGPT, Claude, Cursor or a company's own agent.
The presence of an MCP server does not reveal the full story. Buyers still need to examine:
- whether it supports reading, writing or both
- which product data concepts it covers
- whether agents can start workflows or publication
- how authentication and permissions work
- whether the feature is live, in beta or planned
An MCP server that only retrieves product records is useful for search, support and recommendations. It is not the same as an MCP layer that lets agents update attributes, manage catalogue structures and trigger product operations.
How Do the Five PIM Vendors Compare?
Each vendor takes a different route, from AI-assisted content creation and data checks to connected agents that can read, update and manage product information across workflows. The main difference is not whether AI exists, but how far it can act.
| Vendor | AI functions | Model choice | MCP position | Main agentic commerce direction |
|---|---|---|---|---|
| Bluestone PIM | Autonomous onboarding, enrichment, validation, publishing and product data management | Customers can connect their preferred models | Native MCP with read and write access across core product, catalogue, asset, publishing and workflow concepts | External agents operating governed PIM workflows |
| Akeneo | Onboarding, classification, enrichment, translation and catalogue management | Supports customer-connected LLMs | MCP server in beta | Broad catalogue access, with several operational gaps |
| Inriver | Product data access, content enrichment and developer support | Inriver Inspire and embedded agents | Two MCP endpoints | Querying live data and supporting REST API development |
| Salsify | Conversational assistance and AI tasks inside PXM workflows | Customer AI providers or SalsifyIQ | No native MCP layer presented | AI works mainly within Salsify workflows and channel processes |
| Pimberly | Copy generation, image analysis and reusable AI prompts | Pimbles supports the customer's choice of LLM | No native MCP layer presented | AI supports defined content and attribute tasks inside Pimberly |
The table is based on current vendor product pages and technical documentation.
How Does Each Vendor Approach AI and Agents?
Vendor strategies differ in scope and technical maturity, ranging from AI-supported content generation and automated data validation to agent-based architectures that orchestrate product information across interconnected systems and workflows.
How Does Bluestone PIM Use AI and MCP?
Bluestone PIM combines embedded AI capabilities with a structured product data foundation, an API-first architecture and native MCP support. Its AI tools help teams generate, translate, analyse and review product content, while more than 700 task-level API endpoints provide 100% UI/API parity. This means every operation available through the user interface has a machine-callable API equivalent.
Compatible agents can use MCP to work with core PIM concepts such as products, attributes, relationships, catalogue structures, assets, market contexts, completeness, tasks and publishing. They operate within the platform's existing permissions, validation rules and audit history. Bluestone PIM supports this with a single source of product truth, where data can be validated as it changes and each value can retain its origin and change history. This gives users, connected systems and agents a consistent version of the same product information.
This architecture supports Bluestone PIM's move towards an operating model in which agents take on more repetitive catalogue work across supplier onboarding, enrichment, validation and publishing. The goal is for agents to ingest and map incoming data, fill product information gaps, check records against business rules and prepare approved data for each channel. Product teams remain responsible for goals, brand voice, quality standards, approval rules and exceptions that require judgement. The exact level of automation depends on the workflow, integrations, product configuration and agent tools in use, and MCP coverage should not be treated as identical to the full API surface.
Bluestone PIM already provides the architectural foundation for agent-led product data operations, while end-to-end autonomous execution across every process remains the direction in which the platform is developing.
DOWNLOAD FREE E-BOOK
AI Visibility Guide for Retailers
Learn how to structure product data so AI can find, cite, and recommend your products. Covers GEO, agentic commerce, and 30+ data fields.
How Does Akeneo Use AI and MCP?
Akeneo uses AI across supplier onboarding, product classification, content enrichment, translation and data management. Its approach is focused on helping teams process and improve large volumes of product information more efficiently.
The platform provides an MCP server that supports natural-language access and read and write operations across a broad range of product data. The service remains in beta, and some areas, including media handling and workflow execution, are not yet covered. This gives agents useful access to catalogue records, but they cannot currently carry every process from data retrieval to full workflow completion.
How Does Inriver Use AI and MCP?
Inriver applies AI to product onboarding, enrichment, translation and catalogue processes. Its MCP approach focuses on giving connected AI tools access to live product data and helping developers work with the platform's API.
This makes it useful for search, recommendations, analytics, content support and validation. The scope remains narrower than a full agentic operating layer. External agents can retrieve governed product data and support development tasks, but the platform does not currently present MCP as a way to manage the entire catalogue workflow directly.
How Does Salsify Use AI for PXM and Agentic Commerce?
Salsify places AI inside its existing PXM workflows. It supports content work, data extraction, governance and user assistance as part of processes that combine automated steps with human review.
The platform's approach is centred on helping teams work faster within Salsify and distributing approved product data to external channels, including AI-driven shopping experiences. It does not currently position native MCP as the connection layer through which external agents can directly manage product data and operational workflows.
How Does Pimberly Use AI in Product Data Workflows?
Pimberly uses AI mainly to support product content, image analysis and attribute enrichment. Teams can apply repeatable AI tasks across groups of products to reduce manual work and process catalogue data at scale.
These capabilities remain part of workflows managed inside the Pimberly platform. Its agentic commerce positioning focuses on preparing structured product data for AI-driven discovery and sales channels, rather than giving external agents direct operational access to the catalogue through a native MCP layer.
Which Platform Is Most Ready for Agentic PIM?
Bluestone PIM offers the strongest architectural foundation for companies that want agents to move beyond individual AI-assisted tasks and take a more active role in product data operations.
This position comes from the way the platform is built. More than 700 task-level APIs, full UI/API parity and native MCP give agents machine-callable access to core product data and operations. This foundation supports a growing range of use cases across supplier onboarding, enrichment, validation, workflows and publishing, with the exact level of automation shaped by the company's configuration, integrations and governance rules.
The single source of truth provides the control layer needed for this model. Product data can be validated as it changes, with lineage, permissions and audit history helping teams trace where information came from and how it was updated. This gives agents a governed data foundation to work from as Bluestone PIM develops towards broader end-to-end agentic execution.
Akeneo comes closest in terms of MCP breadth. Its server supports many product data concepts and both read and write operations. The beta status and missing workflow execution limit how far an agent can carry a process today.
Inriver provides MCP access to live product data and tools for API development. This is useful for AI applications and technical teams, but it is a narrower model of agent participation.
Salsify brings AI into PXM workflows and sends product data to AI shopping channels. Pimberly uses AI for repeatable content and attribute tasks. Both can reduce manual work, but neither currently presents the same direct agent-to-PIM operating model.
Is Your PIM Ready for Agents to Do the Work?
AI can help teams write faster, translate more content and find data gaps. Agentic PIM changes the operating model itself.
Instead of waiting for a person to move every product through every step, agents handle supplier onboarding, enrichment, validation and publishing. People define the objectives, rules and exceptions.
Bluestone PIM is built for that shift. Agents run the daily product data work. Your team remains in control of the product truth.
Frequently Asked Questions
Is AI-generated content enough to make a PIM agentic?
No. Content generation produces text or another output from a prompt. It does not mean AI can inspect the catalogue, select the next action, update product data and complete a workflow. An agentic PIM gives AI access to product data and operational tools within defined controls.
Does an MCP server make every PIM agentic?
No. MCP creates the connection, but the vendor decides what the connection exposes. A server may provide read-only search. Another may support data creation, updates, catalogue structure, validation, tasks and publishing. The depth of available tools matters more than the presence of the MCP label.
Why does a single source of truth matter for agentic PIM?
Agents can process product data far faster than people. That speed is useful only when the information underneath is accurate and governed. A single source of truth gives agents consistent product data, clear rules, validation and change history. It reduces the risk of an agent acting on conflicting values from different systems.
What should companies look for in an AI-ready PIM?
Look at the product data foundation first. The platform should support structured attributes, relationships, market contexts, validation and clear ownership. Then examine the operating layer. Can agents access the same product operations as users? Can they write data, start tasks and publish products? Can teams trace every action? Bluestone PIM brings these elements together through its structured data model, task-level APIs, full UI/API parity, native MCP and governed agent workflows.
Which PIM has the best AI?
The right choice depends on the job AI needs to perform. Bluestone PIM has the strongest documented case for open agent operation through MCP. Akeneo combines broad AI functions with a beta MCP server. Inriver links governed enrichment agents with structured AI access. Salsify brings AI into PXM workflows and product-data syndication. Pimberly focuses on scalable content, image and attribute enrichment. A useful selection process starts with workflows, not feature counts.
