1

PROJECT REPORT

ON

ONLINE SHOPPING

PORTAL

Submitted By

Kiran Nadeem

Sana Zehra

Shumaila Fazal

Kapil Dev

Project Supervisor

SyedFarhanMazhar

2

SHOP’N GO

3

Online Shopping Portal

Under The Supervision Of

SYED FARHAN MAZHAR

PROJECT IS SUBMITTED FOR THE

PARTIAL FULFILLMENT OF

REQUIREMENT OF BACHELORS

DEGREE OF COMPUTER SCIENCE

IN YEAR

2016

THE UNIVERISTY OF

4

INSTITUTE OF BUSSINESS MANAGEMENT

FINAL REPORT

Online Shopping Portal

5

Index 1. INTRODUCTION

1.1. Overview of the project

1.2. Objective of the project

1.3. Scope of the project

2. THEORITICAL BACKGROUND

2.1. System Study

2.2. Existing System

2.2.1. Drawback of Existing System

2.3. Proposed System

2.3.1. Benefits of Proposed System

2.4. System Analysis & Design

3. SYSTEM IMPLEMENTAION

3.1. Methodology Adopted

3.2. Hardware and Software Specification

3.3. Technology used

3.3.1. Front End Development

3.3.2. Back End Development

4. COST AND BENEFIT ANALYSIS

Project Cost

5. DETAILED SOFTWARE LIFE CYCLE

5.1. Life Cycle Phases

6. DIAGRAMS

6.1. ERD DIAGRAM

6.2. DATA FLOW DIAGRAM

6.3. SYSTEM FLOW CHART

7. SCREENSHOTS

7.1. BACK END

7.2. FRONT END

7.3. SIGN UP

8. METHODOLOGY USED FOR TESTING

9. GUIDE MANUAL

6

1. INTRODUCTION

Online shopping is a form of electronic commerce which allows consumers

to directly buy goods or services from a seller over the Internet using a web

browser.

It may also be called an e-shop, e-store, or a virtual store where products

are being displayed for customers to choose from. Mobile commerce is

another form of e-commerce that describes purchasing from an online

retailer's mobile application. An online shop evokes the physical analogy of

buying products or services at a bricks-and-mortar retailer or shopping

center.

1.1 Overview of the project

Online shopping has revolutionized the business world by making everything

anyone could want available by the simple click of a mouse button.Shopping-

Go is an online shopping portal that will provide high quality products that

fulfills needs of all types of buyers.The system helps the customer to purchase

the products even without credit card through ‘Cash On Delivery’ services.It

includes sophisticated product and customer management module. It has an

efficient administrative control for ease of the administrator.

1.2 Objective of the project

Shoppin-go is A Centralized System that is developed to provide the customers

with product information within different categories. Our main objective is to

design a modern interactive interface instead of a formal user interface for

accessibility of our customers. This application is not only for the customers

but also for the e-store owner and their IT department for updating inventory

through their admin panel. Also this application allows online access to the

member for upcoming discounts and offers. Our aim is to develop easy to use

7

and efficient computerized system, which provides convenient dashboard

analytics and gives online access to all users globally.

1.3 Scope of the Project

The system focuses on those who run e-store business to sell their products.

The entire data will be easily accessible from anywhere to authorized

personnel. All sub-systems will be integrated with each other so that the

customer feels the ease over our huge inventory and easily keep track of all

units and learn about the most selling products. It shall perform the following

functions.

Storing information of each user

Highly secured, required username and password for login.

Can also buy as a Guest

Provide online access to all

Check validity of each member at the time of signing in

Members and their accounts will be managed timely

The system can run on all Operating Systems (windows, Mac, iOS,

Android)

8

2. THEORETICAL BACKGROUND As we are developing such an application for the very first time, we faced a little

difficulty in the beginning. Similar web based applications are already in the

market thus we tried to take deep literature review from available stuff, a brief

discussion was then carried out to study and examine the existing system and

their drawbacks so that we could come up with a system with least drawbacks.

Since we are implementing this application in a new environment and using

the present technologies, so to make it fast and efficient we need to understand

the application environment and the present technologies.

2.1 System Study

Before starting up with a new project it is necessary to understand and study

the problem of existing systems, therefore we gathered requirements from

different brandswhich helped us in finding alternative and better solution for

their problems.

2.2 Existing System

Existing system refers to the system which is being followed till now. Even

today most of the stores still follow the traditional brick and motor methodology

of selling up their products. It’s a "street-side" business that deals with its

customers face to face in an office or store that the business owns or rents. The

local grocery store and the corner bank are examples of "brick and mortar"

companies. Brick and mortar businesses can find it difficult to compete with

web-based businesses because the latter usually have lower operating

costs and greater flexibility.

9

2.2.1 Drawback of Existing System

i. Time consuming

ii. Difficult to find the record of member

iii. Updating and retrieval are deadly

iv. Lots of paper work create confusion and loss of records

v. Providing efficient customer service is difficult

vi. More operating cost

vii. Employee Costs

viii. Startup and Overhead Costs

2.3 Proposed System

Shoppin-Go is a user friendly web-based application. Members will be known of

the upcoming discounts and offers. They can easily access the site through a

web browser and even their mobile phones or tablets and buy anything without

any limitation of time and place. The system is very simple in design and

implementation.

2.3.1 Benefits of proposed system

i. Increase efficiency

ii. Reduces the cost.

iii. Administrator controls the entire system.

iv. Security of data.

v. Helps in keeping record of each members

vi. No additional cost

vii. Remote Access

viii. Centralized Data

10

2.4 SYSTEM ANALYSIS & DESIGN

The way that is followed while carrying on with the development of the

application is as follows

Phase I (defining a problem)

Defining a problem is one of the foremost activity of establishing the baseline of

the project. The objective is to define precisely the business problem to be

solved & thereby determine the scope of the new system. This phase consist of

2 main tasks.

Review the organization needs that originally initiated the project.

Identify, at an abstract or general level, the expected capabilities of the

new system.

Thus, it helps us to define the goal to be achieved & the boundary of the

system. A clear understanding of the problem will help us in building a better

system & reduce the risk of project failure. Italso specifies the resources that

have to be made available to the project.

Three important factors project goal, project bounds and the resource limits are

sometimes called the project’s term of reference.

Phase II (feasibility study):

The first study aspect is whether the current project is technically

feasible i.e. whether the project be carried out with the current

equipment, existing software and available personnel. If new technology

is required than what is the likelihood that it can be developed?

The second study aspect is whether the project is economically feasible

i.e. are there sufficient benefits in creating the system to make the cost

acceptable. Are the costs of not creating the system so great that the

project must be undertaken?

The third study aspect is whether the project is operationally feasible or

not i.e. whether the system will be used if it is developed and

11

implemented? Project is worth developing only if it can meet institutions

operating requirements.

The fourth study aspect is always resistance, initially to any change in

the system is aimed at reliving the work load of the users to extent the

system is going to facilitate user to perform operations like calculating

total cost and discount deductions. Thus there is no reason to make

system socially unfeasible.

Fourth study is the operational feasibility that is obtained by consulting

with the system users. Check that proposed solution satisfies the user

needs or not. There is no resistance from the customer since new system

is helpful. The existing system is manual system, while the new system is

computerized and extremely user friendly.

Software details of the proposed system:

Front End:- HTML,CSS,JAVASCRIPT

Back End :- MYSQL version 5.5

The feasibility study proposes one or more conceptual solutions to the problem

set for the project. The objective in assessing feasibility is to determine whether

a development project has a reasonable chance of success. It helps us to

determine the input and output of the system. The following are the criteria

that are considered to confirm the project feasibility.

Phase III (System Analysis):

The phase is detailed appraisal of the existing system. This appraisal includes

how the system works and what it actually offers. It also includes finding out

more detail- what are the problems with the system and what user requires

from the system or any new change in the system.

The output of this phase results in detail model of the system. The model

describes the system functionsand system information flow. The phase also

contains the detail set of user requirements are used to set objectives for new

system.

12

System study:

It is always necessary to study and recognize the problems of the existing

system, which will help in finding out the requirements for new system. System

study helps in finding different alternatives for better solution.

The project study basically deals with different operations and steps involved in

generation of total sales. It includes:

1. Data gathering

2. Study of existing system

3. Analyzing problem

4. Studying various documents

5. Feasibility study for further improvements

Following are the steps taken during the initial study:

Initially, we gathered information through surveying, which the customers had

to displayon thee-store. Then we studied the working of the current system

which is manually done. We noted the limitations of the system which

motivated the customers to favor the new system. With the help of these

documents we got basic ideas about the system as well as input & output of

the system.

13

3. SYSTEM IMPLEMENTATION

3.1 Methodology Adopted:

The waterfall model is a sequential design process, used in software

development processes, in which progress is seen as flowing steadily

downwards (like a waterfall) through the phases of conception, initiation,

analysis, design, construction, testing, production/implementation and

maintenance. The product is defined as finished when it satisfies all of its

requirements.

The purpose of this web based application is to provide best information

management system which could fulfill the requirements an online shop like

the one we are creating.

Why Waterfall Mode:

We chose waterfall model for our project as

o Requirements are were pretty clear

o There were no ambiguous necessities.

o Ample resources with required expertise were available

o Technology was well understood

o Product definition is stable

o Low overhead of the methodology compared to other methodologies

Advantages:

o This model is simple and easy to understand and use.

o It is easy to manage due to the rigidity of the model – each phase has

specific deliverables and a review process.

o In this model phases are processed and completed one at a time. Phases

do not overlap.

o Waterfall model works well for smaller projects where requirements are

very well understood.

14

o Waterfall model is simple to implement and also the amount of resources

required for it are minimal.

o In this model, output is generated after each stage , therefore it has high

visibility. The client and project manager gets a feel that there is

considerable progress.

o Project management, both at internal level and client's level, is easy

again because of visible outputs after each phase. Deadlines can be set

for the completion of each phase and evaluation can be done from time to

time, to check if project is going as per milestones.

o This methodology is significantly better than the haphazard approach to

develop software. It provides a template into which methods of analysis,

design, coding, testing and maintenance can be placed.

o This methodology is preferred in projects where quality is more important

as compared to schedule or cost.

Tasks Involved :

1. Communication: helps to understand the objective.

2. Planning: required as many people (software teams) work on the same

project but different function at same time.

3. Modeling: involves business modeling, data modeling, and process

modeling.

4. Construction: this involves the reuse software components and

automatic code.

5. Deployment: integration of all the increments.

15

3.2 HARDWARE AND SOFTWARE SPECIFICATION

Hardware specification

•To access this system PC,MAC or TABLET PCs are required

•Strong internet connection as it is web based application

Software specification

• It is platform independent web application, so it would be running on

windows, MAC, iOS or android

• Supported internet browsers

o Google Chrome

o Internet Explorer

o Mozilla Firefox

o Safari

o Opera

16

3.3 TECHNOLOGIES USED

3.3.1 FRONT-END DEVELOPMENT

For front-end interface development we would be using

HTML5

CSS3

JAVASCRIPT

AJAX

JQUERY

Bootstrap

3.3.2 BACK-END DEVELOPMENT

For back-end programming and database integration we would use

PHP

MYSQL

PHP

PHP makes it easy to develop websites that reflect the current state of user

engagement. PHP, or Hypertext Preprocessor, is a server-side open source

scripting language that is used to help improve and facilitate web

development. Currently, 82% of websites use PHP as their server-side

scripting language. PHP is adopted among web developers because it is easy

to read and understand. Compared to other complex programming

languages, PHP is very clean, eloquent, and organized. PHP works well with

other languages and services such as HTML, CSS, as well as various

databases. PHP scripts can have tags, which makes it easy to insert and mix

between HTML tags, enabling web content to be highly dynamic. Since PHP

is written between tags, code and functions can be written in any order

within a document. This eliminates the need to manage and make sure your

code is in the right place.

17

MySQL

MySQL is the world’s most popular open source database, enabling the cost-

effective delivery of reliable, high-performance and scalable Web-based and

embedded database applications. A unique storage-engine architecture allows

database professionals to configure the MySQL database server specifically for

particular applications, with the end result being amazing performance results.

Whether the intended application is a high-speed transactional processing

system or a high-volume web site that services a billion queries a day, MySQL

can meet the most demanding performance expectations of any system.

18

4. COST AND BENEFIT

ANALYSIS Cost Estimation – Factors

Hardware and Software Costs

Maintenance Cost

Shipment costs

Training Cost

Effort costs

Facilities

Social Security

Project Cost

Direct Costs

o Technical Expertise Cost (Wages)

o Development costs (Software costs)

o Domain and Hosting Cost

o Running cost (Maintenance)

Indirect Costs

o Administration Cost (Wages)

o Electricity Cost

o Accommodative cost (rental, office space/room)

o Other overheads

19

5. DETAILED SOFTWARE LIFE

CYCLE

Requirement Gathering

This is the first step where the user initiates the request for a desired software

product. He contacts the service provider and tries to negotiate the terms. He

submits his request to the service providing organization in writing.

This step onwards the software development team works to carry on the

project. The team holds discussions with various stakeholders from problem

domain and tries to bring out as much information as possible on their

requirements. The requirements are contemplated and segregated into user

requirements, system requirements and functional requirements. The

requirements are collected using a number of practices as given –

Studying the existing or obsolete system and software,

Conducting interviews of users and developers,

Referring to the database or

Collecting answers from the questionnaires

20

Feasibility Study

After requirement gathering, the team comes up with a rough plan of software

process. At this step the team analyzes if a software can be made to fulfill all

requirements of the user and if there is any possibility of software being no

more useful. It is found out, if the project is financially, practically and

technologically feasible for the organization to take up. There are many

algorithms available, which help the developers to conclude the feasibility of a

software project.

System Analysis

At this step the developers decide a roadmap of their plan and try to bring up

the best software model suitable for the project. System analysis includes

Understanding of software product limitations, learning system related

problems or changes to be done in existing systems beforehand, identifying and

addressing the impact of project on organization and personnel etc. The project

team analyzes the scope of the project and plans the schedule and resources

accordingly.

Software Design

Next step is to bring down whole knowledge of requirements and analysis on

the desk and design the software product. The inputs from users and

information gathered in requirement gathering phase are the inputs of this

step. The output of this step comes in the form of two designs; logical design

and physical design. Engineers produce meta-data and data dictionaries,

logical diagrams, data-flow diagrams and in some cases pseudo codes.

Coding

This step is also known as programming phase. The implementation of

software design starts in terms of writing program code in the suitable

programming language and developing error-free executable programs

efficiently.

21

Testing

An estimate says that 50% of whole software development process should be

tested. Errors may ruin the software from critical level to its own removal.

Software testing is done while coding by the developers and thorough testing is

conducted by testing experts at various levels of code such as module testing,

program testing, product testing, in-house testing and testing the product at

user’s end. Early discovery of errors and their remedy is the key to reliable

software.

Integration

Software may need to be integrated with the libraries, databases and other

program(s). This stage of SDLC is involved in the integration of software with

outer world entities.

Implementation

This means installing the software on user machines. At times, software needs

post-installation configurations at user end. Software is tested for portability

and adaptability and integration related issues are solved during

implementation. In the Software Development Life Cycle, the actual code is

written here, and if the system contains hardware, then the implementation

phase will contain configuration and fine-tuning for the hardware to meet

certain requirements and functions.

In this phase, the system is ready to be deployed and installed in customer’s

premises, ready to become running, live and productive, training may be

required for end users to make sure they know how to use the system and to

get familiar with it, the implementation phase may take a long time and that

depends on the complexity of the system and the solution it presents.

Operation and Maintenance

This phase confirms the software operation in terms of more efficiency and less

errors. If required, the users are trained on, or aided with the documentation

on how to operate the software and how to keep the software operational. The

software is maintained timely by updating the code according to the changes

taking place in user end environment or technology. This phase may face

challenges from hidden bugs and real-world unidentified problems.

22

6. DIAGRAMS

6.1 Entity Relationship Diagram (ERD)

An entity-relationship diagram—otherwise known as an ERD—is a data

modeling technique that creates an illustration of an information system's

entities and the relationships between those entities. It is a graphical

representation of entities and their relationships to each other, typically used

in computing in regard to the organization of data within databases or information

systems. An entity is a piece of data-an object or concept about which data is

stored.

An ERD is a data modeling technique that can help define business processes and

can be used as the foundation for a relational database. While useful for

organizing data that can be represented by a relational structure, an entity-

relationship diagram can't sufficiently represent semi-structured

or unstructured data, and an ERD is unlikely to be helpful on its own in

integrating data into a pre-existing information system.

Three main components of an ERD are the entities: which are objects or

concepts that can have data stored about them, the relationship: between

those entities, and the cardinality: which defines that relationship in terms of

numbers.

For example, an ER diagram representing the information system for a

company's sales department might start with graphical representations of

entities such as the sales representative, the customer, the customer's address,

the customer's order, the product and the warehouse. Then lines or other

symbols can be used to represent the relationship between entities, and text

can be used to label the relationships. Finally, cardinality notations define the

attributes of the relationship between the entities. Cardinalities can denote that

an entity is optional.

23

24

Entity:

In a database model, each object that you wish to track in the database is

known as an entity. Normally, each entity is stored in a database table and

every instance of an entity corresponds to a row in that table. In an ER

diagram, each entity is depicted as a rectangular box with the name of the

entity contained within it.

For example, a database containing information about individual people would

likely have an entity called Person. This would correspond to a table with the

same name in the database and every person tracked in the database would be

an instance of that Person entity and have a corresponding row in the Person

table. Database designers creating an E-R diagram would draw the Person

entity using a shape similar to this:

The process to create a rectangular box would then be repeated for each entity

in the data model.

Attributes:

In general, an attribute is a property or characteristic. Color, for example, is an

attribute of your hair. In using or programming computers, an attribute is a

changeable property or characteristic of some component of a program that can

be set to different values.

Tracking entities alone is not sufficient to develop a data model. Databases

contain information about each entity. This information is tracked in individual

fields known as attributes, which normally correspond to the columns of a

database table.

For example, the Person entity might have attributes corresponding to the

person's first and last name, date of birth, and a unique person identifier. Each

of these attributes is depicted in an E-R diagram as an oval, as shown in the

figure below:

25

Domain:

Domain refers to the description of an attribute's allowed values. The

physical description is a set of values the attribute can have, and the semantic,

or logical, description is the meaning of the attribute.

Key:

Further, for each entity set we choose a key. A keyis a minimal set of attributed

whose values uniquely identify an entity in the set. There could be more than

one candidate; if so we designate one of them as primary key.

ENTITIES

Membership Types

Authorization

Subscription

User Registration

26

ENITITIES

27

28

29

30

ERD Diagram for Shopping Go

31

6.2 Data Flow Diagram

A data flow diagram (DFD) illustrates how data is processed by a system in

terms of inputs and outputs. As its name indicates its focus is on the flow of

information, where data comes from, where it goes and how it gets stored.

A DFD describes what data flows rather than how it is processed. Everyone

working on a development project can see all aspects of the system working

together at once with DFD. A non-technical person can also easily understand

a Data Flow Diagram. This is one of the main reason for its popularity.

32

Context Level Diagram

A context diagram is a data flow diagram, with only one massive central

process that subsumes everything inside the scope of the system. It shows how

the system will receive and send data flows to the external entities involved. In

other words, a system context diagram (SCD) in software engineering and

systems engineering is a diagram that defines the boundary between

the system, or part of a system, and its environment, showing the entities that

interact with it. This diagram is a high level view of a system. It is similar to

a block diagram.It is also called as Level 0 DFD. The context diagram provides

a good overview of the scope of the system, showing the system in “context” but

it does not show any detail about the processing that takes place inside the

system.

33

6.3 SYSTEM FLOW CHART

FLOW CHART:

To understand the system well the flow chart are required.

With help of flow chart it will be easy to understand the input and output of

the system which is very helpful in next stages of development of software.

34

35

36

7.SCREENSHOTS

7.1 BACK – END

37

7.2 FRONT – END

38

7.3 SIGN – UP

39

8. METHODOLOGY USED FOR

TESTING Software testing methodologies are the different approaches and ways of

ensuring that a software application is fully tested. Software testing

methodologies encompass everything from unit testing individual modules,

integration testing an entire system to specialized forms of testing such as

security and performance.

Importance of Testing Methodologies

As software applications get ever more complex and intertwined and with the

large number of different platforms and devices that need to get tested, it is

more important than ever to have a robust testing methodology for making

sure that software products/systems being developed have been fully tested to

make sure they meet their specified requirements and can successfully operate

in all the anticipated environments with the required usability and security.

40

It’s a complete solution that includes requirement management,

test , release management and defect tracking all fully integrated from

day one.

Highly intuitive web application that provides a complete picture of a

project’s status and health yet requires only a web-browser.

Ability to leverage your existing technology investments.

Functional Testing

The functional testing part of a testing methodology is typically broken down

into four components - unit testing, integration testing, system testing and

acceptance testing – usually executed in this order. Each of them is described

below:

Unit Testing

The Unit testing part of a testing methodology is the testing of individual

software modules or components that make up an application or system. These

tests are usually written by the developers of the module and in a test-driven-

development methodology (such as Agile, Scrum or XP) they are actually

written before the module is created as part of the specification. Each module

function is tested by a specific unit test fixture written in the same

programming language as the module.

Integration Testing

The Integration testing part of a testing methodology is the testing of the

different modules/components that have been successfully unit tested when

integrated together to perform specific tasks and activities (also known as

scenario testing). This testing is usually done with a combination of automated

functional tests and manual testing depending on how easy it is to create

automated tests for specific integrated components.

41

System Testing

The system testing part of a testing methodology involves testing the entire

system for errors and bugs. This test is carried out by interfacing the hardware

and software components of the entire system (that have been previously unit

tested and integration tested), and then testing it as a whole. This testing is

listed under the black-box testing method, where the software is checked for

user-expected working conditions as well as potential exception and edge

conditions.

Acceptance Testing

The acceptance testing part of a testing methodology is the final phase of

functional software testing and involves making sure that all the

product/project requirements have been met and that the end-users and

customers have tested the system to make sure it operates as expected

and meets all their defined requirements.

Non-Functional Testing

In most testing methodologies, functional testing involves testing the

application against thebusiness requirements. Functional testing is done using

the functional specifications provided by the client or by using the design

specifications like use cases provided by the design team.

On the other hand, non-functional testing involves testing the application

against the non-functional requirements, which typically involve

measuring/testing the application against defined technical qualities (also

known as the ‘-ilities’ because they all end in ‘-ility), for example: vulnerability,

scalability, usability. Some examples of non-functional testing are described

below:

Previously, security was something that was tested after-the-fact. With the rise

in cyber-crime and the awareness of the risks associated with software

vulnerabilities, application security is now something that needs to be designed

42

and developed at the same time as the desired business functionality. Security

testing tests the software for confidentiality, integrity, authentication,

availability, and non-repudiation. Individual tests are conducted to prevent any

unauthorized access to the software code.

Usability Testing

The usability testing part of a testing methodology looks at the end-

user usability aspect of the software. The ease with which a user can access

the product forms the main testing point. Usability testing looks at five aspects

of testing, - learnability, efficiency, satisfaction, memorability, and errors.

Compatibility Testing

The compatibility part of a testing methodology tests that the product or

application is compatible with all the specified operating systems, hardware

platforms, web browsers, mobile devices, and other designed third-party

programs (e.g. browser plugins). Compatibility tests check that the product

works as expected across all the different hardware/software combinations and

that all functionality is consistently supported.

43

9. GUIDE MANUAL

Step 1:

Type the name in the search box of a search engine such as Google – for

example, ‘shopping go’ – and click Search.

• Step 2: A new page will open, taking you to the website. You can now refine your

search by typing in keywords (for example ‘backpack’) in the search box,

which is at the top of the screen. Then click the magnifying glass next to

the search box.

• Step 3: All the related products will be shown on the screen. Click ADD TO CART

under the product that you want to purchase, doing this will save the

details of this item until you’re ready to purchase it.

44

Step 4: You’ll now be taken to your shopping basket, where you can choose to

‘view cart' or 'Continue Shopping'.

45

Step 5: If you wish to discontinue shopping for other items, you will need

click ‘View Cart’. A new page will then open that displays product details.

Step 6: If you are satisfied with the product details that you can ‘Checkout’ for

purchasing.

46

Step 7: Select the Checkout Method. (If you are a MEMBER enter you User ID

and Password or else you can checkout as GUEST). Then click ‘NEXT’.

• Step 8: Fill in the form and enter your billing details.

47

• Step 9: If your billing address is same as the shipping address then Click on the

green block. Your details will automatically be filled in this form.

• Step 10: Select your payment method and then click ‘NEXT’.

48

• Step 10:

Review the order summary and after satisfaction click on ‘Send Order’.

• Step 11:

If you have placed the order correctly then message will be displayed on

screen ‘ORDER EXECUTED WITH SUCCESS’.

49

• Step 12:

You will receive a confirmation mail for your order.

Email you’ll receive: