← BACK TO CASE STUDY GENERATOR
CREATIVE TECHNOLOGYIllustrative retail example

PROPOSED PROJECT

Catalog Search & Product Discovery

Help your audience find what they need within your products and ideas. Understand everyday questions, check prices and availability, and explain why each result fits.

Find your next everyday carry.STOREFRONT CONCEPT
THE SHOPPER’S REQUEST
“An everyday backpack for rainy commutes, under ₱5,000.”
BackpackUnder ₱5,000In stock
Illustrative olive-gray urban backpack, the fictional product shown in this search result.
MATCHED CATALOG RECORD / R-021

Transit 24

₱4,200 In stock

A compact commuter pack with a water-resistant outer fabric.

24 L
Catalog capacity
46 × 29 × 18 cm
Supplied dimensions
Why it appears

Matches the item type, budget, and availability. “Rainy commute” matches the documented water-resistant fabric.

Waterproof performance is not documented.
Illustrative search result and fictional catalog data. This is a static interface example.

Understand the request.
Respect the catalog.

Help your audience find what they need within your products and ideas. Understand everyday questions, check prices and availability, and explain why each result fits.

WHAT IS USUALLY DONE

A shopping chatbot can find products related to a request. It can still suggest something over budget, overlook stock levels, or describe a feature the product record does not confirm.

WHAT SOVRUN CAN DO FOR YOU

Sovrun would build search across your products and ideas that understands questions from your audience and checks them against your product records. Prices, stock levels, and required features act as firm limits. Each explanation shows the facts behind the match. The first version includes a customer search page, a record of why items were shown or excluded, and tests your team can review.

Show why a product
makes the cut.

AI reads the request to find possible matches. Product facts decide which ones can be shown. This example keeps the shopper’s price and stock requirements intact.

INCLUDEDR-021 / Transit 24₱4,200 · in stock · water-resistant outer
EXCLUDEDR-037 / Summit 30₱5,600 · exceeds the price limit
EXCLUDEDR-042 / Metro 20₱3,900 · no available stock
IF THE SHOPPER ASKS FOR WATERPROOF

“None of these records confirms waterproof construction. Would you like to see water-resistant options?”

A search experience
you can inspect.

The pilot includes the storefront result, the rules behind it, and an evaluation report before any wider release.

Fictional result card in the proposed search pilot.Transit 24₱4,200 / R-021

Product facts remain separate from generated explanations.

01 / Search interfaceA first working version for one product category, with explanations linked to product records.
QUERY RECORD / 014

Why this result?

Request
Rainy commute
Price ceiling
₱5,000
Stock rule
Required
Evidence
R-021 / outer material
02 / Match evidenceA record showing the request, search rules, product facts, and items that were left out.
EXAMPLE TESTS

Before it goes live.

  • Under-budget results only
  • Unavailable items excluded
  • Missing features disclosed
  • No-match responses reviewed

Pass criteria agreed with the merchant. No accuracy score is assumed.

03 / Questions for testingQuestions checked by your retail team, covering everyday requests, firm limits, and missing information.

How we’d make it happen.

  1. Prepare product records

    Check the product details, prices, availability, and rules that every result must follow.

  2. Test searches and answers

    Compare search and AI tools using questions reviewed by your retail team. Check both the products returned and those left out.

  3. Review with your team

    Test difficult requests and improve searches that return no result or an explanation the records do not support.

Where AI helps

Models interpret the request and rank retrieved candidates. They explain only supplied attributes. Price limits, stock, stable product IDs, and eligibility are controlled by structured data checks before a result can be shown.

What people approve

Merchandisers define the required filters, approve the attribute vocabulary, and review expected results for difficult queries. Missing evidence triggers a clarification or no-match response.

What we’d need to start

  • Clean catalog export and stable product IDs
  • Search terms and common customer questions
  • Availability and filtering rules

How we’d test it

Measure relevance, unsupported answers, and useful no-result behavior before connecting the pilot to a live storefront.

DISCUSS THIS PROJECT

This is a proposed project, not completed client work. The visuals and numbers show example outputs, not measured results.