Skip to content
Start free
All industries

Ecommerce & retail

Help shoppers find
what fits.

Connect product records, semantic search, keywords, and catalog relationships in one database for your storefront applications.

Build a product catalog Discuss your storefront

Discovery that knows the catalog

One product. Several ways to find it.

A shopper describes a need. Your application retrieves candidates, checks their catalog records, and decides what to show.

From a shopper’s words to a useful productIllustrative catalog · application-orchestrated retrieval
Shopper’s search

“A daypack for wet commutes”

Catalog recordsku_17

Commuter daypack

Price
$89
Inventory
Available
Category
Bags
01Semantic matchVector

Find product descriptions near the query’s embedding.

Candidate ID sku_17
02Keyword intentFull-text

Match words in the indexed product description.

Waterproofdaypackfor daily travel.
03Category relationshipsGraph

Follow the relationships you declare in the catalog.

Commuter gearBagssku_17
Your storefront application

Merge candidate IDs → read catalog rows with SQL → check stock and price → rank results.

Eligible productsOrdered by your merchandising rules

The application combines separate retrieval results. Ranking, stock checks, and merchandising rules stay in your code; index filtering depends on the vector mode you choose.

Explore recommendations

Across the shopping journey

A useful next result. A useful next answer.

01 / Merchandising

Make the shortlist yours.

Find similar products with vectors. Follow declared category or accessory relationships with graph queries. Read price and availability from product rows before your application ranks the shortlist.

  • Exclude unavailable variants.
  • Apply regional catalog rules.
  • Choose how promotions affect ordering.
Build a tailored experience
02 / Customer support

Put the right policy beside the order.

Retrieve product guides and return policies using keywords or semantic similarity. Fetch authorized order records separately, then give your support application the relevant context.

Example question

“Can I return the daypack I ordered?”

Order statusReturn policyProduct guide
Connect retrieval to your assistant

Start with the product ID

A catalog your team can maintain.

Keep the ingestion path explicit so a new price, description, or product variant reaches the right query model.

Follow the catalog example
  1. 01

    Give each product a stable identity.

    Use the row’s primary key as the vector ID and full-text document ID. Declare category and supplier relations in the schema.

    Define your schema
  2. 02

    Write each representation deliberately.

    Row, vector, and full-text updates are separate calls. Re-embed and re-index changed descriptions; retry failed steps. Declared graph edges follow the row write.

    Index your embeddings
  3. 03

    Keep purchase rules close to checkout.

    Recheck inventory and price in your commerce system before purchase. Search relevance does not reserve stock or authorize access to a customer’s order.

    Add keyword retrieval

Before the storefront rollout

Evaluate with your own catalog.

Test real search language.

Compare category terms, product names, and descriptive queries against a shortlist your team has reviewed.

Check change handling.

Change a description, remove a product, and interrupt an indexing step. Verify the application handles missing or stale candidates.

Measure the whole request.

Include embedding generation, retrieval, row lookups, and application ranking when you measure response time.

Build around your catalog

Start with one discovery workflow.

Open the working example Explore the database