ecommerce_ops · ecommerce · workflow

How Sary Used Algolia to Improve Search & Better Understand Its Customers

Sary's early open source search solution created problems with discovery quality, keyword search accuracy, and understanding customer intent, with Arabic-language keyword support being a particularly acute gap.

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 · Customer search or browse
Customers search for specific products or browse categories to improve product discovery.
Tools used
AlgoliaRecommendA/B Testing
Outcome

After adopting Algolia, Sary achieved a 500x improvement in search speed and a 300% boost in click-through rates, with customers frequently buying recommended products and the team gaining the ability to experiment with and understand customer behavior through A/B Testing.

What failed first

The simple open source search solution Sary used in its early days lacked adequate discovery quality, keyword search accuracy, and customer intent recognition, and could not deliver good results from Arabic keywords.

Results
Volume500x
Running since2022
Source

https://www.algolia.com/customers/sary

How we source this →

Grounding & classification
Source type: vendor customer story
26 fields verified against source quotes.
enterprise searchpersonalizationrecommendation systemproduct catalogfailure mode describedmetric backednamed customerproduction runtime claimedsource backedtools describedworkflow describedretailconversion increasecustomer satisfactionemployee productivityresponse time reductionvendor customer storyecommerce opsmarketing opsdata sync enrichmentextract classify route