100 Days of Weaviate guides for WordPress & WooCommerce

Finding Products That Are Actually Available

For a WooCommerce search experience, a relevant product is not necessarily a sellable product. A vector search can return an item because its description matches the shopper’s query even when the item is out of stock, private, discontinued, or unavailable in the shopper’s region. Availability should therefore be modeled as structured data and applied as a filter during the Weaviate search. Relevance determines which products match the query; filters determine which matching products are eligible to appear. Define what “available” means Before creating a Weaviate schema, agree with the merchant on the business rules behind availability. WooCommerce sites commonly need to distinguish between several states: In stock: The product has a positive inventory quantity. Backorderable: The product has no current stock but can still be

Why Filter Design Matters at Scale

At small scale, an inefficient filter can look harmless. A product query may return in a few hundred milliseconds, even if it combines several conditions, scans a large candidate set, or relies on a loosely designed metadata model. As a WooCommerce catalog grows across stores, languages, variations, and inventory states, the same filter can become one of the most expensive parts of the search request. Filter design matters because vector similarity is only one part of a production retrieval pipeline. A typical commerce request must identify the correct tenant or catalog, exclude unavailable products, apply price and category constraints, enforce business rules, and then rank the remaining products by semantic similarity. Poorly designed filters increase latency, consume memory, and make scaling less predictable. Filtering is

Combining “Under €100” With Semantic Search

Price constraints and semantic intent solve different parts of a WooCommerce search request. In a query such as “comfortable waterproof walking shoes under €100,” semantic search should identify the relevant products, while a structured filter should enforce the budget. Do not rely on the vector representation to interpret the price limit. Embeddings capture meaning and product relationships, but they are not a reliable mechanism for enforcing numeric conditions. Store price as a numeric property in Weaviate and apply the constraint as a filter during the search. Model the price as structured data Every product imported from WooCommerce should have a normalized numeric price field. For example: { "product_id": 1842, "name": "Waterproof Trail Shoe", "description": "Lightweight walking shoe with a breathable membrane", "price_eur": 89.95, "currency": "EUR",

Filtering by Price, Brand and Category in Weaviate

WooCommerce product search often needs more than semantic relevance. A shopper may want running shoes under $150, from a particular brand, within a specific category. In Weaviate, these requirements are handled with property filters that can be combined with vector or hybrid search. Model filterable WooCommerce properties Filtering works best when price, brand, and category are stored as structured properties during product ingestion. A practical product object might include the following fields: { "product_id": "wc_4821", "name": "Trail Runner Pro", "description": "Lightweight trail shoes with reinforced grip", "price": 129.99, "brand": "Acme Running", "categories": ["Shoes", "Running", "Trail"], "stock_status": "instock" } Store price as a numeric property rather than text. Store categories as an array when a product can belong to multiple WooCommerce categories. Normalize brand and category

Search Filters Meet Vector Search

For WooCommerce search, semantic relevance is only half the problem. A shopper may search for “lightweight trail shoes” while also requiring a specific size, brand, price range, stock status, or product category. Vector search understands the meaning of the query; filters enforce the shopper’s business constraints. Combining both produces results that are relevant and usable. Why vector search needs filters A vector query can identify products that are conceptually similar to a natural-language query, even when the product title does not contain the exact words. However, similarity alone does not guarantee that a product is available, affordable, or appropriate for the selected storefront context. For example, a WooCommerce agency might receive this request from a storefront: {"query":"waterproof hiking boots","brand":"North Ridge","minPrice":100,"maxPrice":220,"inStock":true} The vector component should find

Brands, Product Codes and Exact Matching

WooCommerce search often needs two different kinds of relevance. A shopper may search for “waterproof hiking jacket” and benefit from semantic similarity, while an agency operator searching for SKU-48392-BLK-M expects one exact product. Brand names and product codes should therefore not be treated like ordinary descriptive text. Why exact matching matters in WooCommerce Product codes, SKUs, manufacturer part numbers, EANs, UPCs, and internal identifiers are usually short, structured values. A vector search can return a semantically similar product instead of the product represented by the code. That is unacceptable for stock lookups, product feeds, customer-service tools, and order-management workflows. Brand names have a similar problem. A search for ACME should not automatically rank products from ACME Outdoor, ACME Accessories, or a misspelled brand above the

Making SKUs Searchable the Right Way

SKU search looks simple until a store contains values such as TSHIRT-BLK-M, TSHIRT BLK M, shirt_blk_m, and supplier codes with leading zeroes. For a WooCommerce agency, the right implementation separates exact identification from useful discovery instead of treating every SKU as ordinary product text. Start with the search requirement There are usually three different SKU use cases: Exact lookup: an operations user enters a complete SKU and expects one product or variation. Prefix or partial lookup: a user enters part of a code, such as TSHIRT-BLK, to find a family of variations. Mixed product search: a shopper or support agent searches for a SKU alongside product names, brands, and descriptions. These cases should not rely on one field or one ranking strategy. Exact lookup should

Tokenization: The Hidden Search Quality Problem

Why tokenization can quietly damage WooCommerce search When a shopper searches for a product, the visible query is only the starting point. Before Weaviate can compare the query with indexed content, it breaks text into tokens. Those tokens determine which terms are available to lexical search, including the BM25 component of a hybrid query. This makes tokenization a search-quality issue that is easy to miss. A product title can look highly relevant to a merchandiser while producing weak lexical matches because the query and the indexed value were split differently. For WooCommerce agencies, this is especially important for product names, variation labels, brand names, model numbers, dimensions, and technical specifications. A small punctuation or casing difference can change the search behavior even when the two

BM25 and What It Means for Product Search

Product search is often described as a relevance problem, but relevance is not one thing. A shopper searching for black leather boots expects matching products to contain those words, while a shopper searching for waterproof hiking shoes may expect semantic matches even when the exact wording differs. BM25 is one of the most useful foundations for the first category: lexical search based on the terms that appear in product data. What BM25 does BM25, short for Best Matching 25, is a ranking function used by search engines to score how well a document matches a text query. In a WooCommerce catalog, the document is usually a product or a product representation containing fields such as the product name, description, SKU, category, brand, and attributes. BM25

Boosting Product Names and Categories

WooCommerce search results often give too much weight to long product descriptions, attributes, and imported metadata. That can make a category name or product name match less prominently than an incidental phrase in the body of a description. Weaviate lets you control this behavior by boosting the fields that matter most to shoppers. Why product names and categories need more weight A customer searching for linen shirt usually expects products with those words in the product name or assigned category to rank ahead of products that only mention linen in their description. A product name is a strong signal of relevance, while a description match is often supporting evidence. For a WooCommerce catalog, useful searchable properties commonly include: name: the WooCommerce product name. categories: one

Finding the Right Hybrid Search Balance

Hybrid search combines lexical matching with vector similarity. In a WooCommerce store, this matters because shoppers use both precise product language and natural, descriptive language. A query such as black waterproof hiking boots contains useful exact terms, while shoes for wet mountain trails depends more heavily on semantic understanding. What the balance controls In Weaviate, the alpha parameter controls the weighting between keyword and vector search: alpha: 0 relies on keyword search. alpha: 1 relies on vector search. Values between them blend both result sets. A starting value such as alpha: 0.5 is useful for testing, but it is not a universal best practice. The right value depends on the product catalogue, query patterns, field configuration, and the commercial consequences of an incorrect result. When

When Semantic Search Should Win

Semantic search should not replace every search strategy in a WooCommerce store. It should win when the customer’s intent is expressed through meaning, context, or a use case rather than an exact product term. Where semantic search has an advantage Traditional keyword search is effective when the query contains a product name, SKU, brand, or precise attribute. Semantic search becomes more useful when shoppers describe a problem or desired outcome. Use cases: “equipment for a small home gym” or “gifts for someone who loves coffee” Descriptive language: “lightweight waterproof jacket for commuting” Incomplete terminology: “non-slip shoes for restaurant work” when the catalog uses “slip-resistant footwear” Natural-language intent: “a sofa that works in a narrow apartment living room” A vector index can represent the meaning of

When Exact Keywords Should Win

Semantic search is useful when a shopper describes an intent in unfamiliar language. However, WooCommerce catalogs contain many queries where the exact keyword should win. A SKU, model number, plugin name, compatibility code, or regulated product term is not merely a hint about meaning. It is an identifier. Why semantic similarity can be wrong for product identifiers Vector search is designed to find text with a similar meaning. That makes it valuable for queries such as “waterproof shoes for winter commuting,” where the shopper may use language that does not appear in the product title. Identifiers behave differently. Consider these searches: SKU-AX410-BLK MK-7 USB-C PD 65W WooCommerce Subscriptions compatible with Epson T04D1 A semantically similar result may contain related products but still be unusable. A

Hybrid Search: Keyword + Semantic Search

WooCommerce search has to handle two different kinds of intent. A shopper searching for waterproof trail shoes expects relevant concepts and attributes, while a shopper searching for SKU TRL-204-BLK expects an exact lexical match. Hybrid search combines keyword relevance with semantic similarity so agencies can support both behaviors in one query. What hybrid search combines Weaviate’s hybrid operator combines a keyword search, typically BM25, with a vector search. BM25 rewards exact terms, term frequency, and useful matches across configured properties. The vector component compares the query embedding with product embeddings, allowing related wording such as rainproof hiking footwear to match a product described as waterproof trail shoes. The alpha value controls the balance: alpha=0 favors keyword search. alpha=1 favors vector search. A middle value, such

Why WooCommerce Search Needs More Than One Search Method

WooCommerce search is not one problem. A shopper looking for a specific SKU, a product category, a compatible accessory, or an idea such as “a lightweight jacket for rainy commutes” is expressing a different type of intent. Treating every query as a keyword lookup creates avoidable gaps in relevance and conversion. For agencies, the practical solution is to combine multiple search methods and route each query through the method, or combination of methods, that best matches the shopper’s intent. Keyword search handles exact product intent Traditional lexical search is still essential for WooCommerce stores. It performs well when the query contains a product name, SKU, brand, model number, or other text that should match directly. SKU queries: TSHIRT-BLU-M Brand queries: TrailMaster boots Product names: stainless

Multilingual Product Search with Weaviate

WooCommerce stores often contain product information in several languages: translated titles, localized descriptions, category names, attributes, and search synonyms. A multilingual vector search layer can connect a shopper’s query with the right product even when the wording differs across languages. Weaviate is useful for this because the same product can be represented as a semantic vector while retaining structured properties for filtering, sorting, stock checks, and WooCommerce identifiers. Design the product representation Start by deciding which localized fields should contribute to the product vector. A practical representation usually includes the product name, short description, long description, categories, attributes, and relevant search keywords. Keep operational fields such as SKU, price, stock status, language availability, and product URL as properties rather than mixing them into the searchable

Semantic Search Across Product Categories

Semantic search becomes more valuable when a WooCommerce catalog spans multiple product categories. A shopper may search for “a lightweight waterproof option for commuting” without knowing whether the best match is a jacket, backpack, shoe, or accessory. Keyword search usually treats those terms as separate filters, while vector search can compare the meaning of the query with product content across the entire catalog. Why cross-category search is different Category-specific search often assumes that the shopper already knows the product type. A query such as “warm layer for cycling to work” can cross category boundaries because the intended solution might be a fleece, softshell jacket, vest, or thermal base layer. For agencies, this creates two requirements: The search index must represent products consistently, regardless of their

Why “Running Shoes for Rain” Beats Exact Keywords

Searchers rarely use the same words as a product catalog. A shopper may type running shoes for rain, while the catalog describes the relevant products as water-resistant trail shoes, weatherproof trainers, or GORE-TEX road-running footwear. An exact keyword query can miss those products even though they satisfy the shopper’s intent. For WooCommerce agencies, this is one of the clearest practical benefits of semantic search. The goal is not merely to find products containing every word in a query. The goal is to retrieve products whose meaning, attributes, and use case match the customer’s request. Why exact keyword matching misses relevant products A traditional keyword search usually scores documents according to the words they share with the query. That works well when product names and search

Searching for Products by Meaning

Keyword search works well when shoppers know the exact product name, SKU, or attribute value. It becomes less effective when they describe an intent, use unfamiliar terminology, or search with a phrase such as “a lightweight jacket for wet city commutes.” Meaning-based search addresses this gap by representing product content and shopper queries as vectors, then retrieving products whose meanings are close in the vector space. What meaning-based product search does A semantic search workflow converts both product records and search queries into embeddings. An embedding is a numerical representation of text generated by a model. Products with related descriptions tend to have vectors that are close together, even when they do not share the same words. For example, a catalog may contain a product

Your First Semantic Product Search

Semantic product search lets shoppers describe what they need in natural language instead of matching only the exact words stored in a product title. A shopper searching for “a lightweight jacket for rainy city commutes” can discover products described as “packable waterproof shell” even when the wording is different. For a WooCommerce agency, the first implementation should be narrow and measurable: index a useful product representation, run a near_text query, return product IDs, and let WooCommerce remain the source of truth for price, stock, and checkout data. Choose the product data to index Do not send an entire rendered product page to the vectorizer. Build a clean text representation from fields that describe the product’s meaning and intended use. Product name: Include the customer-facing name.

Handling Deleted and Out-of-Stock Products

Product availability changes are one of the easiest ways for a WooCommerce search experience to become misleading. A product can be deleted from WooCommerce, hidden from the catalog, or temporarily out of stock while its vector remains in Weaviate. If those states are not synchronized, shoppers may receive recommendations for products they cannot buy. For agencies, the solution is to treat the vector index as a synchronized search projection rather than a permanent product archive. Every indexed object needs enough state to determine whether it is eligible to appear in a particular WooCommerce experience. Model availability as indexed data A Weaviate product object should normally include identifiers and availability fields alongside the text used to generate its vector. A practical schema might include: product_id: The

Handling Product Updates Without Rebuilding Everything

Product catalogs change constantly: prices move, inventory is replenished, descriptions are rewritten, and products are assigned to new categories. A WooCommerce integration should not treat every change as a reason to delete and recreate the entire catalog in Weaviate. The safer approach is to identify the changed product, update only the necessary properties, and refresh its vector only when the searchable content has changed. Separate product changes by type Not every WooCommerce update has the same search impact. Before writing synchronization code, classify fields into groups: Searchable content: product name, description, short description, attributes, category names, and brand information. Filtering data: price, stock status, sale status, category IDs, product type, and visibility. Operational metadata: WooCommerce product ID, SKU, timestamps, image URLs, and synchronization status. A

Keeping WooCommerce and Weaviate in Sync

WooCommerce is the system of record for catalog, pricing, inventory, and publication status. Weaviate is the retrieval layer that makes that information searchable by meaning. Keeping both systems synchronized requires more than sending a product to Weaviate once. A production integration must handle updates, deletions, failed requests, retries, variation data, and changes to the content used for vectorization. Define the ownership boundary first Before implementing synchronization, decide which system owns each field. WooCommerce should normally remain authoritative for transactional and catalog data, including: Product and variation identifiers Names, descriptions, attributes, categories, and tags Prices, stock quantities, and stock status Publication status and visibility Product images and external URLs Weaviate should store the fields needed for semantic search, recommendations, or retrieval-augmented applications. It can also store

Importing a WooCommerce Catalog Into Weaviate

A WooCommerce catalog is a practical first dataset for a product search, recommendation, or shopping assistant built with Weaviate. The import needs to preserve structured commerce fields such as SKU, price, stock status, categories, attributes, and product URLs while also creating searchable text from the product name and description. For an agency, the importer should be repeatable. It should handle pagination, avoid duplicate objects, support incremental updates, and keep Weaviate in sync when products are edited or deleted in WooCommerce. Plan the product representation Before importing products, decide which WooCommerce fields should be stored as properties and which should contribute to the vectorized text. A useful product object commonly includes: Identity: WooCommerce product ID, SKU, slug, and product URL. Commerce data: regular price, sale price,

How Weaviate Stores Product Vectors

In a WooCommerce search integration, a product vector is the numerical representation of product information such as its name, description, attributes, categories, and selected custom fields. Weaviate stores that vector alongside the product object and maintains a vector index so semantic searches can find products by meaning rather than by exact keyword matches. A Product in Weaviate Has Data and a Vector A typical product object contains ordinary properties and a vector. The properties might include the WooCommerce product ID, title, description, SKU, price, stock status, categories, and attributes. The vector is an array of floating-point numbers generated by an embedding model. { "id": "2f4f7b7e-8c39-4f90-a832-3cc7e7b8a9c1", "properties": { "wooCommerceId": 1842, "name": "Waterproof trail running jacket", "description": "Lightweight shell for wet and windy mountain runs", "categories": ["Running",

Product Titles, Descriptions, Attributes and Variations

WooCommerce agencies often start product search projects by embedding only the product name. That is rarely enough. A product title may identify the item, while the description explains use cases, attributes define constraints, and variations determine purchasable combinations such as size, color, capacity, or finish. A Weaviate implementation should represent these fields deliberately so semantic retrieval improves discovery without weakening exact catalog filters. Separate searchable text from structured product data Use a single combined text value for semantic similarity, but retain the original fields as typed properties. The combined value can contain the product title, short description, long description, category context, and important attribute labels. Structured properties should hold values needed for filtering, sorting, synchronization, and display. A practical product record might contain properties such

Which WooCommerce Product Data Should You Index?

Index product data according to how shoppers search For a WooCommerce agency, indexing every available product field is rarely the best approach. Product records often contain duplicated descriptions, HTML fragments, operational metadata, serialized custom fields, and values that change frequently. A useful Weaviate schema should reflect the queries the store needs to answer, not simply mirror the WooCommerce database. Start by listing the search and recommendation experiences you need to support: Keyword search for product names, descriptions, brands, and features. Natural-language discovery such as “waterproof hiking boots under $150.” Structured filters for price, stock status, categories, attributes, and ratings. Product recommendations based on descriptions, categories, and compatible items. Exact lookups by SKU, product ID, slug, or an external catalog identifier. Each use case determines whether

Designing a Product Collection for WooCommerce

A useful WooCommerce search experience starts with a deliberate product model. Before importing products into Weaviate, decide which product facts should be searchable, which should be filterable, which should be returned to the storefront, and which should remain in WooCommerce as the source of truth. Define the search contract first A product collection should support the queries your storefront and merchandising tools actually perform. Typical requirements include: Semantic search such as waterproof commuter backpack for a laptop. Keyword matching for product names, SKUs, brands, and technical specifications. Structured filters for price, stock status, category, brand, attributes, and ratings. Catalog scoping by language, channel, customer group, or store. Stable identifiers that let the application retrieve the authoritative WooCommerce product. Write these requirements down before choosing properties.

Your First Weaviate Collection

In Weaviate, a collection is the top-level container for a type of object. For a WooCommerce agency, a collection might represent products, product documentation, orders, support articles, or store policies. It defines the properties stored on each object and the vector configuration used for semantic search. Choose a collection boundary Start with one business concept rather than creating a single collection for every record in a store. A Product collection is a sensible first example because product data commonly supports search, recommendations, merchandising, and support workflows. A useful product record might include: sku for the WooCommerce product identifier name for the product title description for searchable product content categories for taxonomy values price for filtering or display metadata permalink for linking search results back to

Why Semantic Search Changes Product Discovery

Search That Understands Shopping Intent Traditional WooCommerce search usually matches the words in a query against product titles, descriptions, SKUs, categories, and attributes. That works well when a shopper knows the exact product name, but it struggles when the shopper describes a need instead. A customer searching for “comfortable shoes for walking around a city all day” may be interested in cushioned sneakers, lightweight walking shoes, or supportive casual trainers. A keyword-only search may return products containing “city” or “walking,” while ignoring products that satisfy the underlying need. Semantic search represents the meaning of queries and products, allowing the search system to identify related concepts even when the wording differs. For product discovery, that changes search from a text-matching feature into an intent-matching feature. Keyword

Embeddings: Turning WooCommerce Products Into Meaning

Why product data needs more than keywords WooCommerce search usually starts with exact fields: product title, SKU, attributes, categories, and description. That works when a shopper searches for a phrase stored on the product. It becomes less reliable when the shopper describes an intent instead: “A waterproof jacket for city cycling” “A quiet keyboard for an open-plan office” “Gift ideas for someone who likes espresso” An embedding converts text into a numerical vector that represents its meaning. Products with related descriptions are positioned near one another in vector space, even when they do not share the same words. A WooCommerce agency can use those vectors to build semantic product search, related-product features, catalog recommendations, and support tooling. What to embed from a WooCommerce product Do

What a Vector Actually Represents

A Vector Is a Numerical Representation In a WooCommerce search or recommendation system, a vector is an ordered list of numbers that represents the meaning or characteristics of an item. A product title, description, category, or customer query can be converted into this numerical form by an embedding model. For example, a product such as “waterproof men’s hiking jacket with removable hood” might become a vector containing hundreds or thousands of decimal values: [0.021, -0.184, 0.773, 0.042, …] These values are not individually readable labels. The first number does not necessarily mean “waterproof,” and the second does not necessarily mean “men’s.” Meaning is distributed across the vector as a whole. What the Numbers Represent The numbers encode patterns learned from relationships between words, phrases, and

Keyword Search vs Vector Search for WooCommerce

Choosing the Right Search Method for WooCommerce Search quality directly affects product discovery, conversion rates, and support workload. For WooCommerce stores, the choice is not simply between an old search system and a modern one. Keyword search and vector search solve different problems, and the best implementation often uses both. Keyword search is strongest when shoppers know the exact terms they want to find. Vector search is strongest when shoppers describe a need, use unfamiliar wording, or search by meaning rather than by product name. Agencies should evaluate the store’s catalog, search behavior, product data, and business rules before selecting an approach. How Keyword Search Works Keyword search compares the terms in a query with indexed text from product titles, descriptions, SKUs, attributes, categories, and

Vector Search Explained Without the Hype

What Vector Search Actually Does Vector search finds items by meaning rather than relying only on exact words. A product title, description, category, or attribute is converted into a numerical representation called an embedding. Text with similar meaning produces vectors that are close together in a high-dimensional space. For example, a keyword search for waterproof hiking shoes may miss a product described as weather-resistant trail footwear if those exact terms are not present. Vector search can identify the relationship between the phrases and return the relevant product. This does not mean the search engine understands products like a person. It compares mathematical representations generated from text or other data. The quality of the result depends on the source content, the embedding model, the index, and

What Is Weaviate and Why Should WooCommerce Agencies Care?

Weaviate in Plain Terms Weaviate is an open-source, cloud-native vector database. It stores structured objects, such as products, categories, documentation pages, and support articles, together with vector representations of their meaning. Those vectors make it possible to find content by intent and context rather than by exact keyword matches alone. Weaviate also supports traditional keyword search, metadata filtering, and hybrid search. It can run as a managed Weaviate Cloud instance or be self-hosted, depending on an agency’s operational, security, and budget requirements. Why a Vector Database Matters for WooCommerce WooCommerce product catalogs often contain inconsistent terminology. A shopper may search for “waterproof walking shoes,” while a product title says “women’s trail footwear.” A keyword-only search may miss that product. A vector search can identify the