In many Indian distribution businesses, operational complexity grows silently. What starts as a small and manageable process gradually becomes difficult to control as customer volumes increase, communication channels multiply, and teams expand. Businesses often continue operating using familiar tools like WhatsApp, SMS, phone calls at best emails. There is rarely an e-commerce websites integrated to an ERP or even a CRM at the back end. Often there is one person transferring the information from these digital channels to a diary and then to Tally.
It is not how the businesses want the system to be but it is how the market operates. Orders are given at the store / retail level rather than at a corporate level where the senior executives sit to make purchasing decisions. The seller, in such situation, has limited influence to challenge the customer’s choice of channel to place their order.
WhatsApp vs ERP
This was the exact situation faced by a growing food distribution business led by Mr. Pinaki Sharma (name changed). The company was handling orders from nearly 20–25 companies totaling 45 orders every day mostly on WhatsApp. Alongside WhatsApp, customer orders also arrived through emails and phone calls. Although business demand was steadily increasing, the internal process for managing these orders remained largely manual.
Over time, the business realized that operational efficiency was declining even while revenues were growing. This led Mr. Sharma to look for a digital solution in the market. His requirement was very clear to him and he shared it very eloquently.
- He wanted the system to read all messages received on WhatsApp, consolidate and prepare sales order.
- Give his customer to place order from a customized portal to streamline the ordering process.
- Once the order was fulfilled; Tally should capture the transaction details through integration with the proposed system.
His main requirement was that he wanted a ‘system’ to read all the messages received on WhatsApp. Then it should extract all order related messages and consolidate them into sales order. The system should also be able to read images and audio messages. He didn’t want to miss even a single order. Currently this process was dependent on one of his employees. Once the order is captured then relevant team members will take lead and fulfill the process on the system.
Phased ERP roll out suggested
To address these challenges, the software vendor proposed implementing a phased digital transformation approach using Odoo. Instead of attempting a full ERP rollout immediately, the recommendation was to begin with core operational areas that would deliver immediate value without overwhelming the existing team.
The initial focus areas included WhatsApp integration with Odoo’s internal messaging app called Discuss, CRM and further workflows through Odoo’s integrated modules like Inventory and Accounting etc.
This phased approach was important because the organization was already deeply dependent on workflows built around WhatsApp and Tally. A sudden large-scale ERP implementation could have created resistance within the team and disrupted ongoing operations.
Integrating WhatsApp Into Business Operations
One of the primary objectives was to consolidate customer communication into a single system.
The proposed platform would centralize WhatsApp orders, email-based communication, customer follow-ups, and internal coordination into a unified CRM dashboard.
This would reduce the need for employees to manually forward messages across departments. Instead of relying on scattered conversations, operational teams would gain visibility into all ongoing customer interactions from one centralized interface. The business would benefit from improved tracking, reduced duplication of work, and better accountability across teams.
The proposed solution required the customer to use ‘/lead’ command to enter the order directly into its CRM from the Discuss app that would be integrated with WhatsApp API. To an outsider this would seem simple and straight forward but it didn’t solve the customer’s ‘real’ problem. He still had to depend on somebody to manually capture the order by entering the command and he was RIGHT.
Can AI bridge the Requirement Gap
The most significant insight from the discussions emerged around the topic of automation.
Mr. Sharma’s expectation was straightforward and understandable. The business wanted the entire order consolidation process to become automated. From a business owner’s perspective, this expectation made perfect sense. If customer orders were already arriving digitally through WhatsApp and email, why should employees still spend hours manually reviewing and consolidating them?
However, the software vendor clarified an important operational reality. In real-world distribution businesses, customer communication is rarely structured enough for complete automation.
Not every WhatsApp message represents an order. Conversations often include greetings, delivery updates, clarifications, product inquiries, corrections, quantity adjustments, and partial information.
Similarly, email inboxes contain promotional emails, spam, follow-up conversations, and non-order communication mixed together with actual business orders. Because of this complexity, human validation still remains necessary.
This became the central gap between the customer’s expectation and practical implementation reality.
The customer hoped for end-to-end automation, while the proposed system could realistically deliver structured workflows, improved visibility, reduced manual effort, and partial automation.
It was a classical Agentic AI use-case currently being prototyped in large corporates. The scheduler would run Agents to read all WhatsApp messages for the day or perform the exercise every time a message was received. If the message was an image, it would apply OCR (Optical Character Recognition) to extract information. This information would be passed to another Agent who would make the entry in the CRM. No humans involved and hence no human error.
A Custom Ordering Experience for Repeat Customers
Another important requirement discussed during the meetings was the need for a simpler ordering experience for repeat buyers. The customer wanted regular clients to place orders more easily without repeatedly sending manual WhatsApp messages.
To address this, a custom customer ordering portal was proposed.
Customers would be able to log in, view products relevant to them, access purchase history, modify quantities, and place repeat orders quickly. The portal would also allow the business to display only customer-specific products while highlighting frequently ordered items.
Features such as favorites, repeat ordering, and customer-specific product visibility were intended to simplify the ordering experience while reducing communication dependency on WhatsApp.
Why Full Automation Remains Difficult
Many businesses today assume that AI can instantly automate entire operations. In practice, distribution businesses deal with highly unstructured communication environments. Orders may arrive in multiple languages. Customers may send voice notes instead of typed messages. Quantities may be corrected across several messages. Orders may be edited at the last moment. Some customers communicate informally without following consistent formats.
In such situations, automation becomes significantly more difficult and costly than it appears. Without advanced AI agents trained specifically for the business and its customer behavior patterns, human review remains essential. Exception handling still requires supervision. Workflow validation cannot yet be fully eliminated.
This does not mean automation fails. It simply means automation must evolve gradually and responsibly.
Businesses often achieve the best results when they first standardize workflows, centralize communication, and improve visibility before attempting deeper AI-driven automation.
Automation has to be seen from the lens of trade-off.
- Human Error Vs AI Hallucination
- Cost Vs Economy of scale
The Practical Way Forward
The discussions highlighted a realistic and practical approach that many SMEs can learn from. Instead of chasing complete automation immediately, businesses should focus first on operational structure.
For Mr. Sharma’s business, the ideal next step would be a phased transformation journey:
- First, centralize communication and order tracking.
- Second, standardize workflows across teams.
- Third, gradually move repeat customers toward structured ordering portals.
- Finally, introduce AI-assisted automation selectively in areas where data becomes more structured over time.
This phased approach reduces implementation risk while allowing employees and customers to adapt gradually. The journey from WhatsApp chaos to structured order management is not a single technology project. It is an operational transformation process.
In the end out of his 3 requirements, Odoo was solving 2 and here’s how.
- He wanted the system to read all messages received on WhatsApp, consolidate and prepare sales order. - Integration was possible but understanding the context of the message and entering with a simple command was still manual.
- Give his customer to place order from a customized portal to streamline the ordering process. - This requirement could be delivered 100%.
- Once the order was fulfilled; Tally should capture the transaction details through integration with the proposed system. - Integrations between Odoo and Tally is possible but does the cost and effort justify it for the business of this size.
Share your thoughts in the comments below.