Jewellery retailers, bullion dealers, and gold manufacturers run on a pricing model ERPNext core was never designed for. A ring's sale price is not a fixed rate — it is (metal weight × today's karat-adjusted gold rate) + making charges + wastage + stone value + applicable tax, recomputed the moment the daily rate moves. ERPNext's stock Item carries a single standard_rate, valuation runs on FIFO/moving-average cost, and there is no native concept of purity (22K vs 18K), touch/wastage percentages, making-charge schemes, or old-gold trade-in against a new purchase. Teams end up maintaining rates in spreadsheets and hand-keying prices into the POS, which drifts the instant the market ticks.

ECOSIRE builds a dedicated Frappe app — installed into your ERPNext bench, not a bolt-on spreadsheet — that models the jewellery trade as first-class DocTypes. We extend the Item master with karat, fineness/purity (e.g. 916 for 22K), net metal weight, gross weight, and stone weight fields, and add a Metal Rate DocType holding the daily buy/sell rate per metal and karat. A hooks.py doc event on Quotation, Sales Order, Sales Invoice, and POS Invoice fires a server script that resolves the live rate, applies your making-charge scheme (flat per-gram, percentage, or fixed per-piece) and wastage percentage, and writes the computed line rate back before the document is saved — so the printed price always matches the market. A Making Charge Scheme DocType lets you version schemes by item group, karat, and customer tier without touching code.

Old-gold exchange and buyback are handled as their own transactional flow: an Old Gold Receipt DocType captures the returned item's weight, assessed purity, and deduction, converts it to a metal-value credit at the day's buy rate, and links it to the outgoing Sales Invoice so the customer nets only the difference — with the returned metal booked into a scrap/melt warehouse for reconciliation. Hallmarking and certification are tracked per piece: Hallmark Certificate records the HUID/assay-centre reference, purity grade, and issue date, enforced by permission-scoped role profiles (Sales, Cashier, Valuer, Manager) so only authorised roles can override rates or approve buybacks. A scheduler event pulls or prompts the daily rate, and everything is reachable over the Frappe REST API and whitelisted methods for your POS front-end, price-board display, or e-commerce catalogue. Client scripts add karat/weight validation and live price preview inside the desk forms.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, produce a written specification of DocTypes, rate logic, making-charge rules, and integrations, then build on a staging bench, run UAT with your real rate sheets and item catalogue, and only then install into production. Typical delivery is 2–4 weeks from confirmed scope, targeting Frappe/ERPNext v15 and v16. You receive the full source app and git repository so you are never locked to us.