Lavish Jewel ERP
A jewellery manufacturing ERP — the shop floor tracked stage by stage, from design through casting and setting to quality control, alongside orders, stock, invoicing and jangad consignment.
- Role
- Senior Developer & Project Manager
- Employer
- Orpol Infotech
- Branch
- Professional
- Stack
- Laravel
The work
What I built
The production pipeline is modelled stage by stage — design, CAD/CAM, model, rubber mould, wax tree, casting, grinding, filling, pre-polish, assembly, metal setting, final polishing, rhodium plating and quality control — each its own screen, so a piece can be located anywhere on the floor. Around it: parties, suppliers and purchases; an item master carrying metal type, weight, purity, price per gram and HSN code; a diamond and gemstone register with shape, carat, MM and colour-clarity grading; jangad consignment orders with returns and raw bills; gold and silver invoicing with QR codes and printed barcodes; stock, transactions and tax; employees and departments. Reporting spans customers, employees, gemstones, gold, silver, orders, parties and transactions, with Excel and CSV export. Built as an installable PWA with OTP-verified password reset, an activity log and database backup.
The context
June 2023 · Taking the lead
When I joined, the core team was very small — the CEO, one UI/UX designer and myself. Together we started building the foundation for a more structured and fully functioning software development company.
My role was no longer limited to development.
Across these projects my frontend experience expanded significantly, while my backend work continued to focus heavily on PHP, Laravel, MySQL and REST APIs.
- Technical planning
- Project architecture
- Backend development
- Frontend development
- API development
- Database design
- Client communication
- Project management
- Team coordination
- Testing and debugging
- Deployment and delivery
Professional experience notice
This project was developed as part of my employment with Orpol Infotech. It is presented solely to document my professional role, experience, and contribution. I do not claim ownership of the project or its underlying intellectual property.
No confidential information, credentials, private customer data, proprietary source code, or internal documentation is intentionally disclosed.
View portfolio disclaimer →