Oracle Fusion Cloud Procurement
Independent supplier intelligence for Oracle Fusion Cloud Procurement
Speya is an independent supplier intelligence layer for Oracle Fusion Cloud Procurement. Its AI agents discover, vet, analyze, enrich and monitor suppliers across millions of supplier profiles drawn from 250+ data sources, including suppliers your Oracle instance has never traded with. Shortlists reach Oracle through the Speya API or a structured export. No suite vendor owns Speya.
Book a demo
Your suite today
What does Oracle Fusion Cloud Procurement do for supplier discovery today?
Oracle describes Oracle Fusion Cloud Procurement as an integrated suite spanning Purchasing, Sourcing, Supplier Qualification Management and Self Service Procurement, with Oracle Supplier Model holding supplier master data. Oracle Sourcing runs three negotiation types: RFIs to qualify suppliers, RFQs to collect quotes and auctions for clearly defined goods. Supplier Qualification Management builds questionnaires and qualification initiatives across financial viability, sustainability and compliance. Discovery exists too. Oracle’s 24A readiness note describes Discover New Suppliers Using Generative AI, which finds suppliers “who may or may not be currently registered but possess the capability to provide goods and services for your business.” Release 26B added an in-product agent, Research Suppliers with AI, and Fusion Agentic Applications now include a Sourcing Command Center, a Design to Source Workspace and a Supplier Qualification Workspace.
Where it stops
Where does Oracle Fusion Cloud Procurement supplier discovery stop?
In our reading of Oracle’s own documentation, mostly at the edge of your own instance. Oracle’s 24A readiness note for Discover New Suppliers Using Generative AI documents a cap of up to 5 suppliers per line across the first 10 negotiation lines, and publishes two caveats: the model “doesn’t consider the latest supplier data such as acquisitions, new product introductions, or going out of business,” and the suggestions “may contain inaccuracies and shouldn’t be solely relied upon.” Oracle’s 26B note for Research Suppliers with AI scopes that agent inward: “the search is performed within purchase agreements, purchase orders, negotiations, and supplier profile records.” Oracle documents supplier registration as invitation-based, through a URL the buying organization hands out. Oracle’s SCM documentation describes Oracle Business Network as a trading partner network, and describes its role at supplier creation as matching new suppliers to B2B-ready trading partners.
What Speya adds
What Speya adds alongside Oracle Fusion Cloud Procurement.
Minutes
From need to AI-vetted shortlist
Millions
Supplier profiles, searched live
250+
Data sources, cross-referenced
Speya adds the layer that runs before a negotiation and after the award, and leaves Oracle to do what it does well. A team describes a sourcing need in plain language. AI agents search millions of supplier profiles drawn from 250+ data sources, including official registries, trade and customs data, financial filings and certifications, vet the candidates against certifications, financial health, ESG and sanctions, and return a tiered shortlist in minutes with sources beside every name. Enrich refreshes supplier records you already hold in Oracle Supplier Model: capabilities, certifications, ownership, status. Monitor keeps watching after the award. Every search runs live rather than against a static list. Speya sells no listings and no rankings to suppliers, so no supplier pays to be found.
How it connects
How does Speya connect to Oracle Fusion Cloud Procurement?
Through the Speya API, which is live, with access reviewed per integration and requested at speya.ai/mcp. Integrations are built on request through that open API, where they make technical and commercial sense. It returns structured supplier records a system can write into its own tables. Oracle publishes the receiving side. The Suppliers REST resource supports POST and PATCH on the supplier master and its child collections, so an enriched or newly discovered supplier can be created there. The supplierNegotiations resource adds an invited supplier onto an RFI, RFQ or auction, which is how a shortlist lands rather than a single record. At registration time, supplierRegistrationRequests exposes action/callExternalProviderAPI, which Oracle documents as calling an external service configured to get the details of a company. Import Suppliers FBDI covers bulk loads, and Oracle Integration Cloud can subscribe to the Supplier Created business event. An MCP server is coming so your own agent can call Speya directly. Speya has no connector certified or listed by a suite vendor today.
Book a demo
Questions
Common questions.
Does Speya replace Oracle Fusion Cloud Procurement?
No. Speya is not a source-to-pay suite. It does not run sourcing events, contracts, purchase orders or invoices. It sits beside Oracle as the discovery, vetting and monitoring layer, then hands a tiered shortlist with sources to Oracle through the Speya API or a structured export. Oracle keeps the negotiation, the qualification record, the contract and the transaction.
Does Speya find suppliers Oracle Procurement cannot see?
Yes. Oracle’s outward-facing discovery feature returns up to 5 suppliers per line for the first 10 negotiation lines, and Oracle notes the model “doesn’t consider the latest supplier data such as acquisitions, new product introductions, or going out of business.” The 26B AI search runs inside your own purchase agreements, purchase orders, negotiations and supplier profiles. Speya searches millions of supplier profiles from 250+ data sources with no requirement that a supplier registered anywhere first.
How does a Speya shortlist reach Oracle Fusion Cloud Procurement?
Three documented routes. Supplier records go in through the Suppliers REST resource, which supports POST and PATCH plus child collections for addresses, contacts, sites, business classifications and products and services. A shortlist goes onto a sourcing event through the supplierNegotiations child suppliers resource. At registration, action/callExternalProviderAPI calls an external provider for company details. Bulk loads use the Import Suppliers FBDI template. Shortlists also export as spreadsheets.
Is Speya independent of Oracle?
Yes. Speya is built and operated by Findmyfactory AB in Stockholm and is not owned by, or bundled into, any procurement suite or ERP vendor. Suppliers do not pay to be listed or ranked. In our assessment, ownership shapes roadmaps in this category. Oracle announced the DataFox acquisition on 22 October 2018, and Oracle Support now publishes an end-of-life FAQ for DataFox Supplier Intelligence, Doc ID 2972969.1. Coupa announced a definitive agreement to acquire Scoutbee on 6 October 2025. Coupa Ventures joined the Interos Series C announced on 6 December 2021.
Go deeper
Read next.
The ranking
The best supplier intelligence tools for this suite, compared on coverage, vetting, independence and fit.
Why independent
What independent supplier intelligence means, and why it matters when your suite already has a supplier network.
Sources
Discover New Suppliers Using Generative AI in Sourcing, 24A (Oracle readiness)
Supplier negotiations REST: patch an invited supplier (Oracle docs)
Set up the supplier external data provider integration (Oracle docs)
Supplier Model process integration and the Supplier Created event (Oracle docs)
FAQ: Oracle DataFox Supplier Intelligence Cloud Service End of Life, Doc ID 2972969.1
Oracle Cloud Customer Connect: will the deprecation of DataFox services need to be replaced
Sync ESG Data from EcoVadis to Suppliers in Oracle Procurement Cloud (Oracle doc G10558-01)
Gartner Hype Cycle for Procurement and Sourcing Solutions, 2025 (vendor-hosted reprint)
Disclosure
Speya is not affiliated with, endorsed by or in partnership with SAP, Coupa, JAGGAER, Ivalua, GEP, Oracle, Workday, Zycus or any other vendor named on this page. Product names are trademarks of their respective owners and are used only to identify the products discussed. Statements about third-party products reflect the public sources listed above as of the date shown. Speya does not guarantee they are complete or current and corrects reported errors through the contact page. Speya connects to third-party systems through its open API: enterprise teams can build a custom integration, or ask Speya to scope one, on request and where it makes technical and commercial sense. Speya does not offer a certified or vendor-listed connector for these systems and does not warrant compatibility with, or the availability of, any third-party product.