Case study
Back to workSree Veeranjaneya ERP
Public catalog meets internal commercial ops
Industrial spare-parts platform — public catalog plus internal purchasing, quotations, dispatch, and production.
01 — Overview
Product discovery for customers. Quotations, stock, dispatch, and production for staff.
The business is an industrial spare-parts manufacturer and stockist. Customers browse online; staff run commercial and production workflows inside the same application.
02 — Problem
The product had to hold up as a connected workflow.
The same product must serve public discovery and authenticated ERP operations without feeling like two disconnected systems.
03 — My role
What I owned.
Frontend Product Engineer — Frontend Product Engineer on the Angular product and ERP interface. Primary frontend and UI/UX engineer, with other developers also involved. Backend was handled separately; I contribute there when needed.
04 — Product flow
The path a user actually takes.
I structured the Angular client around the business lifecycle — catalog outward, then purchasing, stock, quotation, sales, dispatch, and production inward.
Conceptual product flow for this domain — not a literal system diagram.
05 — Engineering
Decisions worth explaining.
Separate public and authenticated experiences while keeping them within one application.
Use reusable operational patterns for repeated ERP forms and tables.
05.1 — Architecture
How the pieces sit together.
06 — Challenges
What shaped the build.
Public catalog and ERP in one application
The same Angular client has to support public product discovery and authenticated internal operations without making the two experiences feel disconnected.
Multi-role ERP access
Different staff roles need access to different operational modules and actions.
Commercial quotation workflow
Quotation creation spans customers, products, charges, transport, bank information, terms and GST calculations before producing a printable document.
Industrial operational data
Purchasing, sales, dispatch and production workflows operate on large sets of structured business records.
07 — Outcome
What shipped.
Production
Production product with public domain and backend-connected operations; documented frontend checkout is a development copy
Qualitative — no performance or business metrics are claimed here.
One interface connecting public catalog functionality with internal commercial and production workflows.
The public domain and backend-connected product indicate a real delivered system, while the documented frontend checkout should be treated as a development copy rather than automatically equated with the deployed artifact.
In the product
Angular
REST API services
Role-aware modules
Reactive forms
Operational tables
Quotation generation
GST-aware UI calculations
Frontend consumption of the REST API. Backend ownership is not claimed without separate confirmation.
08 — Learnings
I structured the Angular client around the business lifecycle — catalog outward, then purchasing, stock, quotation, sales, dispatch, and production inward.