Location/Region: Ahmedabad, GJ, India
Industry: Manufacturing & Supply of Valves, Pipe Fittings & Irrigation Products
Scope implemented: Sales, Purchase, Inventory, Dispatch, Invoicing, 3r-Party Integerations
Software Replaced: Tally Prime
Version: Odoo v19 Enterprise
Summary
Kranti Polytech Pvt. Ltd. is an Ahmedabad-based manufacturer and supplier of polypropylene and HDPE products, including ISI foot valves, non-return valves, air valves, ball valves, taps, pipe fittings, hose fittings, and products for agriculture, irrigation and domestic applications.
For years, the company relied on Tally to manage its sales and accounting processes. While the system had supported the business, the sales-order workflow had gradually become a source of friction.
The business needed more flexibility in how sales orders were created, what information was captured, improve visibility into quantities and units of measure, and how sales orders connected with inventory, dispatch and invoicing.
The company had also recognized a larger limitation: as its operations evolved, it needed an ERP platform capable of supporting additional business functions in the future rather than continuing to work around the limitations of an accounting-focused system.
The company initially began its Odoo implementation with another partner. However, the implementation did not meet its expectations, and Kranti Polytech subsequently approached Areterix Technologies to take over the project and deliver a solution aligned with its actual operational requirements.
Areterix redesigned the core operational workflow in Odoo while retaining Tally temporarily for accounting. The result was a connected workflow covering Sales, Inventory, Dispatch, Invoicing and statutory documentation, with additional integrations and workflow improvements built around the company's day-to-day operations.
The Challenge
1. A Sales Process That Required Too Many Workarounds
Tally was capable of handling the company's sales transactions, but the standard sales-order process did not provide the flexibility the business needed.
Over time, users had developed ways to work around these limitations, but the underlying friction remained.
The business needed to capture additional information directly within the sales order, improve visibility into quantities and units of measure, manage transporter information, customize documents and reduce repetitive steps in the order-to-dispatch process.
The challenge was therefore not simply that the existing system "didn't work."
It worked but the business had to keep adjusting its processes around the system.
Kranti Polytech wanted to move to a platform where the ERP could instead be configured around the way the business actually operated.
2. Preparing for the Next Stage of Growth
The need for change extended beyond the sales workflow.
As a manufacturing and supply business, Kranti Polytech needed an ERP platform that could eventually connect sales and inventory with other operational functions as the business grows.
Manufacturing was not part of the current implementation, but scalability was an important consideration when selecting the new platform.
The objective was to establish Odoo as the operational foundation that could be expanded in the future, rather than continuing to build the business around the limitations of its existing accounting system.
3. Recovering an Unsuccessful Odoo Implementation
The company had already started its transition to Odoo with another implementation partner.
However, the initial implementation did not deliver the expected experience, and the company decided to approach Areterix.
This meant the project was not simply a fresh ERP implementation. Areterix first had to understand the company's actual requirements, identify where the existing approach was falling short, and then build the workflows accordingly.
The Solution
Areterix implemented Odoo 19 Enterprise as the company's operational ERP, focusing initially on the complete sales-to-dispatch cycle.
The core workflow was structured around:
Rather than relying entirely on standard screens and reports, Odoo was configured and customized wherever the company's operational requirements demanded additional flexibility.
1. Sales Orders Adapted to the Business
The Sales Order became the central point for capturing the information required to process each customer order.
Transporter Management
Transporter information was incorporated directly into the customer and sales-order workflow.
- A default transporter can be configured at the customer level.
- The transporter can be changed directly on an individual Sales Order when required.
- This avoids repeatedly entering transporter information for regular customers while still allowing flexibility for individual orders.
Product Quantities & Packaging
Kranti Polytech required greater visibility into how products were ordered and dispatched.
The Sales Order workflow was adapted to support:
- Units
- Packages
- Package quantities
- Package-level visibility on individual order lines
This gives users a clearer view of how the order is structured before it moves into delivery and dispatch.
Additional Order Information
Several additional pieces of information were incorporated into Sales Orders, including:
- Serial number information
- Additional business-specific fields
- Discount visibility
- Additional information required on printed Sales Orders
The objective was to keep relevant information within the transaction itself instead of forcing users to maintain separate references or workarounds.
2. Customized Documents for Sales & Dispatch
Standard ERP documents don't always match the practical requirements of a business.
For Kranti Polytech, the relevant documents were customized so that users see the information they actually need while unnecessary information is removed.
Customized documents included:
- Sales Orders
- Customer Invoices
- Delivery Slips
- Picking Slips
- E-Invoices
- E-Way Bills
- Barcode Labels
Both the information displayed and the print layouts were adapted to the company's requirements.
This ensured that the digital transaction and the physical documentation used by the teams followed the same operational process.
3. Reducing Clicks in Workflows
Small workflow improvements can make a meaningful difference when a process is repeated throughout the day.
Additional actions were introduced for frequently performed activities.
For example, users can access the required E-Invoice and E-Way Bill printing actions together, reducing unnecessary navigation between screens.
These changes were designed around a simple principle:
If a task is performed repeatedly, the system should make it as direct as possible.
5. WhatsApp Integration for Customer & Vendor Communication
Communication around orders and transactions was another area where the ERP workflow was extended beyond standard Odoo functionality.
Odoo was integrated with the WhatsApp API to allow the team to communicate with customers and vendors directly from the business workflow.
Depending on the transaction, users can share relevant updates and documents related to:
- Sales Orders
- Order status and updates
- Payment-related information
- Dispatch updates
- Builty images and transport documents
- Account ledgers
- Other transaction-related information
This reduces the need to manually download documents, switch between systems and compose repetitive messages for every transaction.
WhatsApp becomes an extension of the ERP workflow, allowing the team to communicate important business information while keeping the underlying transaction within Odoo.
The result is a more connected workflow:
This was particularly useful for reducing small but repetitive communication tasks that occur throughout the sales, accounts and dispatch processes.
6. Odoo–Tally Integration
Kranti Polytech did not need to make a complete accounting-system switch on day one.
As a transitional approach, the company continues to maintain its core accounting functionality in Tally while using Odoo for its operational processes.
Areterix integrated Odoo with Tally so that relevant sales and purchase data can be transferred from Odoo to Tally for accounting purposes.
This allowed the company to separate the operational and accounting transition:
This approach allowed Kranti Polytech to modernize its operational workflows without forcing an immediate replacement of its existing accounting system.
The Result
The implementation gave Kranti Polytech a more flexible operational system for managing its sales and dispatch processes.
Instead of continuously adapting its workflow to the constraints of Tally, the company now has an Odoo-based process designed around its own requirements.
The current implementation provides:
- A structured Sales Order workflow
- Customer-level and order-level transporter management
- Unit and package-based quantity visibility
- Customized Sales Order and invoice formats
- Customized delivery and picking documentation
- E-Invoice and E-Way Bill workflows
- Reduced clicks for repetitive activities
- Custom barcode labels for receipts and deliveries
- WhatsApp-based Builty handling
- Connected Sales, Inventory and Dispatch processes
- Odoo–Tally integration for the transitional accounting setup
Most importantly, the company now has an ERP platform that can evolve with its operations.
The current implementation focuses on Sales, Inventory, Dispatch and Invoicing. As the business grows and additional functions become relevant, Odoo provides a platform on which those processes can be progressively added rather than requiring the company to redesign its core system again.
Odoo Partner in Ahmedabad | Odoo for Plastic Manufacturer | Odoo for Manufacturing | Tally to Odoo | Odoo 19 | Odoo Partner in India | Odoo ERP | Odoo 20 | Odoo for Distributors | Odoo for Wholesalers