HUSKY, formerly WOOF, is built for WooCommerce stores where the standard category navigation stops being useful: fashion catalogs, spare-parts shops, electronics inventories, wholesale lists, and other projects with dense attribute sets. Its main advantage is not a prettier filter widget, but the range of query sources it can handle—from native product attributes and taxonomies to prices, SKUs, and selected custom fields.
The plugin retains the legacy woof shortcode names and internal identifiers. That naming is slightly untidy after the rebrand, although it preserves compatibility with existing WOOF configurations and code snippets.
Key capabilities
- Taxonomy and attribute filtering: categories, tags, product attributes, and custom taxonomies can use checkboxes, radio controls, dropdowns, hierarchy selectors, images, colors, or labels.
- Optional AJAX processing: refreshes product results without a full page load. Dynamic recounts show how many matching products remain before a customer applies another condition.
- Search beyond taxonomy terms: supports price ranges, SKU lookup, product text search, and numeric or textual metadata.
- ACF field support: products can be filtered through ACF
select,radio, andtrue_falsefields. - Modular extensions: optional components include Turbo Mode, Quick Search, statistics, saved searches, product alerts, infinite scrolling, and step-by-step filtering.
- Builder and multilingual integration: documented compatibility covers Elementor, Divi, WPML, shortcodes, and WordPress widgets. Custom builder grids may need a connector snippet.
- SEO-oriented filter URLs: the SEO URL Request extension can produce readable filter paths suitable for controlled inclusion in a sitemap.
Limitations: AJAX is not universally drop-in. The developer estimates compatibility with roughly 95% of themes because result replacement depends on the theme’s product-loop markup. ACF support is limited to three field types, so repeaters, relationships, and complex nested data need custom development. Large catalogs also require sensible indexing, caching, and careful filter design; enabling every dynamic recount and extension is not a substitute for database tuning.
Suitable projects and users
HUSKY fits developers and agencies assembling faceted navigation without building custom WP_Query logic from scratch. It is particularly useful when one catalog needs different filter forms on landing pages, category archives, or campaign pages. Small stores with a dozen products will rarely benefit from its configuration depth.
Setup and technical implementation
Configuration lives in the plugin options rather than the WordPress Customizer or theme options. Administrators enable the required extensions, select taxonomies, arrange filter controls, and insert the result through the [woof] shortcode or widget. The front-end builder uses [woof_front_builder], while [woof_products] renders a filterable product loop and accepts a custom template through custom_tpl.
This is a plugin, so editing header.php or archive.php is not the normal customization route. Theme-level work belongs in a child theme, usually around archive-product.php, sidebar placement, or builder-specific product-loop integration. Plugin files should not be patched directly; deeper changes are better handled through the documented API, hooks, or an extension based on examples in the ext directory.
The codebase is mature rather than minimalist. Legacy WOOF naming and jQuery-oriented front-end files remain visible, including a compressed front script. CSS and JavaScript weight depends on enabled filter types and extensions, so unused modules should stay disabled. Exact asset weight varies by configuration and should be checked on the target theme before deployment.
FAQ
Does filtering work without page reloads?
Yes. AJAX mode is optional, but theme compatibility must be tested before production use.
Can it filter custom ACF fields?
Yes, for ACF select, radio, and true/false fields.
Does it support custom product templates?
Yes. The [woof_products] shortcode supports custom_tpl in AJAX and redirect modes.
Is WPML supported?
Yes. WPML compatibility is documented by the plugin developer.
