Software Requirement Specification
Inventory Management System
 
 
 
1. Overview
Project Name: Inventory Management System
Prepared By: Mohit Jawanjal, Zach Richmond, Josh Campbell
Date: 12 May, 2025
Version: 1.0

2. Purpose
This system is designed to manage and track inventory in Go-Parts GA Warehouse, reduce operational complexity, and tightly integrate with the Go-Parts environment.

3. Goals
Simple UI for non-technical users.
Real-time inventory updates.
Tight integration with Go-Parts internal systems.
Replace Finale Inventory with a cost-effective alternative.
Valuation & Reporting Features 
Easy stock transfers 
On-Interface Returns check-ins 

4. Key Features


Feature
Description
Product Management
Ability to add Products. 

Ability to add new products automatically if they don’t exist in the Return import or Purchase order Import 

Required Fields:

Product ID 
Supplier Part Number
Partslink 
Supplier 
Average Price
Stock Management
Manage stock for products 

Tracking stock with Locations & Sub-Locations 
Central stock subtraction 	
Single & Bulk stock transfers through a single file
Stock history 
Stock import using Return import & purchase orders 
Average price tracking for both return import & purchase orders 
Flags for non-selling stock (stock that is on a specific Location, but is not listed to sell) 
Purchase Orders
Create & Import purchase orders. 

Easy rollback in case purchase order is deleted/rolled back 
Return Imports
Create Return imports for items which are returned to warehouse rather than purchased (currently only local stock is purchased) 

Facility to input returns as soon as they arrive

Bulk import returns
Locations / Warehouses
Create new Warehouse
Create warehouse locations 


Users and Roles
Ability to create new users and assign view only or edit roles 
Basic Reporting
Stock history reports
Valuation reports
QoH reports 
Integration 
Integrate with Go-Parts systems (partscan_inventory) 




6. Non-Functional Requirements
Performance: Should handle up to 50,000 SKUs efficiently.
Security: Only authenticated users with roles can make changes.
Scalability: Designed for easy addition of new warehouses or features.
Usability: Interface should be minimal, mobile-friendly, and intuitive.

7. Technology Stack (Suggested)


Component
Technology
Backend
PHP
Frontend
PHP/Filament/Tailwind CSS
Database
MySQL 



8. User Roles

Administrator - Complete access over the system 

Warehouse Managers - Complete access to system and reporting. Separated for audit-trail purposes.

Operations - View only access to the inventory, reporting and product modules


9. Timelines