MongoDB Retail United States

Beni

Marketing Personalization

Beni needed to search and rank more than 300 million one-of-one resale listings refreshed by over a million items per day, but its split Milvus and MongoDB architecture created brittle ETL synchronization, expensive operations, and slow schema evolution.

Beni manages over 300 million listings that refresh by more than a million items daily.
Beni saw a 30% improvement in query search clickthrough rate and around a 30-40% increase in total sales.
Beni saw up to a 43% improvement in image search clickthrough rate (CTR).
In the past two years Beni has diverted over $5 million in gross merchandise value to the resale market.

Reported impact

Business outcome

Beni improved image-search clickthrough by up to 43%, increased query-search clickthrough by 30%, translated higher engagement into roughly 30-40% more total sales, and cut monthly infrastructure costs by 20% while scaling an endlessly growing catalog.

  • Cost Reduction
  • Customer Experience
  • Revenue Growth
  • Scalability

Solution

Beni replaced a split architecture built around Milvus and a separate catalog database with a unified MongoDB deployment that holds vector embeddings, product attributes, and user engagement signals in one place. Listings from resale marketplaces such as eBay, Poshmark, and Depop are continuously ingested into MongoDB Atlas, enriched with generated embeddings, and combined with popularity and behavioral data so the company can run hybrid search across more than 300 million one-of-one items. MongoDB Search and MongoDB Vector Search let Beni mix reverse-image and text retrieval with ranking logic based on relevance and shopper activity, while Atlas sharding distributes the growing catalog across smaller, more cost-effective instances. Keeping the ETL pipeline inside one data platform also lets the team add new attributes such as style or boldness without rebuilding an external vector store from scratch.

Data flow

Listings from marketplaces such as eBay, Poshmark, and Depop are ingested into MongoDB Atlas, enriched with embeddings and attributes, combined with user engagement data, and queried through MongoDB Search and MongoDB Vector Search so Beni can return personalized resale results in its extension, app, and website.

Solution architecture

3 components · 2 layers
  1. Storage
    • MongoDB Atlas Stores Beni's resale catalog, engagement data, and vector-bearing product records in one scalable operational platform.
  2. Serving
    • MongoDB Search Supports fast catalog search and relevance-based filtering across a constantly changing inventory.
    • MongoDB Vector Search Enables reverse-image, image-plus-text, and hybrid semantic retrieval over resale listings.

Architecture clues

  • Beni uses sharding to distribute a 300 million-plus catalog across smaller, more cost-effective instances.
  • MongoDB allows Beni to add new catalog attributes such as style or boldness without rebuilding the full vector store.
  • The company ranks results with both semantic relevance and popularity signals stored in the same platform.
  • The old dual-store ETL pipeline was eliminated by consolidating vector embeddings and catalog data into one database.

Evidence from the source

"Beni manages a massive, fragmented, and easily searchable catalog of over 300 million listings that refreshes by more than a million items daily."
"By unifying its database environment with MongoDB, Beni was able to consolidate its vector embeddings, product catalog, and user engagement data."
"We’ve seen up to a 43% improvement in our image search clickthrough rate (CTR), and a 30% improvement in our query research clickthrough rate."
"With MongoDB's text, vector, and hybrid search capabilities, we’re able to pull products from our catalog that are both semantically relevant and also highly popular based on other user engagement data."
Transparency Evidence & methodology 100/100 reference value · 82% confidence · 2 sources

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
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency9/10
    2 source references 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. MongoDB

    Beni customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/beni
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
  2. Beni

    Terms & Conditions

    First-party
    https://shopbeni.com/terms

    The 'Developer Name and Address' section lists Beni at 220 Water Street #106, Brooklyn, NY 11201, supporting United States as the closest defensible operating region.

    Source type
    Official company website
    Supports
    • Region

Date evidence

  • First archived Mar 6, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Mar 16, 2026 · MongoDB · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.