Industrial and electronic components
Extract Electronic Component Data from Supplier Catalogs
Electronic component catalog extraction turns supplier PDF or spreadsheet entries into product records with part number, name, brand, typed technical attributes, and page-and-quote evidence. The current supplier-catalog contract keeps unsupported values absent and marks each new record pending human review.
Updated August 28, 2026
Separate component identity from technical attributes
Component catalogs combine stable identifiers with category-specific specifications. The current supplier-catalog contract keeps supplier SKU, source record key, name, brand, and description in named fields. Category, price, currency, pack quantity, and electrical or mechanical specifications can remain typed attributes without forcing every family into one fixed table.
This distinction matters for distributors and manufacturer product teams. A terminal block may need rated voltage and pole count, while a connector may need pitch, contact count, and mounting style. The field name, value type, unit, and source statement should travel together.
- Keep the exact manufacturer or supplier part number as source identity.
- Represent voltage, current, temperature, dimensions, and counts with explicit units or types.
- Split variants only when the supplier source distinguishes separate orderable records.
- Leave package, tolerance, lifecycle, or compliance values absent when the source does not state them.
Tie ratings and variants to source evidence
Technical tables often use shared headers, footnotes, symbols, and continuation pages. A value can look plausible while belonging to a neighboring variant. Field-level page and quote evidence gives a reviewer a concrete place to verify the proposed mapping.
The catalog contract also records normalization state and validation failures. That supports an explicit exception when a required SKU is missing or a value lacks evidence, instead of silently inventing a default from the product family.
Prepare component records for catalog review
The current tool produces schema-validated JSON as a staging record. Product operations teams can inspect identity fields, flexible attributes, source evidence, and pending review status before deciding how the record maps to their taxonomy.
Reusable generic mapping profiles and approved CSV or JSON export are available. Direct PIM synchronization, distributor cross-referencing, bill-of-material enrichment, stock lookup, and lifecycle lookup are not currently available.
Illustrative example
Example component record with evidence
The current supplier-catalog fixture represents a WAGO PCB terminal block and includes exact field paths, page references, and source quotes.
Supplier catalog · pages 77–78
739-102 | PCB terminal block WAGO · Rated voltage 320 V · 2-pole
SupplierCatalogV1 record
{
"schemaVersion": "1.0.0",
"promptVersion": "1.2.0",
"source": {
"sourceHash": "0000000000000000000000000000000000000000000000000000000000000000",
"supplierName": "WAGO",
"title": "PCB Terminal Blocks and Connectors",
"pageCount": 400
},
"products": [
{
"sourceProductKey": "739-102",
"supplierSku": "739-102",
"name": "PCB terminal block",
"brand": "WAGO",
"attributes": {
"ratedVoltage": {
"type": "text",
"value": "320 V"
},
"poles": {
"type": "number",
"value": 2
}
},
"confidence": 0.95,
"fieldEvidence": [
{
"fieldPath": "sourceProductKey",
"pageNumber": 77,
"quote": "739-102",
"sourceHash": "0000000000000000000000000000000000000000000000000000000000000000"
},
{
"fieldPath": "supplierSku",
"pageNumber": 77,
"quote": "739-102",
"sourceHash": "0000000000000000000000000000000000000000000000000000000000000000"
},
{
"fieldPath": "name",
"pageNumber": 77,
"quote": "PCB terminal block",
"sourceHash": "0000000000000000000000000000000000000000000000000000000000000000"
},
{
"fieldPath": "brand",
"pageNumber": 1,
"quote": "WAGO",
"sourceHash": "0000000000000000000000000000000000000000000000000000000000000000"
},
{
"fieldPath": "attributes.ratedVoltage",
"pageNumber": 78,
"quote": "Rated voltage 320 V",
"sourceHash": "0000000000000000000000000000000000000000000000000000000000000000"
},
{
"fieldPath": "attributes.poles",
"pageNumber": 77,
"quote": "2-pole",
"sourceHash": "0000000000000000000000000000000000000000000000000000000000000000"
}
],
"normalizationStatus": "normalized",
"reviewStatus": "pending",
"validationFailures": []
}
]
}This fixture passes the current supplier-catalog contract. It demonstrates structure and evidence, not a general accuracy rate.
Limitations
- The extraction is not an electrical, safety, lifecycle, or regulatory-compliance verification.
- Dense tables, continuation headers, symbols, and footnotes can require manual variant-by-variant review.
- Cross-references, stock data, BOM enrichment, and direct PIM synchronization are not included.
Frequently asked questions
Which electronic component fields can be extracted?
The catalog contract supports part identity, descriptive fields, commercial values, pack quantity, and flexible typed attributes. The exact technical fields depend on what the supplier source states and what evidence can be retained.
How are component variants handled?
Separate orderable variants should become separate records when the source distinguishes them. Shared headers and footnotes need review so ratings or package details are not copied to unsupported rows.
Does toSchema verify component compliance?
No. It can structure a compliance statement present in a source, but it does not validate certification status, testing, applicability, or current regulatory requirements.
Put it into practice