Skip to main content

Find the Right Product from the Customer’s Description

Customers do not always know the code. Match scattered clues—dimensions, colour, vehicle model, intended use or a photo—against catalogue data.

Scroll down

Direct definition

What Is Smart Product Search?

It is not a simple keyword conversion. The workflow combines catalogue attributes, synonyms and tolerant matching.

Primary source: Meta Reva product and integration documentation.

Smart Product Search
Connected workflow

Smart Product Search

Product names, codes, dimensions, colours and attributes are matched against the catalogue with tolerance; uncertain results trigger clarification.

Capabilities

What this workflow can do

01

Recognise dimensions such as 22 mm and 60×180

Dimensions and units are normalised so 60x180 and 60 × 180 can represent the same intent.

02

Handle misspellings and close matches

Misspellings are tolerated, but low-confidence matches are never presented as certain.

03

Distinguish ERP errors from no-result cases

A source-system failure and a genuine no-result outcome produce different messages and actions.

Controlled delivery

How implementation works

We review catalogue quality and real search phrases, then work with the product team to identify the question that separates similar items.

  1. ScopeDefine data sources, users and permissions.
  2. ConfigureMap WhatsApp steps to ERP and operating rules.
  3. ValidateTest normal, uncertain and failure scenarios.
  4. Go liveRelease with monitoring and agent handoff controls.
Clear answers about boundaries, data and human handoff.

What we clarify before implementation

What data does Smart Product Search require?

We review catalogue quality and real search phrases, then work with the product team to identify the question that separates similar items.

Where should this workflow stop?

A source-system failure and a genuine no-result outcome produce different messages and actions.

Can it work with our current system?

The workflow needs an API, secure database access, file exchange or an existing service layer. We do not claim automation before a viable technical path is confirmed.

Show us how the work runs today and we will define a practical first scope together.

Clarify Your Product-Finding Workflow

Discuss Your Workflow