Catalog Management: Technical and Functional Component Requirements (Part 4) — Catalog Objects and Mobility

It’s possible to build or use a “good” e-procurement solution that has rudimentary catalog management. But it’s impossible to deliver or leverage a great one, unless its catalog management capabilities are best in class compared with the rest of the e-procurement and procure-to-pay (P2P) pack.

Based on our SolutionMap functional requirements for e-procurement, this multipart Spend Matters PRO research brief defines all of the elements of catalog management. It also provides a feature checklist of the elements that comprise each component, defining what constitutes best in class performance in each case. Today, in Part 4, we flesh out catalog objects and mobility capabilities, expectations and requirements.

Those new to this series can catch up with Part 1 (background and supplier network intersections), Part 2 (catalog creation, supplier onboarding and data quality control) and Part 3 (maintenance, workflow and analytics). Whether you’re a procurement organization, supplier, software provider or consultancy, this series provides the bill of materials to inform the assembly of the best possible catalog management solution, either on a unified basis with the same e-procurement platform or integrated with a broader solution.