Alibaba Cloud Retail China Translated from Chinese

Shihuo (识货)

Marketing Personalization

Shihuo needed a more accurate and scalable way to match its product catalog against listings across many external commerce channels so users could compare prices and buy the right items. Its earlier approach of full-text retrieval plus manual review could not keep up with long-tail SKU growth, and the self-managed Milvus cluster it tried next introduced instability, higher operations complexity, and extra infrastructure work.

managed-cluster CPU utilization stayed around 50%
overall QPS improved about 10%
self-managing the cluster would have required more than one-third of operations manpower
write throughput held at 2K TPS

Reported impact

Business outcome

Shihuo improved product-association quality for long-tail commerce data while gaining a far more stable and supportable vector stack. Managed Milvus lifted QPS by around 10% in testing, kept CPU utilization stable near 50% at 2K TPS writes, and eliminated a large share of the hidden people cost that a self-operated vector cluster would have required.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Shihuo redesigned its commerce-matching pipeline around Alibaba Cloud Vector Search Service Milvus Edition and PAI-EAS. For hot products, the business can still preserve precise human curation, but at long-tail scale the platform now combines full-text retrieval, vector recall, and manual verification. Product data and cross-channel catalog signals are embedded with model services exposed through PAI-EAS, then stored in the managed Milvus service as the low-latency similarity-search layer that powers product association in the app. Moving from self-built Milvus to the managed service also gave Shihuo built-in monitoring, alerting, smoother capacity changes, and more predictable runtime behavior under sustained writes. The result is a retrieval architecture that improves matching quality for shopping decisions while keeping the vector platform much easier to operate as SKU counts and cross-channel comparisons continue to grow.

Data flow

Product records from Shihuo and external sales channels are converted into embeddings through PAI-EAS, written into the managed Milvus vector index, and then combined with full-text retrieval and human review to identify the correct cross-channel product matches shown in the app.

Solution architecture

2 components · 2 layers
  1. Compute
    • PAI-EAS Runs the embedding-model training and inference services used to generate vectors for retrieval.
  2. Storage
    • Vector Search Service Milvus Edition Stores product vectors and returns low-latency similarity matches for cross-channel product association.

Architecture clues

  • Milvus is consumed as a fully managed cloud-native service with built-in monitoring and smoother scaling controls.
  • PAI-EAS is used as the model online service for embedding-related training and inference tasks.
  • The final retrieval path combines vector recall, full-text retrieval, and manual review rather than replacing all logic with embeddings.
  • The platform preserves human curation for hot products while using vectors to scale long-tail catalog coverage.

Evidence from the source

Alibaba Cloud's managed Milvus is fully compatible with open source and can launch a retrieval cluster with one click while providing the surrounding operations infrastructure. (original: 阿里云向量检索服务 Milvus 版是 100% 兼容开源版的全托管产品,兼备了开源 Milvus 全部优势的同时,配套了完善的运维基建,可以一键拉起集群快速启用数据检索服务。)
Shihuo also uses PAI-EAS in parts of the embedding model training and inference flow, and PAI-EAS showed high-concurrency, low-latency advantages for search and recommendation. (original: 识货当前在其 Embedding 模型的训练与推理流程中... 在部分环节中还使用了阿里云 PAI-EAS... PAI-EAS 在搜索推荐场景下,体现出了高并发和低延迟的技术优势。)
Shihuo moved from full-text matching plus manual review to a strategy that adds vector recall for higher accuracy on long-tail products. (original: 识货技术团队果断转向采用“向量检索结合全文检索以及人工审核”的策略,在线上业务中增加准确性更高的向量召回链路。)
The self-built Milvus cluster saw CPU utilization swing between 50% and 100%, so the team began looking for a more stable vector service. (original: 自建 Milvus 集群... CPU 使用率常在 50%~100% 的范围内大浮动波动... 因此,识货技术团队开始考虑稳定性更高的向量服务。)
Transparency Evidence & methodology 100/100 reference value · 95% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence95%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Alibaba Cloud

    识货基于阿里云向量检索Milvus搭建电商领域的大规模向量数据检索平台_零售与电商_阿里云客户案例

    First-party
    https://www.aliyun.com/customer-stories/retail-2024-shihuo
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • Published on source page Jul 2, 2024 · Alibaba Cloud · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.