50
Named operator records
scoped operator records
ERP and business systems · October 2026 research
Review 50 named operator records across 49 conservative count groups. The source scopes cover sourcing, buying, suite declarations and buyer-to-supplier transactions, including dated disclosures and undated company guides. Transaction references do not establish exact Buying or Sourcing modules, paid contracts or group-wide deployment.
Research dated 2026-10-25. Original source dates and website scope stay with the records.
50 scoped operator records
Research dated
Contact-free research examples · CSV
Review 50 named operator records across 49 conservative count groups. The source scopes cover sourcing, buying, suite declarations and buyer-to-supplier transactions, including dated disclosures and undated company guides. Transaction references do not establish exact Buying or Sourcing modules, paid contracts or group-wide deployment.
Download the 2-row CSV preview50
scoped operator records
49
conservative groups
30
operator records
20
operator records
Source checks record when a declaration was read; they do not establish when the technology operated.
Research summary and contact-free examples only. Full-file commercial delivery and source reproduction rights remain unresolved.
CSV columns: name · domain · sourceClass · checkedOn · scope
These approved examples illustrate the 2026-10-25 research. They are not a representative sample of all customers.
infrabuild.com
Company sourcing declaration · 2026-10-25
InfraBuild describes Ariba for supplier bids, RFx and auctions. The statement concerns its sourcing workflow; invited suppliers do not become procurement buyers. Publication date and current runtime are unknown.
bbraun.com
Company buying-workflow declaration · 2026-10-25
The company describes Ariba Buying for indirect goods and services. The page excludes Sourcing and Invoicing from its scope. Publication date, current runtime and whole-group coverage are unknown.
WhosBuilt analysis of the saved October 2026 research. Findings describe this selected cohort, not market share.
20 of 50
Twenty of the 50 records concern buyer-to-supplier transactions only. The other 30 describe sourcing, buying or suite scope; those workflow scopes answer different research questions.
Payment, current runtime, whole-organization coverage and purchasing authority remain unknown.
Research 2026-10-25 · operator records · WhosBuilt saved-record analysis
Source checks span 2026-10-24–2026-10-25. Retained observations and examples keep their original dates.
Review 50 named operator records across 49 conservative count groups. The source scopes cover sourcing, buying, suite declarations and buyer-to-supplier transactions, including dated disclosures and undated company guides. Transaction references do not establish exact Buying or Sourcing modules, paid contracts or group-wide deployment.
| Source class | Count | Scope |
|---|---|---|
| Company sourcing declaration | Not separately counted | 50 named operator records across 49 conservative count groups |
| Company buying-workflow declaration | Not separately counted | 50 named operator records across 49 conservative count groups |
Procurement and transaction scopes: 50 named operator records across 49 conservative count groups Source checks record when a declaration was read; they do not establish when the technology operated.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.