<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Victor Ohanyan</title>
    <description>The latest articles on DEV Community by Victor Ohanyan (@vicohanyan).</description>
    <link>https://dev.to/vicohanyan</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4138936%2F7ff18579-8f18-43f4-bc08-d3b5d3558b01.png</url>
      <title>DEV Community: Victor Ohanyan</title>
      <link>https://dev.to/vicohanyan</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vicohanyan"/>
    <language>en</language>
    <item>
      <title>Scaling WooCommerce Product Filtering with a Dedicated Faceted Index</title>
      <dc:creator>Victor Ohanyan</dc:creator>
      <pubDate>Wed, 23 Sep 2026 07:34:54 +0000</pubDate>
      <link>https://dev.to/vicohanyan/scaling-woocommerce-product-filtering-with-a-dedicated-faceted-index-16m4</link>
      <guid>https://dev.to/vicohanyan/scaling-woocommerce-product-filtering-with-a-dedicated-faceted-index-16m4</guid>
      <description>&lt;p&gt;WooCommerce works very well for many stores, but product discovery becomes more challenging as catalogs become larger and more attribute-heavy.&lt;/p&gt;

&lt;p&gt;This is especially noticeable in technical and B2B catalogs where customers may need to filter products by brand, capacity, size, memory type, processor, form factor, speed and other specifications.&lt;/p&gt;

&lt;p&gt;Standard product queries often need to combine several attributes repeatedly as users refine their search.&lt;/p&gt;

&lt;p&gt;For FacetCore, I approached the problem differently: product discovery uses a dedicated index built from WooCommerce product data.&lt;/p&gt;

&lt;p&gt;The idea is simple:&lt;/p&gt;

&lt;p&gt;WooCommerce remains the source of truth, while FacetCore maintains a structure optimized specifically for discovery.&lt;/p&gt;

&lt;p&gt;This makes it possible to support:&lt;/p&gt;

&lt;p&gt;faceted attribute filtering&lt;br&gt;
dynamic result counts&lt;br&gt;
exclusion of impossible filter combinations&lt;br&gt;
product name and SKU search&lt;br&gt;
Table and Grid result views&lt;/p&gt;

&lt;p&gt;The same filtered result set powers both views, so switching between Table and Grid does not change the active search or filters.&lt;/p&gt;

&lt;p&gt;FacetCore is aimed primarily at medium-to-large, structured and technical WooCommerce catalogs.&lt;/p&gt;

&lt;p&gt;The current implementation has been tested with a 50,000-product WooCommerce catalog.&lt;/p&gt;

&lt;p&gt;You can see the product and live implementation here:&lt;/p&gt;

&lt;p&gt;Product: &lt;a href="https://facetcore.skyrix.app/" rel="noopener noreferrer"&gt;https://facetcore.skyrix.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Live demo: &lt;a href="https://facetcore.skyrix.app/demo/" rel="noopener noreferrer"&gt;https://facetcore.skyrix.app/demo/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;FacetCore is also available on Codester:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.codester.com/items/71123/facetcore-woocommerce-product-finder" rel="noopener noreferrer"&gt;https://www.codester.com/items/71123/facetcore-woocommerce-product-finder&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’m interested in hearing how other WooCommerce developers approach filtering and product discovery in larger catalogs.&lt;/p&gt;

</description>
      <category>woocommerce</category>
      <category>wordpress</category>
      <category>php</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
