Problem
Mercari, a Japanese consumer-to-consumer (C2C) marketplace, built a worldwide app targeting 50 countries in 3 years and 4 billion cumulative listings (September 2025). The global search needs several languages, products with variants such as colors, and its own tuning for entertainment and hobby goods. Data volume is orders of magnitude above sales, so cost matters. The Japan search runs on Elasticsearch with features built into Go microservices, and the business feared lower revenue from a new engine.
Example from the article: The product owner kept asking to use specific Japan search features in the global app, but those features were tied to the Japan business services.
Solution in brief
Launch on a fully managed retail search service (Vertex AI Search for Commerce, VAIS:C), and switch to Elasticsearch when traffic makes it too expensive. Keep the new backend independent of the engine through an abstraction layer and query plugins. Move Japan search features one by one into a shared layer on the in-house platform.
Questions this case answers
- How to launch a new search product on a managed engine with a defined exit path to a self-hosted engine, while checking that revenue does not fall below the incumbent search
- How to make search features built inside one product's services reusable by other products without blocking the original team
- How to launch product search for a multi-country app quickly when the incumbent search engine is too costly or too tightly coupled to reuse?
- How to start on a managed search service without being locked in, and when to move to a self-hosted engine?
Tools and methods
- Vertex AI Search for Commerce (VAIS:C) — managed retail search with multilingual support, variants and request-based billing
- Elasticsearch as a Service (EaaS) — in-house Elasticsearch hosting platform, the planned long-term engine
- A/B test — checks that the new engine earns the same revenue as the Japan search
- Plugin mechanism and engine abstraction — hooks for query pre- and post-processing, engine code behind one interface
Google or a one-time email code. No password.
