Pharmaceutical store management system

1
Strategic ICT & eBusiness Implementation
Pharmaceutical Store Management System
Batch January-2019 / B
Project Outline
Team Members
Member Name Student Number Contribution
Ashish Soni 18136664 25 %
Shantanu Deshpande 18125514 25 %
Tushar Dalvi 18134301 25 %
Yash Iyengar 18124739 25 %
Submitted to : Prof. Ciaran Hayden

2
Table of Contents
Contents
1. Background Information on the organization:....................................................................4
1.1. Organization Background: ..........................................................................................4
2. Infrastructure: .......................................................................................................................5
2.1. Rational for Selecting Infrastructure:.........................................................................5
2.2. Benefits and Risks of Infrastructure Selected: ..........................................................5
• Benefits:......................................................................................................................................... 5
• Risks:............................................................................................................................................. 6
3. System Design .......................................................................................................................7
3.1. Integrating Customers: ...............................................................................................7
3.2. Process Diagrams: .......................................................................................................7
3.3. Data Capture Points (DCPs) ..................................................................................... 10
3.4. Management Dashboard:........................................................................................ 10
4. Database Design................................................................................................................. 12
4.1. Entity-Relationship diagrams................................................................................... 12
4.2. Data Flow Diagram:.................................................................................................. 14
4.3. Data Dictionary......................................................................................................... 16
4.4. Process Control Features ......................................................................................... 20
5. Project Architecture........................................................................................................... 21
5.1. Implementation Architecture:................................................................................. 21
5.1.1. Custom Objects: ................................................................................................................... 21
5.1.2. Custom Fields: ...................................................................................................................... 22
5.1.3. View Users within Application:.............................................................................................. 22
5.1.4. Create new Product Record: ................................................................................................. 23
5.1.5. Create New Purchase Record:............................................................................................... 24
5.1.6. Create New Sales Record:..................................................................................................... 25
5.1.7. Create New Customer Record:.............................................................................................. 25
5.1.8. Create new Vendor record:................................................................................................... 26
5.1.9. Create new Employee Registration Record:........................................................................... 27
5.2. Data Fields: ............................................................................................................... 27
5.2.1. Customer Data:..................................................................................................................... 27
5.2.2. Sales Data:............................................................................................................................ 28
5.2.3. Product Master Data:............................................................................................................ 29
5.2.4. Purchase Data:...................................................................................................................... 29
5.3. Validation and Triggers:........................................................................................... 31

3
5.3.1. Sales Fields Validation:.......................................................................................................... 31
5.3.2 .................................................................................................................................................... 32
5.3.2. Login:.................................................................................................................................... 33
5.3.3. Login Logs:............................................................................................................................ 34
5.3.4. Permission Sales Team:......................................................................................................... 35
5.3.5. Permission IT manager:......................................................................................................... 36
5.3.6. Roles:.................................................................................................................................... 37
5.4. Reports:..................................................................................................................... 38
5.4.1. Products purchased:............................................................................................................. 38
5.4.2. Top vendors:......................................................................................................................... 39
5.4.3. Customer Product Sales:....................................................................................................... 40
5.4.4. Top customers:..................................................................................................................... 41
6. Operational Benefits.......................................................................................................... 41
7 Future Work....................................................................................................................... 42
8 References ......................................................................................................................... 42
10 APPENDIX........................................................................................................................... 43

4
Pharmaceutical Store Management System
1. Background Information on the organization:
1.1. Organization Background:
A pharmacy is a retail shop which provides prescription drugs, among other products. At the pharmacy, a
pharmacist oversees the fulfilment of medical prescriptions and is available to give advice on their offerings of
over-the-counter drugs. A typical pharmacy would be in the commercial area of the community. Characteristic
of a good pharmacy includes processing the request quickly and having drug stock available to fill the
prescription. Enabling latest technology at a pharmacy will also enable the patients to have scheduled
prescription reminders and alerts about potential negative drug interactions, which will help in reducing medical
errors.
Medcure is a pharmaceutical store operating in the healthcare industry and is in the business of selling
prescription drugs since 2013. Their motto has always been to provide best service to their customers by having
stock of appropriate products at any given point in time. Their staff dedicatedly offers precise advice to
customers for selecting the appropriate over-the-counter products well suited to their needs. The range of
products and drugs that are offered in store is quite extensive and is well-managed by the current team however
due to the outdated IT system, it becomes difficult at times to manually keep track of inventory, Revenue,
product and day to day activity information which causes lack of efficiency in the process.
It is extremely crucial for a business to integrate IT services in today’s age in order to expand their business and
bring efficiency in the process.

5
2. Infrastructure:
2.1. Rational for Selecting Infrastructure:
Existing process includes a very basic IT system which only has the capability of generating bills but
does not capture customer data and all the necessary data points pertaining to the stock inventory.
As a result of that, it is not possible to derive meaningful insights based on the available data. Additional
drawbacks of the existing process could be summarized as below-
No proper employee authentication/verification process in place:
In the existing system, employee interaction with system is tracked on trust and goodwill. No
proper hierarchical process is defined which will allow the interaction to be verified, always
acknowledged and monitored.
No visual reports:
As stated earlier, there is inconsistency in the data capture process. Due to this, it is not possible for
the management to derive meaningful insights.
Improper inventory management:
In the current system, all the necessary information related to a product is not captured, for example,
the expiry date of a batch of products is not captured by the current system. This results in improper
inventory management and thereby affects profits.
Customer information not retained:
The store currently operates in a retail environment wherein the customer walks-in with the
prescription and walks out with drugs and a bill. The store does not collect any customer details.
This information is crucial in order to become customer-centric and increase profits.
2.2. Benefits and Risks of Infrastructure Selected:
Using Salesforce developer platform to integrate proper IT management system to manage the
inventory and better capture the employee and customer data will help to get accurate insight in store
as well as proper revenue, sales, purchase reports will help in order to increase profitability, efficiency
and bring transparency in the process.
• Benefits:

6
Increased Profitability:
Relying on the IT system will result in reducing manual work which helps in cost cutting and
eventually increases the profitability in the long run.
Can cater to large number of customers:
Implementing IT system helps in retaining the customer information, reach out to customers and
this in turn increases publicity by word of mouth. Also, since we are increasing our scope of
business, having online customers will also widen our customer base.
Proper Inventory management and Data Transparency:
In the proposed system, all the necessary data points pertaining to the drugs/employee/customer
would be precisely captured and updated in real-time also All the data inputs can be verified and
monitored by the supervisor. This will reduce irregular and erroneous inputs.
Efficient and robust system:
An efficient and robust IT management system serves as a backbone of any organization. The
proposed system is capable to handle the existing business in an efficient and also give the
organization a competitive edge over its competitors.
• Risks:
Considerable maintenance cost:
IT systems have a significant upkeep cost as we must deploy the complete system on a Cloud
environment, hence cost might be high or low depending upon the location and infrastructure user
wants to use.
Data Security:
As mentioned above, all the information is stored on a third-partycloud-based system. If the system
is not properly secured there might be a possibility of data breach and the crucial business-related
information can be harnessed by unauthorised users.
User-adaptability:
While designing the IT management system if users’ abilities needs and preferences are not taken
into consideration, even an amazing IT system would be a complete failure. It is extremely
important to have a proper User Acceptance Testing before deploying the IT system.

7
3. System Design
3.1. Integrating Customers:
Integrating customers into our management system is very crucial for smooth functioning of the medical
shop. We have demonstrated how we have integrated customers not only in retail but also in our online format.
It is explained systematically and step by step how we integrate customers into the system with the help of
design flow diagrams, data capture points, Entity Relationship diagram and Database Design diagrams.
3.2. Process Diagrams:
Retail Shop Process:
The Retail Shop Process is different from the Online registration process. In which User will no need
to Register online. This system is totally developed for employee of shops and for owner. Employee will use
this system to sell product in Retail shop in which system will capture stock details, payment method and
customer details. Customer will get to know which medicines are out of stock, which products are near to expiry
date, or which products we will need to restock for future sell.

8
Fig3.2.1 The Cross- Functional diagrams of Retail shop system Process

9
Stock Update Process:
The Inventory management is very important aspect of any pharmacy. If properly managed, this can lead to increased profits and reduced overheads.
This can also reduce the burden on the Manager as system would be keeping track of the inventory. We have designed a process flow for it.
Fig3.2.2 The Cross- Functional diagrams of Stock Update Process

10
3.3. Data Capture Points (DCPs)
The Data Capture Points are represented by a red circle in the process flow diagrams. Error! Reference s
ource not found. shows a list of all the DCPs:
Type Process Flow Diagram DCP Data Captured
Retail
Store
New Customer Walk-In
Process
Customer Come to purchase
medicine from Store
Name of Applicant, Medicines
Name, Quantity
Making list to purchase
of New Products
Creating Purchase order Limited Stock List, Quantity of
Medicines and other product
Name of supplier
Receiving new product Adding new product in
Inventory
Product Name, Quantity of the
products, Expiry Date of
Product, Production Date of
Product, Sellers information,
Payment Details,
Adding New Worker New Worker Details of Worker, Level of
Authentication, Job Profile,
joining Date,
3.4. Management Dashboard:
Analytics Requirement:
The management dashboard aspect for medical management system is crucial to take any decision
related to organisation. Each department or division is responsible for managing their own information,
but all that information leads back to one strategy for the organization. Simply sending out a file
occasionally, to each department isn’t going to cut it. To keep every department constantly updated
(and available for viewing in several different ways), every company need a management dashboard.
This dashboard includes graphs, pie charts, line charts, dials, and tree maps, historical trend graphs, and
leadership boards, the data which we are going to present will be captured from various processes.
User will be able to obtain the following insights: -
• Numbers of product sold within day/month/year.
• Number of products need to be purchased.
• list of products which will expire soon.
• Revenue generated from Retail Store as well as Online website.
• Weekly Analytical reports to check revenue, sales, purchases and other Activity.
The purpose of operational analytics and analytical dashboards is to optimise the business process and
tasks within the store. These reports will be highly beneficial for the store in terms of increasing the

11
revenue, keeping the products in stock. Ultimately, the analysis and dashboards will allow the store
manager to provide the best service to the customers and it will boost the administrative productivity.
Another analytical need of the store is the requirement of gaining insights from the customer
information. The reports can thus be generated and reviewed customer-wise. Some of the important
questions the reporting and analysis will need to answer include:
• What type of products do the customers frequently buy?
• Who the top customers are in terms of spending?
• Which products have less price or high prices?
• Total sale of product depending on different Area?
• Total expenditure for medical shop or online application with categorisation with Monthly,
quarterly or yearly.

12
4. Database Design
4.1. Entity-Relationship diagrams
In order to show the relationships among the entity sets that are stored in the database, we
generally use the Entity-Relationship Diagram, often abbreviated as ER Diagram. Entity is an object, a
component of data whereas an entity set is a collection of multiple similar entities. These entities have
attributes that delineate its properties.
An ER diagram elucidates the logical structure of databases by defining the entities, their attributes and
the relationship between them. Entities are denoted by a square shape in the ER Diagram whereas the
attributes are the facts and properties of an entity. Relationships are denoted by a diamond shape on the
lines connecting the entities together and are often nouns in the description. They depict the links that
entities have among each other.
Refer Fig. No. 4.1, we have our relationships decided, from where we can now move on to particularize
a more detailed Database diagram. The Database diagram has been built upon the ER Diagram from
below, with some added details about the more descriptive attributes of each table/member. The final
design on which the data storage system will be created is based upon this lower level design.

13
Fig No. 4.1: ER Diagram of Pharmaceutical Store Management System

14
4.2. Data Flow Diagram:
Proposed the diagram is Entity Relationship diagram for the database design. It consist of the tables like
User Details, Login Details, Stock Data, Medicine details, Retail Billing, Vendor Invoice, Retail Billing
and Employee Table.
Below is the description of each table:
User Details: This table will capture all the details of user when He/ She first time sign up to the Online
Portal. It basically consists of basic information about the user including Email-id, password etc. The
primary key for this table will be Email-id which will be unique for each user.
Login Details: This tables will store the email-id, password and user name which will be used to
validate the record of the user who will be trying to login to the portal. The table will be updated by the
new user when they successfully signed up to the online.
Medicine Details: This table basically consist details of the medicines. The primary key of this table is
Medicine_id which will uniquely identify each medicines. It will store details related to medicines like
its description type and Cost.
Stock Data: This table will store the data of the medicine available in the stocks. To identify the stock
we have used the primary key like storage location and Medicine Number. It also include the details
like In and Out details of the batch and with the details like Expiry date etc.
Retail Billing: The retail billing is the table which store the data of all the sales done from the store
the primary key for the table is Billing Number which will uniquely identify the sales from the retail
store. And it also consist the details of store, medicine name description etc.
Vendor Invoicing: The vendor invoicing basically consist of the data which will the medical store buy
from the other vendors to fulfil its stocks. In this the invoice number will uniquely identify the data int
the table .It also contains the information like Medicine name, Medicine Description, Batch number etc.
Employee: The employee table basically consist of the employee of the company. To uniquely identify
the table employee data we have made the Employee_id as the primary key for the table. It also Include
the details of the employee role and its description.

15
Fig No. 4.2: Data Flow Diagram

16
4.3. Data Dictionary
“A Data Dictionary is defined as a central repository of information about data such as meaning, relationship to other data, origin, usage, and format.”(IBM
Dictionary of Computing, 1993). Our data dictionary gives a complete description of different data points their relation to the database and field description.
The Data Dictionary is created with the help of Entity Relationship Diagram and Data flow Diagram.
Our data dictionary is divided into 3 main parts Customer Table, Stock Table and Employee Table. These tables have a common flow as to what fields are
mentioned in respective tables and what proper values should be input into the table. Furthermore it gives a description of each field and tells what checks
are to be implemented on the data entered in the respective field.
Product Master Detail
Field Label Data Type Description
Product Name Varchar (50) Name of the Medicine in inventory
Manufacturer Name String Drug manufacturer’s name
Purchase Price Float Cost of the drug
Quantity Int Total no of batches of that product ordered.
Expiry Date Date (dd/mm/yyyy) Approximate date after which drugs must not be consumed.

17
Purchase
PO Number Varchar (12) Purchase Order
Purchase_ID Int not null Primary Key for Purchase Table
Purchase Date Date (dd/mm/yyyy) Date on which Purchase was made
Quantity Int Total no of batches of that product ordered.
Purchase Price Float Cost of the drug
Vendor Name Foreign Key It is a reference field which gives Vendor name from the Vendor
table
Product Name Foreign Key It is a reference field which gives Product name from the Product
Master table

18
Sales Table
Sale Order Number Varchar (12) Gives the sales order for the medicine sold
Sale_ID Int not null Primary Key to Sales table
Sale Date Date (dd/mm/yyyy) Date on which sales was made
Quantity Int Number of units of that drug purchased
Sale Rate Float Selling price of the drug
Customer Name Foreign Key It reference Customer Name from the Customer
Table
Product Name Foreign Key It is a reference field which gives Product name
from the Product Master table
Customer Table
Customer_ID Int not null Primary key for Customer Table
Customer Name String Name of Customer
Mobile Number Int Contact number of the customer

19
Vendor Table
Vendor_ID Int not null Primary key for Customer Table
Vendor Name String Name of Vendor
Mobile Number Int Contact number of the customer
Vendor Address Varchar (50) Address of production factory.
Bank Details Varchar (12) Bank Account details of the vendor
Employee Table
Employee Name String Name of the Employee
Birth Date Date (dd/mm/yyyy) Date of Birth of Employee
Contact Number Int Contact number of the customer
Employee Address Varchar (50) Address of Employee
Employee Designation String Post of the Employee
PPS Number Int Personal public service number of the Employee
Password Varchar (12) Password for employee
Employee_ID Int not null Primary Key for Employee Registration Table

20
4.4. Process Control Features
• Employee details are registered into the Employee Table once the employee is hired for the job, default employee id and password are
created.
• Depending on the designation of the employee, he is given access for different levels.
• An employee with a basic access includes access to Customer, Sales, Product Master Details.
• Once a customer enquires for a medicine, the employee first checks for its availability by checking quantity of the stock in the Product
Master object. If available, he gives the medicine to the customer.
• The customer details are entered in the Customer object table by the employee.
• Invoice is generated and the details are stored in the sales object table.
• Detailed explanation of level of access to different employees is explained in the next section.
• Inventory management is handled using the two objects Product Master, Purchase and Vendor.

21
5. Project Architecture
Project implementation has been done using the Salesforce platform. We have designed custom
objects like Customer, Vendor, Product Master etc.
5.1. Implementation Architecture:
The basic architecture of our Sales Force project consists of the elements like Data Structures,
Custom Objects, Workflows, Email triggering etc. In below screen shot you can see some of the
objects. The details of all the built-in objects are discussed here.
Many custom objects are created for storing the data. We have opted for creating the Custom
Object because we have to define the relationship between them and used them for calculations.it
can be more complex in future So Custom object will be more suited for our project. The Custom
Object behave like the Database which stores the values.
5.1.1. Custom Objects:
Below are the Custom Objects which are created for the project to store the data for our MedCure
Store. Many objects are related to the other objects using the Look-up field in the Object.
Fig5.1.1 Custom Objects

22
5.1.2. Custom Fields:
We have also used the Contact to store some of the Customer related data. A detailed information
about the customer is added to the Contacts fields. We have added some of the Custom fields to
store detailed information about the Customer. Below screen shot consist of Custom fields added to
the Contacts.
Fig5.1.2 Contact Custom Fields & Relationships
5.1.3. View Users within Application:
The Administrator perform task like creating and Editing the Users. The users in the company are the
employee like Manager, IT specialist, Team Leads etc. The people who want to access the records for
the company. The level of the Users decides what type of access are needed to assign the Users and
what types are Access needs to be granted to the Users. Below is the screen shot which consist of
the users which we had created for our MedCure App.

23
Fig5.1.3 User Access
5.1.4. Create new Product Record:
The below screen shot is the input screen for the Product Master Data. The fields highlighted in red
are the mandatory fields. We have created the many of the fields as mandatory because we don’t
want to make meaningless entry in the table. We added the validation for the fields Quantity and
Expiry Date. For Quantity if negative value inserted it will throw the error message. For expiry data
the validation is that it can be a future date and Current date but it cannot have an entry with a date
in the past. If a past date is entered it will throw the error message.
Fig5.1.4 New Product Master

24
5.1.5. Create New Purchase Record:
The purchase fields consists of all the field mandatory. The Custom object Purchase consist of the
record purchase done by the company till date. Field Purchase date has a validation that any
employee cannot create a new entry in system with a purchase date in the past. Also the quantity
field should have only positive values. So the Purchase date will not accept any past dates and
quantity will not accept any negative value.
Fig5.1.5 New Purchase Record

25
5.1.6. Create New Sales Record:
The Custom Object consist of the records of the Sales done by the stores. All the fields are mandatory
in the table. The Object consist of the values like Sales Date, Quantity, Sale Rate, Product Name,
Customer Name. The field Sale date has validation that it cannot be past date. This object contains
two lookup fields – one is the product name that references the product master data and the second
one customer name which references the customer object. Selection of any particular product or
customer using lookup will also create another transaction record in the respective objects.
Fig5.1.6 New Sales Record
5.1.7. Create New Customer Record:
The customer object consists of two fields – the name of customer and mobile number. Since our
system is designed for a retail store, we are able to capture only these two fields from the customer
during the purchase. This will provide an insight into the past orders of the customer and thereby
help the manager in segregating customers based on their preferences and previous orders.

26
Fig5.1.7 New Customer Record
5.1.8. Create new Vendor record:
The vendor object consists of several fields like the vendor name, vendor address, number and bank
details. For the restocking of sold products we need to raise the Purchase orders. We have a vendor
database from whom we purchase our products. In order to add new vendor in system, we are
making use of this object. Through reports, the store manager can visualize the spend on each
vendor and the products being purchased, this will help the manager in key decision making.
Fig5.1.8 New Vendor Record

27
5.1.9. Create new Employee Registration Record:
The Custom Object Employee Registration stores the Employee details. The Employee Registration
consist of the following fields Employee Name, Employee Designation, Birthdate etc.
The fields highlighted in red are the Mandatory fields for the Registering the employees to the Firm.
The Validation for the field Email has been done like a valid mail Id should be entered if the Mail ID is
not valid it will throw the error message to the user.
The Email and password field entered by the Employee for the first time of registering are stored
and validate every time the user try to login to the System.
Fig 5.1.9 New Employee Registration Object
5.2. Data Fields:
5.2.1. Customer Data:
The below screen shot shows the data which loaded in the Customer table. This data shows us the
existing customers of our retail store. They are present in system as a result of any past purchase
from the store.

28
Fig5.2.1 Customer Data fields
5.2.2. Sales Data:
The below screen shot show the data available in the Sales Custom Table. This data shows us the
products that have been sold in the past along with the quantity, price and the customer who
purchased the product. Capturing this data is important because this will help the manager in
generating reports and understand which products have sold more and the associated revenue it has
generated.
Fig5.2.2 Sales Data Field

29
5.2.3. Product Master Data:
The Product Master consist of the data as shown in the below screenshot. This data represents the
products in the store and the available quantity and associated price. This is our master database,
any changes during purchase and sale will reflect in this data. For example, if a product is being sold
multiple times and the available quantity comes down below 30, it will create a trigger and send an
automatic email to the store manager and remind to restock the product.
Fig5.2.3 New Sales Record
5.2.4. Purchase Data:
This Purchase object consists of the following data as shown in the below screenshot. Several fields
have been captured during the process which can be used eventually for analysis and decision
making by store manager.

31
5.3. Validation and Triggers:
5.3.1. Sales Fields Validation:
Similar validation has been done for the Custom Object Sales. If the date is less then the current date
and quantity is negative value it will throw the Error message as shown in the below screen shot.
Fig5.3.1 Validation in Sales field.

32
5.3.2 Email Trigger:
An email notification will be sent to Store Manager if any quantity in the Store is running out of
stock. The product is considered out of stock if the quantity is less than 30.
Fig5.3.2 Email notification for low stock

33
5.3.2. Login:
This is our internal login page that can be accessed by the employees of the store. The email id and
password is verified with our employee registration table data and if matched correctly, provides
access to internal processes like product master, purchase, sales etc.
Fig5.3.2 Employee Login Portal

34
5.3.3. Login Logs:
These logs show us data of all past login attempts in system. Any erroneous entry can be tracked and
traced down by the store manager.
Fig5.3.3 Login History

35
5.3.4. Permission Sales Team:
As the roles are assigned according to the designation of the person in the Organisation. So below
screen shot show the access provided to the Sales Team. The action which a Sales Team can perform
on the System are like they can create a record, view a record and Edit the record but cannot Delete
the record.
Fig5.3.4 Employee Access

36
5.3.5. Permission IT manager:
Below screenshot shows the permissions granted to the IT manager. As visible, the IT manager has
the complete ownership of the objects as well as fields; like he can read, create, edit, delete, and
modify the records.
Fig5.3.5 Manager Access

37
5.3.6. Roles:
Below screenshot shows us the role hierarchy assigned in the system. As we can see the manager
controls and monitors the purchase team, sales team and the team lead.
Fig5.3.6 Designation Hierarchy

38
5.4. Reports:
The reports are based on the data that has been generated through past purchases and sales. These
reports are basically useful for gaining insights into the store’s business and derive key decisions out
of it.
5.4.1. Products purchased:
This report shows us which products are purchased the most and also the frequency of purchase.
This report can be further drilled down on the basis of the spend value on each product.
Fig5.4.1 Purchased Products Dashboard

39
5.4.2. Top vendors:
This report shows us the top vendors from whom the store is getting their products from. We can
also compare the price of a product with several vendors to see which vendor is selling us at lowest
price.
Fig5.4.2 Top Vendors Dashboard

40
5.4.3. Customer Product Sales:
This report shows us which product is frequently bought by the customers. Based on the product
purchase history, the stock can be refilled by the store manager. This will help in avoiding the loss
generated by keeping inventory of only those products that are sold frequently. This report can be
further drilled down to see the contribution of each product to the total sales revenue generated.
Fig5.4.3 Product Sales Dashboard

41
5.4.4. Top customers:
This report provides us insights into the top customers of the store and the products that they have
bought from the store. The store manager can understand from the report which customers are
valuable to the store’s business and can devise marketing strategies to improve the sales.
Fig5.4.4 Top Customers Dashboard
6. Operational Benefits
• A robust CRM solution with almost no development cost.
• The solution is user friendly and it’s very easy to understand the functionality of the
CRM.
• The solution provides various levels of accessibility to the employee depending on
the employee’s designation.

42
• The solution is designed in such a way that multiple users can access it
simultaneously.
• Entire store process is automated and manual labour is reduced to minimum this
results in minimizing errors.
• Live reports and visualisations can be generated which adds the analytics aspect to it
that helps in making better business decisions.
7 Future Work
The retail business has been completely incorporated onto the salesforce platform. This will
not only reduce manual labour but will also improve the profitability of the store. For further
enhancement in the business the e-commerce side of things should be taken into
consideration. An online presence by developing a website which accepts orders and makes
sales online will increase their profitability immensely.
Furthermore, mobile application development will make it easy for the customers to place
orders. This will increase the collection of customer data in the database. This data will later
help deduce strategies to increase the business.
8 References
Hayden, C. (2019) Course Notes: Strategic ICT & eBusiness Implementation: NCI. Available
at:https://moodle.ncirl.ie/course/view.php?id=1862 (Accessed: 22 October 2019).
Salesforce Developers Forums. (2019). DeveloperForce. [online] Available at:
https://developer.salesforce.com/forums/?id=9060G000000Xb3cQAC (Accessed 20 Apr. 2019)
Help.salesforce.com. (2019). Help | Training | Salesforce. [online] Available at:
https://help.salesforce.com/articleView?id=dashboards_add_component.htm&type=5
(Accessed 20 Apr. 2019)
Ramchandani, J. and Ghias, A. (2019). US7962361B2 - Customer relationship management
system for physical locations - Google Patents. [online] Patents.google.com.
Available at: https://patents.google.com/patent/US7962361B2/en [Accessed 20 Apr.
2019].

43
10 APPENDIX
Visusalforce Pages codes.
Login Page
<apex:page standardController="Employee_Registration__c" showheader="False">
<style>
@import url(https://fonts.googleapis.com/css?family=Exo:100,200,400);
@import url(https://fonts.googleapis.com/css?family=Source+Sans+Pro:700,400,300);
body{
margin: 0;
padding: 0;
background: #fff;
color: #fff;
font-family: Arial;
font-size: 12px;
}
.body{
position: absolute;
top: -20px;
left: -20px;
right: -40px;
bottom: -40px;
width: auto;
height: auto;
background-image: url(http://ginva.com/wp-content/uploads/2012/07/city-skyline-wallpapers-
008.jpg);
background-size: cover;
-webkit-filter: blur(5px);
z-index: 0;
}
.grad{
position: absolute;
top: -20px;
left: -20px;
right: -40px;
bottom: -40px;
width: auto;

44
height: auto;
background: -webkit-gradient(linear, left top, left bottom, color-stop(0%,rgba(0,0,0,0)), color-
stop(100%,rgba(0,0,0,0.65))); /* Chrome,Safari4+ */
z-index: 1;
opacity: 0.7;
}
.header{
position: absolute;
top: calc(50% - 35px);
left: calc(50% - 255px);
z-index: 2;
}
.header div{
float: left;
color: #fff;
font-family: 'Exo', sans-serif;
font-size: 35px;
font-weight: 200;
}
.header div span{
color: #5379fa !important;
}
.login{
position: absolute;
top: calc(50% - 75px);
left: calc(50% - 50px);
height: 150px;
width: 350px;
padding: 10px;
z-index: 2;
}
.login input[type=text]{
width: 250px;
height: 30px;
background: transparent;
border: 1px solid rgba(255,255,255,0.6);
border-radius: 2px;
color: #fff;
font-size: 16px;

45
font-weight: 400;
padding: 4px;
}
.login input[type=password]{
width: 250px;
height: 30px;
background: transparent;
border-radius: 2px;
color: #fff;
font-size: 16px;
font-weight: 400;
padding: 4px;
margin-top: 10px;
}
.login input[type=button]{
width: 260px;
height: 35px;
background: #fff;
border: 1px solid #fff;
cursor: pointer;
border-radius: 2px;
color: #a18d6c;
font-size: 16px;
font-weight: 400;
padding: 6px;
margin-top: 10px;
}
.login input[type=button]:hover{
opacity: 0.8;
}
.login input[type=button]:active{
opacity: 0.6;
}
.login input[type=text]:focus{
outline: none;
}

46
.login input[type=password]:focus{
outline: none;
}
.login input[type=button]:focus{
outline: none;
}
::-webkit-input-placeholder{
color: rgba(255,255,255,0.6);
}
::-moz-input-placeholder{
color: rgba(255,255,255,0.6);
}
</style>
<apex:form >
<div class="body"></div>
<div class="grad"></div>
<div class="header">
<div><b>Medcure</b>
<br></br>
<span><b>Medical Management System</b></span></div>
<br></br>
<br></br>
<br></br>
<br></br>
<br></br>
<apex:inputField value="{!Employee_Registration__c.Email__c}" id="Contact" style="width:
250px;height: 30px;background: transparent;border: 1px solid rgba(255,255,255,0.6);border-radius:
2px;color: #fff;font-family: 'Exo', sans-serif;font-size: 16px;font-weight: 400;padding: 4px;margin-
top: 10px;" />
<br></br>
<br></br>
<apex:outputLabel Value="UserName" style="width: 250px;height: 30px;background:
transparent;color: #fff;font-family: 'Exo', sans-serif;font-size: 20px;font-weight: 400;padding:
4px;margin-top: 10px;" ></apex:outputLabel>
  
<br></br>

47
<br></br>
<apex:outputLabel Value="Password " style="width: 250px;height: 30px;background:
transparent;color: #fff;font-family: 'Exo', sans-serif;font-size: 20px;font-weight: 400;padding:
4px;margin-top: 10px;" ></apex:outputLabel>
  
<apex:inputsecret value="{!Employee_Registration__c.Password__c}" style="width:
250px;height: 30px;background: transparent;border: 1px solid rgba(255,255,255,0.6);border-radius:
2px;color: #fff;font-family: 'Exo', sans-serif;font-size: 16px;font-weight: 400;padding: 4px;margin-
top: 10px;" />
<br></br>
<br></br>
              
          
             
<apex:commandbutton onclick="return confirmSave();" style="width: 150px;height:
35px;background: #fff;border: 1px solid #fff;cursor: pointer;border-radius: 2px;color: #a18d6c;font-
family: 'Exo', sans-serif;font-size: 16px;font-weight: 400;padding: 6px;margin-top: 10px;"
action="{!save}" value="Employee Login"/>
</div>
</apex:form>
<script>
function confirmlogin()
{
return confirm("Welcome Home !");
}
public class ValidUI {
public String UserName {get; set;}
public String Password {get; set;}
public database__c fre{get; set;}
public PageReference login(){
if(UserName!=null & & Password!=null )
{
db= [select User_Name__c,Password__c from Employee_Registration__c ]
if(UserName==db.Email__c & & Password==db.Password__c)
{
pagereference ref = new
pagereference('https://c.ap1.visual.force.com/apex/ApplicationForm');
ref.setredirect(true);

48
}
else{
ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.INFO, 'TRY AGAIN... .'));
return null ;
}
}
}
</script>
</apex:page>
Employee Registration
<apex:page standardController="Employee_Registration__c" showheader="False">
/*
<style>
.employee {
background:-webkit-gradient(linear, left top, left bottom, color-stop(0.05, #599bb3), color-stop(1,
#408c99));
background:-moz-linear-gradient(top, #599bb3 5%, #408c99 100%);
background:-webkit-linear-gradient(top, #599bb3 5%, #408c99 100%);
background:-o-linear-gradient(top, #599bb3 5%, #408c99 100%);
background:-ms-linear-gradient(top, #599bb3 5%, #408c99 100%);
background:linear-gradient(to bottom, #599bb3 5%, #408c99 100%);
filter:progid:DXImageTransform.Microsoft.gradient(startColorstr='#599bb3',
endColorstr='#408c99',GradientType=0);
background-color:#599bb3;
-moz-border-radius:7px;
-webkit-border-radius:7px;
border-radius:7px;
display:inline-block;
cursor:pointer;
color:#ffffff;
font-family:Arial;
font-size:15px;
font-weight:bold;
padding:10px 25px;
text-decoration:none;
}
.employee:active {
position:relative;
top:1px;
}
</style>

49
<apex:pagemessages ></apex:pagemessages>
<apex:stylesheet value="http://netdna.bootstrapcdn.com/twitter-bootstrap/2.3.2/css/bootstrap-
combined.min.css"/>
<apex:form >
<apex:pageBlock >
<apex:image url="https://tushartd-dev-ed--
c.eu16.visual.force.com/resource/1555599070000/header2" width="1600" height="50"/>
<div align-content="center">
<table border='0' cellspacing='0' cellpadding='0'>
</table>
</div>
<apex:pageBlockSection showHeader="true" title="Employee Details" columns="1"
collapsible="False">
<apex:inputField onmousemove="changebg(this)" onmouseout="normalImg(this)"
value="{!Employee_Registration__c.Email__c}" style="width:300px;height:15px;"
Required="False"/>
value="{!Employee_Registration__c.PPS_Number__c}" style="width:300px;height:15px;"
Required="False"/>
value="{!Employee_Registration__c.Contact_Number__c}" style="width:300px;height:15px;"
Required="False"/>
value="{!Employee_Registration__c.Birthdate__c}" style="width:300px;height:15px;"
Required="False"/>
value="{!Employee_Registration__c.Employee_Designation__c}" style="width:300px;height:15px;"
Required="False"/>
value="{!Employee_Registration__c.Employee_Address__c}" style="width:300px;height:15px;"
Required="False"/>
value="{!Employee_Registration__c.Password__c}" style="width:300px;height:15px;"
Required="False"/>
</apex:pageBlockSection>
</div>
<div align="center">
<apex:commandbutton onclick="return confirmSave();" action="{!save}"
styleClass="employee" value="Submit"/>
</div>
</apex:pageBlock>
</apex:form>
*/
<script>

50
function confirmSave()
{
return confirm("Thank you, New Record Updated!");
}
</script>
<script>
function changebg(x) {
x.style.backgroundColor = "lightgrey";
}
function normalImg(x) {
x.style.backgroundColor = "transparent";
}
</script>
</apex:page>
Home Page
<apex:page standardController="Contact" showheader="False">
combined.min.css"/>
<apex:form >
<apex:pageBlock >
</table>
</div>
<apex:pageBlockSection showHeader="true" title="PLEASE ENTER EMPLOYEE DETAILS"
columns="2" collapsible="False">
value="{!Contact.Firstname}" style="width:300px;height:15px;" Required="False"/>
value="{!Contact.Lastname}" style="width:300px;height:15px;" Required="True"/>

51
value="{!Contact.Email}" style="width:300px;height:20px;" Required="True"/>
value="{!Contact.Gender__c}" />
value="{!Contact.Gross_Pay__c}" style="width:300px;height:20px;" Required="True"/>
value="{!Contact.PPS_Number__c}" style="width:300px;height:20px;" Required="True"/>
</div>
<apex:commandbutton onclick="return confirmSave();" value=" SUBMIT "
action="{!save}" />
</div>
</apex:pageBlock>
</apex:form>
<script>
{
}
</script>
<script>
}
}
</script>
</apex:page>
Product Master
<apex:page standardController="Product_Master__c" showheader="False">
/*
<style>
.employee {
#408c99));

52
border-radius:7px;
cursor:pointer;
color:#ffffff;
font-family:Arial;
font-size:15px;
font-weight:bold;
padding:10px 25px;
}
.employee:active {
position:relative;
top:1px;
}
</style>
combined.min.css"/>
<apex:form >
<apex:pageBlock >
</table>
</div>
<apex:pageBlockSection showHeader="true" title="Enter Product Details" columns="1"
value="{!Product_Master__c.Manufacturer_Name__c}" style="width:300px;height:15px;"
Required="False"/>
value="{!Product_Master__c.Quantity__c}" style="width:300px;height:15px;" Required="False"/>
value="{!Product_Master__c.Purchase_Price__c}" style="width:300px;height:15px;"
Required="False"/>

53
value="{!Product_Master__c.Expiry_Date__c}" style="width:300px;height:15px;"
Required="False"/>
</div>
</div>
</apex:pageBlock>
</apex:form>
*/
<script>
{
}
</script>
<script>
}
}
</script>
</apex:page>
Customer History
<apex:page standardController="Customer_History__c" showheader="False">
/*
<style>
.employee {
#408c99));

54
border-radius:7px;
cursor:pointer;
color:#ffffff;
font-family:Arial;
font-size:15px;
font-weight:bold;
padding:10px 25px;
}
.employee:active {
position:relative;
top:1px;
}
</style>
combined.min.css"/>
<apex:form >
<apex:pageBlock >
</table>
</div>
<apex:pageBlockSection showHeader="true" title="Customer History" columns="1"
value="{!Customer_History__c.Customer_Name__c}" style="width:300px;height:15px;"
Required="False"/>
value="{!Customer_History__c.End_Date__c}" style="width:300px;height:15px;"
Required="False"/>
value="{!Customer_History__c.Start_Date__c}" style="width:300px;height:15px;"
Required="False"/>
</div>

55
</div>
</apex:pageBlock>
</apex:form>
*/
<script>
{
}
</script>
<script>
}
}
</script>
</apex:page>
Mass Delete Contact
<apex:page extensions="MassDeleteExtension" standardController="Contact"
recordSetVar="sobjects" standardStylesheets="false" sidebar="false" applyBodyTag="false"
docType="html-5.0">
<html xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<head>
<apex:stylesheet value="{!URLFOR($Resource.mdslds212, 'assets/styles/salesforce-
lightning-design-system-vf.css')}" />
</head>
<body>

56
<div class="mass-delete">
<div>
<div aria-hidden="false" aria-labelledby="prompt-heading-id" aria-describedby="prompt-message-
wrapper" role="alertdialog" class="slds-modal slds-modal--prompt slds-fade-in-open">
<div class="slds-modal__container slds-modal--prompt" role="document" id="prompt-message-
wrapper" tabindex="0">
<div class="slds-modal__header slds-theme--warning slds-theme--alert-texture">
<h2 class="slds-text-heading--medium" id="prompt-heading-id">Confirm Delete</h2>
</div>
<div class="slds-modal__content slds-p-around--medium">
<div>
<p>Are you sure you want to delete {!mySelectedSize} records?</p>
</div>
</div>
<div class="slds-modal__footer slds-theme--default">
<apex:form >
<apex:commandLink action="{!cancel}" value="" id="cancel">
<button class="slds-button slds-button--neutral">Cancel</button></apex:commandLink>
<apex:commandLink action="{!deleteRecords}" value="" id="delete">
<button class="slds-button slds-button--neutral">Delete Records</button></apex:commandLink>
</apex:form>
</div>
</div>
</div>
<div class="slds-backdrop slds-backdrop--open"></div>
</div>
</div>
</body>
</html>
</apex:page>

Pharmaceutical store management system

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Pharmaceutical store management system

Similar to Pharmaceutical store management system (20)

More from Shantanu Deshpande

More from Shantanu Deshpande (7)

Recently uploaded

Recently uploaded (20)

Pharmaceutical store management system