Wer liefert was (WLW) Scraper

Turn WLW (werliefertwas.de) into a clean, ready‑to‑use B2B supplier lead list.

This actor is built to help agencies and sales teams turn WLW search results into usable lead data — without fighting pagination limits, messy exports, or brittle scrapers.

---

🚀 Built for agencies

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

• One company = one row 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 WLW (required).
region	string	—	Country filter (alpha‑2, e.g. DE, AT, CH).
verifiedOnly	boolean	false	Include only verified WLW companies.
maxPages	number	—	Max number of result pages to scrape (WLW hard‑limit ≈ 100).
enableExperimentalPartitioning	boolean	false	Attempts to exceed WLW’s page limit. Advanced / experimental.

Example:

{
  "query": "CNC machining",
  "region": "DE",
  "verifiedOnly": false
}

---

📦 Output: built for spreadsheets & CRMs

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

⭐ Recommended columns for outreach

If you just want leads, these columns are usually sufficient:

• 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.

This ensures the dataset represents unique suppliers rather than repeated listings.

---

🧪 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
• Continues scraping even if some fields are missing or change shape

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.