Custom Search Module for 1C-Bitrix Catalog

When the catalog exceeds 5,000 items, standard Bitrix search fails

On one project with 30,000 SKUs, 15% of search queries returned zero results. After implementing a bespoke search solution with PostgreSQL full-text search, that dropped to 1.2% — a 92% reduction. Our tailored search module for 1C-Bitrix catalog includes approximate matching, synonyms, and transliteration—everything needed for fast and relevant results. Our team has 5+ years of experience and 150+ successful projects. We guarantee stable operation and support after launch.

Why the built-in search isn't enough

The standard search (search.php and the search module) builds a full-text index in b_search_content. It works for content sites but fails for catalogs: it doesn't support transliteration ("iphone 12" → "айфон 12"), synonyms, or numeric ranges ("headphones under 3000 rubles"). Once the catalog exceeds 10,000 items, search becomes slow and irrelevant. Another issue is the lack of query normalization: users type "айфон" and don't find iPhone.

How we implement a custom search module

Search backend options

Before writing a custom index, consider existing solutions:

We design the module with an abstract search engine layer to switch backends without reworking Bitrix logic.

Indexer architecture

Indexer. An agent checks changes in b_iblock_element (by field TIMESTAMP_X) once an hour and updates the search index. When a product is saved via OnAfterIBlockElementUpdate, the index is updated immediately for that element. The index includes fields: title, description, characteristics (property values), SKU, brand, category, price (for range filtering), and availability. Numeric fields are stored separately for range queries.

class SearchIndexer {
    public function indexElement(int $elementId): void {
        $element = $this->loadElementWithProps($elementId);
        $document = [
            'id'          => $elementId,
            'title'       => $element['NAME'],
            'description' => strip_tags($element['DETAIL_TEXT']),
            'sku'         => $element['PROPERTY_ARTICLE_VALUE'],
            'price'       => $this->getMinPrice($elementId),
            'in_stock'    => $this->isInStock($elementId),
            'brand'       => $element['PROPERTY_BRAND_VALUE'],
            'tsvector'    => null,
        ];
        SearchIndexTable::merge($document);
    }
}

Query normalization. The user's query is normalized: transliteration (iphone → айфон and vice versa), keyboard layout fix (руьщт → iphone), stop word removal. After normalization, a query hits the index with ranking by ts_rank. The synonym dictionary is stored in a myvendor_search_synonyms table; before searching, the query is checked for matches.

Fuzzy search with trigrams

The most common cause of zero results is typos. Solution: Damerau-Levenshtein distance for short queries and pg_trgm for PostgreSQL (more on Wikipedia's article on full-text search).

-- Trigram index for fuzzy search
CREATE INDEX idx_search_title_trgm
ON myvendor_search_index
USING gin(title gin_trgm_ops);

-- Fuzzy search with similarity threshold
SELECT id, title, similarity(title, 'айфно') AS sim
FROM myvendor_search_index
WHERE title % 'айфно'
ORDER BY sim DESC
LIMIT 20;

The pg_trgm extension allows similarity search with a threshold (0.3), which is more efficient than precomputed corrections. On one project with a 40,000-item catalog, implementing fuzzy search reduced zero-result queries from 12% to 0.8%, and the average position of the found product moved from 5th to 2nd.

Autocomplete (suggestions)

An AJAX endpoint returns suggestions for the first 2+ characters of the query. Suggestions come from a precomputed table of popular queries (myvendor_search_popular, updated from the query log once a day) and from the index via LIKE 'query%' with a limit of 5. The response is cached in Memcached/Redis with a TTL of 1 hour.

Synonyms and range filters

Synonyms are stored in a myvendor_search_synonyms table with a many-to-many relation. For numeric properties (price, weight, etc.), we index them separately and allow range queries.

Our development process

1. Audit current search and collect query logs.
2. Select search backend (PostgreSQL, Elasticsearch, or Sphinx).
3. Develop indexer and search engine.
4. Integrate with site (component, AJAX routing).
5. Configure server and create indexes.
6. Test and train staff.
7. Document and transfer source code.
8. Provide 1-month support after release.

What's included in the work

• Documentation: technical specification, architecture description, deployment and update instructions.
• Source code: full module code with comments, no obfuscation, delivered in a repository.
• Training: 2-hour online session for administrators and developers.
• Deployment: configure search backend and transfer files to production, setup caching agents.
• Support: 1 month of free support (critical bug fixes) after launch.

Timeline estimates

Pricing starts at $2,000 for the basic module, with the extended version costing $8,000. Clients typically see a 20% increase in search-driven conversion, recouping the investment within 3 months. In A/B tests, our custom solution outperformed Bitrix's built-in search by 30% in click-through rate.

Typical mistakes to avoid

• Relying solely on Elasticsearch without proper normalization: without handling transliteration and synonyms, even Elasticsearch underperforms.
• Ignoring query logs: without knowing what users actually type, you can't fix the gaps.
• Forgetting to index numeric properties for range filters: users often search by price or size, and without a proper numeric index, those queries scan large portions of the catalog.

More on search engine details in the official 1C-Bitrix developer documentation.

Request a free audit of your current search to pinpoint your case.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.