Product Data for Cables: Types, Cross-Sections, Standards

Type codes, cross-sections and cut-to-length logic: cable data has to be exact to the millimetre — where ETIM helps, and where the longtail forces manual work.

Jakob Feinböck, ProductbayJuly 4, 20267 min read
☝️Key takeaways
  • Cable data is precision-critical: type code (NYM-J, H07V-K), cross-section in mm² and number of cores must be typed and validated — one wrong value ships the wrong product.
  • ETIM defines clean feature sets for the common cable classes, but thins out in the longtail: special cables, connectors and niche brands arrive without a clean class.
  • Cables are cut-to-length goods — the selling unit, price per metre and step quantities belong to the product data too.
  • Productbay normalises type, cross-section and core count into one structure and uses AI enrichment exactly where ETIM stops: the accessory longtail.

A cable looks like the simplest product in the catalog and behaves like one of the least forgiving. There is almost no marketing copy to write — but every one of the handful of attributes that does matter has to be exactly right. Ship a 1.5 mm² NYM-J where the customer needed 2.5 mm² and you haven't just sent a slightly-off product; you've sent the wrong one, and on the electrical side that can be safety-relevant.

Product data for cables are the precise, typed attributes that identify a wire exactly — type code, cross-section in mm², number of cores, rated voltage, standard — plus the cut-to-length selling logic on top. This is a focused corner of the broader electrical wholesale data challenge: same multi-supplier pain, but concentrated into a few attributes that leave no room for error.

Which type and standard attributes make cable data so unforgiving?

Where soft goods tolerate a bit of fuzzy free-text, cables demand exact, typed values. The core attribute set is small but strict:

  • Type code: NYM-J, H07V-K, NYY-J, H05VV-F and dozens more — a compact shorthand that already encodes construction, insulation and use case. It has to be parsed, not treated as a random string.
  • Cross-section in mm²: 1.5, 2.5, 4, 6 … safety-relevant and non-negotiable. A comma-versus-dot mismatch or a value in the wrong field turns a correct feed into a wrong product.
  • Number of cores: 3G1.5, 5G2.5 — the core count and protective-earth marker sit inside the type notation and have to be read out consistently.
  • Rated voltage & standards: 300/500 V, 450/750 V, plus VDE / DIN / harmonised HD references that buyers filter and compare on.

Add the cut-to-length (Meterware) logic — selling by the metre, on the drum or in fixed ring lengths, with a base price per metre and step quantities — and the data model gets a second dimension most other products never have. Miss it, and the shop miscalculates prices or offers unsellable quantities.

How far do ETIM features cover cables — and where do they stop?

ETIM is the classification standard of the electrical trade, and for cables it is genuinely strong: it defines clean feature sets for the common classes, so type, cross-section, core count and rated voltage line up across manufacturers. For the core assortment, an ETIM-classified feed is close to plug-and-play. But it is honest to say where it thins out:

Data layerWhat ETIM deliversWhere it stops
Core cable classesClean feature sets: type, mm², cores, voltageSpecial & hybrid cables often lack a clean class
Accessory longtailThin coverageConnectors, glands, small parts arrive unclassified
Niche manufacturersBig brands mostly mappedSmall suppliers ship Excel / PDF without ETIM codes
Cut-to-length logicNot the job of a classificationSelling unit, price per metre, ring lengths missing
Sales contentNot the job of a classificationDescriptions, SEO text, application notes absent

So ETIM gives you a strong feature skeleton for the branded core and nothing for the selling logic, the sales content, or the accessory and niche longtail. That gap is exactly where the manual datasheet work lives.

How does Productbay make cable data complete?

The job is the same three steps every multi-supplier catalog needs — but for cables, completeness and precision are the whole point, and that is what Productbay is built for:

  • Consolidate: import every source once — supplier CSV, Excel, feed URL, FTP, API, PDF datasheet — and match by SKU or GTIN/EAN so existing products update and new ones are created, ETIM-classified core and unclassified longtail side by side.
  • Enrich: AI parses type codes, reads cross-sections and core counts out of titles and PDF datasheets, aligns them to ETIM features, writes descriptions, translates via DeepL and flags implausible values — a 400 mm² in a domestic-cable row — for review before anything goes live.
  • Publish: two-way sync to Shopify and Shopware, ERP connections (Xentral, weclapp) and feed exports for marketplaces, each with the per-channel unit and price-per-metre transformations cut-to-length goods require.

Productbay starts where the ETIM feed ends: it validates the precision-critical attributes the core relies on, and fills in the special cables, accessories and niche brands the standard never carried. For the full picture across the wholesale range, see the electrical wholesale overview. It's built for specialist retailers running multi-supplier, multi-channel catalogs — from mid-sized shops to large distributors.

Frequently Asked Questions

Let's look at your cable data

Type codes, cross-sections, core counts and cut-to-length pricing — cable data has zero tolerance for fuzzy fields. See how Productbay consolidates, normalises and enriches your cable range in a 30-minute walkthrough.

Get started