Technical specifications
Feature under development
Technical specification detection is under development and not yet generally available. It is enabled per solution on request, and the behavior described here may change in future releases.
A technical specification is the part of a product name that states a measurement, a rating, or a standard: Ø360x76cm, 7W, IP65, 5W30, 2 pcs, 205/55R16 91V. Technical specification detection lets Ecommerce Search read that text as one unit with a meaning, instead of as ordinary words.
Why ordinary word matching is not enough
A shopper rarely writes a specification the way the product data does, and small differences in symbols and spacing then decide whether a product is found:
| Search phrase | Without detection | With detection |
|---|---|---|
pool 360 |
No match for Pool Ø360x76 cm, because the 360 sits inside a longer word |
Finds it, because the numbers inside a specification can also be matched on their own |
GU 10 |
Two unrelated words, so any product with a 10 in its name competes |
Read as the lamp socket standard GU10 |
27 W |
Matches Combi oven 27 L 900 W, which is neither 27 W nor relevant |
Read as a power rating of 27 W, so that product is not a match |
5W30 |
Split into a power rating and a number | Read as the oil viscosity grade it is |
205/55 R16 |
No match for Tyre 205/55R16, because the space splits the size differently |
Read as the same tyre size |
skrue 4x20 |
Matches a 20-pack of 4 x 30 mm screws, because both numbers are in the name |
Read as one size, so that product is not a match |
In the first five cases the shopper and the product data mean the same thing, and only the writing differs. In the last case the product name holds the same numbers, but they mean something else.
How a search phrase is handled
When a search phrase contains a specification, Ecommerce Search reads the phrase in two parts:
- The specification becomes a requirement. A product has to carry that specification to be a match.
- The remaining words are matched and scored the way they always were.
Both parts have to be satisfied, so pool Ø360x76cm returns the products that are pools and carry those measurements. A specification narrows the result set, it never widens it.
Specifications are read out of free text. Filters remain the way to search on structured product data.
Tyre sizes
A tyre size such as 205/55R16 91V holds two things: the size, 205/55R16, and the load and speed code, 91V. They are read as two specifications:
- When the shopper writes both, a tyre must carry both to be a match.
tyre 205/55 R16 91Vdoes not return a tyre marked94W. - When the shopper writes only the size, every tyre of that size is a match, whatever its load and speed code.
- The size is recognized with or without a space before the
R, and in upper or lower case. 91Von its own is still read as 91 volts. It is only read as a load and speed code when it follows a tyre size.
Dimensions
A dimension, such as 4x30 or 120x80x14,4, is read as numbers that belong together:
- The order of the numbers does not decide whether a product is found.
4x30also finds a product written30x4, but ranks it below a product written4x30. - A shorter dimension finds a longer one.
120x80finds120x80x14,4. - A diameter or a thread on its own finds the full size.
pool ø360findsPool Ø360x76cm, andbolt m8findsBolt M8x40. - The numbers must come from one size.
skrue 4x20does not find a 20-pack of4 x 30 mmscrews, even though both numbers are in its name.
When a specification is read wrongly
Reading meaning out of free text is never perfect, so the feature is built so that a wrong reading cannot lose a product. When no product carries the detected specification, its original text is matched as ordinary words instead, exactly as the shopper typed it. That gives the same result as before the feature existed.
A phrase that holds no specification at all is unaffected, and search behaves exactly as it does today.
Effect on the order of results
A product that matches a specification more completely ranks above one that matches only part of it. For pool Ø360x76cm, a pool marked Ø360x76cm can rank above one marked 360x76, which can rank above one marked 76x360. How far apart they rank depends on how relevant the product name is configured to be, as described below.
A number on its own, such as the 360 in pool 360, narrows the result, but it does not lift any product above another. Only a full or partial match of a size does that.
How much a specification can lift a product follows the relevance already configured for the product name, so a solution that treats the product name as highly relevant treats its specifications as highly relevant too. Specifications also share the same scoring budget as the words of the phrase, which stops a long phrase full of specifications from crowding out everything else.
You can see the result in two places:
- The playground shows what a specification contributed to a product's score, as a Technical Specification row in the score breakdown.
- The pipeline analysis shows the detected specification as the first step, before the text analysis steps.
What is not covered yet
The first version is deliberately narrow:
- The product name, the SKU name, the short description, and the long description are read in a new solution, as long as they are searchable. Other searchable text fields can be read as well when they are chosen for the solution, and a solution set up before this release keeps the fields it reads today.
- Tyre sizes are recognized in the common car and van formats only, such as
205/55R16and215/65R16C.ZRsizes, other tyre formats, markings such asXL, and wheel and rim sizes are not. A tyre size spread over several attributes is not combined. - The set of recognized specifications is small. It holds the most common shapes for power, voltage, volume, weight, length, diameter, threads, dimensions, ingress protection, sockets, oil grades, and counts, and it grows over time.
- A size spread over several words or attributes, such as
width 4 cm, length 30 cm, is not combined into one dimension, and neither is a size with a different unit on each value, such as6cm x 80mm. A search for4x30or6 x 80 mmdoes not find those products. - A unit spelled out in words, such as
10 meterinstead of10 m, is not recognized. - Count words, such as
pcsorstk, are recognized in Danish and English only. - Decimal and thousands separators that differ between languages are not unified, so
30.5and30,5are not yet treated as the same value. - A product gains its specifications the next time it is indexed. Products that are not updated keep being found the way they are today.