Catalogs, fields and ranking
Catalogs
The Каталоги (Catalogs) tab selects index sources and storefront/CRM connections. Infoblocks with native element or section indexing enabled are listed. Each entry shows both flag states and a link to its Bitrix settings.
Save changes and rebuild the affected data. Related offers are added automatically, subject to their native search settings.
Participating fields
Сортировка поиска (Search sorting) lists available basic product and section fields, active searchable product properties, and searchable section user fields.
| Source | Enable or disable it in |
|---|---|
| Basic fields: name, codes, descriptions, tags, barcodes | The module table's Поиск (Search) checkbox |
| Product properties | The native property setting for participation in search |
| Section user fields | The user field's native searchable setting |
Disabled basic fields remain in the table so they can be enabled again. Product and section IDs do not participate. Product symbolic code, external code, short description and full description are disabled by default and can be enabled manually.
Supported product properties include S/N/L, ordinary strings, HTML, Date/DateTime and multiple values; list properties use their display values. Supported section user fields are string, integer, double, boolean, date, datetime and enumeration. Files, element/section links, highload directories and other special types need separate handlers and are not listed as available search fields.
Matching modes
| Mode | Behavior | Example |
|---|---|---|
| Точное значение (Exact value) | Matches the entire field value | 000123 matches 000123, not 123 |
| По словам (Words) | All query words must occur in allowed text fields of the document, possibly across fields | тепловая пушка requires both words |
| Частичное совпадение (Substring) | Product name: all query parts in any order; other fields: the entire query consecutively | 001 matches AB-001-CD; пушки matches Тепловые пушки |
Matching ignores case and normalizes outer/repeated spaces. Zeros and punctuation are preserved. In substring mode, % and _ are literal characters, not SQL wildcards. Separate values of a multiple property are not concatenated.
Since 0.1.30, product Name substring matching treats a space and the ordinary hyphen - as interchangeable: passat 150 finds PASSAT-150, and passat-150 finds PASSAT 150. No separate switch is needed: select Частичное совпадение (Substring) for the field. A literal full-value match retains its relevance advantage.
This does not join words: passat150 does not become equivalent to PASSAT-150. The rule does not apply to section names, identifiers or other fields, does not replace other punctuation, and does not change Exact value or Words modes. Updating to 0.1.30 and switching an already indexed product name to Substring mode require no rebuild.
Since 0.1.31, product-name substring search requires all space-separated query parts in one name, in any order and with other words allowed between them. сварочный инвертор 200 finds Сварочный инвертор AuroraPRO Inter TIG 200 AC/DC Pulse. The wrong-layout query cdfhjxysq bydthnjh 200 uses the same rule after layout correction. Every part is required; 200 can also match within 2000 because this is substring mode. Explicit punctuation is preserved, but separate fragments may occur on either side of punctuation: AB 001 finds AB/001. Other fields still require the entire consecutive query. No rebuild is needed.
Substring matching is not morphology: пушки does not match пушка. Use synonyms when appropriate.
Result order
A full match against a participating field ranks above word or substring matches, in all three modes. Within each group, a lower Sorting number ranks higher. The range is 0–10000. Enter a number, drag a row using ↕, or use ↑ / ↓. Equal scores are ordered by ID.
Autocomplete has an additional rule: selected catalog sections appear before products, even before an exact product match. This does not change the normal results page or CRM order. See autocomplete rules.
Rebuild requirements
- Mode and sorting changes apply on save without rebuilding.
- Disabling a field excludes it immediately.
- Enabling a new field or changing sources requires a rebuild.
- If settings change during an unfinished pass, restart it.
Read the message after saving. An error can cancel the save and cause the previous checkbox state to reappear.