Stock Management System

ABSTRACT

This work is aimed at developing a hardware based system named Stock

Management System for managing the stock system of any organization. The
Stock Management System (SMS) refers to the system and processes to manage
the stock of organization with the involvement of Technology system. This
system can be used to store the details of the stock, stock maintenance, update
the stock based on the sales details, and generate sales and stock report daily or
weekly based. This project is categorize individual aspects for the sales and
stock management system. In this system we are solving different problem
affecting to direct sales management and purchase management. Stock
Management System is important to ensure quality control in businesses that
handle transactions resolving around consumer goods. Without proper stock
control, a large retail store may run out of stock on an important item. A good
stock management system will alert the wholesaler when it is time to record.
Stock Management System is also on important means of automatically tracking
large shipment. An automated Stock Management System helps to minimize the
errors while recording the stock.

1. INTRODUCTION

Stock management is the supervision of noncapitalized assets or inventory and

stock items. As a component of supply chain management, inventory
management supervises the flow of goods from manufacturers to warehouses
and from these facilities to point of sale. A key function of inventory
management is to keep a detailed record of each new or returned product as it
enters or leaves a warehouse or point of sale. Organizations from small to large
businesses can make use of inventory management to track their flow of goods.
There are numerous inventory management techniques, and using the right one
can lead to providing the correct goods at the correct amount, place and time.
Inventory control is a separate area of inventory management that is concerned
with minimizing the total cost of inventory, while maximizing the ability to
provide customers with products in a timely manner. In some countries, the two
terms are used synonymous compared to larger organizations with more
physical space, in smaller companies, the goods may go directly to the stock
area instead of a receiving location. If the business is a wholesale distributor,
the goods may be finished products, rather than raw materials or components.
Unfinished goods are then pulled from the stock areas and moved to production
facilities where they are made into finished goods. The finished goods may be
returned to stock areas where they are held prior to shipment, or they may be
shipped directly to customers. Inventory management uses a variety of data to
keep track of the goods as they move through the process, including lot
numbers, serial numbers, cost of goods, quantity of goods and the dates when
they move through the process. Inventory management software systems
generally began as simple spreadsheets that track the quantities of goods in a
warehouse but have become more complex since. Inventory management
software can now go several layers deep and integrate with accounting and
enterprise resource planning (ERP) systems. The systems keep track of goods in
inventory, sometimes across several warehouse locations. Inventory
management software can also be used to calculate costs -- often in multiple
currencies -- so accounting systems always have an accurate assessment of the
value of the goods.

1.1 Objective of the Project

1.1.1 Primary objective

The primary objectives of the project are mentioned below:

 To fulfill the requirement for achieving the Bachelor’s degree of

Computer Information System.
 To know the fundamentals of the .Net Technology and Visual Studio with
the .Net Framework

1.1.2 Secondary objective

The secondary objectives of this project are mentioned below:

 To develop an application that deals with the day to day requirement of

any production organization
 To develop the easy management of the inventory
 To handle the inventory details like sales details, purchase details and
balance stock details.
 To provide competitive advantage to the organization.
 To provide details information about the stock balance.
 To make the stock manageable and simplify the use of inventory in the
organization.
1.2 Features of Project

This application is used to show the stock remaining and details about the sales
and purchase. It gives the details about the stock on daily based and weekly
based. The details components are described below: Login page: As application
starts the login page appears. Admin login is determined by the username and
password that has all the authority to add, update and delete the stock of the
organization as per the requirement.

Create Godwom: We can create godwom if we need to extend or we have

more than one godwom. We can create the godwom along with the date.

Sales details: It show the details about the sales and the remaining stock of
sales. It also show the details about the sales in return.

Purchase details: It shows the details about the purchase made by the
organization along with the price and dates.

1.3 Scope of the Application

Inventory Management System (IMS) is targeted to the small or medium

organization which doesn’t have many godwom or warehouses i.e. only to those
organization that has single power of authority. Some of the scope are:

 Only one person is responsible in assigning the details or records

 It is security driven.
 Godown can be added as per the requirement.

2. LITERATURE SURVEY

Title: Web Service Based Food Additive Inventory Management with

Forecasting System
Author: Pikulkaew Tangtisanon
Year: 2018
Description: Recently, food industries have been growing rapidly due to the
development of novel technology. Numerous research has been conducted to
improve products to satisfy the needs of customers. As a result, various food
additives have been used to compose the product and which makes it difficult in
recognizing and managing food additive stock. To be able to survive in a
competitive world, the industry must find a practical stock management solution
since under-stocking causes the industry to lose an opportunity to sell while
overstocking causes a deficit. This paper focuses on an inventory management
and a stock forecasting system. Web service was implemented as a new
approach for an inventory management system that helps to manage and to find
the food additives that exist in the international food additive database
authorized by Codex Alimentarius Commission. Using web services has many
advantages than a traditional web base. The service provider does not have to
reveal the database access method to the client, and the information or business
model can be changed at any time, and no need to update the client side. The
client can access the service via any platform. The web service has been
developed through Hypertext Markup Language 5 (HTML5), Node JavaScript
(NodeJS), and My Structured Query Language (MySQL), Database
Management System, Hypertext Preprocessor (PHP). The stock forecasting was
done by Python with four machine learning models which are Naive Bayes,
Decision Tree, Linear Regression and Support Vector Regression to predict
stock of food additive. Accuracy is used to measure the performance of these
techniques. The experimental result indicated that the most accurate model for
stock forecasting is Linear regression.
Title: Integrated Inventory Management Control Framework
Author: Ganesha H. R., Sreeramana Aithal
Year: 2020
Description: The concept of minimum display quantity (MDQ) is unavoidable
in brick-and-mortar retailing format owing to which, retailers need to ensure a
minimum level of inventory displayed at each store irrespective of the revenue
or inventory turns generated by a particular store. It is observed that majority of
bricks-and-mortar retailers in India assume; a) existing inventory management
system is ideal to their store, b) software solutions record accurate inventory
movement, c) involving store management team in inventory-related decision
making is risky/biased and most importantly d) loss of sale due to stock-outs is
inevitable. Such assumptions and widely followed practice have created a
predisposition and mindset in-store managers and they believe that their store
delivers revenue and profit to the best of its potential with the inventory which
is made available to them through existing inventory management system and
we cannot avoid the number of instances consumers are unsatisfied due to
stockout situations. In this research, we have analysed the existing decision-
making process and control systems related to inventory management of a select
retailer, attempted to design a new framework, and applied the same through an
experiment to evaluate the change in a) overall store profitability and b)
inventory-related key performance indicators.
Title: Maximization of the return on inventory management expense in a
system with price- and stock-dependent demand rate
Author: Valentín Pando, L.A. San José
Year: 2021
Description: This paper considers an inventory model where the demand rate
depends on the selling price and the stock level. A lower price or higher stock
level lead to a higher demand rate. Three decision variables are considered: the
selling price, the order-level and the reorder point. The goal is the maximization
of the return on inventory management expense (ROIME), which is defined as
the ratio between the profit and the total cost of the inventory system. The
optimal values of the selling price, the order level, the reorder point, the lot size,
the maximum ROIME and the cycle time are proposed, and the condition that
ensures the profitability of the inventory system is established. The partial
derivatives of these optimal values with respect to the initial parameters are
calculated to analyse the sensitivity of the optimal policy concerning the
parameters of the model. The profitability thresholds for each parameter,
keeping all the others fixed, are also evaluated. A comparison between the
solution with maximum ROIME and the solution with maximum profit per unit
time is illustrated by using a numerical example. The solutions can be very
different. Maximizing the return on inventory management expense leads to a
zero-ending policy at the end of an inventory cycle, so the order-level is equal
to the lot size. On the other hand, maximizing the profit per unit time requires a
lower selling price, a higher lot size and a non-zero reorder point.
Title: Applying inventory classification to a large inventory management
system
Author: Benjamin Isaac May, Michael P. Atkinson
Year: 2017
Description: Inventory classification aims to ensure that business-driving
inventory items are efficiently managed in spite of constrained resources. There
are numerous single- and multiple-criteria approaches to it. Our objective is to
improve resource allocation to focus on items that can lead to high equipment
availability. This concern is typical of many service industries such as military
logistics, airlines, amusement parks and public works. Our study tests several
inventory prioritization techniques and finds that a modified multi-criterion
weighted non-linear optimization (WNO) technique is a powerful approach for
classifying inventory, outperforming traditional techniques of inventory
prioritization such as ABC analysis in a variety of performance objectives.
Title: Reinforcement learning approaches for specifying ordering policies
of perishable inventory systems
Author: AhmetKara, IbrahimDogan
Year: 2018
Description: In this study, we deal with the inventory management system of
perishable products under the random demand and deterministic lead time in
order to minimize the total cost of a retailer. We investigate two different
ordering policies to emphasize the importance of the age information in the
perishable inventory systems using Reinforcement Learning (RL). Stock-based
policy replenishes stocks according to the stock quantities, and Age-based
policy considers both inventory level and the age of the items in stock. The
problem considered in this article has been modeled using Reinforcement
Learning and the policies are optimized using Q-learning and Sarsa algorithms.
The performance of the proposed policies compared with similar policies from
the literature. The experiments demonstrate that the ordering policy which takes
into account the age information appears to be an acceptable policy and learning
with RL provides better results when demand has high variance and products
has short lifetimes.
Problem Statement
After analyzing many existing IMS we have now the obvious vision of the
project to be developed. Before we started to build the application team had
many challenges. We defined our problem statement as:
 To make desktop based application of IMS for small organization.
 To make the system easily managed and can be secured.
 To cover all the areas of IMS like purchase details, sales details and stock
management.
3. SYSTEM ANALYSIS
3.1 Proposed System
This project is categorize individual aspects for the sales and stock management
system. In this system we are solving different problem affecting to direct sales
management and purchase management. Stock Management System is
important to ensure quality control in businesses that handle transactions
resolving around consumer goods. Without proper stock control, a large retail
store may run out of stock on an important item. A good stock management
system will alert the wholesaler when it is time to record. Stock Management
System is also on important means of automatically tracking large shipment. An
automated Stock Management System helps to minimize the errors while
recording the stock.
Advantage
 Inventory management software can also be used to calculate costs.
 Accounting systems always have an accurate assessment of the value of
the goods.
 Inventory management Organizations from small to large businesses can
make use of inventory management to track their flow of goods.
3.2 Existing system
Numerous research has been conducted to improve products to satisfy the needs
of customers. As a result, various food additives have been used to compose the
product and which makes it difficult in recognizing and managing food additive
stock. Existing inventory management system and we cannot avoid the number
of instances consumers are unsatisfied due to stock out situations. The SDSM
was not used to simulate and confirm the parameters for the STS method. It was
also not used to compare the three inventory management methods against a
theoretical environment and actual data sets.
Disadvantage
 Slow data processing
 Lot of paper work
 Time consuming
 Less accurate
4. SYSTEM REQUIREMENT

HARDWARE REQUIREMENTS:

 System : Pentium IV 2.4 GHz.

 Hard Disk : 40 GB.

 Floppy Drive : 1.44 Mb.

 Monitor : 14’ Colour Monitor.

 Mouse : Optical Mouse.

  Ram : 512 Mb.

SOFTWARE REQUIREMENTS:

 Operating system : Windows 7 Ultimate.

 Coding Language : Php.

 Front-End : Php.

ANALYSIS AND DESIGN

4.1 Requirement Analysis

We collected a number of requirements for project from our primitive research,

website visits, and interview to the concerned personnel and their experiences
regarding the concepts of its development. We have even visited some
organization in Kathmandu valley and analyze its importance and try to develop
the project by fulfilling all the weakness that were found in the application. We
then decided to bulid same type of application with different logic flow and new
language which will be suitable for the small organization.

4.2 IMS Requirement

The goal for the application is to manage the inventory management function
of the organization. Once it is automated all the functions can be effectively
managed and the organization can achieve the competitive advantage. Business
requirement are discussed in the Scope section, with the following additional
details:

 Helps to search the specific product and remaining stock.

 Details information about the product sales and purchase.
 Brief Information of the organization todays status in terms of news,
number of present inventory as per the date entered.
  It helps to identify the total presented inventory in the company. 9
 To know the balance and details of sales distributed in specific date.
 There is proper transaction management of inventory.
 All transaction have specific entry date along with quantity and rate.
 Only admin can login in the page.

4.3 Users Requirement

User requirement are categorized by the user type

4.3.1 Admin

 Able to create new godwom along with date.

 Able to edit the entry as per entry.
 Able to add, modify and delete the stock entry.

4.3.2 Inventory management

 Able to check the stock available.

 Able to check the balance payment.
 Able to view the remaining sales stock.

4.4 Feasibility Analysis

This software has been tested for various feasibility criterions from various
point of views.

4.4.1 Economic Feasibility

The system is estimated to be economically affordable. The system is medium

scale desktop application and has affordable price. The benefits include
increased efficiency, effectiveness, and the better performance. Comparing the
cost and benefits the system is found to be economically feasible.
4.4.2 Technical Feasibility

Development of the system requires tools like:

 Visual Studio 2015

 .NET Framework 4.5
 Microsoft SQL server 2008, etc

Which are easily available within the estimated cost and schedule. 10

4.4.3 Operational Feasibility

The system provides better solution to the libraries by adding the typical
requirement and necessities. The solution provided by this system will be
acceptable to ultimate solution for the stock management.

4.4.4 Schedule Feasibility

The organized schedule for the development of the system is presented in the
schedule sub-section. The reasonable timeline reveals that the system
development can be finished on desired time framework.

5. MODULES
5.1 SYSTEM MODEL
After analyzing many existing SMS we have now the obvious vision of the
project to be developed. Before we started to build the application team had
many challenges. We defined our problem statement as,
• To make hardware based system of SMS for small organization.
• To make the system easily managed and can be secured.
• To cover all the areas of SMS like purchase details, sales details and stock
management
The proposed solution to the stock management. Integration of RFID to the
traditional inventory management will help in loss prevention and as an enabler
for locating misplaced stock, anticounterfeiting of stock, and availability of
stock on shelves. In this architecture, RFID serves as a replacement for the bar
code scanners which are normally used to track products and shipments in
similar ways (Smith 2000). This architecture fully integrates the technical
advantages of RFID to provide feedback on the process to the inventory
manager. RFID system consists of three fundamental components. Initially, the
RFID tag is attached to a product in the inventory. The tag contains information
about the particular inventory or product and also may include sensors. The next
component is the RFID reader, which communicates with the RFID tags. The
last component is the backend system, which links the RFID readers to a
centralized database or server. The centralized database will store all the
information of the products, such as price, for each RFID tagged item. In this
proposed architecture for inventory management, the passive tags will be used
due to their low cost. Among the functionalities expected to be performed by
this system includes:
• Checking the availability of stock on shelves:
• Identifying misplaced stock on shelves.
• Identifying expired stock.
• Identifying counterfeit products.
• Sending updates to the inventory manager.
• Support JIT Inventory
• Visibility of inventory throughout the supply Chain
• Perform the inventory functions with less manual intervention
The Electronic Product Code (EPC) is a unique global identifier of each product
in RFID technologies which is used to track and trace products (Yan 2008). The
EPC RFID readers will be placed among the shelves and the products will be
programmed with EPC RFID enabled tags. EPC RFID tags will send out the
signal which will be received by the EPC RFID readers in the radio frequency
field. The readers will receive the signal through their antennas and transmit the
stored information, i.e. Validation, tracking, counts, and error messages to the
EPC middleware. The EPC middleware will filter out the repeating and
irrelevant information. Thereafter, information will be sent to the local server.
The local server computer system will pass on the information to the inventory
manager i.e. reports on inventory, aggregate counts, errors occurred, misplaced
stock etc. The end user or owner will receive the notification on inventory
through his/her display. This system gives effective technical reference for
enterprise managers to monitor whole process of inventory without them being
physically involved in the process. The consumers of the products will benefit
also in this proposed architecture. They can query information about the product
on the remote server using the EPC (Electronic Product Code); the ONS (Object
Naming Service) is network system which works similar to the DNS (Domain
Name Service). We started research by identifying the need of SMS in the
organization. Initially we bounded our research to find the general reasons that
emerged the needs of Stock Management System. We used different techniques
to collect the data that can clearly give us the overall image of the application.
The techniques we used were interview with the developers, visiting online
websites that are presented as the templates and visiting some organization to
see their SMS application. Basically the following factors forced us to develop
SMS application:
• Cost and affordability
• Lack of stock management.
• Effective flow of stock transfer and management.
• Difficulty in monitoring the stock management.
5.2 PROPOED SYSTEM IMPLEMENTATION
We collected a number of requirements for project from our primitive research,
website visits, and interview to the concerned personnel and their experiences
regarding the concepts of its development. We have even visited some
organization in Dhaka and analyze its importance and try to develop the project
by fulfilling all the weakness that were found in the application. We then
decided to build same type of application with different logic flow and new
language which will be suitable for the small organization.
a. SMS Requirement
The goal for the application is to manage the stock management function of the
organization. Once it is automated all the functions can be effectively managed
and the organization can achieve the competitive advantage. Business
requirement are discussed in the Scope section, with the following additional
details: Helps to search the specific product and remaining stock. Details
information about the product sales and purchase. Brief Information of the
organization todays status in terms of news, number of present stock as per the
date entered. It helps to identify the total presented inventory in the company.
To know the balance and details of sales distribute.
5.3 Database Theory
A database is a collection of information that is organizes so that it can easily be
accessed, managed and updated. In one view, database can be classified
according to types of content: bibliography, full-text, numeric, and image. In
computing, database are sometime classified according to their organizational
approach. A distributed database is one that can be dispersed or replicated
among different points in a network.
5.3.1 Relational Database
IMS has the relational database model. A relational database is a digital
database whose organization is based on the relational model of data. This
model organizes data into one or more tables of rows and columns. These tables
here have the relation. The relation is maintained by the unique key defined in
each row. The key can be primary and foreign depending on their nature of
connection. The standard user and application program interface to a relational
database is the structured query language (SQL). SQL statement are used both
for interactive queries for information from relational database and for gathering
data for reports.
Primary Key
The primary key of a relational table uniquely identifies each record in the table.
It can either be a normal attribute that is guaranteed to be unique or it can be
generated by the DBMS. A primary key’s main features are:
 It must contain a unique value for each row of data.
 It cannot contain null value.
Foreign Key
A foreign key is a column or group of column in a relational database table that
provides a link between data in two tables. In foreign key reference, a link is
created between two tables when the column or columns that hold the primary
key value for one table are referenced by the column or column in another table
thereby establishing a link between them. Creating a foreign key manually
includes the following advantages:
 Changes to primary key constraints are checked with foreign key
constraints in relation table.
 An index enables the Database Engine to quickly find related data in the
foreign key tables.
5.3.2 Structured Query Language (SQL)
The structured Query language (SQL) is the set of instructions used to interact
with a relational database. In fact, SQL is the only language the most database
actually understand. Whenever you interact with such a database, the software
translates your commands into SQL statement that the database knows how to
interpret. SQL has three major Components:
 Data Manipulation Language (DML)
 Data Definition Language (DDL)
 Data Control Language (DCL)
5.4 ACID Property
Every database transaction obeys the following rules: Atomicity – Either the
effects of all or none of its operation remain (“all or nothing” semantics) when a
transaction is completed (committed or aborted respectively). In other words, to
the outside world a committed transaction appears (by its effects on the
database) to be indivisible, atomic, and an aborted transaction does not leave
effects on the database at all, as if never existed.
Consistency – every transaction must leave the database in a consistent
(correct) state, i.e., maintain the predetermined integrity rules of the database
(constraints upon and among the database’s objects). A transaction must
transform a database from one consistent state to another consistent state
(however, it is the responsibility of the transaction’s programmer to make sure
that the transaction itself is correct, i.e., performs correctly what it intends to
perform (from the application’s point of view) while the predefined integrity
rules are enforced by the DBMS). Thus since a database can be normally
changed only by transactions, all the database’s states are consistent. An aborted
transaction does not change the database state it has started from, as if it never
existed (atomicity above).
Isolation – Transactions cannot interfere with each other (as an end result of
their executions). Moreover, usually (depending on concurrency control
method) the effects of an incomplete transaction are not even visible to another
transaction. Providing isolation is the main goal of concurrency control.
Durability – Effects of successful (committed) transactions must persist
through crashes (typically) by recording the transaction’s effects and its commit
event in a non-volatile memory.
6. SYSTEM DESIGN
6.1 Architecture Diagram
Fig 1: Architecture Diagram
This is an illustration of a Network Architecture for Inventory management
system. Network architecture may help with security, which is becoming more
critical as more consumer devices connect to the network. The network's design
and protocols must facilitate rapid and efficient user detection and authorisation.
The Open Systems Interconnection Model, or OSI, is used in the majority of
network topologies. This conceptual paradigm divides network jobs into seven
logical levels, from the most basic to the most complex. The Physical layer, for
example, is responsible for the network's wire and cable connections. The
uppermost tier, the Application layer, has APIs for application-specific tasks
such as chat and file sharing. Download this free EdrawMax template to easily
create your own network architecture!
6.2: Process Flow Diagram
Process Flow Diagram or Flowchart is a diagram which uses geometric symbols
and arrows to define the relationships. It is a diagrammatic representation of the
algorithm. The Process flow Diagram of our application is shown below:

Figure 2: IMS Process flow diagram

6.3 Use Case Diagram
Its purpose is to present a graphical overview of the functionality provided by a
system in terms of actors and their goals. The main purpose of a use case
diagram is to show what system functions are performed for which actors.
6.3.1 Diagram Building Block
Use cases
A use case describes a sequence of actions that provide something of
measurable value to an actor and is drawn as a horizontal ellipse.
Actor
An actor is a person, organization or external system that plays a role in one or
more interactions with the system
System boundary boxes (optional)
A rectangle is drawn around the use case called the system boundary box to
indicate scope of the system.

Figure 3: IMS Use Case Diagram

7. SYSTEM TESTING
PHP requirements
Some individual modules may have specific requirements for PHP extensions
and configurations beyond those listed below, so, please check the module's
documentation as well.
PHP versions supported

1. Drupal 10 requires at least PHP 8.1. PHP 8.1.6 is recommended.

2. Drupal 9.4 dropped official support for PHP 7.3. Sites on PHP 7.3 may
still be installed and updated to Drupal 9.4 (with a warning), but their
security coverage is not guaranteed unless they update to at least PHP 7.4.
What does it mean for a PHP version to be supported? What does it mean
for the PHP installation to be "too old"?
Drupal minor versions receive a predefined window of security coverage
(typically 12 months) so long as you are using a supported PHP version.
We prefer to allow sites to receive security updates even if they are using a
version of PHP that is no longer supported. However, Drupal's upstream
dependencies may drop support for older PHP versions before the Drupal major
version reaches its end of life. If this happens, the Drupal site will no longer be
able to install security updates for that dependency, so we can no longer
guarantee its security coverage.
Site owners will receive warnings on their site status report that their PHP
installation is "too old" if the site's PHP version is old enough that a dependency
is likely to drop support for it.

If a dependency does drop support for a PHP version that was initially
supported by the Drupal major version, an unscheduled minor release may be
created to require the new PHP and dependency versions. For example, Drupal
9.0.0 supported PHP 7.3, so if a Drupal 9 dependency drops support for PHP
7.3 before Drupal 9's end-of-life date in November 2023, we may create a new
minor version outside the normal schedule that increases the PHP version
requirement to 7.4 and the dependency's version requirement to the supported
version.

What does it mean for a version of PHP to be "recommended"?

Drupal will work on all supported PHP versions. Recommended PHP versions
are the best choice for building a Drupal site because they will remain supported
longer.
PHP extensions needed
Extensions used by Drupal core are defined in Core's composer.json file - see
for example the file for Drupal 9.1.x. Look at the "require" section and the keys
starting with "ext-".
Note: Adding a PHP extension to your system, at least on Linux (and Mac),
means finding and installing the relevant PHP package using your package
manager. Typically the package name for the Foo extension is named "php-foo"
or "php7-foo", but this isn't always the case. Some extensions are part of the
core PHP package and hence are enabled by default.
Database extensions
The PHP Data Objects (PDO) extension must be activated for Drupal 9 and
higher to install and run correctly. The PECL version of PDO is not compatible
with Drupal 9 and cannot be used. In addition, a PHP extension for connecting
to your chosen database must be installed and enabled.
Drupal's currently supported database connectors are SQLite, mysql (the
original MySQL extension), mysqli (an improved connector for newer MySQL
installations), and pgsql (for PostgreSQL).
XML extension
PHP XML extension (for Blog API, Drupal, and Ping modules). This extension
is enabled by default in a standard PHP installation; the Windows version of
PHP has built-in support for this extension. Enabling the XML extension also
enables PHP DOM. DOM is now a systems requirement.
Image library
An image library for PHP such as the GD library is a required extension in
Drupal 9 and higher, and is needed for image manipulation (resizing user
pictures, image and image cache modules). ImageMagick is also supported for
basic image manipulations in Drupal core but there is much less support from
contributed modules.
OpenSSL
The PHP OpenSSL extension is recommended to allow Drupal to make
outgoing requests using HTTPS and is required when using the Update
Manager. Read PHP OpenSSL requirements for more information.
JSON
Drupal 9 and higher require PHP compiled with JSON. JSON support is
normally compiled as part of PHP core, but in case you're getting errors like
PHP Fatal error: Call to undefined function Drupal\\Component\\Serialization\\
json_encode() in core/lib/Drupal/ Component/ Serialization/Json.php try adding
the JSON extension.
cURL
The PHP cURL extension is required for automated testing in Drupal 9 and
higher, as well as Aggregator and some contributed modules. Many Linux
 distributions and development stacks will have it enabled by default, but if your
system doesn't either enable it in php.ini (typically on Windows) or install it
using your package manager (typically on Linux).
Mbstring
The PHP mbstring extension provides multibyte specific string functions used
for Drupal installation in other languages except for English and also
multilingual sites in Drupal. It helps deal with multibyte encodings in PHP and
also handles Unicode based encoding like UTF-8 or UCS-2.
PHP configuration settings
Memory requirements
PHP memory requirements can vary significantly depending on the modules in
use on your site. The minimum required memory size is 64MB.
Warning messages will be shown if the PHP configuration does not meet these
requirements. However, while these values may be sufficient for a default
Drupal installation, a production site with a number of commonly used modules
enabled could require more memory. Typically 128 MB or 256 MB are found in
production systems. Some installations may require much more, especially with
media-rich implementations. If you are using a hosting service it is important to
verify that your host can provide sufficient memory for the set of modules you
are deploying or may deploy in the future. (See the Increase PHP memory
limit page in the Troubleshooting FAQ for additional information on modifying
the PHP memory limit.)
.htaccess settings
Some of the memory settings are contained in the default .htaccess file that
ships with Drupal, so you shouldn't need to set them explicitly. Note, however,
that setting PHP configuration options from .htaccess only works under the
following conditions:

 With Apache (or a compatible webserver)

 If the .htaccess file is actually read, i.e. AllowOverride All in the main Apache
configuration (usually httpd.conf) is enabled
 If PHP is installed as an Apache module
In some shared hosting environments, access to these settings is restricted. If
you cannot make these changes yourself, please ask your hosting provider to
adjust them for you.

Other interfaces

See the PHP manual for how to change configuration settings for other
interfaces to PHP.
Xdebug
If using Xdebug:
Setting: xdebug.show_exception_trace = 0
Reason: Could cause Drupal's installer to crash.
Using Xdebug with Drupal 9:
Setting: xdebug.collect_params = ?
Reason:Setting xdebug.collect_params too high will prevent Drupal 9 from
installing and working properly.
Setting:xdebug.max_nesting_level = 256
Reason:Using the default max_nesting_level of 100 (in xdebug versions < 2.3)
causes some pages to crash.
PHP from different sources
Drupal is designed to work with PHP as distributed on PHP.net. Every effort is
made to make it work with PHP versions from other sources but this is only
done on a best effort basis. In particular, Suhosin is known to break certain
features; and some operating systems move core components into other
packages.
PHP requirements details
See the phpinfo() page on Drupal.org to learn how to use Phpinfo to get the
details of your system. For example, Phpinfo will tell you if you have a database
already installed and what versions of PHP, MySQL, etc. your system is
running. Phpinfo will also tell you what PHP variables are set as well as many
other helpful things.
It is often possible to update to a newer version of PHP that ships with your
Linux distribution. Please read the documentation for your Linux distribution.

Some notable points

 Be aware of the limitations of 32-bit PHP.

 The Drupal 9 Update manager can install/update modules and themes via
SSH if the required libraries have been installed on the server. (On
Debian the package is named "libssh2-php".)
 If the native opcache is enabled, settings opcache.save_comments must
be enabled (set to 1 which is the default), otherwise Annotations will not
be saved/loaded.

8. CONCLUSION
The importance of stock management is very serious, it is one of the most
important aspects of any business. Once it is automated all the functions can be
effectively managed and the organization can achieve the competitive
advantage. Business requirement are discussed in the Scope section, with the
following additional details: Helps to search the specific product and remaining
stock. Details information about the product sales and purchase. Brief
Information of the organization todays status in terms of news, number of
present stock as per the date entered. It helps to identify the total presented
inventory in the company.
9. FUTURE SCOPE
 The Fourth Industrial Revolution will continue to drive technological
change that will impact the way that we manage inventories.
 Collaboration with supply chain partners, coupled with a holistic
 approach to supply chain management, will be key to effective inventory
management.
 The nature of globalization will change, impacting inventory deployment
decisions dramatically.
 Increased focus on supply chain security, and concerns about the quality
of inventory itself, will be primary motivators to changing supply chain
and inventory strategy.
10. REFERENCE
[1]. Tangtisanon, P., 2018, April. Web Service Based Food Additive Inventory
Management with Forecasting System. In 2018 3rd International Conference on
Computer and Communication Systems (ICCCS) (pp. 448- 452). IEEE.
[2]. Ignaciuk, P. and Wieczorek, Ł., 2019. Networked base-stock inventory
control in complex distribution systems. Mathematical Problems in
Engineering, 2019.
[3]. HR, G. and Aithal, P.S., 2020. Integrated Inventory Management Control
Framework. International Journal of Management, Technology, and Social
Sciences (IJMTS), 5(1), pp.147-157.
[4]. Botha, A., Grobler, J. and Yadavalli, V.S., 2017. System dynamics
comparison of three inventory management models in an automotive parts
supply chain. Journal of Transport and Supply Chain Management, 11(1), pp.1-
12.
[5]. Pando, V., San-Jose, L.A., Sicilia, J. and Alcaide-Lopez-de-Pablo, D., 2021.
Maximization of the return on inventory management expense in a system with
priceand stock-dependent demand rate. Computers & Operations Research, 127,
p.105134.
[6]. May, B.I., Atkinson, M.P. and Ferrer, G., 2017. Applying inventory
classification to a large inventory management system. Journal of Operations
and Supply Chain Management (JOSCM), 10(1), pp.68-86.
[7]. Yuvaraj, K., Oorappan, G.M., Megavarthini, K.K., Pravin, M.C., Adharsh,
R. and Kumaran, M.A., 2020, November. Design And Development Of An
Application For Database Maintenance In Inventory Management System Using
Tkinter And Sqlite Platform. In IOP Conference Series: Materials Science and
Engineering (Vol. 995, No. 1, p. 012012). IOP Publishing.
[8]. Kara, A. and Dogan, I., 2018. Reinforcement learning approaches for
specifying ordering policies of perishable inventory systems. Expert Systems
with Applications, 91, pp.150-158.
[9]. Diamant, A., Milner, J., Quereshy, F. and Xu, B., 2018. Inventory
management of reusable surgical supplies. Health care management science,
21(3), pp.439-459.
[10]. Nemtajela, N. and Mbohwa, C., 2017. Relationship between inventory
management and uncertain demand for fast moving consumer goods
organisations. Procedia Manufacturing, 8, pp.699-706.
[11]. Rodriguez‐Gonzalez, C.G., Herranz‐Alonso, A., Escudero‐Vilaplana, V.,
Ais‐Larisgoitia, M.A., Iglesias‐Peinado, I. and Sanjurjo‐Saez, M., 2019. Robotic
dispensing improves patient safety, inventory management, and staff
satisfaction in an outpatient hospital pharmacy. Journal of evaluation in clinical
practice, 25(1), pp.28-35.