ecommerce_ops · ecommerce · workflow
Kesko Senukai Digital Improves CTR From Site Search by 47%
Kesko Senukai Digital's in-house Elasticsearch site search returned irrelevant results and could only be managed by engineers, excluding the merchandising team and leading to low search usage and poor conversion rates.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Visitor submits search query
A customer submits a search query and the system works to understand its context and return the most relevant results.
Tools used
SearchNodeNLPBitREC · partnerElasticsearch
Outcome
After deploying SearchNode, CTR from site search sessions rose 47% and add-to-cart YOY rate grew 22%. In 2020, sessions with site search surged 86% YOY and conversion rates from site search grew 56% YOY.
What failed first
KSD's self-built Elasticsearch search solution was overly simple and required a large, expensive dedicated engineering team, making it unsustainable and unable to fulfil sophisticated merchandising and personalization requirements.
Results
Volume47%
Running since2018
Grounding & classification
Source type: vendor customer story
32 fields verified against source quotes.
enterprise searchpersonalizationrecommendation systemproduct catalogfailure mode describedhuman review describedmetric backednamed customerproduction runtime claimedsource backedtools describedvendor confirmedworkflow describedecommerceretailconversion increaseemployee productivitythroughput increasetime savedvendor customer storyecommerce opsmarketing opsdata sync enrichment