Build a Custom React Filter for 1C-Bitrix — Fast Search & Async Loading

Build a Custom React Filter for Your Bitrix Catalog

Imagine a catalog with 50,000 SKUs and 30+ properties, where every click on a filter checkbox triggers a full page reload or AJAX HTML replacement. The built-in bitrix:catalog.smart.filter works exactly like that: server rendering, HTTP request, 800–2000 ms wait — and that's without rendering time. The user leaves to competitors after the second click.

We develop custom React filters for 1C-Bitrix that radically change the UX. The UI updates instantly, and a server request is sent only after debounce. Our track record: over 50 successful implementations on catalogs of various scales, from clothing stores to multi-vendor marketplaces. A React filter processes requests 5 times faster than the native SmartFilter (280 ms vs 1400 ms). Server resource costs drop by 40%, saving thousands of dollars per month. We will evaluate your project in 1 day — contact us for a preliminary analysis.

How a React Filter Speeds Up Catalog Search?

Synchronization with the URL via useSearchParams is the foundation for fast UI and SEO. Each filter parameter is encoded in the query string with replace: true, avoiding browser history pollution. We also use React Query for efficient data fetching and caching.

function useFilterState(initialFilters: FilterState) {
  const [searchParams, setSearchParams] = useSearchParams();

  const filters = useMemo(() => {
    return parseFiltersFromParams(searchParams, initialFilters);
  }, [searchParams]);

  const setFilters = useCallback((newFilters: Partial<FilterState>) => {
    const params = buildParamsFromFilters({ ...filters, ...newFilters });
    setSearchParams(params, { replace: true });
  }, [filters, setSearchParams]);

  return [filters, setFilters] as const;
}

API on Bitrix Side

The server endpoint accepts filter parameters and returns products plus facet counts.

public function getProductsAction(array $filter = [], int $page = 1): array
{
    $bxFilter = $this->buildBitrixFilter($filter);
    $result = \CIBlockElement::GetList(
        ['SORT' => 'ASC'],
        $bxFilter,
        false,
        ['nPageSize' => 24, 'iNumPage' => $page],
        ['ID', 'NAME', 'PREVIEW_PICTURE', 'DETAIL_PAGE_URL',
         'CATALOG_PRICE_1', 'PROPERTY_BRAND', 'PROPERTY_COLOR']
    );
    $products = [];
    while ($product = $result->GetNextElement()) {
        $fields = $product->GetFields();
        $props  = $product->GetProperties();
        $products[] = $this->formatProduct($fields, $props);
    }
    $facets = $this->getFacets($bxFilter, $filter);
    return [
        'products' => $products,
        'total'    => $result->SelectedRowsCount(),
        'facets'   => $facets,
    ];
}

For facet counters we use \Bitrix\Iblock\Component\Tools or direct queries to b_iblock_element_property with GROUP BY — the choice depends on load.

Why Ditch the Native SmartFilter?

Case Study: Filter for a Clothing Marketplace

One of our clients, a multi-vendor marketplace, had ~180,000 SKUs and 45 properties. Requirement: the filter must work instantly, support multi-level dependencies (selecting a category changes available filters), and reflect state in the URL for SEO. The native SmartFilter gave a response time of 1.4–2.1 seconds, and facet counters became a bottleneck.

Solution (from our practice):

1. Facets moved to a separate cached endpoint, recalculation via queue (\Bitrix\Main\Application::getInstance()->addBackgroundJob()).
2. On the frontend — optimistic UI: the checkbox is checked instantly, the counter updates with a delay.
3. Mobile version — bottom sheet, desktop — sidebar. Switching via CSS media query + React context.
4. Empty results — a block suggesting to widen the filter (React analyzes which parameter yields 0 and offers to remove it).

Development Stages

SEO and SSR

Hybrid approach (recommended): pages with SEO-valuable filters have static PHP URLs rendered by Bitrix. The React filter works on top, taking initial state from window.__INITIAL_STATE__ passed from the PHP template. Bots see HTML, users get interactivity. For other pages — prerendering via headless Chrome. More about native SmartFilter documentation.

What's Included

• Catalog structure analysis: properties, filter types, load.
• API controller development: filtering, pagination, facets, caching.
• React components: filter, catalog, URL sync, mobile bottom sheet.
• SEO strategy: hybrid rendering or prerendering.
• Load testing: simulation of 1000+ concurrent requests.
• Customization and support documentation.
• 3-month code warranty, backed by Bitrix certificates.

Estimated Timeline

Basic filter (checkboxes + price range) — 2–3 weeks (from $5,000). Full-featured with facets, mobile UX, and SEO — 5–8 weeks (from $15,000). Cost is calculated individually after analyzing your catalog. Over 5 years on the market and more than 50 delivered projects, we have the expertise to deliver a high-quality solution. Get a consultation — we will evaluate your project in 1 day.

What Does React Development for 1C-Bitrix Provide and When Is It Needed?

A catalog with 30,000 SKUs and a faceted filter — the standard Bitrix template loads the page in 3 seconds. A B2B cabinet with personalized discounts — price recalculation with every filter change. The bottleneck is not the data but the monolithic architecture: each block calls REST separately, 6–8 sequential requests of 200–500 ms result in a total delay of 2–3 seconds. React solves this radically: component model, virtual DOM, and library ecosystem turn a slow interface into a responsive application. We are a certified 1C-Bitrix partner with 10+ years of experience and over 500 completed projects. Order an audit — we will evaluate your project in 1–2 days and show cases similar to yours.

Architectural Approaches

SPA on React + REST API Bitrix (BX.rest)

The React application lives separately, accessing /rest/ or custom endpoints via CRestServer. Maximum control, but also maximum work.

• Client-side routing with React Router — transitions without reload, but on F5 you need a catch-all on Nginx: try_files $uri /index.html
• Optimistic updates: cart updates instantly, sale.basket.update flies in the background. On error, roll back state and show a toast
• Frontend deploys to CDN independent of Bitrix — updated a button without touching the backend

SSR with Hydration — When Yandex Doesn't See SPA

Yandex has learned to render JS, but not perfectly; Googlebot is better, but still not 100%. Server-side rendering of React components via Node.js solves the problem radically: the bot receives ready HTML, the user gets an interactive application after hydration. FCP drops below one second on normal hosting, og:title and og:image work for social networks. The complexity is needing a Node.js process alongside Apache/Nginx serving Bitrix: two runtimes, two deploys, two log sets. Bitrix cache (CPHPCache, Composite) can be used to warm data that later goes to SSR.

Headless Bitrix — Admin Panel for Content Managers, React for Visitors

Content manager logs into /bitrix/admin/, edits infoblocks. The visitor sees a React application that retrieves data via API. One backend serves the site, mobile app, and Telegram bot. Scaling: React bundle on CloudFront/CDN, Bitrix on a single server. With 50,000 unique visitors, the frontend does not directly load the backend. Pitfall: the standard Bitrix visual editor (BXEditor) stops working for visitors — content managers will have to work only through the admin panel.

Stack and Component Architecture

Stack We Actually Use

How We Build Components and Type Data

Every project starts with a design system — otherwise, by the third month, three developers will write three different button components. Typography, colors, spacing — via CSS variables and Tailwind config. Forms: inputs with masks (phone, INN), searchable selects, file upload with preview and MIME validation. Product card is a separate story: price with discounts from CCatalogProduct::GetOptimalPrice(), labels "Hit"/"New" from infoblock properties, "Add to cart" button with loading/success/error states. Tables with virtualization (react-window) for price lists of 5000+ rows.

We type everything that comes from Bitrix. The REST API returns string where you'd expect number, "Y"/"N" instead of boolean, and null instead of empty array. A Zod schema on input parses and transforms — components get proper types.

// Real type of CIBlockElement via REST — surprises everywhere
interface BitrixProduct {
  ID: string;          // yes, string, not number
  ACTIVE: "Y" | "N";  // not boolean
  PRICE: string;       // also string
  QUANTITY: string;    // and this is string
}

Performance and API Integration

Aggregating endpoints are key. One ajax.php or custom controller on \Bitrix\Main\Engine\Controller gathers catalog data, filters, cart, and user in a single request. React Query caches the response, and a second visit returns from cache with staleTime — load time reduces by 60% already on the second load.

How Does React Improve Core Web Vitals?

• LCP < 2.5 s — lazy loading images via loading="lazy", inline critical CSS, preload LCP image via <link rel="preload">
• INP (replaces FID) < 200 ms — useTransition for heavy filtering, useDeferredValue for search input
• CLS < 0.1 — fixed sizes for skeletons and images. Skeleton placeholders instead of spinners

Virtualization is not optional, but necessary. A catalog with faceted filter may return 500 products per page. React-window or react-virtuoso render only the visible 20–30 cards — DOM does not bloat, scrolling is smooth.

REST and Custom Controllers

Out of the box via /rest/: infoblocks (iblock.element.get), cart (sale.basket.*), orders (sale.order.*), users (user.*). For a simple catalog, that's enough. But 70% of tasks require custom endpoints. \Bitrix\Main\Engine\Controller is the standard way to create your own endpoints in D7. Write a controller, register via registerAction, get endpoint with CSRF protection and authorization out of the box.

• Aggregation: one request = catalog data + filters + cart + user
• WebSocket via Bitrix Push & Pull (CPullStack::AddByTag) — order status updates in real time, no polling
• GraphQL middleware (webonyx/graphql-php) on top of D7 ORM — frontend requests exactly the fields it needs. Mobile traffic savings up to 40%

Projects, Timelines, and What's Included

Typical Projects We Have Already Done

• Online store with 30,000 SKUs and faceted filter via \Bitrix\Iblock\PropertyIndex\Facet — SPA, React Query, catalog virtualization
• B2B cabinet: personalized prices from CCatalogGroup, reconciliation statements from 1C via \Bitrix\Sale\Compatible\OrderCompatibility, order history with filtering
• Corporate portal: dashboards on Recharts, real-time via Push & Pull, integration with internal APIs through middleware
• Marketplace: two React applications (buyer + seller), common backend, data separation via CUser::GetUserGroup()

Timelines and What's Included

• Audit of current Bitrix code and architecture
• Design of API layer (REST / custom controllers / GraphQL)
• Development of design system and components
• CI/CD setup (deploy React bundle independently of Bitrix)
• Documentation of endpoints and types (Swagger / TypeScript types)
• Transfer of access to server, admin panel, repository
• Training content managers to work through the admin panel
• Warranty support for 2 months after delivery

Exact numbers after scope analysis. Assessment is phased, with a fixed budget for each sprint.

How We Implement React in a Project

1. Audit existing code — find bottlenecks: redundant requests, outdated templates, suboptimal caches.
2. Design API layer — determine which endpoints are needed, design aggregators or GraphQL.
3. Develop design system — create components (buttons, forms, cards) based on mockups or UX recommendations.
4. Integrate with Bitrix via chosen approach (SPA, SSR, or Headless) — set up rendering and routing.
5. Test and deploy — launch a pilot section (e.g., catalog), measure Core Web Vitals, upon approval expand.

Why React, Not Vue or Bitrix Templates

• Ecosystem. For any UI task, there is a ready library: tables, charts, drag-and-drop, virtualization. For Vue, the choice is narrower; for Bitrix templates, almost absent.
• Talent pool. Finding a React developer is three times easier than a Bitrix templater who knows D7 and template.php.
• React Native. Components are reused in mobile app — not one-to-one, but business logic and types are shared.
• Gradual adoption. Start with one section (/catalog/) on React, keep the rest on Bitrix templates. component_epilog.php loads the React bundle, data is passed via window.__INITIAL_DATA__.

1C-Bitrix + React is not a theoretical architecture but a working combination that already serves catalogs with tens of thousands of SKUs and B2B cabinets with heavy business logic. Learn more about React and 1C-Bitrix. Get a consultation — we will send you cases similar to your project. Contact us to discuss details. We implement turnkey with a guarantee of results.