We extract industrial automation catalogues, technical specifications, IO-Link profiles, and compliance certificates from ifm. Delivered as clean JSON, CSV, or Parquet to your infrastructure.
Structured, schema-consistent data across all major object types — delivered clean, typed, and ready to query.
Complete list of extractable fields for Product Specifications objects from ifm.com. All fields typed and schema-versioned.
"article_number": "O5D100", "product_name": "Photoelectric distance sensor", "measuring_range": "0.03...2 m", "operating_voltage": "10...30 DC V", "output_function": "OUT1: normally open / normally closed; OUT2: normally open / normally closed / analogue", "connection_type": "M12 connector", "protection_rating": "IP 65; IP 67", "weight": "0.285 kg"
| # | article_number | product_name | category | sub_category | measuring_range | operating_voltage |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Documentation & CAD objects from ifm.com. All fields typed and schema-versioned.
"article_number": "O5D100", "data_sheet_url": "https://www.ifm.com/download/files/O5D100_DS_EN", "operating_instructions_url": "https://www.ifm.com/download/files/O5D100_OI_EN", "cad_3d_step_url": "https://www.ifm.com/download/cad/step/O5D100", "rohs_status": "Compliant", "eplan_macro_url": "https://www.ifm.com/download/eplan/O5D100_edz", "ce_declaration_url": "https://www.ifm.com/download/files/CE_O5D100"
| # | article_number | data_sheet_url | operating_instructions_url | cad_3d_step_url | cad_2d_pdf_url | ce_declaration_url |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Pricing & Availability objects from ifm.com. All fields typed and schema-versioned.
"article_number": "O5D100", "list_price": 345.5, "currency": "EUR", "region_code": "DE", "stock_status": "In stock", "lead_time_days": 2, "moq": 1, "packaging_unit": "1 piece", "price_timestamp": "2026-05-12T10:15:00Z"
| # | article_number | list_price | currency | region_code | stock_status | lead_time_days |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for IO-Link Data objects from ifm.com. All fields typed and schema-versioned.
"article_number": "O5D100", "vendor_id": "310", "device_id": "875", "bit_length": "32", "process_data_in": "Distance, Switching signal", "min_cycle_time": "6.6 ms", "sio_mode_supported": true, "iodd_file_url": "https://www.ifm.com/download/iodd/O5D100"
| # | article_number | vendor_id | device_id | bit_length | process_data_in | process_data_out |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Accessories & Topology objects from ifm.com. All fields typed and schema-versioned.
"article_number": "O5D100", "accessory_articles": "['E21228', 'E20870']", "connection_cables": "['EVC001', 'EVC004']", "mounting_kits": "['E21228']", "replacement_for": "O5D105", "replaced_by": "None", "compatible_masters": "['AL1100', 'AL1300']"
| # | article_number | accessory_articles | mounting_kits | connection_cables | replacement_for | replaced_by |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Our ifm pipeline handles the technical complexity of industrial component data: dynamic specification tables, regional pricing logic, IO-Link parameter extraction, and nested accessory graphs.
Extract electrical design, measuring ranges, outputs, and environmental parameters. We normalise units and key-value pairs across different sensor categories.
Capture list prices, currency, and availability for specific global regions by managing session cookies and location headers.
Extract vendor IDs, device IDs, process data bit lengths, and cycle times directly from the product pages or associated IODD metadata.
Index direct download URLs for STEP files, 2D PDFs, operating instructions, and CE declarations for every article number.
Map connection cables, mounting kits, and IO-Link masters to their compatible sensors, building a complete relational topology.
Identify phased-out components and extract the direct replacement article numbers to maintain accurate procurement databases.
Extract pinout configurations and wiring colour codes associated with M8/M12 connectors and specific sensor outputs.
Scrape the recommended application domains (e.g. food and beverage, machine tool, mobile machines) for specific component lines.
Monitor specific article numbers for specification updates, firmware revisions, or price changes, delivering only the diffs.
Brief in. Clean data out.
Provide specific article numbers, product families (e.g. pressure sensors), or regional domains. We design the extraction schema.
We configure Scrapy/Playwright crawlers to navigate ifm's dynamic tables, manage regional cookies, and parse technical metadata.
Schema validation, unit normalisation checks, and accessory graph verification before full execution.
Structured technical data pushed to your S3 bucket, Postgres database, or via Webhook on your defined schedule.
Extracting engineering data requires handling inconsistent table structures and regional session states. Here is how our infrastructure manages the ifm catalogue.
A pressure sensor has entirely different specifications than an inductive proximity switch. Our parsers dynamically map ifm's technical tables into structured JSON key-value pairs, regardless of the product category.
ifm routes users and displays pricing based on geography. We inject specific regional cookies and headers into our Playwright sessions to extract accurate local list prices and stock availability.
Industrial components rely on specific cables and mounts. Our crawlers traverse the 'Accessories' and 'Compatible Products' tabs, building an adjacency list of article numbers to map the full system topology.
Instead of downloading heavy CAD files or PDFs during the crawl, we extract the direct, authenticated URLs for STEP files, IODD zips, and data sheets, delivering them as clean string fields for downstream processing.
While B2B catalogues are less aggressive than retail sites, scraping 80,000 components rapidly triggers rate limits. We distribute requests across rotated IP pools and enforce concurrency limits to ensure zero 429 HTTP errors.
Procurement teams ingest list prices and stock availability into ERP systems to optimise purchasing and monitor lead times for critical spares.
Industrial distributors sync ifm technical specifications, images, and documentation links directly into their own PIM systems.
Engineering firms extract CAD links and dimensional data to populate 3D modelling software and digital twin environments.
Sensor manufacturers scrape technical parameters to build automated cross-reference tools against ifm's product lines.
Automation engineers extract IO-Link process data lengths and cycle times to pre-configure PLC networks and fieldbus modules.
Maintenance teams monitor product pages for 'phase-out' warnings and automatically log the replacement article numbers in their CMMS.
"Ifm's catalogue contains the baseline parameters for millions of automated systems worldwide — but extracting structured IO-Link profiles requires a purpose-built pipeline."
Extracting MRO and industrial sensor data requires navigating complex technical tables, regional pricing contexts, and nested accessory graphs. DataFlirt manages the proxy rotation, session state, and schema normalisation so your engineers receive clean, queryable telemetry.
Everything supported by our ifm.com scraper — rendered SPA elements, auth walls, rate-limit evasion and beyond.
Open-source tooling on proven cloud infra — no vendor lock-in, full observability.
Scrapy manages the crawl frontier across ifm's category tree, while Playwright handles the dynamic rendering of technical tables and regional cookie states.
Raw technical attributes are ingested into PostgreSQL, where complex JSONB queries normalise inconsistent unit formatting across thousands of sensor types.
Apache Airflow schedules the pipelines, manages regional context switching, and handles the delivery of structured files to client data lakes.
Data delivered to where your team already works — no new tooling required.
About ifm.com scraping, legality, and pipeline operations.
Ask us directly →Yes. We configure pipelines to target specific ifm regional domains (e.g., ifm.com/de, ifm.com/us) or inject appropriate location cookies to ensure the pricing and stock availability match your required geography.
Our standard pipeline extracts the direct download URLs for CAD files, PDFs, and IODD archives. If you require the physical files, we can configure an S3 sync job to download and store the assets in your environment.
ifm uses dynamic tables based on product type. Our parsers dynamically extract the key-value pairs from the DOM and map them into a flexible JSON structure, ensuring no technical parameter is dropped regardless of the sensor category.
Scraping publicly available catalogue data, technical specifications, and list pricing is generally permissible. DataFlirt targets only public, non-authenticated engineering data. We do not circumvent B2B login walls to extract proprietary customer discounts.
Yes. We can monitor specific article numbers on a daily or weekly cadence. If the product status changes to phased out, we capture the change and extract the recommended replacement article number.
For defined lists of critical article numbers, we can run daily or hourly extraction pipelines. For the entire global catalogue, we typically recommend a weekly or monthly refresh cycle to balance compute costs.
20-minute scoping call. Pilot dataset within the week. Production within two. Whether you need a complete catalogue export for your PIM system or continuous monitoring of MRO pricing — we scope, build, and operate the pipeline. Tell us what you need.
