Back to Hub

So You Want to Build a P2P Marketplace? An Introduction to Unique B2B Technology, Platform and Application Requirements

Procure-to-pay (P2P) solutions do not just have to take the form of “vanilla” cloud/SaaS applications. Increasingly, organizations are becoming aware of the power of B2B marketplace models and platform-as-a-service (PaaS) models, which can enable greater flexibility to configure P2P capabilities for a combination of internal and third-party users — and in certain cases, to leverage the buying, distribution, payment / financing (in the case of banks), and supply chain assets of the marketplace sponsor to create entirely new business models through the use of technology.

In many ways, this is the realization of the vision of the original B2B marketplaces from two decades ago (e.g., Commerce One MarketSite, i2 TradeMatrix, Ariba/Tradex, Atlas Commerce, etc.), but with technology that can support the complex requirements involved in many-to-many and multi-tier collaboration models, as well as integration approaches that go beyond standard API calls.

This is B2B nirvana for procurement and supply chain geeks like us who have lived through multiple cycles of marketplace enthusiasm (madness?). The fact that a number of vendors exist today that can service these models effectively is testament to just how far technology has come in recent years. This includes not only the usual P2P best-of-breed subjects supporting these models (e.g., Basware, Coupa, Ivalua, SAP, Tradeshift, etc.) but also names you might not be familiar with as well.

This Spend Matters PRO brief provides an introduction to the types of platform and functional capabilities necessary for organizations considering building a marketplace model or leveraging an existing PaaS application ecosystem to go outside the box of standard P2P process models and operating models for internal use only.

Leveraging Spend Matters’ experience in managing the technology selection processes for marketplace initiatives and our SolutionMap vendor RFI requirements, our analysis introduces a range of platform and application requirements that companies should consider when evaluating solutions that can power the requirements of marketplace models for B2B relationships beyond the standard requirements expected of P2P solutions.

These include core platform components, data schema, data management, workflow, personalization, supplier portal, supplier information management, analytics, globalization and related requirements.

This article requires a paid membership that has access to AP Automation / Invoice-to-Pay or Procure-to-Pay.
Please log in or create an account to view this article