ERPNext Jewellery Management Suite

ECOSIRE builds a proper Frappe app (its own module, DocTypes, hooks, and permissions) that layers karat-aware pricing on top of ERPNext instead of fighting it. We add custom fields and child tables to Item and Sales Invoice for purity_karat, gross_weight, net_weight, stone_weight, and wastage_percent, and introduce a Gold Rate DocType plus a Metal Rate Card that drives billing. A hooks.py doc_events handler recomputes line value on Sales Invoice and Quotation validate/before_save — metal value = net weight x current karat rate, making charge applied as flat-per-gram or percentage, wastage added on gross, then taxes — so the amount a customer sees is always derived, never hand-typed. Client Scripts give counter staff live recalculation as they change weight or karat on the form, and a role profile ("Jewellery Counter", "Jewellery Manager") keeps rate-card edits away from the sales floor.

Live gold-rate handling is wired for how a shop actually opens each morning. A scheduler event (scheduler_events in hooks.py) can pull your day rate from an internal source or an external feed and stamp a dated Gold Rate record, and whitelisted REST methods (@frappe.whitelist()) let a tablet or your website read the current rate and post a locked quote. Old-gold exchange is modelled as a first-class flow: a child table captures each returned item's weight, tested purity, and agreed rate, values it against today's card, and settles it against the invoice as a metal-credit line with a full audit trail — so the melt value, the deduction, and the net payable all reconcile inside ERPNext rather than on a calculator. Hallmarking (HUID / BIS) and certificate numbers are captured per item and printed on invoices and tags via custom Print Formats.

Because this is build-to-order, you are not downloading a generic marketplace app and hoping it fits. After a short scoping call we confirm exactly which flows you need — karat set, rate source, making-charge rules, tax treatment, old-gold policy, label/tag formats — then build your version, test it on a staging bench, run UAT with your team, and deploy to your Frappe/ERPNext v15 or v16 site. Typical delivery is 2-4 weeks from confirmed scope. You receive the installable source, a git repository, technical and user documentation, a training session, and a post-go-live support window. No fabricated benchmarks, no instant-download claim — a real app, built for your shop and handed over cleanly.