All Posts

Should you Manage your Product Information Taxonomy In a TMS or a PIM System?

It’s a very open question … as they always are … and it depends on the weighting of some of the considerations we’ll look at below.

We’re working with a client right now – a manufacturer who is a definite success story in both the technologies they sell and also in online B2B (and also e-procurement) – on re-platforming their whole content supply chain, from incoming supplier’s product information all the way through to web and web search presentation.  They have business needs for multiple taxonomies that will support appropriate content description enrichment and multiple, successful, findability pathways for customers.

Managing Product Information from Suppliers

Because they manufacture, and also sell consumables and other items from 3rd party partners, they own, alongside all major companies who ingest product information from suppliers, the business challenge of managing all aspects of product information that enters their content supply chain.  Many, many challenges – product information “cleansing”,  normalization, outputting product attributes to their own publishing standards, building rules to catch exceptions in attribute value ranges and attribute value co-relationships etc.

And then … there is the product taxonomy – the hierarchy of products in “families” that their product managers need to maintain.  The reason that we have this question – “where are you going to maintain this product hierarchy?” – is that Product Information Management (PIM) systems mostly all have capability to manage taxonomy, i.e. product hierarchy.  And indeed, as an aside, so too do applications one step upstream from PIM; Oracle PDQ, as one exemplar, manages product hierarchy robustly at the data-cleansing stage. 

So … let’s count on our fingers (old fashioned I know) the complexity.  Our large manufacturer is going to manage product taxonomy and multiple other business-essential taxonomies.  They are re-platforming their total content supply chain … so vendor selection includes PIM (Product Information Management), e-commerce, CMS (content management system), TMS (taxonomy management system) and DAM (digital asset management).  As well as the whole back-end ERP ecosystems integration and a front end of dynamic web site, first class site search and parallel first-class e-procurement.

Requirements Considerations and Trade-offs with TMS

TMS or PIM for the product taxonomy?  In a complex content supply chain, that depends … on very surgical and precise analysis.  Of?  Dataflows, workflows, actors (with very, very different needs that need to work in unison as the technology will do), successful governance, and the UX of customers.  And more.

For this client we did compare PIM vendors and their taxonomy management capabilities with enterprise taxonomy management systems – using our own taxonomy comparison requirements matrices.  And we also holistically looked at taxonomy dataflows, taxonomy workflows, the business needs of all actors who interact with “their” product taxonomy, derived from the canonical, source-of-truth product taxonomy, and governance.  Several decision facets were quite clear.  Different actors who work with product taxonomy have very different business needs and should they all be “forced” to work in the same application?  Product managers, from a taxonomy point of view, have very different needs (and tasks and outcomes) from product marketers … and from the financial group who utilize product taxonomy in their business intelligence.  Dataflows and architecture are synergistic … and that impacts also what to do with taxonomy.  Product taxonomy is not the only taxonomy in play here.  Far from it (remember description enrichment and findability?).

The Taxonomy Management Solution

We walked shoulder to shoulder with this client and … product taxonomy was to be managed (canonically) in the PIM we assisted them in selecting.  All other taxonomies were to be managed in a TMS we assisted them in selecting.    The PIMs we looked at just did not have all the rich taxonomy functionality needed to support all the content enrichment and content choreography this client needed from taxonomy.  And all taxonomies were to be propagated through the content supply chain from the TMS.  It is a better practice to propagate taxonomy into a complex content supply chain from one “hub” – a TMS – rather than from multiple taxonomy hubs.

Final Thoughts - Guidelines for those Considering Similar Initiatives

No one solution is the same for all.  Analyze (weighted) it through.  Be (very) open to non-standard solutions.  The key really for this client, and for any group undertaking similar content supply chain initiatives, is to be crystal clear on dataflows and actors and their content choreography tasks (that all need to mesh together in sequence).  Taxonomy dataflow is complex in a complex content supply chain. 

Earley Information Science Team
Earley Information Science Team
We're passionate about enterprise data and love discussing industry knowledge, best practices, and insights. We look forward to hearing from you! Comment below to join the conversation.

Recent Posts

First Party Data: The New Imperative

The need for accurate data to support digital transformation and the emergence of new restrictions on the use of third-party data have prompted many companies to focus their attention on first party data.

Knowledge Graphs, a Tool to Support Successful Digital Transformation Programs

Knowledge graphs are pretty hot these days. While this class of technology is getting a lot of market and vendor attention these days, it is not necessarily a new construct or approach. The core principles have been around for decades. Organizations are becoming more aware of the potential of knowledge graphs, but many digital leaders are puzzled as to how to take the next step and build business capabilities that leverage this technology.

[RECORDED] Powering Personalized Search with Knowledge Graphs

Transforming Legacy Faceted Search into Personalized Product Discovery The latest in e-commerce trends is the transformation of legacy faceted search into a more personalized experience. By applying semantic reasoning over a knowledge graph, contextual information about a customer can be combined with product data, delivering relevant search results tailored to them. The first half of this webinar is designed for the business executive. We’ll focus on why personalized search is an essential e-commerce ingredient. And we’ll demystify the process of implementing a more personalized product discovery experience for your customers. The second half of the webinar is designed for the data strategist. We’ll cover the data modeling required to build knowledge graphs for successful personalized search. We’ll discuss some real-world cases and cover the steps you can take to get started. Who should attend: Executives who care about e-commerce and the data experts who enable them. Speakers: