Product search becomes expensive long before the embedding model becomes interesting. In a gaming marketplace, the bill is usually dominated by how many listings are indexed, re-read, and re-ranked, not by the final text response. My default is a staged retrieval contract: filter by tenant and listing state first, query a bounded candidate set, then attach traceable source context. That shape keeps the application replaceable when an index vendor, region, or ranking policy changes.
Short answer: use explicit collections, metadata filters, bounded queries, and source identifiers; keep the retrieval contract in your service so Elasticsearch, OpenSearch, Algolia, Pinecone, or an HTTP vector service can be swapped without rewriting checkout or moderation code.
Start with the cost-and-retention ledger
An e-commerce listing has a surprisingly long life.…