The existing store
Plastic System sells packaging products through a 1C-Bitrix catalog. Its product pages, categories, regional prices and stock already have owners in that store. Search needed to find those same products and categories without moving checkout or rebuilding the storefront. WGP Site Search is deployed as a separate search service; the Bitrix module connects the existing storefront to it.
This is a Russian-language deployment. A separate Frontbox store may use another search implementation; the live example here is the standalone Site Search product on Plastic System.
How search connects
- The Bitrix module exports active catalog products and categories to a structured feed. The feed includes product identifiers, names, URLs and regional price and availability data. Product dimensions and article-number variants are included as search terms where the source catalog supplies them.
- A scheduled import reads the feed, validates it and builds a new Elasticsearch index generation. The read alias switches only after the new index is ready, so a failed import does not replace the previous searchable generation.
- The storefront module requests suggestions and full results through the search service. The search field shows category suggestions and product cards. The results page uses the store's product cards, category selection, sorting and catalog filters.
The export and import schedules are separate. For another catalog, confirm the complete delay from a source price or stock change to the visible search result. A configured schedule alone is not proof of freshness.
Inspect the live result
Open Plastic System's live search for “мясной ящик” ↗. The phrase means “meat crate.” On 9 November 2026, the public results page showed 19 products across two categories, with sorting and catalog filters. The exact counts can change as the catalog is updated. On the store homepage, typing the phrase into the header search showed category and product suggestions.
You can also inspect an exact article search for “PS 4269m” ↗. On 9 November 2026, its product appeared first, followed by the similar article “PS 4269ml.” This is one observable ranking check, not a guarantee for every catalog or SKU format.
Region matters too. On 9 November 2026, “DFLC 1000” had no result on the main storefront, where that item was not sold. The same article appeared first in Plastic System's Vladivostok search ↗, with an in-stock price. This checks one regional availability case; it does not measure how quickly stock changes reach the index.
This is a practical inspection, not a controlled relevance benchmark. Try the product links, a category, an article number and a query that should have no result. Check the store's mobile search as well as desktop if your team is evaluating an integration.
What this example proves
English product names, abbreviations and typos need a separate pilot using an English catalog. Integrations outside 1C-Bitrix also need their own field mapping and interface checks. We do not extrapolate performance or commercial outcomes from one visible query.
Test your own catalog
Start with a representative catalog export and 20–30 real buyer queries. Include exact SKUs, name variants, categories, likely typos, and known empty results. Record expected products before tuning, then inspect the returned order and links. Change a test product's price or availability and measure when the update reaches search.
Use our free relevance scorecard to keep the query results, and follow the site search pilot guide for filters, freshness and launch checks. See Site Search integration options or share your catalog to scope a pilot.