From Facets to Intent Engines: The History of On Site Product Discovery

In the early 1930s, librarian and mathematician S. R. Ranganathan proposed a way to organize knowledge by facets rather than by one rigid hierarchy. A book could be understood through its subject, material, form, place, or time, allowing several paths to the same answer. Nearly a century later, an online shopper can enter “red pumps for a Christmas party” and expect a product catalog to infer occasion, color, category, and intent. The interface has changed dramatically, but the underlying problem is familiar: how can a system help people move through abundance without forcing them to understand its filing system?
That question explains the path from faceted navigation to Shopify Search & Discovery, structured metaobjects, and AI informed personalization. It also explains why the strongest modern ecommerce experiences are not built from search technology alone, but from the relationship between language, product data, interface design, and commercial judgment.
1930s to 1990s: Classification becomes a way through complexity
Traditional classification arranged information into a hierarchy. A library shelf could place a book in one principal location, even though the book might concern several subjects. Ranganathan’s faceted classification introduced a more flexible logic, breaking an object into attributes that could be combined according to the question being asked. As the University of California Pressbooks explanation of faceted classification records, the 1933 model identified recurring dimensions such as the thing itself, its material, its action, its space, and its time.
Digital catalogs made this logic increasingly practical. Instead of browsing one tree, a user could narrow a collection through multiple attributes, such as author, format, language, and date. Information retrieval systems later extended the idea through indexes, keyword matching, and relevance ranking. The central shift was consequential: discovery no longer depended entirely on a perfectly designed category structure. It could respond to a combination of signals.
This is why modern product filters look familiar even when the catalog is visual, mobile, and commercially optimized. Color, size, brand, material, availability, price, and occasion are contemporary facets, translated from a theory of knowledge organization into the language of retail.

2000s: Faceted navigation meets the ecommerce catalog
As ecommerce catalogs expanded, category pages became less like digital brochures and more like working databases. Shoppers needed to reduce hundreds or thousands of products without opening each product page, so sidebars, filter drawers, sorting controls, breadcrumbs, and result counts became standard components of product discovery.
The benefit was not merely convenience. Facets gave merchants a way to expose the structure of a catalog while giving shoppers control over the path. A fashion store could separate cut, color, size, fabric, and occasion. A furniture store could combine room, dimensions, finish, and style. The interface was doing more than displaying inventory. It was teaching the customer how the inventory had been modeled.
Research from Baymard’s ecommerce product-listing study illustrates the commercial consequence of getting this layer wrong: sites with mediocre product-list usability have recorded abandonment rates between 67% and 90%, compared with 17% to 33% for stronger experiences. The figures do not mean that filtering alone determines conversion, but they show why product discovery became a usability discipline rather than a decorative feature.
The weakness of faceted navigation was equally clear. It required shoppers to translate a personal need into the merchant’s vocabulary. “Something polished for a warm evening” had to become a sequence of category, color, material, and price choices. The system could narrow known attributes, but it did not reliably understand the reason behind the search.
2010s: Search shifts from matching words to interpreting intent
On site search developed as a second route through the catalog. Early implementations were often literal: a query returned products containing the same words in titles or descriptions. Spelling tolerance, synonyms, stemming, autocomplete, and merchandising rules gradually softened that rigidity.
The important distinction was between a product name and a shopper’s language. A brand might call a bag a “sling,” while customers searched for “belt bag.” A catalog might use “trainers,” while a customer entered “sneakers.” Shopify’s documentation on custom synonyms and product boosts describes this practical layer, in which equivalent terms can be connected and selected products can be made more visible for specific queries.
Search therefore became a negotiation between relevance and commercial intent. Exact matching protected precision; synonyms recovered lost demand; merchandising rules supported launches, stock levels, and seasonal priorities. Analytics from searches with no results turned failed queries into evidence about missing vocabulary, weak product data, or gaps in the assortment.
2020s: Shopify Search & Discovery adds semantic context
The current phase extends the same history through semantic understanding. Shopify explains that Search & Discovery semantic search uses related words, concepts, categories, product descriptions, image text, and colors to expand results. A search for “Christmas party shoes,” for example, can associate the occasion with red pumps even when the product does not contain those exact words.
That is a meaningful change in the job of search. The system is no longer only asking whether a product matches a phrase. It is estimating which products belong to the situation implied by the phrase. Shopify currently states that this semantic capability is available for eligible stores on the Grow, Advanced, and Plus plans with fewer than 200,000 products, and that it does not apply to predictive search or the Japanese locale. Those constraints matter because AI assisted discovery remains a product capability with defined operating conditions, not a universal layer that can be assumed to work identically everywhere.
Search & Discovery also retains the useful controls inherited from earlier eras: filters, synonym groups, product boosts, result type settings, and controls for out of stock products. The present system looks intelligent because it combines these older mechanisms with contextual interpretation.

Metaobjects: the catalog becomes a knowledge model
Semantic search cannot compensate for a catalog that has been described inconsistently. This is where Shopify metaobjects become important. According to Shopify’s developer documentation, a metaobject is structured data with multiple related field values, unlike a metafield that generally attaches a single value to an existing resource. Metaobjects can represent reusable entities such as materials, designers, care instructions, room types, fit guides, or editorial themes.
A product can then reference a structured “occasion” object rather than relying on scattered prose. A collection can connect to a style profile, a size guide, or a sustainability explanation. Through the Storefront API metaobject reference, these relationships can support reusable, composable experiences across product pages, landing pages, filters, and custom storefronts.
The historical payoff is direct. Facets once described the attributes of an object; metaobjects make those attributes operational across a living commerce system. Better structure improves filtering, search relevance, merchandising, content reuse, and the quality of signals available to personalization models.
From personalization rules to intent engines
Personalization is the next layer, but it should be understood as an extension of discovery rather than a replacement for it. A recommendation system can combine stated intent, browsing behavior, purchase history, product relationships, inventory, margin, and context. The result might change the order of products, suggest complementary items, or adapt editorial content while preserving the shopper’s ability to search and filter directly.
The strongest architecture is therefore a stack: clean product and metaobject data at the foundation, Search & Discovery for query interpretation and catalog controls, a fast interface for exploration, and AI models used carefully to rank, recommend, or generate useful connections. Privacy, consent, explainability, and the ability to override automated decisions remain essential, as Shopify’s discussion of personalization trends also emphasizes.
For a design led agency such as Mifzi, this is where brand identity and technical implementation meet. A fashion, home, or lifestyle catalog needs a discovery system that reflects its visual language without sacrificing speed, accessibility, or measurable performance. Strategy can define the commercial vocabulary, design can make the paths legible, and Shopify development can connect structured data to a scalable storefront within a defined delivery process.

The history leaves a practical implication. If a product catalog is treated as a pile of pages, search becomes a repair job. If it is treated as a structured language of needs, attributes, relationships, and intent, search becomes part of the experience itself. The modern Shopify stack works best when the interface remembers the lessons of the library: there should be several useful paths to the same answer, and the system should quietly understand why the question was asked. For brands planning the next stage, Shopify’s platform provides the commerce foundation, while careful modeling and creative development determine whether discovery feels like navigation or guidance.












