This example will demonstrate how to create a Point of Sale (POS), how it operates, and its performance.

# 1 Introduction

The NIXIP company (used here as a fictional example) is a multinational based in the sports industry. Aside from a few operations, the main part of the business concerns wholesale to other companies. The company sells the latest athletic products leading the market.

As can be imagined, the sales team is one of the most important areas of the company. In this example, followup will be performed on the sales team employees: representatives who visit or contact clients to sell products.

# 2 POS Configuration

The POS is a module that manages documents. In this case, it will manage every receipt generated by the sales representative to indicate a client purchased an item.

To be able to execute these processes, POS parameters must be defined.

## 2.1 Store

A store will be defined in the system to identify the source of items sold.

The form must be filled in with all desired parameters.

Before the Store form is filled in, certain other parameters must first be defined: Catalog, Tax Code, Country and Currency.

### 2.1.1 Catalog Definition

A 'Generic' catalog has been selected for this example:

### 2.1.2 Currency and Country Selection

A country must be selected along with its corresponding currency:

Currency Menu Path: Mobile / Point of Sales / Settlement / Currency
Currency Country

### 2.1.3 Taxes

A national tax has been selected for the country used in the example, as seen below:

### 2.1.4 Store Final Result

After all past configuration of required points, all fields in the Store form can be filled. The Store Result configuration can be found below:

This process can be added simultaneously to as many sections as the user desires. It uploads an Excel file to the system.

This option can be found in the 'Processes' part of the system. The path to access it is shown below.

The process to upload the desired data is explained in the Data Load Process section.

### 2.2.1 Excel Parameters

For example, the Excel file has been filled in as follows:

#### Stocks

Once the Excel file is filled in with all desired data, it will be uploaded to the system.

## 2.3 Terminal

Once the item warehouse and item family structure is defined for the app, the terminal settings can be configured as follows. These settings will allow the user to interact with the store.

### 2.3.1 Terminal Settings

The terminal has been configured in a family tree view.

To configure the family tree, a logical family structure must be established for the group of items.

Every family level must have the same number of digits. The pattern to be followed is indicated in the terminal configuration.

The family tree parameters are below:

Level 1 (TYPE OF SPORT)

S01 - SNOW

S02 - FIELD

Level 2 (SPORTS)

S010 - SKI

S011 - SNOWBOARDING

S020 - SOCCER

S021 - TENNIS

S022 - HOCKEY

Level 3 (Clothes and Items)

S0100 - JACKETS

S0101 - BOOTS

S0102 - HELMETS

S0103 - TROUSERS

S0104 - SKIS

S0110 - JACKETS

S0111 - BOOTS

S0112 - HELMETS

S0113 - TROUSERS

S0114 - BOARDS

S0200 - SOCCER BALLS

S0201 - T-SHIRTS

S0202 - SHORTS

S0203 - BOOTS

S0210 - SHOES

S0211 - T-SHIRTS

S0212 - SHORTS

S0213 - RACKETS

S0214 - TENNIS BALLS

S0220 - T-SHIRTS

S0221 - SHORTS

S0222 - BOOTS

S0223 - STICKS

S0224 - HOCKEY PUCKS

This family configuration will in turn establish terminal configuration, filling in the "Family Configuration" field with the following values: [3,1,1]. The first level contains 3 digits, the second level 4, and the third level 5.

### 2.3.2 Terminal Configuration

Once we have defined all the necessary data, the configuration of the Terminal can be executed.

## 2.4 Receipts

There are many types of preset receipts. However, this example will only utilize one type of receipt, SALP. This receipt type is designed to indicate customers' order proposals.

To insert item images into the system, ZIP files must be uploaded with the necessary images.

Following the steps explained in the Data Load Process section, the images will be inserted into the system.

After creating the folders, placing item images inside them, and compressing them into a ZIP file, the file is ready for processing.

File Processing:

File Upload into System Process Execution

### 2.5.1 Items with Multiple Colors

The system allows a set of images to be added for the same item, for cases where the item is available in several colors. Additional images must be added manually from the object form, as follows below.

Menu Path: Mobile / Point Of Sales / Items / Items --> Tab: Item images and colors

A color already defined in the 'Color' section must be selected and associated with the desired image. The process is shown below:

Item Section Item Images and Colors Tab

Interface Result:

Black Green

## 3.1 Users

The users of the app, in this case the van/truck drivers (distributors), will have to be loaded in the app. First, the administrator or manager must register the users in the server, with all necessary permissions.

Next, they must be registered in the application. The below form must be filled in with all necessary user information for app registration.

### 3.2.1 First Step: Task Form Configuration

#### Set the task form's values.

The system can automatically create five attributes (autosync, map, phone number, SMS and email), using the checkboxes at the top-right corner of the form. For this example, the map and phone attributes have been chosen.

### 3.2.3 Third Step: Questions

#### Set the questions that you want the user to answer.

Assign questions to one of the groups defined before. Next, specify the question type, and indicate if an answer is required or optional. An activation condition can also be set. This means that, if the condition evaluates to true, the question will appear.

In this example, the following condition is set: if there is an order, all questions related to the order will be answerable, except for Question 6, where the condition will be reversed.

Question 2 is a POS question. The employee must indicate which items the customer wishes to purchase. The code will indicate the type of document used (SALP), and the label given to the POS button. (This question has been explained in detail in Section 2, POS Configuration, above.)

### 3.2.4 Fourth Step: Checkboxes

#### To make the user choose only one option from a set, a checkbox must be created. See images below.

Create Checkbox:

Go to the 'Options' tab and set the different answer options:

#### Once a task has been defined, it must be AUDITED. After that, the task will not be modifiable.

Tasks must be audited before being assigned to users.

## 3.3 Assignments

After the task is audited, it must be assigned to a user. The assignment form must then be filled out, indicating the user who has the task assigned to them. A specific time and date must also be assigned for users to execute the task. More details may also be needed, such as the customer who the user will be helping.

The form must be filled in with the chosen user, task, date and time. Once this is complete, an assignment will be created.

To finalize an assignment, the 'Confirm' button (bottom-left side) must be pressed. This will upload assignments to the device once it has been synchronized.

The process can be seen below. To create an assignment in the system:

Once the assignment is configured, to upload to the device with the 'Confirm' button:

# 4 Interface

The following video demonstrates performance and interaction with the interface.