The real margin lives in nuanced recommendations — not telling users where their package is.
The AI transformation in e-commerce is not about flashy chatbots or simple FAQ automation. The actual value lies in building intelligent agents that support complex decision-making and personalized user journeys. This requires a clear architectural vocabulary, an understanding of memory systems, and a disciplined approach to technology readiness.
For Indian companies like 91mobiles, which operate in a highly dynamic and competitive mobile commerce space, these concepts are not academic. They are the foundation for delivering AI-powered features that users trust and that generate sustainable business value.
The Planner/Worker pattern unlocks scalable AI agents
The architecture of AI agents in e-commerce is often misunderstood. A naive approach is to build static templates or simple rule-based bots, which quickly break under dynamic pricing, complex user queries, or evolving catalogs.
The Planner/Worker pattern splits the AI agent into two distinct components:
- Planner: Decides what action to take next based on the current context and goals.
- Worker: Executes the chosen action using available tools and data.
Consider a price-drop alert system. The Planner decides when to notify the user, while the Worker fetches the latest prices and formats the message.
This separation is crucial for flexibility and maintainability. If you add a new Tool — say, a Price-Drop notifier — the Planner must decide when to call it, but the Worker handles the actual execution.
AI architecture workshop at 91mobiles Bangalore office
Talvinder (Instructor): “Notice which option smells like 2015 chatbots — why would static templates break in dynamic pricing?”
Learner: “Because prices change rapidly and static scripts don't adapt.”
Talvinder (Instructor): “Exactly. If you added a Price-Drop tool to the agent, would the Planner or the Worker decide when to call it?”
Learner: “The Planner decides, since it controls flow logic.”
Talvinder (Instructor): “Right. The Worker just executes the call.”
Understanding component responsibility avoids brittle AI bots.
This pattern is not just theory. The 91mobiles content agent uses code functions like choose_action() (Planner) and execute_action() (Worker) to orchestrate content generation. This modularity lets them add new capabilities without rewriting the whole agent.
Memory systems enable personalized, persistent user journeys
Unlike a one-off FAQ bot, a modern AI-powered e-commerce assistant must remember user preferences, past interactions, and contextual signals across sessions.
There are two memory types:
- Short-term memory: Holds transient context within a session, such as the current query or recent conversation turns.
- Long-term memory: Stores persistent user data, historical preferences, and learned behaviors across sessions.
Understanding where to store each type is essential:
| Memory Type | Storage Technology | Example Use Case | Indian Context Example |
|---|---|---|---|
| Short-term | Redis (in-memory) | Session context, recent queries | Remembering Rajesh's price sensitivity during one browsing session |
| Long-term | Postgres (persistent DB) | User profiles, purchase history | Retaining Rajesh's price sensitivity over multiple visits |
Redis offers low-latency access for ephemeral data, while Postgres provides reliable persistence for data that must survive restarts and long-term analysis.
This layered memory approach lets the AI agent deliver personalized recommendations that evolve with user behavior — a competitive advantage in India's diverse e-commerce market.
Retrieval-Augmented Generation (RAG) fuses static knowledge with dynamic data
Generative AI models like GPT-4 are powerful but limited by their training data cutoff and context window size. To produce accurate, up-to-date content — such as phone comparisons or spec explanations — RAG pipelines combine a retrieval system with a language model.
The process:
- The user query triggers a search in a vector database or document store.
- Relevant documents or data points are retrieved.
- The language model generates a response grounded in the retrieved information.
For example, 91mobiles uses LlamaIndex and GPT-4 Turbo to create product comparison articles that reference the latest specs and user reviews.
This approach overcomes hallucination and factual errors common in pure LLM outputs. It also enables real-time content generation that reflects dynamic catalogs and pricing.
Technology Readiness Level (TRL) guides AI project scoping
When evaluating AI ideas, especially in startups or fast-moving enterprises, it is critical to assess whether the technology is mature enough for production.
TRL is a 9-level scale measuring the maturity of technology:
| Level | Description | Indian Startup Implication |
|---|---|---|
| 1-3 | Early research and concept | Idea stage, unproven AI model |
| 4-6 | Prototype in relevant environment | Dockerized model running on staging servers |
| 7-9 | System proven in operational environment | Live pilot with real users (e.g., 91mobiles content agent) |
Talvinder explains TRL 6 as having a prototype running in an operational environment, like their Docker-compose setup with staging traffic.
Using TRL helps your CFO and leadership understand the risk and investment needed. It prevents over-commitment to immature AI projects that are costly and unlikely to ship soon.
Scoring AI opportunities by data readiness and TRL
Beyond TRL, data readiness is a gating factor. Good AI requires clean, structured, and accessible data.
Ask yourself:
- Is the data you need available now, or will it require months of engineering effort?
- Is it clean, labeled, and reliable?
For example, 91mobiles' phone specs data is well-structured, enabling rapid AI content generation. Other companies with messy or multilingual data face a bigger challenge.
In workshops, teams score AI ideas on weighted opportunity matrices, balancing strategic fit, impact potential, TRL, and data readiness.
Quality metrics anchor AI content production
Tokens per second or model accuracy are interesting to engineers but irrelevant to users if the output is wrong or misleading.
At 91mobiles, the focus is on:
- Business relevance: Does the content help users make buying decisions?
- Factual accuracy: Are specs and comparisons correct?
- User trust: Does the AI maintain credibility?
For instance, a phone comparison article that hallucinates specs will lose user trust instantly.
Hands-on: Building a content agent for phone comparisons
In Lab 1 of the 91mobiles workshop, learners build a content agent that:
- Takes structured product specs as input.
- Generates full-length comparison articles (1000–1500 words).
- Produces SEO meta descriptions and social CTAs.
The architecture involves:
Prompt → LLM Agent → Tools (search, structure, brand voice) → Final Content
Key technologies include GPT-4 Turbo, LlamaIndex, Docker, and a custom brand voice module.
This is not a toy demo — it is a real production scaffold that ships to millions of users.
- Set up the Docker environment and load the 91mobiles product specs CSV.
- Implement the Planner/Worker pattern functions:
choose_action()andexecute_action(). - Integrate Redis for session memory and Postgres for user profiles.
- Use LlamaIndex to build a vector index of product specs.
- Query the agent with natural language questions about phones under ₹40k with specific features.
- Generate a comparison article and meta description.
- Evaluate output quality against the business relevance and accuracy rubric.
Test yourself: Evaluating an AI pilot opportunity
You are the product lead at a mid-stage Indian e-commerce startup planning to build an AI-powered product comparison feature. The engineering team estimates 3 months to build a prototype using GPT-4 API and vector search. The data team reports that product specs are only 70% cleaned and structured. The CFO wants a go/no-go decision.
The call: Do you greenlight the project now? How do you communicate the risks and next steps to leadership?
Your reasoning:
You are the product lead at a mid-stage Indian e-commerce startup planning to build an AI-powered product comparison feature. The engineering team estimates 3 months to build a prototype using GPT-4 API and vector search. The data team reports that product specs are only 70% cleaned and structured. The CFO wants a go/no-go decision.
Your task: Do you greenlight the project now? How do you communicate the risks and next steps to leadership?
your reasoning:
Where to go next
- Deepen your AI architecture understanding: AI Product Architecture Patterns
- Learn retrieval-augmented generation: RAG Fundamentals and Applications
- Master data readiness for AI: Data Strategy for AI Products
- Explore Technology Readiness Levels: TRL and AI Project Management