A 37-year-old agrochemical manufacturer with a pan-Gujarat distribution network needed more than a software upgrade — they needed an operations backbone built to handle 200+ peak-season invoices, complex commission structures across thousands of SKU variants, and real-time inventory visibility across geographically split locations.
Company: Fengle Crop Sciences Pvt. Ltd.
Location: Gondal, Gujarat
Industry: Agrochemicals — Insecticides, Fungicides, Herbicides, Fertilizers, PGR
Model: Contract manufacturing + own-label distribution
Coverage: Pan-Gujarat dealer network, field sales team
Solution: Odoo 18 Enterprise
The Challenge: When Peak Season Becomes Peak Chaos
Fengle Crop Sciences operates in a business where timing is non-negotiable. The kharif and rabi seasons compress months of sales volume into tight windows — and every operational weakness that is manageable in a quiet month becomes a full-blown crisis when 200+ invoices are flying out the door in a single week.
Before Odoo, the team was managing on spreadsheets, Tally entries, and manual cross-checks between the warehouse and the sales office. It worked — until peak season hit.
Invoice Overload
200+ invoices per peak season, each manually created and cross-checked — no automation, no batch processing.
Split Inventory Blindspot
Warehouse and sales office stock tracked in separate registers. No unified view — reps promised stock that wasn't confirmed available.
Commission Complexity
Thousands of product variants, different commission rates per SKU, per rep, per geography — calculated manually at month-end with regular disputes.
Multi-UOM Pricing Risk
Products sold in ml, litres, grams, and kilograms — often on the same order. Manual unit conversion created constant pricing error risk.
Order vs Billed Gap
No system to reconcile ordered vs dispatched vs billed quantities. Over-billing and under-billing discovered only after dealer disputes arose.
No Rep Accountability
No visibility into individual rep performance by territory, product, or collection — incentive planning was based on gut feel, not data.
💡 What made this hard: Agrochemical distribution in Gujarat isn't just seasonal — it's hyper-local. The same product ships in five different pack sizes to five different dealer types, each with different credit terms and different commission structures. Generic ERP configuration doesn't solve this. It required a context-aware implementation built around how the business actually operates.
The Odoo Implementation: What We Built
Tatvamasi Labs implemented Odoo 17 Enterprise across Fengle's operations. The scope combined standard module configuration with targeted custom development for the commission engine and the order-billing reconciliation layer.
Modules Deployed
- ✓Sales & Order Management
- ✓Inventory (Multi-Location & Multi-Warehouse)
- ✓Invoicing & Accounting (GST-compliant)
- ✓Purchase Management
- ✓CRM (Sales Team & Territory Tracking)
- ✓Custom Commission Module
Custom Development
- ✓SKU-level commission engine with variant & territory support
- ✓Multi-UOM pricing (ml/L/g/kg) with auto-conversion
- ✓Order vs delivery vs billing reconciliation dashboard
- ✓Territory-wise rep performance reports
- ✓Peak season batch invoice processing workflow
- ✓Warehouse ↔ sales office stock transfer with approval flow
How Each Problem Was Solved
01 — Peak Season Invoice Volume
We configured Odoo's Sales module with batch order confirmation and automated invoice generation triggered on delivery validation. Orders confirmed by the sales team now flow directly into picking, dispatch, and invoice creation — no re-entry of data at any stage. The accounts team moved from spending 3–4 hours per day creating invoices during season to reviewing and approving a queue — a shift from data entry to oversight.
02 — Real-Time Inventory Across Locations
Fengle's Gondal warehouse and the sales office now exist as distinct locations within Odoo's multi-warehouse inventory framework. Stock movement between them follows an internal transfer workflow with approval. The consolidated inventory dashboard shows unified, live stock across both sites. Sales reps check availability before committing to a dealer — eliminating the back-and-forth calls that were consuming 30–45 minutes per rep per day.
03 — Order vs Delivery vs Billing Reconciliation
We built a custom reconciliation dashboard that surfaces, for every sales order, the ordered quantity, quantity delivered, and quantity billed — with automatic flags for any mismatch. The system blocks invoice creation where delivery is incomplete, and requires sign-off on partial delivery scenarios before billing proceeds.
💡 Outcome: In the first complete peak season after go-live, Fengle reported zero billing dispute incidents with dealers — a first in the company's recent operating history.
04 — Commission Engine for Thousands of Variants
Fengle's product catalogue spans hundreds of SKUs across five categories, each with multiple pack sizes. Commission rates vary by product, pack size, rep, and dealer tier. We built a custom commission configuration layer within Odoo's sales framework — rules are set once per variant and applied automatically at order confirmation. Month-end commission statements now generate automatically, broken down by rep, product, and territory, ready for payroll processing in minutes instead of days.
05 — Multi-UOM Pricing Without Errors
Agrochemicals ship in combinations of weight and volume — 100ml, 250ml, 500ml, and 1L packs of the same active ingredient, each with its own price point anchored to a base unit. We configured Odoo's Units of Measure system with Fengle's specific UOM categories and conversion factors. Sales reps select the pack size; the system prices it correctly, every time, without manual calculation.
Running a distribution or manufacturing business with seasonal peaks?
Book a free discovery call — we'll map your exact challenges to a configured Odoo solution, not a generic demo.
The Results: One Full Season Later
The real test of any ERP implementation in an agricultural business isn't the go-live. It's the first peak season. Fengle went into their next crop season with Odoo fully live — and came out with a qualitatively different experience of running the business.
| Area | Before Odoo | After Odoo |
|---|---|---|
| Invoice creation (peak season) | Manual, 3–4 hrs/day | Auto-triggered on delivery |
| Stock visibility | Siloed per location, delayed | Unified real-time dashboard |
| Dealer billing disputes | Recurring every season | Zero incidents post go-live |
| Commission calculation | Manual month-end, error-prone | Auto per SKU/rep, same day |
| UOM pricing accuracy | Manual conversion, high risk | System-enforced, zero errors |
| Management reporting | Weekly Excel summaries | Live dashboards, always on |
What This Implementation Demonstrates
Fengle Crop Sciences didn't need more software. They needed the right software, configured by people who understood the operational realities of agrochemical distribution in Gujarat. The challenges they faced — seasonal invoice spikes, split inventory, complex commission structures, multi-UOM pricing — are not unique to Fengle. Any agri-input distributor or manufacturer with a field sales team and a seasonal demand cycle will recognise them.
What Odoo provided — with the right implementation partner — was a single system of record where every order, delivery, invoice, and commission calculation is connected. The business stopped running on tribal knowledge and started running on data.
For a 37-year-old business entering its next chapter of growth, that's not a small thing.
If you run an agrochemical, FMCG, or distribution business with seasonal demand peaks, a field sales team on commission, and products in multiple pack sizes — your operational challenges are almost certainly the ones Fengle just solved. The implementation playbook exists. The question is when.
Frequently Asked Questions
Prefer a quick chat? WhatsApp our team — we respond within the hour.
💬 Chat on WhatsApp