Case study
Back to workSGreens ERP
Poultry operations in one connected workspace
Poultry farm ERP — production, inventory, purchases, sales, hatchery, and accounts in one operations system.
01 — Overview
Production, inventory, purchases, sales, and accounts — with role-aware access for farm staff.
SGreens supports a multi-branch poultry business. Staff need consistent operational records across eggs, birds, feed, hatchery, medicine, inventory, and finance.
02 — Problem
The product had to hold up as a connected workflow.
Disconnected manual processes make stock, purchases, and sales hard to reconcile. Different roles also need different levels of access to sensitive operations.
03 — My role
What I owned.
Frontend Product Engineer — Frontend Product Engineer on the Angular operations application. I owned frontend and UI/UX; backend was handled separately, and I contribute there when needed.
04 — Product flow
The path a user actually takes.
The frontend is organized by business module — each department gets dedicated workflows built on shared form, table, and API patterns.
Conceptual product flow for this domain — not a literal system diagram.
05 — Engineering
Decisions worth explaining.
Keep operational resources separated into feature/service boundaries.
Use shared form/table patterns across repeated business workflows.
05.1 — Architecture
How the pieces sit together.
06 — Challenges
What shaped the build.
Role-based access across a large operational surface
Multiple staff roles need different access to operational data and actions.
Cross-module stock consistency
Inventory quantities and remaining stock appear across multiple operational modules, making consistency a core product concern.
Installment and due-payment workflows
Operational purchase and payment flows need to represent outstanding amounts alongside business records.
Large operational data surfaces
The ERP relies heavily on tables, pagination, filtering and search across business records.
07 — Outcome
What shipped.
Production
Production product — public site at sgreens.com; operations ERP is authenticated.
Qualitative — no performance or business metrics are claimed here.
A broad operational interface covering the core workflows of a poultry business, integrated with a separate REST backend.
The project documentation indicates a production-oriented client system, while the available frontend checkout is not sufficient to prove that exact snapshot was the deployed artifact.
In the product
Angular SPA
REST service layer
JWT-aware API integration
Reactive forms
Operational tables
Role-aware UI patterns
Consumed the separate REST backend; backend ownership is not claimed from the available frontend workspace.
08 — Learnings
The frontend is organized by business module — each department gets dedicated workflows built on shared form, table, and API patterns.