Jewelry Store Management (POS + Inventory)

We build a dedicated Odoo module that models jewelry the way the trade actually works. New models extend product.template with fields for metal_type (gold/silver/platinum), karat, gross_weight, net_weight, stone_weight and stone_value, and a making_charge that can be configured per-gram, as a percentage, or fixed. A metal.rate model holds the daily rate per metal and purity, and a computed field on the sale line uses @api.depends('product_id', 'quantity', 'metal_rate_id') so that the ornament's price is derived at the moment of sale — never stale, always tied to the rate the counter staff confirmed. Making and wastage charges layer on top through the same compute chain, and everything flows into a QWeb invoice/tag report that itemizes metal value, making, wastage, stones and tax so the customer sees exactly what they are paying for.

Around that pricing core we build the retail workflow: a POS screen (extending Odoo's Point of Sale) that lets counter staff scan or select an ornament, confirm the live rate, and complete a sale with the correct breakdown printed on the receipt; hallmark and certificate tracking with the assay/hallmark number and lab certificate ID stored against each piece (and surfaced on reports and the customer record); and an old-gold exchange and buyback flow that weighs and values returned scrap by karat, generates a purchase/credit document, and nets it against the new sale. Access is locked down with ir.model.access.csv plus record rules so counter staff, valuers and managers see only what their role permits, and optional automated actions can push a daily rate update or flag pieces awaiting hallmarking. Where you need external price feeds or accounting sync, we expose the data over Odoo's XML-RPC/JSON-RPC API rather than bolting on brittle scripts.

Because this is a build-to-order product, you are not downloading a generic app and forcing your showroom into it. After a short scoping call we confirm your exact requirements — metals and purities you deal in, how you compute making and wastage, your hallmark/certificate rules, POS hardware, and whether you are on Odoo Community or Enterprise — and produce a fixed scope. We build against your target version (Odoo 17.0, 18.0 or 19.0), test on a staging database with your own sample catalog, run UAT with your team, and only then install on production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, and you receive the full installable source and a git repository so the module is yours to keep and extend.