Claude vs ChatGPT for developers: lessons from real ERP builds
Claude or ChatGPT? A working developer's comparison, including how we built X3 Retail ERP with parallel Claude Code agents that learn from their own mistakes.
Read articleClient project · ERP
A jewellery ERP that tracks every gram and karat through purchasing, karigar production, multi-branch stock and live gold-rate sales.

Generic inventory software can't track what matters in jewellery across branches: weight, purity, production stages and consignment. A piece is not just a quantity on a shelf. It starts as gold of a certain karat, goes out to a karigar, comes back as finished jewellery with a different weight, and may sit in another branch or with a consignment partner before it is sold at that day's gold rate. Tracking this in spreadsheets and generic stock tools left gaps between branches, made it hard to know where metal actually was, and stock queries were slow once the item count grew.
An ERP built around jewellery operations: weight and purity tracking, production stages, consignment management, sales, and fast stock queries backed by Redis caching. Every item carries its weight and karat from purchase onwards, so purchasing, karigar issue and receipt, branch transfers and sales all work in grams and purity rather than plain units. Production is tracked stage by stage, consignment stock stays visible even when it is outside the shop, and sales are priced against the live gold rate. The system is a Next.js front end on a NestJS and PostgreSQL back end, with Redis caching the stock reads that staff run all day. Role-based access keeps each branch and each person to the screens they need. It is live at ophir.eaquirstech.com.
Eaquirs Tech built Ophir. Client: Jewellery trade, multi-branch.
Generic inventory software can't track what matters in jewellery across branches: weight, purity, production stages and consignment. A piece is not just a quantity on a shelf. It starts as gold of a certain karat, goes out to a karigar, comes back as finished jewellery with a different weight, and may sit in another branch or with a consignment partner before it is sold at that day's gold rate. Tracking this in spreadsheets and generic stock tools left gaps between branches, made it hard to know where metal actually was, and stock queries were slow once the item count grew.
Ophir is built with Next.js, NestJS, Node.js, TypeScript, PostgreSQL, Redis, Tailwind CSS.
Stock reads in under a second, thanks to Redis caching. Inventory controlled across every branch. Production and sales that account for weight and purity. Consignment and karigar stock visible in the same system as shop stock. Sales priced against the day's gold rate instead of a fixed price list.
Yes. It is live at https://ophir.eaquirstech.com/.
Book a free consultation and we'll give you a clear plan for your ERP project.