Problem
Traditional inventory systems fail to handle complex allocation rules, role-based purchasing control, and multi-portal distribution, making them unsuitable for organizations with structured product distribution workflows.
Professional ExperienceBusiness System
Rule-Based Inventory & Allocation System with Multi-Portal Architecture
A configurable inventory and allocation platform enabling vendors to create rule-driven portals, manage product distribution, and control purchasing workflows across user groups.
Full-stack developer (complex UI workflows, allocation logic, and bulk operations)
Key highlights
- Rule-driven inventory allocation with hierarchical constraints
- Configurable multi-portal system for controlled product distribution
- Complex allotment engine with inheritance and fallback logic
- Flexible data modeling with runtime allocation computation
Primary stack
React (TypeScript, complex multi-step form handling)
Node.js + Express (monolithic architecture, TypeScript)
Data layer
MongoDB
System Preview
Solution
Contributed to building a flexible inventory platform that allows vendors to configure custom portals with rule-based product allocation, user grouping, and controlled purchasing flows. Focused on building complex UI workflows and bulk data operations.
Features
Capabilities & System Features
Security & Auth
User grouping and role-based access control per portal
Configurable approval workflows (admin approval / open access)
Data & Storage
Bulk product management and editing
CSV-based data import and API-based product ingestion
Pagination for scalable data handling
Automation & Jobs
Renewal logic (monthly, yearly, custom, joining date-based)
Core
Multi-portal system with isolated configurations per vendor
Dynamic portal creation with multi-step workflow
Rule-based product allocation (category, subcategory, product-level)
Allotment system (unit or monetary limits)
Draft and publish system for controlled rollout
Engineering challenges
Complex problems solved
01
Hierarchical Allotment System with Inheritance Logic
Problem
The system required a flexible allotment mechanism where product limits could be assigned at multiple levels (category, subcategory, and individual product), while ensuring consistent deduction logic and visibility control across users and groups.
Solution
Designed a hierarchical credit system where allotments are structured in a parent-child relationship. Implemented logic allowing child-level allotments (e.g., specific products or subcategories) to be consumed first, with automatic fallback to parent-level allotments when limits are exceeded. Ensured that sibling categories remain unaffected, preserving independent allocation boundaries.
Impact: Enabled highly flexible and scalable product distribution rules, supporting real-world scenarios where organizations need both granular and generalized control over resource allocation.
02
Dynamic Product Visibility & Allocation Constraints
Problem
Users should only access products assigned to their group or role, while vendors needed the ability to configure product access and allotments dynamically across multiple hierarchy levels.
Solution
Implemented a rule-based filtering system that dynamically restricts product visibility based on group assignments. Built logic to ensure that only eligible categories and products are available during allotment configuration, reducing invalid assignments and maintaining system consistency.
03
Mandatory Product Attachments Without Allotment Impact
Problem
Certain products required mandatory add-ons (alterations) that should automatically be included in purchases without affecting the user’s allotment limits.
Solution
Designed an attachment system where products can have optional or mandatory linked items. Ensured that these attachments are included in transactions while excluding them from allotment deduction logic, maintaining accurate allocation tracking.
04
Flexible Allotment Data Modeling with Runtime Computation
Problem
The system required a highly flexible allotment structure supporting multiple hierarchy levels (category, subcategory, product) with dynamic rules and inheritance behavior. A rigid schema would limit scalability and make future changes difficult.
Solution
Designed a unified 'credit' schema where all allotments (categories, subcategories, and products) are stored in a structured array. Instead of hardcoding relationships in the database, implemented the core logic at the service layer to dynamically compute allotment consumption, inheritance, and fallback behavior at runtime.
Impact: This approach provided high flexibility, allowing new allocation rules and hierarchy levels to be introduced without major schema changes, while keeping the database structure simple and maintainable.
Architecture
System structure
Frontend
React (TypeScript, complex multi-step form handling)
Backend
Node.js + Express (monolithic architecture, TypeScript)
Database
MongoDB
Technologies
Tooling used
ReactTypeScriptNode.jsExpressMongoDBREST API
Building something complex?
I design and build scalable systems like this — from architecture to production-ready implementation.
Talk about your system