Catalog Management: Technical and Functional Component Requirements (Part 5) — Catalog Contracts and Marketplace/Internet Search [PRO]

kolyadzinskaya/Adobe Stock

Today we conclude our multi-part research brief exploring catalog management functional and technical requirements with an emphasis on the last two requirements we consider in our SolutionMap functional requirements for e-procurement.

The first requirement that we analyze is what we term “catalog contracts,” capability which focuses on pre-negotiated pricing through group purchasing organization (GPO) arrangements, leveraged buying or otherwise third-party negotiated typically contracts outside of what a procurement organization would negotiate itself. The second area, marketplace / internet search and catalog visibility, extends the scope of catalog management capability to integration with online marketplaces (e.g., Amazon Business) and electronic commerce storefronts on the Internet, a requirement which is increasingly becoming more important in the evaluation of e-procurement solutions overall.

If you’re new to the series, check out Part 1 (overall definition/background and supplier network intersections), Part 2 (catalog creation, supplier onboarding and data quality control) and Part 3 (maintenance, workflow and analytics) and Part 4 (catalog objects/methods and catalog mobility capabilities, expectations and requirements).

Whether you’re a procurement organization, supplier, software provider or consultancy, our goal with this series is to provide the bill of materials to allow 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.

For full access to this PRO content: