EU Procurement Buyer & Supplier Intelligence

Find the organizations behind EU public procurement. This Actor aggregates official Tenders Electronic Daily (TED) notices into buyer profiles, winning supplier profiles, and verified buyer-supplier award relationships.

What buyers get

• One organization row per observed buyer or published winning supplier.
• One relationship row per buyer-supplier pair observed in a published result.
• Official identifiers when TED publishes them; conservative fallback identity when no identifier exists.
• Notice counts, award counts, CPV coverage, first/last observed dates, country, city, and official TED source links.
• No personal contact fields. Organization names only.
• Values are never converted between currencies and are never allocated across multiple winners without an unambiguous source value.

Business use cases

• Build account lists for public-sector sales teams.
• Identify repeat-buying authorities by sector and country.
• Find established suppliers and partnership targets.
• Map buyer-supplier relationships for market entry and competitor research.
• Refresh CRM and BI tables with bounded date windows.

Quick start

Use a small seven-day window, choose a buyer country such as FRA, set CPV prefix 72 for IT services, and keep maxNotices at 25 for a first run. Choose both to receive profiles and relationship rows.

The Actor uses a maximum 31-day inclusive window, a maximum of 1,000 source notices per run, and TED's stable iteration paging (de-duplicated by notice) to keep cost predictable.

Output fields

Organization rows use record_type=organization, organization_role=buyer or supplier, and include organization_id, organization_name, official_identifier, country_code, notice_count, award_count, cpv_codes, official_notice_urls, and source_notice_ids.

Relationship rows use record_type=relationship and include buyer_id, buyer_name, supplier_id, supplier_name, country codes, award_count, cpv_codes, award dates, and official notice URLs. They also include source_notice_ids for traceability to the exact published notices.

Data boundary

TED result notices can omit winner information. A relationship is emitted only when TED marks a tenderer with winner status. A notice-level monetary amount is not copied into every supplier row when several winners exist. Verify the linked official notice before commercial, legal, procurement, or compliance decisions.

Data sourced from EU Tenders Electronic Daily (TED), https://ted.europa.eu. This is an independent transformed dataset and is not an official EU product, endorsement, or affiliation.

Pricing

The launch price is $1.90 per 1,000 intelligence rows. Apify platform compute and storage charges may apply separately. Start with a small bounded run before scaling a recurring workflow.

Reliability and billing

• Temporary source errors (timeouts, rate limits, 5xx responses) are retried automatically with backoff before a run gives up.
• Rows are published only after the source query finishes. If the official source stays unavailable, the run fails with a clear message and no rows are delivered or charged.
• Rows are de-duplicated across result pages, so you never pay twice for the same record.
• The Actor respects your maximum cost per run: it fetches only as many rows as your budget allows and says so in the status message and RUN_SUMMARY.

Support

For a run problem, open an issue from this Actor's Apify page and include the run ID, sanitized input, timestamp, and first relevant log message. Never share Apify tokens or private customer data. For commercial or integration questions, contact Arclay at https://arclay.tn. Target response time is two business days. and platform usage included where configured in Apify Store. Check the live Pricing tab for current tier details. Start with 25 notices to preview output.