Repeated product questions
Customers regularly need product lists, prices, stock information, delivery details, and basic product answers that should not require manual replies every time.
This WhatsApp ecommerce automation for product questions and orders was built for a confidential retailer that needed a faster way to handle repetitive product questions and turn customer conversations into structured orders while keeping predictable business logic in control.
The goal was not to build a chatbot that sends every message to AI. The goal was to automate repeatable customer-service and order steps while keeping the conversation practical and controlled.
Customers regularly need product lists, prices, stock information, delivery details, and basic product answers that should not require manual replies every time.
The system needed to remember selected products and the current conversation stage so customers could continue naturally across multiple messages.
Order details had to be collected, totals calculated, records saved, the customer confirmed, and the business owner notified without manually copying the same information between tools.
The workflow uses Meta WhatsApp Cloud API and n8n as the automation layer, with product data, session memory, AI routing, order storage, and notifications connected behind the conversation.
Meta sends the customer message to the n8n webhook. The workflow normalizes supported message types and filters delivery/read callbacks that should not be processed as customer requests.
Greetings, product menus, product selection, price, stock, and other structured questions can be answered from store data without making an unnecessary AI call.
Recommendation, comparison, and natural-language questions can be routed to OpenAI with controlled product context rather than unrestricted business data.
When the customer decides to buy, the conversation collects the required order information, calculates the payable amount, and saves the confirmed order in Google Sheets.
The customer can receive a WhatsApp confirmation and email while the business owner receives an automated new-order alert.
Each part has a clear job so AI does not replace predictable business logic unnecessarily.
Product names, descriptions, prices, stock status, delivery estimates, and notes are available to the workflow for structured answers.
The workflow can retain the selected product, conversation stage, and order details needed to continue a multi-message interaction.
A decision layer determines whether the request needs AI. Straightforward store questions remain deterministic; recommendations and comparisons can use OpenAI.
Confirmed orders are stored in Google Sheets, followed by customer confirmation and an automated business-owner alert.
The case study uses functional outcomes from the implemented system rather than invented conversion percentages or sales claims.
A customer greeting displayed the product menu, and selecting a product returned its price, stock, delivery estimate, description, and ordering instructions.
A recommendation question such as which product was suitable for university use was identified as a reasoning request and routed to AI using the available store data.
One successful test created a Wireless Mouse order at Rs. 1,999 plus Rs. 200 delivery, saved the Rs. 2,199 total to the order flow, and triggered WhatsApp, customer-email, and owner notifications.
The project included Meta webhook verification, WhatsApp Business configuration, API permissions, event subscriptions, and troubleshooting the difference between real customer messages and WhatsApp status callbacks.
Webhook subscriptions, access configuration, and production WhatsApp events had to be connected correctly before incoming messages could reach n8n.
The workflow distinguishes customer messages from delivery and read-status callbacks so irrelevant Meta events do not trigger the customer-response logic.
A stale-session edge case was identified during testing, showing why conversation-state handling needs continued validation as the automation evolves.
The production system combines n8n, Meta WhatsApp Cloud API, OpenAI, Google Sheets, Gmail, JavaScript, webhooks, and HTTP/API integrations.
The client identity is intentionally anonymized, but the project architecture and functional testing described here come from the real implementation.
Yes. This was built as a production automation system for an e-commerce retailer. The client name and private customer information are withheld from the public case study.
No. Predictable requests such as product menus, selections, prices, and stock information use business logic and structured data. AI is used mainly when recommendations, comparisons, or natural-language reasoning are useful.
The implemented flow can save the confirmed order in Google Sheets, send the customer a WhatsApp confirmation and email, and notify the business owner about the new order.
CodelyHub can map your product or service data, customer conversation flow, order or lead process, notifications, and AI requirements into a practical automation system.
Tell us what customers repeatedly ask on WhatsApp, what information your team handles manually, and what should happen after a lead or order is confirmed.