i

SMART RECEIPT WITH QR GENERATED POINT OF SALE SYSTEM

LUQMAN AL – HAKIM B AZHAR

BACHELOR OF COMPUTER SCIENCE (INTERNET COMPUTING)

FACULTY OF INFORMATICS AND COMPUTING

UNIVERSITI SULTAN ZAINAL ABIDIN

SEPTEMBER 2019

ii

DECLARATION

This dissertation is submitted as a partial fulfillment for the award or a Bachelor of Computer

Science (Internet Computing) with Honours at University of Sultan Zainal Abidin (UniSZA). The

results of this work are on my own investigations. All sections of text and results which have been

obtained from other sources are full referenced. I understand that cheating and plagiarism

constitute a breach of university regulations and will be dealt with accordingly.

Signature : …………………………………..

Name : LUQMAN AL – HAKIM B AZHAR

Date : ……………………………………......

iii

CONFIRMATION

This is to confirm that :

The project conducted and the report was under my supervision.

Signature : ……………………………………..

Name : DR. NUR FARRALIZA BT MANSOR

Date : ……………………………………..........

iv

DEDICATION

First of all, praise to Allah, the Most Gracious and the Most Merciful for blessing and giving me

the opportunity to undergo and complete my proposal for final year project, Smart Receipt with

QR generated Point of Sales System.

I would like to take this opportunity to express my heartiest gratitude to my supportive

supervisor, Dr. Nur Farraliza bt Mansor for her motivation, guidance and help throughout my

project. Without her time, her support and guidance, it is impossible for me to finish my project

successfully. Thank you for the kindness. May Allah bless her.

Besides, I would like to extend my appreciation to both of my parent, my family members

and all of my friends especially to Mohd Zulhilmi b Mohd Sofi that always been there in my hard

and easy times. May Allah protects and bless all of them.

Lastly, thank you to all my lecturers who taught me throughout my education from

Semester 1 until Semester 6 at University of Sultan Zainal Abidin (UniSZA). May Allah bless all

of them.

v

ABSTRACT

In recent years, smart devices have evolved from mere trends to becoming part of our daily

lives. As such devices are advanced with new technological advances in both software design and

hardware capabilities, system developers are looking for more innovative ways for users to

complete daily tasks for users. As our shopping habits change, so do our way of keeping the

shopping receipts. Before the advent of smart devices, keeping personal shopping receipts, through

the process of manual transactions using paper was very time consuming and costly. Instead, with

smart devices, records will be easily stored as digital data in easily accessible media. With this

"Smart Receipt with QR generated Point of Sales System" can help users and store owners to save

time and cost to print and save their shopping receipts just by scanning a QR code as a data transfer.

vi

ABSTRAK

Sejak beberapa tahun kebelakangan ini, peranti pintar telah meningkat dari sekadar trend

sehingga menjadi sebahagian kehidupan seharian kita. Oleh kerana peranti sedemikian maju

dengan kemajuan teknologi baru dalam kedua-dua reka bentuk perisian dan keupayaan

perkakasan, pembangun sistem mencari cara yang lebih inovatif bagi pengguna untuk

menyelesaikan tugas harian bagi pengguna. Apabila cara kebiasaan membeli-belah kita berubah,

begitu juga dengan cara kita menguruskan resit belanja. Sebelum munculnya peranti pintar,

menyimpan resit membeli-belah peribadi, melalui proses transaksi manual menggunakan kertas

amat memakan masa dan kos yang banyak. Sebaliknya, dengan peranti pintar, rekod akan

disimpan dengan mudah sebagai data digital dalam media yang mudah diakses. Dengan “Smart

Receipt with QR generated Point of Sales System” ini dapat membantu pengguna dan pemilik

kedai untuk menjimatkan masa dan kos untuk mencetak dan menyimpan resit belanja mereka

hanya dengan mengimbas kod QR sebagai pemindahan data.

vii

LIST OF CONTENTS

DECLARATION ii

CONFIRMATION iii

DEDICATION iv

ABSTRACT v

LIST OF CONTENTS vii

LIST OF FIGURES ix

LIST OF TABLE xi

LIST OF ABBREVIATIONS xii

CHAPTER 1 INTRODUCTION

1.1 Project Background 1

1.2 Problem Statement 2

1.3 Objectives 2

1.4 Scope 3

1.5 Expected Results 3

CHAPTER 2 LITERATURE REVIEW

2.1 Introduction 4

2.2 Overview with Current System 4-6

2.3 Added Value for The Proposed System 7

2.4 Chapter Summary 7

CHAPTER 3 METHODOLOGY

3.1 Introduction 8

3.2 Proposed Development Methodology 8-10

3.2.1 Requirement Gathering and Analysis 9

3.2.2 Quick Design 9

3.2.3 Build Prototype 10

3.2.4 User Evaluation 10

3.2.5 Refining Prototype 10

viii

3.2.6 Engineer Product 11

3.3 System Requirement 12

3.3.1 Software Requirement 12

3.3.2 Hardware Requirement 13

3.4 Process Model 14

3.4.1 Context Diagram 15

3.4.2 Data Flow Diagram (DFD Level 0) 16

3.4.3 Data Flow Diagram (DFD Level 1) 17-21

3.4.4 Entity Relationship Diagram (ERD) 22

3.5 Data Dictionary 23

3.5.1 Table of Admin 23

3.5.2 Table of User 23

3.5.3 Table of Product 24

3.5.4 Table of Cart 25

3.5.5 Table of QR 25

3.5.6 Table of Receipt 26

3.6 Summary 27

CHAPTER 4 PROTOTYPE

4.1 Point of Sales System Interface 28-32

4.2 Smart Receipt Interface 33-35

CHAPTER 5 CONCLUSION

5.1 Introduction 36

5.2 Project Contribution 36

5.3 Result Discussion 37

5.4 Project Limitations 37

5.5 Future Work 37

5.6 Conclusion 38

REFERENCES 39

ix

LIST OF FIGURES

FIGURE TITLE PAGE

2.1 Main Interfaces of Receipts by Wave 4

2.2 Main Interfaces of Monefy – Money Manager 6

3.1 Smart Receipt Context Diagram 15

3.2 Smart Receipt DFD Level 0 16

3.3 DFD User Account ( Level 1 ) 17

3.4 DFD Receipt ( Level 1 ) 18

3.5 DFD Admin ( Level 1 ) 19

3.6 DFD Cart ( Level 1 ) 20

3.7 DFD Product ( Level 1 ) 21

3.8 Smart Receipt ERD 22

4.1 Layout of Point of Sale System (Main Page) 28

4.2 Layout of Point of Sale System (Dashboard) 29

4.3 Layout of Point of Sale System (Add Product) 29

4.4 Layout of Point of Sale System (Edit and Delete Product) 30

4.5 Layout of Point of Sale System (Product List) 30

4.6 Layout of Point of Sale System (Product Cart) 31

4.7 Layout of Point of Sale System (Generate QR Code) 31

4.8 Layout of Point of Sale System (Report) 32

4.9 Layout of Smart Receipt Application (Main Page) 33

4.10 Layout of Smart Receipt Application (Register Account) 33

x

4.11 Layout of Smart Receipt Application (Home Page) 34

4.12 Layout of Smart Receipt Application (User Info) 34

4.13 Layout of Smart Receipt Application (Scan QR Code) 35

4.14 Layout of Smart Receipt Application (Receipt List) 35

xi

LIST OF TABLE

TABLE TITLE PAGE

2.1 Receipts by Wave Comparison 5

2.2 Monefy – Money Manager Comparison 6

3.1 Software Requirement 12

3.2 Hardware Requirement 13

3.3 Admin Table 23

3.4 User Table 23-24

3.5 Product Table 24

3.6 Cart Table 25

3.7 QR Table 25-26

3.8 Receipt Table 26

xii

LIST OF ABBREVIATIONS

QR Quick Respond

SDLC Software Development Life Cycle

ERD Entity Relationship Diagram

DFD Data Flow Diagram

CD Context Diagram

PHP Hypertext Preprocessor

HTML Hypertext Markup Language

CSS Cascading Style Sheets

1

CHAPTER 1

INTRODUCTION

1.1 PROJECT BACKGROUND

There are millions of purchases made by shoppers all over the world today and the

only way to prove that they indeed bought the goods has over the years often been through

a receipt that they are given upon payment. A large fraction of these receipts are printed on

paper for customers/shoppers. Generating all these bulky sets of receipts is an expensive

process to businesses, individual customers and the environment which therefore results in

the need for a way of storing these receipts in an integrated fashion. Paper-based receipts

are also easily lost, damaged and are cumbersome. Having the process of issuing the

receipts in a paperless form can address this problem.

Smart Receipt is a mobile application that provides a means for the user to get the

receipt and storing it straight away through a user account digitally; which businesses can

use to send a receipt instead of printing it. User just need to scan a QR code that is given

at shop and done ! The payment will be automatically done and they will get their receipt

digitally just on their mobile phone.

2

1.2 PROBLEM STATEMENT

Current paper-based receipt system has several drawbacks :

1. Users need to keep a large amount of paper receipts each time they shopping.

2. Users often lose their receipt if they want to return or make claim of their purchase

items.

3. Shop owner need to spend a lot of cost in printing the paper receipt.

1.3 OBJECTIVES

We have identified main objectives of the project. It can be identified as the following :

1. To analyze the current system features and problems before developing the new

proposed system.

2. To design the Smart Receipt system using the right model to make sure the system

was user friendly.

3. To develop the Smart Receipt system using QR code as a sensor feature to receive

the digital printed receipt.

3

1.4 SCOPE

1.4.1 User

The user of the system will be categorized into 2 level users as the following :

1. User Level 0 (Customer)

I. Use smartphone to scan the QR Code using the developed

application.

II. Get digital-generated receipt.

2. User Level 1 (Shop)

I. Use the developed Point Of Sale System to generate the QR Code.

II. Add, Update, Delete item into the system.

III. View customer transaction.

1.4.2 Place

Focus on entire Terengganu.

1.4.3 Project Scope

Use Android smart phone for this application.

1.5 EXPECTED RESULT

1. The shop able to cut down cost to buy paper to print the receipt.

2. The customer able to obtain and store their receipt smartly.

4

CHAPTER 2

LITERATURE REVIEW

2.1 INTRODUCTION

This chapter will continue with the discussion and idea from previous research, website,

application or article that related to the system. The idea previous resource or available resource

helps to achieve all the objectives of this application.

2.2 OVERVIEW WITH CURRENT SYSTEM

2.2.1 Receipts by Wave

Figure 2.1 : Main Interfaces of Receipts by Wave

5

Platform Advantages Disadvantages

• Mobile

Application

• Works even when it’s

not connected to the

Internet so you can

scan receipts anytime,

anywhere.

• The app syncs

automatically the next

time your device is

online.

• Manually added

transaction.

• Still use paper usage.

Table 2.1 : Receipts by Wave Comparison

6

2.2.2 Monefy – Money Manager

Figure 2.2 : Main Interfaces of Monefy – Money Manager

Platform Advantages Disadvantages

• Mobile

Application

• In this application

user can set their

spending by the

category.

• Transactions are added in

the form of notes.

• Does not support receipts

saving.

Table 2.2 : Monefy – Money Manager Comparison

7

2.3 ADDED VALUE FOR THE PROPOSED SYSTEM

Some added values have been applied to the proposed system where the enhancements are

made to improvise the current systems. In relation to the previous system will be added functions

such as:

• For shop

o It will have the Point of Sales system that will generate the QR Code for the

receipts sharing method.

• For Customer

o It will have the QR Code scanner that automatically get the digitaly

generated receipts saved in the application after scanning.

2.4 CHAPTER SUMMARY

Basically in this chapter several research have been done in order to have a deep

understanding of the method that is going to be implement in proposed application. Besides a

review of related existing systems also have been done at this chapter. From the existing system,

we can have an idea of how the proposed application can be developed so that it is functioning

well and beneficial to all user.

8

CHAPTER 3

METHODOLOGY

3.1 INTRODUCTION

This chapter will explain the details of methodology being used in a software development.

This project methodology is important because it helps to organize investigation in a scientific way

to overcome problems, structure, plan and control the process of developing an information

system. After system has been completely developed, it should be tested to make sure this system

achieves the objectives has been set.

3.2 PROPOSED DEVELOPMENT METHODOLOGY

For the development of this system, we will apply the prototyping model methodology.

This model was chosen because it is suitable to be applied when the detailed information related

to input and output requirement of the system is not available.

In this model, it is assumed that all the requirements of the system were not identified at

the start of the system development. This model allows the users to interact and experiment with

the working model of the system. This model will give the users an actual feel of the system. At

any stage, if the users were not satisfied with the prototype, it can be discarded and an entirely new

system can be developed.

9

3.2.1 Requirement Gathering and Analysis

During this phase, the existing system can be analyzed and all the requirements

needed for the system development are identified. Furthermore, the information regarding

the Smart Receipt system are gathered and studied. The finding was then summarized to

find the requirement of the system for the functional and non-functional requirement. Then,

the system will implement the requirement and uses the QR Code as a medium for the

sensor for data transfer.

3.2.2 Quick Design

For this phase, the Context Diagram (CD), Data Flow Diagram (DFD), and Entity

Relationship Diagram (ERD) including the framework were designed. These diagrams will

help us to understand the process flow of the system. It is not a detailed design and it’s only

includes the important aspect of the system which gave us an idea of the system to the user.

A quick design will help us on developing the system. This system will be developed as a

mobile and web-based system by using Android, PHP and MySQL.

10

3.2.3 Build Prototype

In this phase, the interface design was developed for the purpose of delivering the

data into the system. We used MySQL as a database to store data and bootstrap to design

the interface of the system. After that, the system was created and developed based on the

functionalities of the system requirement such as scan QR Code, viewing receipt, and

manage the wallet. The data or requirements obtained during this phase was transformed

into the design. The information gathered from the design was modified to form the system

prototype.

3.2.4 User Evaluation

For this phase, the system will be evaluated for testing whether the objective of the

system was achieved or not. The proposed system will then be presented to the users for

thorough evaluation of the prototype system to recognize its strength and weaknesses.

Comments and suggestions are collected from the users to improve the system.

3.2.5 Refining Prototype

This phase was important because any changes the users does in the evaluation

phase will be tested again. The system code, functionality and upgrades will be refined to

develop the new prototype with the information provided by the users. This process will

continue until the requirements specified by the users were met. When the users were

satisfied with the new developed prototype, a finalized system will be developed from the

basis of the final prototype system.

11

3.2.6 Engineer Product

In this final prototyping model phase, the finalized system will be evaluated

thoroughly and followed by the routine of maintenance of regular basis to prevent a large-

scale failure of the system and minimizing the system downtime. Finally, once the

evaluation was done for this system, it will be implemented.

12

3.3 SYSTEM REQUIREMENTS

To develop the system, there are two requirements needed which are software requirements

and hardware requirements. This is to ensure the smooth development of the project and for future

references. The software and hardware requirements for the system are:

3.3.1 Software Requirement

Software Description

Microsoft Word 2019

Microsoft Power Point 2019

Tools for viewing, editing and creating

documents and slide presentation.

Windows 10 Operating system used to house all the

application and tools.

XAMPP Server Create connection between Apache and

MySQL in local host server.

Draw Io Tool for drawing diagram.

Android Studio Used to code the program of the system

especially for android mobile application.

Visual Studio Code Used to code the program of the system

especially for web application.

Google Chrome Web browser used to run the localhost and

searching information.

Table 3.1 : Software Requirement

13

3.3.2 Hardware Requirement

Hardware Description

Laptop To develop the system, edit and view the

documents.

Processor Intel Core i5-5200U

Operating System Windows 10

Memory 12 GB RAM, used to store, transfer data file

and backup data

Printer To print out all the documents and files of the

system.

Table 3.2 : Hardware Requirement

14

3.4 PROCESS MODEL

The framework and design for Smart Receipt system such as context diagram (CD), data

flow diagram (DFD) level 0, level 1 and entity relationship diagram (ERD) are explained. Data

modelling is required to facilitate the interaction between system designer, programmer and end-

user. Making an early modelling can help to identify the needs, problem and possible solutions

during the project. All design in data modelling is focused because this data model will determine

on how the flow of the system. But the more importantly was the CD because it will show which

entities that interact with the system.

Process models are processes of the same nature that are classified together into the model.

One possible use of the process model is to prescribe how things could be done in contrast to the

process itself which is really what happens. A process model is roughly an anticipation of what

the process will look like. What the process shall be will determined during actual system

development.

15

3.4.1 Context Diagram

The context diagram in figure 3.1 shows the data flow for the Smart Receipt system

using QR Code. There are two main actors which were user (which is customer) and Point

Of Sales system (which is the shop). The context diagram shows the overall function of the

system. The customer only needs to scan the QR Code generated by the Point of Sales

system as the basic step when using this system to get their receipt record.

Figure 3.1 : Smart Receipt Context Diagram

16

3.4.2 Data Flow Diagram ( DFD Level 0 )

The Data Flow Diagram (DFD) is a graphical presentation of the data flow in the

system.

Figure 3.2 : Smart Receipt DFD Level 0

Figure 3.2 shows DFD Level 0 of Smart Receipt consist of seven process which is Manage User

Account, QR code, Manage Receipt, Manage Admin Account, Manage Cart, Manager Product

and Generate Report. There are two entities which is User and Point of Sales System which is

Admin. All the information will be stored in database which is User, QR, Receipt, Admin, Cart

and Product.

17

3.4.3 Data Flow Diagram ( DFD Level 1 )

For the DFD level 1, the diagram will show the detailed process involved in several process

in the system :

Figure 3.3 : DFD User Account ( Level 1 )

Figure 3.3 shows DFD Level 1 for User Account process. This process is specifically designed for

user. So user can create their account in process 1.1 with their requirement information. User also

need to login every time they want to start the application. User can update their account in process

1.2 with their new requirement information. User also can delete their account in process 1.3.

18

Figure 3.4 : DFD Receipt ( Level 1 )

Figure 3.4 shows DFD Level 1 for Receipt process. This process is designed for user. So user can

get and manage their receipt in process 3.1 after scanning the QR code. User also can delete their

receipt in process 3.2 if they don’t want to keep it.

19

Figure 3.5 : DFD Admin ( Level 1 )

Figure 3.5 shows DFD Level 1 for Admin process. This process is specifically designed for admin

of point of sales system. So admin can add their account in process 4.1 with their requirement

information. Admin need to login every time they want to start the application. Admin also can

update their account in process 4.2 with new requirement information.

20

Figure 3.6 : DFD Cart ( Level 1 )

Figure 3.6 shows DFD Level 1 for Cart process. This process is designed for admin to add product

into cart when customer buy it. So admin can add the product into the cart in the process 5.1 with

the product information. Admin also can delete the cart in process 5.2 if the customer doesn’t want

to buy the product.

21

Figure 3.7 : DFD Product ( Level 1 )

Figure 3.7 shows DFD Level 1 for Product process. This process is designed for admin to add new

product into database. So admin can add the new product in the process 6.1 with the requirement

information. Admin can update the product in process 6.2 with the new product requirement.

Admin also can delete the product in process 6.3.

22

3.4.4 Entity Relationship Diagram ( ERD )

Entity Relationship Diagram (ERD) is a specialized graphical form that shows the

relationship between the entities and the data in the database. ERD is important for creating a good

database design. It is also used as the high-level logical data model, which is helpful in developing

conceptual design for database. The elements involved in ERD are entity, attributes, and

relationship between entities.

Figure 3.8 : Smart Receipt ERD

23

3.5 DATA DICTIONARY

3.5.1 Table of Admin

Table 3.3 : Admin Table

Column Type Key Default Comment

id int Primary key Primary key for

admin

username varchar

email varchar

password varchar

date datetime Current_Timestamp

The table 3.3 above shows the table in database for admin. The tables consist of id, username,

email, password and date.

3.5.2 Table of User

Table 3.4 : User Table

Column Type Key Default Comment

user_id varchar Primary key Primary key for

user

user_name varchar

user_email varchar

user_password varchar

24

user_phone int

wallet int

user_date datetime Current_Timesatamp

The table 3.4 above shows the table in database for user. The tables consist of

user_id,user_name, user_email, user_password, user_phone, wallet and user_date.

3.5.3 Table of Product

Table 3.5 : Product Table

Column Type Key Default Comment

Product_id int Primary key Primary key for

product

Product_name varchar

Price Int

Quantity Int

Admin_id Int Foreign Key Foreign key for

admin

Product_date Datetime Current_Timestamp

The table 3.5 above shows the table in database for product. The tables consist of product_id,

product_name, price, quantity, admin_id and product_date.

25

3.5.4 Table of Cart

Table 3.6 : Cart Table

Column Type Key Default Comment

Bil int Primary key Primary key for

cart

C_productid Int

C_quantity Int

C_totalprice Int

Qr_id varchar Foreign Key Foreign key for

qr

The table 3.6 above shows the table in database for cart. The tables consist of bil, c_productid,

c_quantity, c_totalprice and qr_id.

3.5.5 Table of QR

Table 3.7 : QR Table

Column Type Key Default Comment

Qr_id varchar Primary key Primary key for

QR

Admin_id Int Foreign Key Foreign key for

admin

Total Int

26

Qr_date Datetime Current_Timestamp

The table 3.7 above shows the table in database for QR. The tables consist of qr_id, admin_id,

total and qr_date.

3.5.6 Table of Receipt

Table 3.8 : Receipt Table

Column Type Key Default Comment

Qr_Id Varchar Foreign key Foreign key for

qr

User_id Varchar

Total Int

Receipt_date datetime Current_Timestamp

The table 3.8 above shows the table in database for receipt. The tables consist of qr_id, user_id,

total and receipt_date.

27

3.6 SUMMARY

The most important thing to make sure the system development process run smooth is

methodology. There are many different software development methodology that is good to use to

develop a system. However, choosing the right methodology is important because it will affect the

work flow of the system development process. The project can be done in time if the right

methodology is used to develop a system. Finally, all phase in the methodology used are explained

straightly so that it can be understood easily.

In system modelling and design, the detail about the system data flow and entities involved

in the system is explained and all the module also being described completely from one module to

another. The Data Flow Diagram (DFD) design give an insight about the flow of the system and

the explanation about each flow easy to understand while the Entity Relationship Diagram (ERD)

and database design give a clear understanding on database of the system and relation between

each table.

28

CHAPTER 4

PROTOTYPE

4.1 POINT OF SALES SYSTEM INTERFACE

Figure 4.1 : Layout of Point of Sale System (Main Page)

Figure 4.1 shows the main page of Smart Point of Sales System. Here admin need to login with

registered username and password. If admin doesn’t have an account yet, they need to register it

first for the first time.

29

Figure 4.2 : Layout of Point of Sale System (Dashboard)

Figure 4.2 shows the dashboard for Smart Point of Sale System. There are 5 menu which is

Dashboard, Sales, Product List, Add Product and Report.

Figure 4.3 : Layout of Point of Sale System (Add Product)

Figure 4.3 shows the interface for adding product into the database. Admin need to insert product

detail such as product id, product name, product price and stock quantity to add the product.

30

Figure 4.4 : Layout of Point of Sale System (Edit and Delete Product)

Figure 4.4 shows interface of edit and delete product. Admin can update the product with new

requirement information, and also admin can delete the product.

Figure 4.5 : Layout of Point of Sale System (Product List)

Figure 4.5 shows list of added product that are insert into the database. Here admin can edit and

delete the product.

31

Figure 4.6: Layout of Point of Sale System (Product Cart)

Figure 4.6 shows interface for sales. Here admin can insert the product that the customer buy

based on the product id into the cart to make the sales. Then admin can checkout the sales.

Figure 4.7 : Layout of Point of Sale System (Generate QR Code)

Figure 4.7 shows the interface of generated QR code with receipt id after checkout from the

sales. Here customer can scan the QR code and get their receipt.

32

Figure 4.8 : Layout of Point of Sale System (Report)

Figure 4.8 shows the interface of report in Point of Sale System. Admin can view all transaction

that has been made and also can search all of transaction sort by date and by receipt id.

33

4.2 SMART RECEIPT INTERFACE

Figure 4.9 : Layout of Smart Receipt Application (Main Page)

Figure 4.9 shows main page for smart receipt application. User need to login with registered

email and password.

Figure 4.10 : Layout of Smart Receipt Application (Register Account)

Figure 4.10 shows interface for register account. User need to register account in order to use this

application.

34

Figure 4.11 : Layout of Smart Receipt Application (Home Page)

Figure 4.11 shows home page for smart receipt. Here there are 4 menu which h is Scan QR, Shop

Receipt, User Account and Add Money.

Figure 4.12 : Layout of Smart Receipt Application (User Info)

Figure 4.12 shows interface of user account. The registered user detail will be show here.

35

Figure 4.13 : Layout of Smart Receipt Application (Scan QR Code)

Figure 4.13 shows interface of scanning QR code after user click on Scan QR menu at the home

page.

Figure 4.14 : Layout of Smart Receipt Application (Receipt List)

Figure 4.14 shows interface of receipt list that user get after scanning the QR code. When user

click on the receipt list, user will see all of the product list that they bought.

36

CHAPTER 5

CONCLUSION

5.1 INTRODUCTION

This chapter will discuss a conclusion of this project and the content on this chapter are

summary for the whole of this project, project contribution, project limitation and some suggestion

for the future.

5.2 PROJECT CONTRIBUTION

Smart Receipt with QR generated Point of Sales System have been developed for user all

around Terengganu. It has achieved the objectives and scope of this project. Below is the list of

the achievements on this project :

i) Creating an application that can save user shopping receipt digitally on mobile.

ii) This application gave benefits to both user which is customers and also to the shop

owner in term of reducing the cost of paper printing.

37

5.3 RESULT DISCUSSION

Generally, this project have been carried out and follow the objectives that have

been explained in Chapter 1. This project has provides a solution for the customer and shop owner

in term of generating and capturing QR Code, replacing the traditional way of printing and

collecting the paper receipt. Besides, QR Code will keep data of customer receipt in the database,

from scanning the QR Code that the Point of Sales System generate.

5.4 PROJECT LIMITATIONS

There are few problems and limitations that occur throughout the development of these

project. The problems and limitation in conducting this study are :

i) This application can only run on android mobile phone.

ii) Payment on product still be made by cash on hand.

5.5 FUTURE WORK

Here is some suggestion that can be made to upgrade the system to be more efficient in

future work. Some suggestion that need to be considered area :

i) Re-construct the QR Code technique of generating dynamic QR Code.

ii) Adding new feature like e-wallet for mobile application which can pay and get digital

receipt when scanning the QR Code.

38

5.6 CONCLUSION

Smart Receipt with QR generated Point of Sales System is the application that focus on

generating and transferring the customer receipt digitally. Based on the previous study and

discussion with supervisor, the suitable approach that will be implement in this project is QR Code.

QR Code can ease the way of generating and transferring customer receipt on user mobile phone.

Hopefully, this application can help all user to get an efficient way of generating and storing

shopping receipt.

39

REFERENCES

[1.] Murphy, Patricia; Kallin, Randa; Grasso, Kyle; and Ramey, Taryn, "Proposal for

Implementation of an E-Receipt System and NonToxic Compostable Receipt Paper at UMass

Dining Facilities" (2017). Student Showcase. 23.

Retrieved from https://scholarworks.umass.edu/sustainableumass_studentshowcase/23

[2.] Hines, W. (2013). Going paperless: The hidden cost of a receipt. The Huffington Post.

Retrieved from http://www.huffingtonpost.com/will-hines/going-paperless

[3.] Chukwudi Kingsley Williams, (2017). Online Invoice Management System Software as a

Service

[4.] Ali N. Adapting e-invoicing: benefits, challenges and future strategies to overcome challenges

[online]. Vaasa, Finland: Vaasan Ammattikorkeakoulu; 29 February 2016. URL:

https://publications.theseus.fi/bitstream/handle/10024/108392/Ali_Nazish.pdf?sequence=1.

[5.] Moghe, S. (2018). Everyone wants Digital Receipts, So Why Is the Retail Industry Not

Adopting It? Hackernoon.

Retrieved from https://hackernoon.com/digital-receipts-in-retail-b415fbdfde3f

[6.] Green America. (2019). Skip the Slip to Reduce Paper Receipts.

Retrieve from https://greenamerica.org/skiptheslip

https://scholarworks.umass.edu/sustainableumass_studentshowcase/23http://www.huffingtonpost.com/will-hines/going-paperlesshttps://hackernoon.com/digital-receipts-in-retail-b415fbdfde3f

40

APPENDIX

GANTT CHART FINAL YEAR PROJECT 1

GANTT CHART FINAL YEAR PROJECT 2

TASKS W1 W2 W3 W4 W5 W6 W7 W8 W9

Installation and configuration of

Android Studio

Setup PHP for Admin page.

Project progress and panel’s

evaluation

Create function for Point of Sale

System

Development of application using

Android Studio

Final project presentation

Thesis draft submission to

supervisor

Final thesis submission.