At a glance

Faceted search and filtering is one of the parts of a Visualsoft store merchants worry about losing during a Shopify migration. It is also one of the parts where Shopify has invested heavily in the last few years, and where the experience on the new platform is usually as good or better than what came before, with the right setup.

This post walks through how filtering tends to work on Visualsoft today, what Shopify offers natively, where apps fill the gaps, and how the SEO side of filtered URLs gets handled in the migration.

What faceted search needs to do

Before talking about either platform, worth being clear on what good filtering actually does for a store. The shopper experience boils down to a few things:

  • Multi-select filters. A shopper picks "blue" and "size 10" and "under £50" and sees only products matching all three.
  • Live result counts. Each filter option shows how many products it will return before you click it, so shoppers do not run into empty results.
  • Price ranges. Either preset bands or a slider.
  • Sensible defaults. The right filters for the right categories. Size and colour matter on a dress page, dimensions and material matter on a furniture page.
  • Fast response. Filter changes update results in well under a second, ideally without a full page reload.
  • Mobile-friendly layout. Filters work well on a small screen, where most shopping now happens.
  • Search relevance. Free-text search returns the right products, handles typos, and respects synonyms.

Most Visualsoft stores have these working to some degree, often tuned over years to suit a specific catalogue. The migration job is to land in Shopify with the same shopper experience or better, without losing any of that tuning.

What Shopify offers natively

Shopify's filtering story has changed significantly. A few years ago it was a real weak point, today it is genuinely capable for most stores.

Storefront filters

Shopify's native filtering, built into modern themes, supports multi-select filters, price ranges, and live result counts out of the box. Filters can be driven by product options (size, colour), tags, vendors, and metafields. For most stores with a reasonably clean catalogue, native filtering covers the bulk of what is needed.

The setup work sits in two places: making sure your product data is clean and structured (consistent option names, sensible tags, metafields where appropriate), and configuring which filters appear on which collections through the theme editor. Both are migration tasks, both are worth doing properly.

Native search

Shopify's built-in search has come a long way. It handles typos, partial matches, and synonyms, and supports custom synonym rules for store-specific language. For many catalogues it is good enough without anything extra.

Metafields for richer filtering

Where a store needs to filter on something beyond the standard product attributes, metafields are the answer. A furniture store might filter by material, room, and style. A skincare store might filter by skin type, concern, and ingredient. Metafields let you define those attributes once, attach them to products, and then expose them as filters in the theme.

This is the part of Shopify that quietly does a lot of heavy lifting. It is more flexible than fixed-attribute systems because you define the attributes your store actually needs, rather than picking from a predefined list.

Where apps fill the gaps

For stores with more complex needs, the native tooling sometimes hits its limits. The honest list of when an app makes sense:

  • Very large catalogues. Once you are into the tens of thousands of SKUs, dedicated search and filter apps tend to outperform native on speed and relevance.
  • Advanced merchandising rules. Boosting certain products in search results, hiding out-of-stock items intelligently, pinning bestsellers to the top of filtered views. These are app territory.
  • Heavy synonym management. If your store relies on a long-tuned synonym dictionary built up over years, a dedicated app gives you more control over how it migrates and evolves.
  • Personalised search. Showing different results to different shoppers based on browsing history or segment. Native search does not do this.
  • Custom filter UI. Colour swatches in filters, size grids, or other visual filter types beyond what the theme supports natively.

The choice between native and app territory is one of the most important calls in the migration. Going native when it is enough saves cost and complexity. Going app when it is needed prevents disappointment on launch day. Picking the right side of that line is one of the things a specialist migration partner does in discovery.

The SEO side: filtered URLs

This bit is worth flagging because it surprises some merchants. On Visualsoft, filter selections often appear as their own URLs, which means filtered category pages can pick up SEO traction over time. On Shopify, filters apply via query strings on the underlying collection URL, which works differently from a search engine perspective.

The practical implications:

  • Most filtered URLs on Visualsoft will not have direct equivalents on Shopify, because the structure is different by design
  • The small subset of filtered URLs that have genuine SEO value (organic traffic or backlinks) need careful handling, usually by redirecting to the parent collection
  • For ongoing SEO, dedicated landing pages for high-value filter combinations are often a better long-term strategy than relying on auto-generated filtered URLs

This is covered in more depth in our piece on Visualsoft to Shopify URL redirects, which is worth reading alongside this one if you are planning a migration.

What changes for shoppers

The thing worth flagging to merchants who worry about losing filter functionality is that the shopper-facing result is usually a step forward, not back. A well-configured Shopify store with modern filters tends to load faster, look more polished on mobile, and respond more quickly to filter changes than a comparable Visualsoft setup. That is a function of Shopify's infrastructure, modern theme architecture, and the maturity of the filter ecosystem.

The merchant-facing result is that filters become something you can configure through the theme editor rather than briefing in. Adding a new filter to a collection, hiding one for a specific category, or changing the filter order on mobile becomes a job your team can do in minutes.

What gets done in a properly handled migration

Pulling all of this together, the filtering and search side of a Visualsoft to Shopify migration involves:

  1. Auditing how filtering is currently working, including which filters exist on which categories and how shoppers actually use them
  2. Cleaning product data so options, tags, and metafields land in Shopify in a structured, filterable form
  3. Deciding native vs app territory based on catalogue size, complexity, and tuning history
  4. Configuring filters per collection in the theme editor
  5. Migrating any synonym dictionary, merchandising rules, or boost rules into the new search setup
  6. Handling filtered URL redirects as part of the SEO mapping
  7. Testing the shopper experience on real catalogues, real categories, real mobile devices before launch

None of this is hard in isolation. The trick is doing it in the right order, with the right scope decisions made early, so the launch-day experience matches or beats what shoppers had before.

Migrating a Visualsoft store and worried about preserving the filter experience your shoppers are used to? We have done this work across multiple migrations and treat it as a project-critical deliverable rather than a launch-day afterthought. Get in touch for a no-pressure conversation, or read more about our Visualsoft to Shopify migration service.