ecommerce

Custom/API

Visidea brings AI-powered product discovery to your store through visual search, semantic search, product recommendations, and conversational discovery.

Overview

Businesses running a custom ecommerce site, headless storefront, proprietary platform, marketplace, or unsupported commerce system can evaluate an API-based or custom integration with Visidea. The goal is to connect selected product-discovery experiences with the business’s product catalog and customer-facing surfaces, within a scope defined around its technical environment.

Visidea accepts CSV files for data ingestion and provides two frontend integration options: its JavaScript library for the full Visidea experience, or direct API integration for greater control over the user experience, with greater implementation effort.

Typical custom product-discovery use cases include:

  • Ecommerce search
  • Visual Search from shopper-provided images
  • Semantic and AI-assisted product search
  • Product recommendation experiences
  • Conversational product discovery
  • Product discovery across large or complex catalogs
  • Merchandising-oriented discovery experiences
  • Storefront search and recommendation interfaces

The final configuration should reflect the store's catalog structure, merchandising strategy, storefront experience, and technical environment.

Features

  • Visual Search: Shoppers can use an image to find visually similar products within the ecommerce catalog.

  • Semantic Search: Shoppers can search using natural-language queries instead of relying only on exact keyword matches.

  • Product Recommendations: Visidea supports recommendation experiences that surface relevant products across the customer journey.

  • Conversational product discovery: Visidea provides an AI conversational assistant that helps shoppers discover products and ask questions about the business.

  • Storefront discovery experiences: Search, visual discovery, recommendations, and conversational interfaces can be positioned according to the store's UX and merchandising requirements.

  • Catalog-aware discovery: Product attributes, categories, variants, languages, currencies, and merchandising requirements can influence how discovery experiences are configured.

  • Custom product discovery: Visidea extends custom storefronts with additional product-discovery experiences designed to help shoppers find relevant products.

Technical overview

Visidea’s custom ecommerce integration combines data ingestion with a selected frontend implementation approach. Visidea accepts three CSV files: Items for product catalog records, Users for user account records, and Interactions for events such as purchases or cart adds. Its JavaScript library provides the full Visidea experience; direct API integration provides greater UX control with greater implementation effort. The files and capabilities required for a particular project must be confirmed during scoping.

Separate the product catalog source, approved data mapping, selected Visidea product-discovery capability, customer-facing presentation layer, and operational monitoring and ownership. Define the actual interface between systems after reviewing technical constraints and confirming the capabilities available through the selected approach.

Catalog assessment may consider product IDs, titles, descriptions, categories, attributes, variants, images, URLs, and availability or other business-critical fields where relevant and approved. This assessment does not establish that every field is mandatory or supported. Confirm field requirements and mapping rules before implementation.

The Items file contains one product per row, the Users file one user per row, and the Interactions file one event per row. All three CSV files follow the same formatting rules. [TECHNICAL DETAIL REQUIRED: approved CSV formatting specification, field definitions, and examples.]

Agree on data freshness, record lifecycle, error handling, retries, validation, observability, and rollback as implementation requirements. Do not assume these behaviors from the availability of CSV ingestion or API access. Determine whether Users or Interactions files are needed for the selected scope, and obtain the relevant privacy and security review before including their records.

Setup steps

  1. 1

    Define the product-discovery objective Specify the shopper problem, business context, and intended role of the discovery experience. Establish which journeys need attention and what successful functional behavior looks like. Use these criteria to guide scope decisions without assuming a particular commercial outcome or recommendation quality.

  2. 2

    Map the shopper journey and discovery surfaces Identify where shoppers will encounter the experience and what they need to do next. Review the relevant customer-facing surfaces, presentation requirements, and internal ownership. Use this map to compare the JavaScript library with direct API integration and understand the responsibilities of each approach.

  3. 3

    Review the catalog source and data model Identify the authoritative product catalog and review its identifiers, descriptions, imagery, variants, and relevant attributes. Confirm how product records will be represented in the Items CSV. Assess data quality and establish who owns exports, mapping decisions, corrections, and ongoing catalog maintenance.

  4. 4

    Confirm the selected Visidea capability scope Confirm which Visidea discovery capabilities are included and available through the proposed integration. Validate the requirements of each selected experience, including any necessary data inputs. Resolve unsupported assumptions before implementation and document the functional boundaries that engineering and product teams will use for acceptance.

  5. 5

    Define the integration contract and operating requirements Agree on the responsibilities connecting catalog data, Visidea capabilities, and the presentation layer. The contract may include data fields, validation rules, ownership, update expectations, and error-management expectations. Define access requirements and operational behavior jointly, without prescribing a protocol before reviewing the actual technical constraints.

  6. 6

    Implement and validate in an appropriate environment Build the agreed integration and validate it in an environment suitable for the project. Test functional behavior, product relevance, data quality, user experience, and operational safeguards. Review failures and acceptance criteria with accountable teams before deciding whether the implementation is ready for production use.

  7. 7

    Launch, monitor, and refine Agree on ownership, monitoring, privacy review, security review, incident handling, and change management before production use. Release the validated scope, monitor the agreed indicators, and investigate issues through the assigned owners. Refine the implementation as catalog content, shopper needs, and operating requirements change.

Ready to connect your catalog?

Talk to our team and see how to bring Visidea discovery to your platform.

Book a demo