Help shoppers find the products they were trying to describe.

Shaupa turns a room, occasion, budget, photo, fit preference or half-formed idea into relevant products from your catalogue. Start with a feed, CSV or API. Launch as a hosted branded assistant, embed it on your site, or use Shaupa behind your own UI. Product pages and checkout stay with you.

  • Live with real products
  • Works from product feeds
  • Hosted, embedded, or API
  • Pilot controls agreed upfront
  • Built in Australia

Live now

This is already working with real products.

Shaupa is not a concept demo. Shoppers can already search naturally, save products, build boards, visualise ideas, and click through to retailer websites. For a retailer pilot, we can start from your existing product feed and create a focused branded experience around your catalogue.

Fashion discovery

Build a polished work outfit under $250

Natural-language search, outfit suggestions, budget-aware refinement.

Live Shaupa example using approved retailer products. Prices and availability may change.

Try fashion demo

Home discovery

Find a coastal sofa and coffee table under $2,000

Product discovery for rooms, styles, spaces, materials, and budgets.

Live Shaupa example using approved retailer products. Prices and availability may change.

Try home demo

Jewellery discovery

Show minimalist jewellery under $150

Guided jewellery discovery when shoppers do not know the exact product name.

Live Shaupa example using approved retailer products. Prices and availability may change.

Try jewellery demo

Why it matters

Your shoppers do not
think in filters.

Shoppers arrive with occasions, budgets, moods, constraints and half-formed ideas, not clean keywords. Shaupa turns how people actually talk into guided journeys towards relevant products.

01

Search misses intent

“Black dress” is easy. “Wedding guest outfit under $250” is where shoppers get stuck.

02

Filters hide demand

Failed and abandoned searches hide what shoppers actually wanted.

03

Shoppers need confidence

Fit preferences, budget and styling all affect whether a shopper feels confident continuing to a product page.

Capabilities

A complete product-discovery layer.

Everything shoppers need to move from a vague idea to the right product. Open any tile for detail.

How it works

From shopper language to product action.

  1. Connect your catalogue

    Send a feed, CSV, or API. Your IDs, prices, and links stay yours.

  2. Understand intent

    Shaupa turns natural language into the right products, budgets, and styles.

  3. Guide the shopper

    It shows what fits, explains why, and refines without starting over.

  4. Continue to the retailer

    Shoppers reach the retailer product page with their preferences already clarified. Product information, cart and checkout remain with the retailer.

Pilot controls

Controls agreed before launch.

Retailer controls are defined with the Shaupa team during pilot setup. This includes catalogue scope, brand tone, priority collections, exclusions, guardrails and the events used to measure the experience.

Catalogue scope

Choose the eligible catalogue, categories, collections and product sources.

Brand tone

Agree how the assistant should speak and how much explanation it should provide.

Priority collections

Identify seasonal ranges, launches, campaigns or high-priority categories.

Exclusions and claims

Define products, categories, materials and unsupported claims the assistant should avoid.

Stock and availability

Agree how current price, availability, variants and product URLs are handled.

Measurement plan

Choose the searches, refinements, saves, clicks and weak-result events to capture.

Define Configure Review Adjust

These controls are configured with Shaupa during onboarding. A self-service retailer dashboard is planned for a later stage.

Intent analytics

See the demand your filters never captured.

Pilot reporting can show what shoppers asked for, where results were weak, which products were saved or clicked, and which catalogue gaps affected discovery.

Illustrative example data

The example below demonstrates the types of signals a pilot can produce. It is not a Shaupa customer result.

EXAMPLE DATA Illustrative only
  • Searches
  • Refinements
  • Saved products
  • Product clicks
  • Weak-result queries
  • Assisted journeys

What shoppers actually wanted

Top shopper intentSmall-space furniture under $2,000
Weak-result queryWashable bouclé, pet-friendly, not beige
Useful follow-upDo you need delivery before next weekend?
Common budgetWedding guest outfits under $250
Saved product themeMinimalist gold jewellery
Catalogue gapWide-fit black heels under $120

Catalogue inputs and measurement options

Start with the retail data you already have.

Product data from common retail platforms can be mapped through feeds, exports or APIs. Most pilots can begin without replacing current site search.

Supported now

  • Affiliate or product feeds
  • CSV exports
  • Google Merchant Center-compatible feeds
  • Existing ecommerce exports
  • Custom APIs
Shaupa Discovery layer

Maps catalogue data, reads shopper intent, returns agreed pilot signals.

Available through pilot mapping

  • Shopify
  • BigCommerce
  • WooCommerce
  • Adobe Commerce
  • ERP or PIM exports
  • GA4 events
  • UTM tracking
  • Affiliate links
  • Product-click events
  • Saved-product events
  • Assisted-journey events
  • Server-side click logs

Planned or custom

Deeper integrations, retailer-specific event paths and additional ecommerce platform mappings can be considered after the initial experience is measured.

Most pilots can begin without replacing current site search. Deeper integrations can be considered after the initial experience is measured.

Deployment options

Start light. Go deeper when the proof is there.

Shaupa can start as an external discovery partner or hosted branded page, then expand into embedded AI search, white-label or API after the retailer has measured the initial experience.

Lightest touch

Discovery partner

Products can appear in Shaupa when relevant, with tracked click-through to retailer product pages.

Best for
Testing demand with low effort
Setup
Product feed or affiliate feed
Commercial model
Affiliate, referral or performance-based
Light

Hosted branded assistant

A retailer-focused page powered by Shaupa and scoped to the approved catalogue.

Best for
Fast pilot
Setup
Product feed, brand rules, launch URL
Commercial model
Monthly pilot or subscription
Deeper

Embedded AI search

A conversational discovery layer beside existing search, category or campaign journeys.

Best for
Retailers with search or discovery pain
Setup
Feed plus front-end integration
Commercial model
SaaS plus usage
Deepest

White-label / API

Shaupa catalogue intelligence behind a retailer-controlled interface.

Best for
Larger retailers and product teams
Setup
API, events, rules, security review
Commercial model
Custom

Value estimator

Estimate the value and break-even point.

Use your own monthly online revenue, gross margin and pilot cost to estimate the potential value of embedded AI product discovery and the uplift required to cover the monthly cost.

Illustrative model, not a guarantee

Editable assumptions

Estimate monthly value

The default values are an illustrative retailer example, not an Australian retail average. Replace them with your own figures.

These are relative sitewide conversion or sales uplift assumptions. A 2.5% relative uplift changes a 2.00% conversion rate to 2.05%. It does not add 2.5 percentage points.

Calculate revenue from traffic instead

AOV uplift is optional and defaults to 0%. The external research used here found limited evidence of higher cart value.

How this estimate works

This model applies an editable relative sales or conversion uplift to monthly online revenue. It assumes average order value is unchanged unless the user adds a custom assumption. Estimated ROI is calculated from incremental gross profit after the monthly Shaupa cost, not from revenue alone.

The model is a planning tool, not a forecast. Actual outcomes depend on catalogue quality, traffic, product range, placement, shopper adoption, stock availability, implementation and measurement.

Benchmark context

External research, not Shaupa customer results. The 2.5% scenario is an intentionally selected research anchor, not a reported industry average, expected Shaupa result or guaranteed result.

Etsy personalised semantic retrieval

5.58% increase in search purchase rate and 2.63% increase in site-wide conversion rate across live A/B tests.

Source

Best Buy long-tail ecommerce retrieval

3% conversion improvement in an online A/B test after embedding-based retrieval was added to the existing recall system.

Source

Generative AI field experiments in online retail

Search-query refinement and product-description applications produced sales effects in the approximate 2-3% range. The study found gains mainly through higher conversion, while average cart values were largely unchanged.

Source

JD.com generative faceted search

2% relative increase in user conversion rate in online A/B testing.

Source

All calculations run locally in the browser. Shaupa does not send, log or store raw retailer financial inputs from this estimator.

Pricing

Start with a low-risk pilot, then scale with your catalogue.

Pricing depends on catalogue size, launch surface, usage, and integration depth. Most Australian retailers can start with either a discovery partnership or a hosted branded pilot before committing to embedded search or white-label deployment.

Performance-based discovery partner

Approved products can appear in Shaupa when relevant.

Approved products can appear in Shaupa when relevant, with tracked click-through to the retailer website. Commercial terms can follow an affiliate, referral or performance-based model.

No fixed monthly platform fee Apply as a retailer

Starter Pilot

For a single-catalogue hosted pilot.

A$750/mo

A$500 setup

Start a pilot
  • Up to 5,000 products
  • Hosted Shaupa-powered assistant
  • Natural-language product discovery
  • Follow-up refinement
  • Product saves and click tracking
  • Standard intent analytics
  • Email support

Scale

For high-volume catalogues and embedded surfaces.

A$3,500/mo

A$2,000 setup

Talk to sales
  • Up to 100,000 products
  • Embedded AI search surface
  • API discovery layer
  • Advanced product ranking controls
  • Product feed refresh rules
  • Custom analytics report
  • Dedicated onboarding
  • Priority support

Enterprise

For white-label, API, and custom deployments.

Custom
Contact sales
  • Unlimited or custom catalogue size
  • White-label assistant
  • Custom integrations
  • Security and data review
  • SLA and onboarding plan
  • Dedicated success support
  • Custom reporting
  • Enterprise commercial model

Intro pilot pricing is available for early Australian retail partners. Final pricing depends on catalogue size, launch surface, usage, and integration depth.

FeatureDiscovery PartnerStarter PilotGrowthScaleEnterprise
Product inclusion in Shaupa consumer assistantYesOptionalOptionalOptionalOptional
Hosted discovery pageNoYesYesYesYes
Branded assistantNoLightYesYesCustom
Embedded on-site surfaceNoNoOptionalYesYes
White-labelNoNoNoOptionalYes
API accessNoNoNoYesYes
Natural-language searchYesYesYesYesYes
Follow-up questionsYesYesYesYesYes
Visual discoveryBasicBasicYesYesCustom
Product boards and savesYesYesYesYesCustom
Campaign journeysNo13UnlimitedCustom
Merchandising rulesBasicBasicAdvancedAdvancedCustom
Intent analyticsBasicStandardAdvancedAdvancedCustom
GA4 eventsReferral onlyBasicYesYesCustom
SupportEmailEmailPriorityPrioritySLA

FAQ

Frequently asked questions.

How is Shaupa different from a basic chatbot?

A chatbot usually answers questions. Shaupa is built for product discovery. It understands shopper intent, maps requests to catalogue data, shows relevant products, asks follow-up questions, supports saved boards and visualisation, and sends shoppers to retailer product pages to purchase.

Can Shaupa work with our existing product feed or API?

Yes. Shaupa can start from a Google Merchant Center feed, ecommerce product feed, CSV export, API, ERP/PIM export, or affiliate feed. A pilot can begin with a simple export and move to deeper integration later.

Can brand tone, catalogue scope and exclusions be agreed before launch?

Yes. These are agreed with the Shaupa team during pilot setup. The pilot can define catalogue scope, tone, priority collections, exclusions, guardrails and measurement events. A self-service retailer dashboard is planned for a later stage.

Does this replace our current search?

Not necessarily. Shaupa can start beside your current search as a hosted branded assistant, campaign page, or embedded discovery surface. Retailers can move toward deeper AI search only after a pilot proves value.

Can it run as a pilot first?

Yes. The recommended first step is a hosted branded pilot using your catalogue. This lets your team test shopper journeys, product relevance, analytics, and setup effort before committing to a larger deployment.

What data and insights do retailers receive?

Pilot reporting can include search-intent trends, weak-result queries, common budgets, styles and materials, saved products, clicked products, follow-up questions and assisted journeys, depending on the agreed measurement setup.

Does Shaupa handle checkout?

No. Shaupa helps shoppers discover and decide. Product pages and checkout stay on the retailer’s website.

Is Shaupa a marketplace or comparison site?

No. Shaupa is an AI shopping assistant and product discovery layer. The catalogue powers guided shopping experiences, but checkout remains with the retailer.

How does pricing work?

Pricing depends on catalogue size, launch surface, usage, and integration depth. Retailers can start with a discovery partnership, a hosted branded pilot, or a larger SaaS/API deployment.

What categories work best?

Shaupa is strongest where shoppers need guidance, taste, confidence, or context. Its current category focus is fashion and apparel, footwear, jewellery and accessories, furniture, homewares, and other home or space-related shopping.

Pilot request

Tell us what you sell. We’ll show the best pilot path.

Share your website, category, and preferred launch path. We’ll respond with a practical pilot recommendation and, where possible, a branded demo using your catalogue.

  1. 01Retailer website
  2. 02Catalogue source
  3. 03Pilot preference
  4. 04Search challenge

Get started

Help shoppers find the products they were trying to describe.

Module

  1. 01

    Built for fuzzy shopping language.

    Shaupa reads intent across category, style, colour, material, size, budget, room, occasion, and uncertainty. It can ask a follow-up question when the shopper has not given enough context.

  2. 02

    Useful when

    Your catalogue has products shoppers need help narrowing down across furniture, homewares, fashion, footwear, jewellery, accessories, styling, sizing, or other high-consideration purchases.

  3. 03

    Pilot input

    Product feed or sample catalogue, known search pain points, priority categories, and examples of real shopper questions.

Module

  1. 01

    Boards, looks, rooms, and product combinations.

    Shoppers can save products, arrange ideas, and visualise combinations before clicking through to the retailer product page.

  2. 02

    Useful when

    Fit, styling, room context, colour, material, or bundled products affect buying confidence.

  3. 03

    Pilot input

    Product imagery, category scope, styling rules, visual use cases, and product-page handoff requirements.

Module

  1. 01

    Recommendations that respect the brief.

    Shaupa can account for budgets, price ranges, available sizes and total board cost, then explain why a product matches the shopper's request.

  2. 02

    Useful when

    Shoppers care about price, available sizes, styling, or building a complete look without going over budget.

  3. 03

    Pilot input

    Product pricing, available sizes, variant data, and any budget or bundle rules you want respected.

Module

  1. 01

    Configured when imagery and visual matching are suitable.

    Image input can be configured for pilots where product imagery and visual matching are suitable.

  2. 02

    Useful when

    Shoppers know the look they want but not the product name or the right search terms.

  3. 03

    Pilot input

    Product imagery, category scope, and the kinds of visual references your shoppers typically bring.

Module

  1. 01

    Focused journeys for specific buying missions.

    Launch focused guided experiences for seasonal edits, event dressing, rooms or category education without replacing the full site experience.

  2. 02

    Useful when

    You have a campaign, category, or product story that needs more guidance than a grid can provide.

  3. 03

    Pilot input

    Campaign theme, eligible products, visual direction, desired calls to action, and launch timing.

Live capture

Live Shaupa screenshot

Selected live Shaupa screenshot