Wer liefert was (WLW) Scraper (Pay-Per-Result)

Turn WLW (werliefertwas.de) into a clean, ready‑to‑use B2B supplier lead list — with pay‑per‑result pricing.

This actor is built for agencies, sales ops, and automation builders who want WLW supplier data without a monthly commitment. You only pay for successfully extracted, deduplicated company records.

Looking for the most cost‑effective option for ongoing or high‑volume scraping?
If you run large or recurring workflows, see the WLW Scraper (Rental) version.

---

🚀 Built for agencies

This scraper focuses on what agencies actually need: clean company rows, predictable structure, and data that drops straight into outreach workflows.

• Pay per result You are charged only for each unique company record written to the dataset — no subscription required.

• One company = one result Results are deduplicated at company level using WLW’s stable internal company identifiers, so you get a clean dataset — no manual cleanup required.

• Outreach‑ready data Emails, phone numbers, websites, locations, company size, and supplier categories — flattened for Excel, Google Sheets, or direct CRM imports.

• What they actually sell Product names, categories, and portfolio keywords help you segment, personalize, and prioritize outreach without additional research.

• Scales beyond WLW’s UI limits An optional experimental partitioning mode allows broader searches when WLW’s page limit gets in the way.

• Built for unattended runs Rate‑limited, resilient, and designed to run reliably on large queries.

• Clean exports by default Works out of the box with CSV, Excel, JSON, and Apify’s table view.

---

🎯 Typical use cases

• B2B Lead Generation – Build supplier lists by industry, size, and region
• Procurement Research – Map potential vendors and manufacturers
• Market Mapping – Understand who operates in a given niche
• Sales Ops / CRM Enrichment – Add missing contact and portfolio data
• Automation Agencies – Feed WLW data directly into pipelines

---

⚙️ Input

Parameter	Type	Default	Description
query	string	—	Search term you’d type on Europages (required).
region	string	—	Country filter (alpha‑2, e.g. DE, FR, IT).
verifiedOnly	boolean	false	Include only verified Europages companies.
maxPages	number	—	Max number of result pages to scrape (Europages hard‑limit ≈ 100).
enableExperimentalPartitioning	boolean	false	Attempts to exceed Europages’ page limit. Advanced / experimental.
latitude	number/string	—	Center latitude for geo‑radius search (optional).
longitude	number/string	—	Center longitude for geo‑radius search (optional).
radius	number	50	Search radius in kilometers. Used only when latitude & longitude are set.

Geo‑radius filtering behavior

• Geo filtering is applied only if both latitude and longitude are provided.
• If only one of latitude, longitude, or radius is set, no geographic filtering is applied and a warning is emitted.
• When latitude and longitude are provided without radius, a default radius of 50 km is used.

Example:

{
  "query": "CNC machining",
  "region": "DE",
  "verifiedOnly": false,
  "latitude": 48.1372,
  "longitude": 11.5756
}

---

📦 Output: built for spreadsheets & CRMs

Each dataset row represents one unique company with flattened, spreadsheet‑friendly fields.

⭐ Recommended columns for outreach

• name
• website
• email
• phone
• address_countryCode
• address_city
• companySize
• supplierTypes
• productKeywords

For a complete, field‑by‑field description of all available properties, see the Detailed output schema section below.

---

🔍 About result counts

WLW sometimes displays approximate totals in its UI.

This actor returns canonical companies, deduplicated by WLW’s internal company ID. As a result, your final dataset may contain fewer rows than WLW’s UI estimate — but no duplicated companies.

---

🧪 Experimental partitioning (advanced)

WLW enforces a hard limit of 100 pages per search (roughly equal to 3000 results).

When enableExperimentalPartitioning is enabled, the actor attempts to split the search space using WLW’s own filters (region, company size, supplier type) to collect larger datasets.

• May issue significantly more requests
• May generate overlapping queries
• Overlaps are automatically deduplicated

Recommended only for broad searches.

---

🛡️ Reliability & maintenance

• Automatic retries and rate limiting
• Schema‑validated output
• Safe to stop and restart without duplicating results

If WLW changes their structure, just re‑run and attach the log — fixes are rolled out quickly.

---

📘 Detailed output schema

Below is a high‑level explanation of the available output fields. All fields are optional unless stated otherwise.

Source & identifiers

• source – Always "wlw"
• source_companyId – Stable WLW company ID (primary deduplication key)
• source_listingId – Listing‑level identifier (if available)
• source_uuid, source_slug – WLW internal references for traceability

Core company identity

• name – Official company name
• shortName – Shortened or alternative company name (if available)
• description – Company profile description
• logoUrl – Company logo URL

Location & geography

• address – Full formatted address
• address_street, address_postalCode, address_city, address_countryCode – Parsed address components
• geo_latitude, geo_longitude – Geographic coordinates (if available)

Contact channels

• website – Company website
• email – Public contact email
• phone – Public contact phone number

Business classification & filters

These fields are especially useful for segmentation and prioritization.

• supplierTypes – Supplier / business type labels
• companySize – Employee count or size bracket
• industryTags – Industry or category labels

Portfolio & offerings

• productNames – Flattened list of product or service names
• productKeywords – Aggregated keywords describing the offering
• portfolio – Structured portfolio entries (if available)

Trust & quality signals

• isVerified – Indicates WLW verification status
• certifications – Listed certifications (if available)
• foundingYear – Year the company was founded

Metadata

• meta.scrapedAt – Timestamp of the scrape
• meta.query – Search query used for this run

---

💬 Support

Questions, edge cases, or feature requests?

Open a support ticket or attach a failing run log — we’ll take care of it.