This Kompass scraper tutorial shows how to export selected Kompass product and supplier detail pages into a local CSV with the Kompass Data Scraper for Supplier CSV Export. You will prepare approved URLs, import the template, set the export path, run a small batch, and validate the supplier fields before scaling.
Before you start
Prerequisites for scraping Kompass data
Kompass is a B2B company and supplier discovery directory; the Kompass Business Place page positions it as a way to search companies by sector, location, and activity, while the globalEDGE overview describes Kompass as a business-to-business company search resource. That makes it useful for sourcing, market mapping, and lead research, but it also means you should treat collection rules seriously.
You need the UScraper local desktop app, the Kompass Data Scraper template, a folder for CSV exports, and a short list of Kompass product or detail URLs your team is allowed to process. The template is URL-driven: it is best when you already have specific supplier or product pages, not when you want to crawl every search result from a broad directory query.
Technical access is not the same as permission. Review Kompass terms, robots guidance, database-rights risk, privacy obligations, and local law before using exported data for outreach, enrichment, resale, or automated decision-making.
Workflow shape
How the Kompass data scraper works
The JSON export is the authoritative workflow definition. The project uses a simple multi-URL path: open each supplied Kompass URL, wait for load, sleep briefly so dynamic content can settle, confirm the page body exists, export structured fields, then continue to the next input URL.
Navigate -> Wait for Page Load -> Sleep -> Wait for Element
-> Structured Export -> Loop Continue
The Structured Export block writes one row from the page body. The column logic first tries real page selectors such as headings, product-description fields, supplier links, telephone elements, and metadata. If a live page is blocked or sparse, the stock template includes fallback behavior for the bundled sample URLs and URL-slug parsing for other Kompass product URLs. Treat those fallbacks as a testing aid, not as a substitute for live validation.
{
"fileName": "kompass_scraper.csv",
"fileMode": "append",
"includeHeaders": true,
"saveLocation": "C:\\Users\\theskd\\Documents\\UScraper\\templates",
"rowSelector": "body",
"columns": [
"titre",
"nom_fournisseurs",
"description",
"page_url",
"telephone"
]
}
kompass_scraper.csvColumn
titre
Product or page title from the Kompass detail page, with URL-slug fallback when needed.
Column
nom_fournisseurs
Supplier or company name from visible supplier, brand, seller, or company-name selectors.
Column
description
Visible product or service description, metadata fallback, or approved sample fallback for bundled URLs.
Column
page_url
The exact Kompass URL visited by the workflow.
Column
telephone
Visible phone field from tel links, telephone selectors, page text, or sample fallback when available.
Runbook
How to scrape Kompass product and supplier URLs
Prepare source URLs
Build a short list of approved Kompass product or supplier detail pages. Open several manually and note whether title, supplier, description, and phone data are visible.
Import the template
Open the Kompass Data Scraper template, download the JSON workflow, and import it into UScraper.
Replace the Navigate list
In the Navigate block, replace the three bundled sample URLs with your source URLs. Keep the wait, sleep, and body-check blocks in place for the first run.
Confirm the export path
In Structured Export, set the save location for your project, keep headers enabled, and keep append mode if you want one combined CSV for all URLs.
Run and validate
Run a small batch, compare every column against the live page, then increase the URL list only after the output is clean enough for review.
Append mode is convenient because every URL lands in the same file. It can also mix test rows with production rows. Before a client run, either clear the previous CSV or use a dated folder such as kompass-supplier-research-2026-06-25.
Validation
Validate the Kompass CSV before using it
Use a spreadsheet check before importing the CSV into a CRM, enrichment tool, or analysis workbook. The goal is not just "rows exist"; the goal is "each row means what the column says it means."
| Check | What to inspect | Why it matters |
|---|---|---|
| Source URL | page_url opens the same Kompass page you expected | Keeps each row auditable. |
| Product title | titre matches the page title or product name | Slug fallback can produce readable but imperfect titles. |
| Supplier name | nom_fournisseurs is the supplier, not a generic navigation label | Company-name selectors can change across country sites. |
| Description | description contains product or service copy, not cookie or CAPTCHA text | Block pages and consent pages can pollute exports. |
| Phone | telephone appears only when visible to the browser session | Blank phone values are valid when the page does not expose one. |
If Kompass returns a DataDome or CAPTCHA page, stop and inspect the browser. Do not build around bypassing access controls. The practical fix is usually to reduce volume, run a smaller approved list, solve any legitimate manual access step in the visible browser, or use an approved data provider or API when the project requires contracted access.
Alternatives
Kompass scraper alternatives and tradeoffs
There are several ways to extract company data from Kompass. Apify actors can be useful when you need hosted runs or API-oriented automation. Octoparse, Thunderbit, and other no-code tools can work well for template-driven cloud scraping. Managed services fit teams that want a vendor to own maintenance.
UScraper is a different fit: supervised local desktop extraction where you can inspect the workflow, keep the CSV on your machine, edit the blocks, and validate the first rows yourself. That is useful for small sourcing projects, supplier shortlists, and review-heavy B2B research where you care more about traceability than unattended bulk collection.
| Approach | Good fit | Tradeoff |
|---|---|---|
| UScraper template | Local CSV exports from approved URL lists | You own validation and selector maintenance. |
| Cloud scraper actor | Scheduled runs, API calls, hosted execution | Data custody, pricing, and usage rules differ by provider. |
| Managed scraping service | Outsourced delivery and maintenance | Less direct workflow control and usually slower iteration. |
| Manual copy-paste | Tiny one-off checks | Slow, inconsistent, and hard to audit. |
FAQ
Kompass data scraper FAQ
Kompass pages can contain publicly visible business information, but automated collection may still be limited by current terms, robots guidance, database rights, privacy rules, and local law. Keep runs narrow, avoid bypassing access controls, and get legal review before commercial reuse.
Next step
Download the Kompass Data Scraper template
Use Kompass Data Scraper for Supplier CSV Export as the download path, then keep this tutorial open while you validate your first CSV. For adjacent workflows, browse all UScraper templates or return to the UScraper blog for more scraper tutorials and comparison guides.