Inventory Management System Checklist

Requirements for Inventory Management System
(Software)
1. Backup/Restore
o The system must have options to backup and restore full data.
o Take Automatic backup with set time
2. Barcoding / RFID
3. Cost Tracking
4. Custom Pricing Models
5. Data Capture
o Accept data from multiple input methods including; bar code,
RFID
o Enter the value desired directly or from a drop down table of
valid values through standard mouse selection procedure
o Require mandatory fields to be filled before the user can exit the
screen
o Support real time data entry auditing quality control
o Support real time data entry feedback preventing data entry
errors from being recorded
o Provide appropriate calculations at time of data entry
o Log transactions at time of data entry
o Maintain transaction log history
o Provide asynchronous and synchronous data synchronization
6. Data Validation
o The system must validate every entry before saving. i.e. Prevent
from saving duplicates
7. Documentation and Help System Requirements
o A user manual shall be provided which describes the operation of
the system and provides references to the commands and user
interface displays of the system.
o The user manual shall contain a brief tutorial covering the basic
aspects of each part of the system (e.g. inventory update,
reporting access, etc.).
o The user manual shall be available in both on-line and printed
versions.
o The user manual shall be available in Amharic and English
o There shall also be an IT help form that can be filled out if more
help is needed.
o The vendor of the system must provide periodic maintenance
and should be available all time in the event of a failure requiring
immediate attention during working hours, by identifying the
location or device.
8. Ease of Access
o No more than 2 levels of navigation shall be required for a user
to enter or retrieve item information
o Provide simple navigational tools on all forms, with links to other
data entry items.
o Must conform to Microsoft GUI interface and user presentation
standard
o User input form shall contain data entry verification entry for
critical data
o Use combination and list boxes generously.
o Provide type-ahead functionality on list and combination boxes.
o Provide search capabilities on appropriate lists.

o Maintain a balance between the number of windows and the
amount of information contained on each window. This will
reduce the difficulty of navigation and the amount of information
that is required for viewing on a single screen.
o Have the ability for an administrator to add or eliminate fields,
organize the arrangement or tab order on data entry forms.
o Dynamic forms shall be generated where applicable. An
example of this is in the Element object, where each element
type can be customized with unique attributes and unique links.
9. Inventory Forecasting
o Forecast inventory sales from history
10.
Inventory Optimization
o Reorder point: the number of units that should trigger a
replenishment order
o Order quantity: the number of units that should be reordered,
based on the reorder point, stock on hand and stock on order
o Lead demand: the number of units that will be sold during the
lead time
o Stock cover: the number of days left before a stock out if no
reorder is made
o Accuracy: the expected accuracy of the forecasts
11.
Inventory Overview
o Inventory Item Descriptions
All of the items should have well-defined unique

descriptions, for many of the same reasons that apply to
locations.
Item Numbers
Units of Measure
o Show the current status of inventories by
12.
Stock location of item
Date item stocked
Name of stocker
Multi-Location
o Well-Organized Location Names & Location Labels That Are Easy
to Read and Unambiguous
13.
Multiple Users
o Inventory management program must have multiple
users/profiles and the ability to edit or restrict permissions/scope
of use
14.
Order Entry
15.
Performance
o The following performance requirements apply for the SITS
system and software.
User Response Time: software shall not exceed an average

user response time of 5 seconds over any continuous 4
hour period of time.
Transaction Response Time and Transaction Throughput:
The system shall not exceed an average transaction

time of 1 second as measure over a 1 hour period of
time.
The system shall not exceed a maximum transaction

response time of 5 seconds.
The system shall support a minimum transaction rate

of 60 transactions per minute.
Capacity: The system shall be capable of supporting a

minimum of 50 users at one time
16.
Purchase Order Management
17.
Reorder Management
o Should inventory reach a specific threshold, a company's
inventory management system can be programmed to tell
managers to reorder that product. This helps companies avoid
running out of products or tying up too much capital in inventory.
18.
Report Generation
o The system shall provide a means to query and report data.
o The system must track and generate pick lists, inventory, and
reports sorted on various data points, such as item number, UPC,
name, etc.
o The user shall have the ability to define standard reports and
allow the user to input query parameters.
o Generate Reports in multiple formats including but not limited to
Excel Format
PDF Format
19.
Search / Filter
20.
Users must be able to search the system through different filters

such as date, Invoice No, Amount, Item etc.
Serialized Inventory Tracking
o When a product is in a warehouse or store, it can be tracked via

its tracking criteria, such as serial number, lot/batch number or
revision number. Nowadays, inventory management software
often utilizes barcode, radio-frequency identification (RFID),

and/or wireless tracking technology.
21.
Supplier Management
o The system must maintain a detailed information of vendors i.e
Name, TIN no. Address etc.
22.
Traceability
23.
Training
o Training shall require from one to two days depending on users
o Follow-up training shall be available
24.
Transfer Management
25.
Warehouse Management
26.
User
o Each user will have the following attributes:
User Identification fields to identify this unique user.
Contact Information.
Assignment Information these fields will identify which

group and department this individual is assigned to, or
what role they play.
User Rights this set of allowable actions attributes will

allow a user-definable set of rights for each individual user,
by user type, by location, or by department. Rights shall
include view, read, modify, and delete.
User Status
Active The user is currently active in the system.
Retired The user is no longer active in the system.

These will be retained in the user list, however, to
maintain the integrity of the database.

Inventory Management System Checklist

Uploaded by

Copyright:

Available Formats

Inventory Management System Checklist

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Inventory Management System Checklist

Uploaded by

Copyright:

Available Formats

Requirements for Inventory Management System

o Provide search capabilities on appropriate lists.

All of the items should have well-defined unique

o Show the current status of inventories by

Stock location of item

Date item stocked

User Response Time: software shall not exceed an average

Transaction Response Time and Transaction Throughput:

The system shall not exceed an average transaction

The system shall not exceed a maximum transaction

The system shall support a minimum transaction rate

Capacity: The system shall be capable of supporting a

Purchase Order Management

Users must be able to search the system through different filters

o When a product is in a warehouse or store, it can be tracked via

often utilizes barcode, radio-frequency identification (RFID),

User Identification fields to identify this unique user.

Assignment Information these fields will identify which

User Rights this set of allowable actions attributes will

Active The user is currently active in the system.

Retired The user is no longer active in the system.

You might also like