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.
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.
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 group, generic name, technical name, long name and product description help customers find the product when there are many alternatives.
The usage unit, sales unit and conversion factor define what the customer actually buys and what is delivered to the site.
Package dimensions, weights, volumes and GTIN codes support warehousing, transport, pallet locations and automated warehouses.
The pricing unit, minimum sales quantity and conversion factor prevent incorrect deliveries and errors in project pricing.
The ETIM class and technical properties move into design software, comparison tools, product selection and documentation.
GWP values, EPD/PEP data, documents and compliance data support low-carbon construction and transparency.
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.
Product data is best understood as two complementary areas: the product’s commercial and logistical basic data, and its technical, comparable property data.
Basic data, names, codes, dimensions, logistics, packaging data, images, links, documents, markings, pricing bases and environmental fields. Fields are identified using TT codes.
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.
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.
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.
Product identification and classification.
Who is responsible for the product and under which brand is it known?
Findability, search terms and the customer’s first understanding of the product.
Physical data for design, warehousing and site work.
Sales units, conversion factors, packages and transport.
Warranties, origin, customs code, replacement products and spare parts.
Commercial information between the supplier and the wholesaler.
Note: these details are not stored in the Sähkönumerot.fi service; they are between the supplier and the wholesaler.
Materials in the right places, so they also transfer correctly through integrations.
Compliance and approvals in a clear, machine-readable format.
Carbon footprint, environmental declarations and comparability.
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.
Minimum data opens the product, but a good product card also needs dimensions, images, documents, ETIM properties, logistics data and environmental data.
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.
When the whole is divided according to purpose, completing the data becomes clearer. Each section answers one supply chain question.
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.
Example hierarchy: one lamp → transport package of 10 lamps → larger transport packages → pallet.
Package size 0
The package closest to the product, also known as the primary or consumer package. Package size 0 is mandatory and is almost always 1.
If package size 2 contains 4 boxes and each box contains 10 products, package size 2 is 40 products.
The minimum sales quantity is entered in its own field. Package size 1 describes the smallest transport package.
If a certain transport package size is not used, leave its fields empty.
Dimensions are extremely important to users. They affect design, warehousing, transport, shelving, automation and correct product selection.
Choose the front face. Width is measured from left to right, depth from front to back, and height from the base to the top.
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.
Measure including the pallet. Height is from the base upwards, width from the shorter side and depth from the longer side.
For cables, package size 0 describes one metre: length is 1000 mm, while width and height are the cable diameter.
When climate and environmental data is machine-readable, it can be used in design, comparison, procurement, cost calculation, reporting and property life cycle management.
Global warming potential is reported by stage, such as A1–A3 and the use, demolition and recycling stages, when the data is available.
Environmental declarations increase transparency and help compare products using shared calculation principles.
When the environmental declaration, DoP, safety data sheet and other documents are in the correct place, the data also transfers correctly to other systems.
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.
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.
The product group defines the first part of the electrical number and also affects product findability.
Brand, generic name, technical name, usage unit, sales unit, conversion factor and GTIN, if the product has one.
Ask: would a contractor, designer or wholesaler find this product using these words?
Enter millimetres, kilograms and litres according to the guidance. The package size value is the number of products, not the number of boxes.
The individual product and different package sizes may each have their own GTIN codes.
Technical data makes the product comparable and usable in software.
Product image, dimension drawing, installation instructions, user instructions, 3D model, environmental declaration and other documents each serve different purposes.
Once the product is already in the wholesale chain, incorrect data is quickly copied into many systems.
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.