TL;DR
- Use procurement notices to understand buyers, suppliers, awards and purchasing context. An award is evidence of a reported procurement outcome, not proof that a supplier now needs your product.
- Start with Find a Tender for the relevant UK notices, TED for covered European procurement and SAM.gov's documented opportunity/award routes for US federal work.
- Keep notice, procedure, lot, buyer and supplier identifiers separate. Several notices can describe one procurement, and several suppliers can share an award.
- Buy an aggregator when it demonstrably improves coverage, matching, history or workflow. Public API access still has integration and review costs.
What procurement evidence adds
Public procurement data can reveal that an organisation buys a category, that a supplier serves public-sector customers or that a contract has a stated value and term. It is useful account context for vendors selling to suppliers, public buyers or adjacent service providers.
Interpret the stage first. A planned procurement, invitation, award and modification are different observations. A supplier listed in a tender document is not necessarily the winner. An award ceiling is not necessarily money already paid. Preserve the notice wording and status rather than turning every value into realised supplier revenue.
Coverage depends on market, thresholds, authority and notice requirements. This guide does not establish a universal legal rule for publication. Verify the source's current coverage and the relevant procurement rules for a specific bidding or legal decision. Our company data guide covers the commercial identity layer alongside these public records.
Three official source routes
| Source | Useful scope | Technical basis | Main account-research limitation |
|---|---|---|---|
| Find a Tender | Relevant UK public procurement notices | Published notice/OCDS interfaces | Notice coverage is not every UK purchase |
| TED | Covered European procurement | Search API and published notices | Version, lot and multilingual interpretation |
| SAM.gov | US federal opportunities and awards via documented services | Separate opportunity/award APIs | Access, data scope and versions vary by service |
Find a Tender
The UK government's Open Contracting publication links Find a Tender's OCDS release-package interface and data documentation. A structured release lets an engineering team retain procedure and party relationships rather than scraping a notice page into unrelated text fields.
Use it when the UK notice scope fits the account research. Retain the procurement identifier and release/version information, then inspect related notices before calling a procedure new. Map buyer and supplier roles separately; both can be organisations, but they imply different commercial relationships.
The limitation is coverage and interpretation. Not every purchase or supplier appears in the same portal or notice stage. Choose a direct official route for a bounded UK programme with technical ownership. For a broader estate, assess other official portals or an aggregator, and keep the underlying source trail.
TED
TED's Search API documentation describes access to published notices for analysis and reuse. Its developers' corner explains APIs and notice formats, including eForms. This is useful for a multi-country programme needing a consistent starting interface.
Preserve country, language, classification, notice type, procedure and lot. A notice's title may not describe the exact lot awarded to a supplier. The search help also explains that versions and search options affect which notices appear, so a latest-version filter can hide the history needed to understand a change.
Choose TED for its covered market and official evidence. Avoid treating it as a complete list of every purchase in every European country. Validate the specific geography and category, and model legacy/eForms differences before comparing fields across a long history.
SAM.gov
GSA's Get Opportunities API documents public opportunity search and points to data services for versions. The Contract Awards API documents a separate award service with access-dependent data. A current opportunity endpoint should not be used as a presumed complete award history.
This route fits US federal account research where the documented fields and account access meet the requirement. Use the appropriate API key/access, pagination and date filters, then reconcile known records against the portal or supported extracts. Keep identifiers rather than matching opportunities by title alone.
The non-fit is assuming one API contains every state, local and federal procurement with identical disclosure. Define the market and stage first. Select the official data service that owns it, and retain source/access limitations in the account evidence record.
Connect notices to the right account
Keep buyer, supplier, contracting entity and commercial group distinct. A public buyer can have an administrative name unlike its website brand. A supplier may be a consortium or a subsidiary of the company your seller recognises. Match registration identifiers and jurisdiction where available; names alone should create candidates.
Retain procedure, lot, notice and award IDs. Deduplicate updates under the same procurement rather than deleting similar titles indiscriminately. An amendment can change value, dates or scope and therefore belongs in the history.
Normalise currency and units only with an explicit rule. Keep original values and whether tax is included where stated. Do not sum estimated tender values and awarded values as though they were different completed contracts. A multi-year ceiling should not be divided into annual revenue without a clearly labelled assumption.
The B2B data API guide covers enrichment after the public-party match. The ABM research guide covers further investigation. Procurement evidence can improve a brief without establishing that the account is ready to buy from you.
Research a thousand suppliers
Consider 1,000 suppliers across two markets, split equally for this hypothetical exercise. Suppose retrieving relevant notices produces 3,000 notice records. Grouping versions and lots leaves 1,800 procurement relationships, and identity review accepts 800 unique suppliers. These counts are assumptions, not measured portal coverage.
Review missing and ambiguous identities separately. A supplier with no result can be outside the source's coverage or have a different legal name; it is not automatically inexperienced in public procurement. Check a known positive subset and a difficult-name subset to expose matching errors.
Assume integration/data processing costs $100 and 200 ambiguous suppliers take five minutes each at a loaded $60 per hour. Review is $1,000, so total is $1,100, or $1.38 per accepted supplier, rounded. Official access fees, where applicable, and supporting services should be checked separately; the calculation is an operating scenario.
If an aggregator costs an assumed $500 but reduces review to 60 cases, review becomes $300 and total $800 before integration differences. That can be rational, but only if the sample confirms the claimed reduction and preserves source evidence. A dashboard's polished supplier profile is not enough.
Use the ABM Account Scoring Template to connect accepted procurement facts to a defined suitability rule. For example, repeated relevant awards may establish public-sector experience, while a particular contract term may warrant additional research. Neither should automatically become an unsolicited urgency claim.
When an aggregator earns its price
Evaluate aggregators on the exact markets, sources, history, entity matching and export/API rights required. Ask for a sample with known awards and difficult suppliers. Require originating notice links and revision history so a buyer can inspect the evidence behind the profile.
An aggregator is useful when it saves maintaining several interfaces or adds reliable normalisation. It is weaker value if it repackages one public source while obscuring the identifiers your integration needs. Obtain a quote showing users, alerts, records, API access, refresh and downstream rights. This article does not invent a universal tariff for procurement intelligence software.
Start with official sources for a bounded programme. Add a commercial layer when its accepted coverage and operator savings justify the contract. Keep the account research decision distinct from legal eligibility or bidding advice, which needs the relevant current rules and responsible specialist.
FAQ
Does a contract value equal supplier revenue?
Not necessarily. It can be an estimate, ceiling, total over several years or a value shared across suppliers/lots. Retain the notice's scope and label any derived estimate explicitly. Do not report the number as realised revenue without supporting evidence.
Is no notice evidence that a supplier has no public customers?
No. Coverage, thresholds, naming and procurement routes can produce missing results. Check source scope and identity before drawing a conclusion. Treat absence as absence from the valid search, not the whole market.
Should amendments count as new opportunities?
Keep them as revisions linked to the procedure, while identifying material changes. A changed deadline or scope can matter, but counting every update as a new procurement inflates activity and confuses the account history.
When should we buy a paid procurement platform?
When the exact sample demonstrates useful additional coverage, reliable matching or lower operating work, with retained provenance and appropriate rights. Compare the whole research cost and accepted supplier output rather than the number of alerts offered.
