Skip to content
Product data is not a form – it is the supply chain’s operating instructions

The electrical number identifies the product. Product data makes the chain work.

This page explains to manufacturers and importers what they need to understand about electrical numbers and product data: why detailed data is needed, how the data moves, and why individual details have a direct impact on sales, design, logistics, site work and the building’s life cycle.

Why is so much product data needed?

A single field may look small, but in the supply chain it becomes a search result, an order line, a pallet location, design data, a basis for invoicing or an input for environmental calculations.

🔍

The product is found using the right words

The product group, generic name, technical name, long name and product description help customers find the product when there are many alternatives.

Purchasing and goods receipt work correctly

The usage unit, sales unit and conversion factor define what the customer actually buys and what is delivered to the site.

🚚

Logistics can be automated

Package dimensions, weights, volumes and GTIN codes support warehousing, transport, pallet locations and automated warehouses.

🧾

Pricing and invoicing remain aligned

The pricing unit, minimum sales quantity and conversion factor prevent incorrect deliveries and errors in project pricing.

📐

Design receives technical properties

The ETIM class and technical properties move into design software, comparison tools, product selection and documentation.

🌱

Environmental and responsibility data becomes usable

GWP values, EPD/PEP data, documents and compliance data support low-carbon construction and transparency.

How does product data move?

The manufacturer or importer is the source of the data. Once the data has been entered in a shared format, it can be distributed to wholesalers, contractors, designers and software without separate manually maintained versions.

1. Manufacturer or importerApplies for the electrical number and completes the product data as early as possible.
2. Sähkönumerot.fiThe product card brings together identifiers, basic data, logistics, images, documents and technical data.
3. Wholesalers and retailersUse the data on product pages, in orders, warehouses, EDI messages and pricing.
4. DesignersSearch for dimensions, technical properties, documents and environmental data.
5. ContractorsOrder, receive and compare products using the electrical number and product data.
6. Property and maintenanceFind spare parts, replacement products, user instructions and installation instructions throughout the life cycle.
7. Reporting and recyclingResponsibility, environmental and material data support decisions after the use phase as well.

Two languages, one product card

Product data is best understood as two complementary areas: the product’s commercial and logistical basic data, and its technical, comparable property data.

Product Data Standard

Basic data, names, codes, dimensions, logistics, packaging data, images, links, documents, markings, pricing bases and environmental fields. Fields are identified using TT codes.

TT010 electrical numberTT052 GTINTT300–304 dimensionsTT400–451 logisticsTT701–769 materials

ETIM

A technical classification model in which products have classes, properties and predefined values. When technical properties are in a standardised format, the product can be searched, compared and transferred between systems accurately.

product groupsclassespropertiesvaluesmultilingual codes

Product Data Standard fields in practice

In the Product Data Standard, the basic data on the product card is divided into fields identified by TT codes. The idea is simple: the same data is always stored in the same field, so it can be read correctly by wholesalers, online shops, design software, contractors and other systems.

Why is the TT code important?

The TT code acts as a permanent field identifier. When, for example, the GTIN is always in field TT052 and the product’s technical name is in field TT201, the data does not need to be interpreted manually in every system. This reduces errors and speeds up product opening, maintenance and distribution.

1. IdentifyWhich product is it and which product group does it belong to?
2. DescribeHow is the product found and how does the customer understand it?
3. DeliverHow is the product sold, packaged, transported and received?

1. Product-related codes

Product identification and classification.

TT010–TT081
TT010Electrical number: a seven-digit national identifier whose beginning indicates the product group.
TT011–012Swedish and Norwegian electrical numbers, if the product has corresponding identifiers.
TT020–032Identifiers related to HVAC and building product numbers.
TT050–052Supplier’s product codes and the GTIN code of the individual product.
TT060–081ETIM class, S2010, RYTJ, hEN, DoP, UNSPSC and SCIP.

2. Supplier, brand and series

Who is responsible for the product and under which brand is it known?

TT100–TT120
TT100Supplier name. Changes to the company name are corrected separately in the service data.
TT101Field reserved for the VAT identifier; not used in the product data of electrical products.
TT110Brand name. If there is no brand, the supplier’s name is used without the Ltd/Oy suffix.
TT120Product series or product family, if it is an actively used series by the manufacturer.

3. Names and product description

Findability, search terms and the customer’s first understanding of the product.

TT200–TT208
TT200The generic name is selected from the harmonised generic names of the product group.
TT201Technical name: the most important technical details in a compact form, up to 30 characters.
TT202Long product name: a broader explanation or short technical description, up to 255 characters.
TT203/208Product description in HTML format and a plain version exported without formatting.
TT204–207English and Swedish generic names and technical names.

4. Product dimensions

Physical data for design, warehousing and site work.

TT300–TT304
TT300Product length or depth in millimetres.
TT301Product width in millimetres.
TT302Product height in millimetres.
TT303Product weight in kilograms.
TT304Product volume in litres.

5. Logistics data

Sales units, conversion factors, packages and transport.

TT400–TT451
TT400–402Usage unit, conversion factor and sales unit. These must be logically consistent.
TT408–409Minimum sales quantity and nominal batch quantity for products delivered on a reel.
TT407/438–444Package size 0: unit package and its dimension, weight, volume and GTIN data.
TT403/410–416Package size 1: smallest transport package and the number of products in the package.
TT404–406Package types for package sizes 2–4.
TT417–437Package sizes 2–4: larger transport packages and pallet package.
TT450–451Dangerous goods marking and standard delivery reel type.

6. Other data and life cycle data

Warranties, origin, customs code, replacement products and spare parts.

TT500–TT591
TT500/504Warranty period in months and information on any additional conditions.
TT501–502Country of origin and customs code.
TT510–513Archiving, publication, modification and creation dates.
TT520–521Electrical numbers of the replacement product and the replaced product.
TT530–533Required products, spare parts, parallel products and accessories.
TT590–591Automatic name + product series field and information on whether professional installation is required.

7. Price data

Commercial information between the supplier and the wholesaler.

TT600–TT609
TT600Supplier’s discount group.
TT601–603Currency, price and price code.
TT604Pricing unit.
TT605Procurement time in working days.
TT606–609Purchase discounts and price effective date.

Note: these details are not stored in the Sähkönumerot.fi service; they are between the supplier and the wholesaler.

8. Images, links and documents

Materials in the right places, so they also transfer correctly through integrations.

TT701–TT769
TT701–711Image locations: main image, line drawing, dimension drawing, wiring diagram, technical image, light distribution curve, advertising image, application image and energy label.
TT731–741Links: supplier’s product page, user instructions, 3D model, DoP, light distribution curve, videos, SDS, environmental declaration, RoHS and REACH.
TT751–769Documents: brochures, 3D model, installation instructions, user instructions, dimension drawing, technical data, DoP, CE, warranty terms, environmental declaration, SDS, M1, RoHS and REACH.

9. Marking data

Compliance and approvals in a clear, machine-readable format.

TT780–TT784
TT780CE marking.
TT781M1 classification.
TT782FI-certified product.
TT783RoHS compliance yes/no.
TT784REACH compliance yes/no.

10. Environmental data

Carbon footprint, environmental declarations and comparability.

TT790–TT802
TT790Manufacturer-declared product stage A1–A3 GWP value.
TT791–792GWP calculation standard and third-party verification.
TT795–798Type, identifier, validity and declared unit of the environmental declaration.
TT799Mass unit conversion factor in kg/unit.
TT800–802GWP values for the use stage, end-of-life stage and carbon handprint.
TT793–794Building emissions database ID and the conservative GWP value retrieved from it.

Minimum data first

Product group, brand, generic name, technical name, usage unit, sales unit, conversion factor, GTIN if the product has one, and package size 0 or, during the transition period, package size 1 are critical basic data.

Mandatory does not mean sufficient

Minimum data opens the product, but a good product card also needs dimensions, images, documents, ETIM properties, logistics data and environmental data.

Fill each field according to its purpose

A dimension drawing belongs in the dimension drawing field, user instructions in the user instructions field and a package GTIN in logistics data. The right location determines whether the data moves forward correctly.

The product card should be structured like this

When the whole is divided according to purpose, completing the data becomes clearer. Each section answers one supply chain question.

1. What is the product?Electrical number, product group, GTIN, supplier’s product code and ETIM class.
2. Whose product is it?Supplier, manufacturer, brand, product series and the party responsible for maintaining the data.
3. Under which name is it found?Generic name, technical name, long name, product description and search-supporting data.
4. What size is it?Product length, width, height, weight and volume in the correct units.
5. How is it sold?Usage unit, sales unit, conversion factor, minimum sales quantity and pricing unit.
6. How is it delivered?Package sizes 0–4, package types, dimensions, weights, volumes and package GTIN codes.
7. What material is needed?Product images, dimension drawings, installation instructions, user instructions, links, videos and 3D models in the right places.
8. Which requirements apply?CE, RoHS, REACH, FI, M1, declarations of performance, safety data sheets and environmental declarations.

Packaging and logistics data: the 2026 way of thinking

The most important change: package size fields state the number of products, not the number of packages. This harmonises the data and reduces the risk of incorrect delivery quantities.

Select a package size

Example hierarchy: one lamp → transport package of 10 lamps → larger transport packages → pallet.

Package size 0

1 product

Unit package

The package closest to the product, also known as the primary or consumer package. Package size 0 is mandatory and is almost always 1.

1If the product is unpackaged, also enter the dimensions of the unpackaged product in the product dimension fields.
2The GTIN is entered both in the product GTIN field and in the package size 0 data when it refers to the same unit.

Do not enter the number of boxes

If package size 2 contains 4 boxes and each box contains 10 products, package size 2 is 40 products.

Size 1 is not the same as the minimum sales quantity

The minimum sales quantity is entered in its own field. Package size 1 describes the smallest transport package.

An empty field is better than incorrect data

If a certain transport package size is not used, leave its fields empty.

Measuring: four practical principles

Dimensions are extremely important to users. They affect design, warehousing, transport, shelving, automation and correct product selection.

Unit package

Choose the front face. Width is measured from left to right, depth from front to back, and height from the base to the top.

Transport package

Define the base. Height is from the base to the top, width is the shorter side of the base and depth is the longer side.

Pallet load

Measure including the pallet. Height is from the base upwards, width from the shorter side and depth from the longer side.

Reels and cables

For cables, package size 0 describes one metre: length is 1000 mm, while width and height are the cable diameter.

Environmental data is not a separate add-on

When climate and environmental data is machine-readable, it can be used in design, comparison, procurement, cost calculation, reporting and property life cycle management.

CO₂

GWP values

Global warming potential is reported by stage, such as A1–A3 and the use, demolition and recycling stages, when the data is available.

📄

EPD and PEP

Environmental declarations increase transparency and help compare products using shared calculation principles.

🔗

Documents in the right fields

When the environmental declaration, DoP, safety data sheet and other documents are in the correct place, the data also transfers correctly to other systems.

The most common errors quickly show up in the chain

In the supply chain, an error does not remain only on the product card. It becomes an incorrect order, an unclear product, a missing document or unnecessary customer service work.

Incorrect sales unit or conversion factorThe customer orders one quantity, but the system interprets another. This may result in an incorrect delivery quantity and invoicing problems.
The number of packages is entered in package size fieldsThe warehouse and site receive an incorrect view of the actual product quantity. Under the 2026 guidance, the number of products is entered.
The generic name or technical name is weakThe product is not found in search or ends up in the wrong comparison set. A good name helps both people and systems.
Images, links or documents are in the wrong placeA system integration may fail to transfer the material even if it is present on the product card.
ETIM properties are not completedThe product cannot be compared technically as well in design and procurement systems.

Checklist for manufacturers and importers

Review the product in this order. The idea is to first identify the product, then make it findable, deliverable, comparable and useful throughout its life cycle.

Select the correct product group before applying

The product group defines the first part of the electrical number and also affects product findability.

Complete the minimum data properly from the start

Brand, generic name, technical name, usage unit, sales unit, conversion factor and GTIN, if the product has one.

Check names from the customer’s point of view

Ask: would a contractor, designer or wholesaler find this product using these words?

Complete dimensions and package sizes using the same logic

Enter millimetres, kilograms and litres according to the guidance. The package size value is the number of products, not the number of boxes.

Add GTINs at the correct levels

The individual product and different package sizes may each have their own GTIN codes.

Complete ETIM and technical properties

Technical data makes the product comparable and usable in software.

Place images, links and documents in the correct fields

Product image, dimension drawing, installation instructions, user instructions, 3D model, environmental declaration and other documents each serve different purposes.

Update the data before deliveries begin

Once the product is already in the wholesale chain, incorrect data is quickly copied into many systems.

Good product data reduces friction at every stage.

It improves findability, reduces incorrect purchases, speeds up deliveries, supports design, makes documentation easier and turns environmental data into something genuinely usable. This is why detailed data is needed – not for bureaucracy, but because the supply chain depends on it.

Draft source material: the Sähkönumerot.fi Information and instructions section, Sähkönumerot.fi Product data, the product data, ETIM, environmental data and interface content on tuotetieto.stkliitto.fi, and the Package size guidance 2026.

Electrical number and product data – the shared language of the supply chain. A page draft for the onboarding of manufacturers and importers.