On June 17, 2026, the Goods and Services Tax Network issued Advisory No. 664. This advisory outlines changes to the e-Invoice API, the e-Way Bill by IRN API, and a new optional e-Way Bill closure feature.Â
Out-of-the-box, Odoo is built to track inventory in kilograms, pieces, and standard units of measure. That works well for most manufacturing sectors. It falls short the moment you’re running a diamond or jewelry unit, where a single lot can carry a twelve-times value swing depending on whether it’s natural or lab-grown, and where yield has to be tracked to the milligram, not the gram.
The real question for a factory director or IT head evaluating Odoo isn’t “can it handle diamond manufacturing” -it’s “what does it actually take to make it handle diamond manufacturing.” The honest answer is that the base platform gets you most of the way there -strong lot tracking, configurable work centers, flexible warehouse routing -and a properly scoped customization layer does the rest.
Here’s how that layer would typically come together, module by module.
Odoo’s native stock.lot model tracks a lot number, a quantity, and a handful of standard fields -enough for most industries, not enough for a stone that needs to carry its 4Cs (cut, color, clarity, carat), a linked GIA or IGI certificate reference, and a clear flag for whether it’s CVD-grown, HPHT-grown, or natural.
The customization here is straightforward in principle: extend stock.lot with a custom model layer that adds these fields directly to the lot record, so every downstream document -internal transfers, manufacturing orders, delivery orders, invoices -inherits that data automatically instead of relying on a parallel spreadsheet.
Once this extension is in place, a lot isn’t just a quantity anymore -it’s a stone with a full identity, and every module downstream can act on that identity.
defines expected inputs, a work order records what actually happened, and the system tells you if the two matched. That premise holds for diamond production -the tuning is in how precisely you define “what actually happened.”
For a diamond unit, that means configuring separate work centers for each meaningful stage of the process -Sawing, Bruting, Polishing, Faceting, Grading -rather than one generic “Production” step. Each work center is set up with:
To illustrate what that looks like in practice: a manufacturing order wouldn’t just tell you “the batch is complete” -it would tell you “the batch completed at 94.2% of expected yield,” with the shortfall flagged as an exception the moment it’s recorded, rather than surfacing three weeks later during a cost review.
This is where the lot-level category flag from step one and the work-center configuration from step two come together inside Odoo’s Warehouse Management.
Standard Odoo warehouse routing lets you define locations, routes, and putaway rules. For a diamond operation, those routes get built around the category flag rather than a generic product category:
This turns segregation from a floor-level discipline -reliant on training, attention, and a good day -into a system-level constraint that doesn’t depend on any of those things.
None of this is exotic from an Odoo architecture standpoint -extending models, configuring work centers, building routing rules are all standard capabilities of the platform. What matters is whether the partner configuring it takes the time to understand diamond manufacturing well enough to model the right fields, the right stages, and the right constraints in the first place. A generic Odoo rollout will give you inventory tracking. A rollout scoped around how a stone actually moves from rough to polished, and how a karigar’s job-work ledger actually gets reconciled, is what protects your margin.
That’s the distinction worth asking about when you’re evaluating implementation partners -not just whether they know Odoo, but whether they’re willing to go deep enough into your process to configure it for an industry where a rounding error is a customer relationship, and a wrong vault transfer is a compliance incident.
Model extensions, work-centre configuration, and segregation-aware routing rules are core to how we approach Odoo development and customisation at Greytrix Business Solutions, and the pattern above is exactly how we’d scope this kind of build for a diamond or jewelry manufacturing unit. We’ll be talking through more of this hands-on, in person, in the weeks ahead.
If you’re a CTO, IT head, or factory director currently evaluating what an Odoo implementation would actually look like for your operation, reach out to Greytrix Business Solutions for a technical scoping session. We’ll walk through your specific production stages and show you exactly where the platform needs to be extended -and where it already does the job.
This piece is mostly Odoo platform/technical content, so only one factual claim traces back to external sourcing -the ~12x per-carat price gap between lab-grown and natural diamonds referenced in the opening paragraph:
