The situation
Retail and marketplace teams rarely lack AI ideas. The backlog already holds semantic search, personalised recommendations, generated product descriptions, a support assistant and dynamic pricing. What is missing is a way to choose between them, and a measure that will tell you, after the work, whether it helped.
In retail that measure matters more than in most sectors, because mistakes are visible and commercial. A search change that surfaces out-of-stock items, a recommendation carousel that pushes low-margin products, or a support answer that misstates the returns policy shows up in revenue and contact volume within days. The work therefore starts with the baseline, not the model.
What the work involves
Search and discovery. Most failures come from vocabulary and structure, not from the lack of a large model: shoppers use words your catalogue does not, attribute queries (“waterproof, size 9, under a budget”) are not parsed into filters, and lexical search misses close matches. Hybrid retrieval, combining lexical and vector search with metadata filters and a re-ranker, usually beats either alone. I build a labelled query set from your logs with your category experts, so every change is measured on the queries your shoppers actually type.
Recommendations. A production recommender has three layers: candidate generation (fast and recall-oriented), ranking (slower and precision-oriented) and re-ranking for business rules such as stock, diversity, freshness and margin. The largest gains are often in the data underneath: clean event tracking, de-duplicated identities and consistent product attributes. I built a Word2Vec-based recommendation system for Lenskart and designed the content recommendation engine and data pipeline for Momspresso; both depended on getting that foundation right.
Catalogue quality. Marketplaces and multi-supplier retailers inherit messy listings. Language models are useful here for extracting structured attributes from supplier text, flagging duplicates and drafting descriptions for a merchandiser to approve, with every generated field traceable to its source.
Support. Order-status, returns and product questions can often be answered from existing policy and catalogue content. I have integrated AI assistance into the trade chat of a peer-to-peer marketplace; the lesson carried over is that escalation to a person, and keeping policy content current, matter more than the model.
The signature deliverable, illustrated
The first output is an opportunity brief. Illustrative example, not a client result:
| Candidate | Measure | Data readiness | Risk | Recommended approach |
|---|---|---|---|---|
| Zero-result searches | Share of searches with no results; search exit rate | Logs available; synonyms unmanaged | Low | Hybrid retrieval plus synonym mining |
| ”You may also like” carousel | Add-to-basket from carousel in a controlled test | Events incomplete on mobile app | Medium | Fix tracking first, then candidate model |
| Supplier attribute gaps | Share of listings with complete key attributes | Supplier feeds vary by format | Low | Extraction with merchandiser approval |
| Returns-policy questions | Contact rate on returns topics | Policy pages current | Medium | Answer flow with escalation |
The brief is followed by one evaluated pilot and a rollout plan stating guardrails (stock and margin rules, fallback to current behaviour), monitoring and owner.
How acceptance is judged
The measure, the baseline and the decision rule are written into the scope before the build. Your product owner accepts the pilot on those terms. A pilot that does not beat the baseline is a valid result: you learn which assumption failed and avoid rolling out a change that would have cost money.
Ownership and handover
The product owner owns the measure and the rollout decision; the engineering owner owns the code and the evaluation harness. Merchandisers keep control of business rules, which sit in configuration rather than inside a model.
When to choose something else
If the problem is an existing knowledge assistant giving wrong answers, use RAG quality rescue. For a retrieval system beyond product search, see RAG and enterprise search engineering. If your support team needs to adopt AI in its daily workflow rather than a built system, see AI enablement for customer support. If you sell software to retailers, AI product delivery for B2B SaaS is closer. Other sectors are on the industries overview.