Skip to main content

Storefront search, autocomplete and CRM

Standard results page​

After building the index, enable Поиск магазина (Storefront search) on the Catalogs tab. Standard CSearch and bitrix:search.page are supported. Selected catalogs use matches from the module's index; mixed searches retain results from other modules.

Field sorting affects relevance order. Separate date ordering remains in effect. Normal catalog product order is not changed.

The module also adds zorka.search to the native Search module's full-text engine selector in its Morphology settings. Selecting this engine does not enable morphology for the module's own index.

Header autocomplete​

Standard bitrix:search.title is supported, including calls using the corp template. You do not need to replace the component call manually. The engine and a service AJAX template connect the module while the site's original template continues rendering results.

Selected catalogs use the module's index and respect disabled fields. Other catalogs and modules retain their previous search.

The standard component has additional rules:

  1. Matching sections appear before products, even before exact product matches.
  2. If only sections match, remaining slots are filled with products from those sections and their descendants. Product names do not have to contain the query.
  3. A direct product match or a result from another module prevents this expansion.

TOP_COUNT, permissions, activity, dates, native indexing flags and presence in the module index apply. Added products are ordered by native SORT, then ID, without duplicates. Sections take the first slots; a full limit may leave no room for products.

All results opens the ordinary search page with its own rules. Direct CSearchTitle use outside the component keeps native reordering. A third-party template may further modify result order or membership.

Since 0.1.28, when arturgolubev:search.title calls the Bitrix search engine, the module uses the component's original query for selected catalogs. This fixes cases where the component removed the hyphen from passat-150 before passing it to the engine, leaving full-page search working while autocomplete missed the product. No Bitrix core or third-party module edits, or reindexing, are required.

This compatibility covers query handling. The standard bitrix:search.title rules for section ordering and product expansion are not guaranteed for a third-party component: verify its template and server filters separately.

Autocomplete performance​

Since 0.1.29, when component filters unambiguously restrict the search to specific catalogs, the module searches only those catalogs from the start. This reduces work on sites with several selected infoblocks. Permissions and remaining filters still apply. If the filter cannot safely be narrowed, the original lookup is retained.

This optimization applies automatically without rebuilding the index. Response time also depends on the database, template and product-card loading. Compare AJAX response times using the same queries and permissions; this change does not promise equivalent speed on the full results page.

Bitrix24 CRM product selection​

Enable Товары и категории в CRM Б24, save and reload CRM. The module supports the modern native UI Entity Selector entities product, product_variation, variation and section.

Native catalog restrictions, prices, loading and card presentation remain in effect. For selected catalogs, the client extension preserves server order and disables local prefix-match additions. Recent products remain available.

Offers are searched by their own fields; a parent product match is handled by the native variation-selection mechanism.

Separate verification required​

Legacy CRM dialogs, mobile forms and third-party search forms are not automatically connected unless they use supported mechanisms. Original-query handling for arturgolubev:search.title is supported as described above; other behavior in third-party implementations requires examination of their server code. A similar-looking input does not prove a query passes through zorka.search.

The module does not edit Bitrix core files, but its adapters depend on search engine classes and CRM providers. After Bitrix updates, check Совместимость (Compatibility), test queries, and actually add a product in CRM. Tested versions are listed under installation.