Overview
Kankriya Enterprises Pvt Ltd is a manufacturing and distribution company with operations spread across multiple locations.
The business deals in roll-based material manufacturing, covering everything from raw material procurement through to production, quality checks, and final dispatch.
It's a detailed, process-heavy operation, and over the years, Kankriya built a solid reputation for precision and reliability in its field.
But as the business kept growing, the systems holding everything together started showing their age, and the cracks became harder to ignore.
The Problem
For over 15 years, Kankriya had been running on a custom-built software system. In its time, it did the job. But by the time the team reached out to GSUS, that system had become a real bottleneck.
- The most consistent complaint was speed; the software was slow, not occasionally, but every single day, and it was starting to affect how work actually got done. Dig a little deeper, and the speed problem was only part of the story. Business data was scattered across too many places.
- Production tracking lived in Excel. Spare inventory for maintenance was logged by hand. Bank reconciliation was done manually.
- Attendance records had to be downloaded from a biometric device and uploaded separately into a payroll tool. Lead management was yet another spreadsheet.
- Nothing connected to anything else. Every department was working in its own silo, piecing together information from wherever it happened to live that day.
- When Kankriya came to GSUS looking for a solution, they had one non-negotiable condition: They needed speed, and they needed continuity.
Our Approach
Before anything else, the GSUS team took time to properly understand how Kankriya actually works, not just on paper, but on the ground.
That meant mapping out the full operational flow: how purchase requests come in, how materials move through production, how quality is checked, how rolls get allocated to orders, and how everything finally makes it out to the customer.
The existing legacy system was reviewed carefully. The data structures, the business logic, and the workflows had been built around, and all of it was documented so nothing would be missed or misunderstood during the transition.
Everything that came out of that process was compiled into a detailed Business Requirement Document, covering the core modules the new system would need to handle. That document was reviewed and signed off by both sides before a single line of implementation began.
The Solution: Odoo ERP
After understanding the full picture, GSUS proposed Odoo as the platform to bring all of Kankriya's operations under one roof. The reason Odoo made sense here wasn't just features; it was flexibility.
- A business as operationally specific as Kankriya couldn't be forced into a generic setup. Odoo's modular structure made it possible to configure exactly what was needed and build targeted customizations where the standard features didn't quite reach.
- A business as operationally specific as Kankriya couldn't be forced into a generic setup. Odoo's modular structure made it possible to configure exactly what was needed and build targeted customizations where the standard features didn't quite reach.
- Wherever standard Odoo functionality covered the requirement, it was used as-is. Where gaps existed, and with a business this specific, there were a few- GSUS built the customizations needed to make sure nothing was compromised.
Solution Implementation
The rollout followed a phased approach, prioritized around what Kankriya needed most urgently.
Each module was built, configured, and handed to the Kankriya team for real-world testing before the next one was touched. When something didn't feel right or needed adjusting, it was caught and corrected before moving forward.
That back-and-forth was intentional; with an operation this detailed, getting it right mattered more than getting it done quickly.
Key customizations were developed in close collaboration with the teams who would actually be using them day to day, so the final system felt like it was built for Kankriya, not like a generic tool they had to work around.
Customer Impact
From the day the system went live, the difference was obvious. The sluggishness that had plagued daily operations was gone. But beyond speed, what Kankriya gained was something more valuable, visibility.
- Production teams could finally trace every roll from the moment it arrived to the moment it left for the customer. Warehouse staff had the information they needed, generated automatically, reducing errors on the floor.
- HR moved from a messy manual attendance process to a fully automated payroll cycle with compliance built in. And management could pull up real-time reports across sales, purchase, production, and finance from one place.