ecommerce_ops · ecommerce · workflow
Rugs.com returns to Algolia after nine-month OpenSearch experiment causes revenue decline
After replatforming to OpenSearch in March 2022, Rugs.com found business users nearly unable to make search changes without developer involvement, search speed was extremely slow, discoverability suffered, and revenue began to decline.
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 · Replatform to OpenSearch
In March 2022, Rugs.com replatformed their operations and left Algolia to adopt Shopify with OpenSearch.
Tools used
AlgoliaOpenSearchShopifyDynamic Re-RankingVisual EditorDynamic SynonymsAI Distributed Search Network
Outcome
After returning to Algolia, Rugs.com was back up and running in less than a day, business users regained ease of search management, and the company posted revenue gains instead of losses.
What failed first
OpenSearch lacked the basic features and ease-of-use that Algolia had provided, requiring developer involvement for nearly every change, producing slow search and poor discoverability, and ultimately causing revenue losses.
Results
Time savednine months
Cost replacedrevenue started to decline
Grounding & classification
Source type: vendor customer story
29 fields verified against source quotes.
personalizationrecommendation systemproduct catalogfailure mode describedmetric backednamed customerproduction runtime claimedtools describedworkflow describedecommerceretailcycle time reductionemployee productivityrevenue increasevendor customer storyecommerce opsdata sync enrichment