Once setup has been performed in the central system, the tools required to execute all configured sale and payment operations are available on the mobile device. The results of these operations will be transferred to the central system following the established synchronization rules. In this way, the central system and mobile device exchange information in two directions.

1 Global Transaction Process

The creation of a receipt is followed by a series of steps, outlined below:


1.1 Receipt Type

First, the type of operation which will be performed must be selected as New Operation. This may include: direct sale, return, client sale with invoice, or other types defined in the central system's parameters.

Button to select the type of receipt:
List to select the type of receipt to generate:
  • The first time a user wants to generate a receipt, the system does not have any type prepared, and one must be selected. However, once the receipt is finalized, the system always preassigns the same type of document used in the last transaction. As such, it is not necessary to select the document type unless the user wants to create a different type of document than the most recent one.
  • The list of the possible document types which can be selected varies according to user role. Roles can limit or restrict certain types of documents to users.
  • The document type is modifiable as long as there are no items on the receipt. To switch to a different document type once an item has been added, the current document will have to be paused, canceled, or finalized.

2 Data Associated with Receipt Type

Information associated with the selected document type.

Access button to data associated with receipt type
Receipt which requires a customer (new customers can be registered)
Receipt which requires a source receipt
  • The data associated with the document type is used to complete receipts.
  • Depending on document type parameters, the system will request different data. For example, if a user wants to perform an item return transaction and have the system check the quantities, the original sale receipt must be reported to verify information.
  • Data entered as input can be validated via BeanShell (Java).

3 Add Items

Once operation type and customer are configured, users can select products and quantities. To this end, the system allows two catalog visualization options: by tree or by families. In the case of sizeable catalogs, we recommend tree mode. On the other hand, presenting the catalog in family mode is more intuitive for the user.

At this point, we assume that the customer will be looking at the device screen along with the vendor. Therefore, it is very important to have information correctly configured to facilitate item identification: name, image, and details.

The various options used to add items to the cart are explained below:


1- Add items from the Properties screen. Filtering by properties and tapping item images to add them.

2- Add items from the list of items. Tapping on a line in the items list.

3- Add items via the Item Detail screen. By tapping on the item image, users can access the Item Detail screen according to the selected family. Pressing the "+" or "-" button adds or removes items.

4- Add items by pressing and holding the item image.

5- Add item using the search tool. Typing description or item code.

6- Add items using the item EAN code. Enter EAN code to add an item.

Prices and discounts can be modified if the user has the appropriate role for authorization.

All users can eliminate an item from a previously-added receipt.

Once the receipt is processed and pending finalization, it cannot be modified. Users must return to the main screen to perform modifications.

4 Finalize Receipt

Once the item has been entered on the receipt, the receipt closure process begins. If the receipt requires validation from the central system (as in the case of returns/refunds), it must be processed before users can access the payment window. If the receipt type indicates a charge, the form of payment must be entered before the receipt is finalized or printed.

Close or process receipt and/or execute payment. Any of the following actions: close, print receipt or send email copy, finalize receipt.

Process Receipt Close, print, send via email, execute previously-reported payments.

  • The printing of a receipt implies its closure and finalization.
  • Payments can be validated via the BeanShell script. This may occur, for example, to prevent a user from inputting different forms of payment for the same receipt.
  • The system does not allow cash returns on payments originally performed via card or check. Cash returns can, however, be performed on cash transactions.

5 Printing

To print receipts, printers must be configured in the APPS Core Printer network.

If only one printer has been defined, the system will directly send jobs to that device. However, if multiple printers are listed and none has been set as default, the system will bring up a selection screen of available printers in range.

Receipt printing implies that the receipt is closed and can no longer be modified.

The system contains standard printing defaults, but customized printouts can also be configured through a BeanShell script.

The type of receipt indicates the number of copies which must be printed.


Normal Printing Invoice Printing Gift Receipt Printing

5.1 Reprints

Receipts can be reprinted, as long as they have not been synchronized to the central system.

To reprint receipts, a menu in the main transaction screen must be used.

Reprint Receipts
Button to recall the most recent receipt generated Button to print it
Reprint Past Receipts
Button to open list of past receipts List of device's closed receipts
Button to open receipt preview Button to reprint receipt

5.2 Print Gift Receipt

Gift receipt printing consists of a reprint, where receipt prices or discounts do not appear.

Intended for customers purchasing gifts who do not want the item price to appear on the receipt.

Gift receipt printing consists of multiple possible modes: all items on one receipt, or one receipt printed for every item unit.

Gift receipt printing must be permitted by the user role.

Gift Receipt Printing
Button to open the gift receipt menu Select the printing mode

6 Pause and Recover Receipts

While a receipt is being generated, the process can be paused and ended later.

To be able to perform this action, users must have an appropriate role assigned to them.

If the system only has one paused receipt, the system will recover it automatically when accessing the transaction menu. However, if multiple paused receipts exist, the system will display them in a list. The list contains information on the number and type of paused receipts and their items. If the receipt has a customer associated with it, the customer will be shown to help locate and recover the receipt.

Button to pause a receipt in progress Button to access the list of paused receipts
List of paused receipts Receipt item list

1) Button to recover paused receipt

2) Button to show receipt items

If the receipt has a customer associated with it, it will be shown first on the list.

7 Cashaudit

7.1 Opening

When the Axional POS app starts up, the system will check whether the user has authorization over the cash till, then report whether opening has been performed. If the till has not been opened, the system will automatically redirect the user to the Opening screen.

If no opening is found, the system will not allow the user to exit until an opening amount has been entered. The system will check whether the amount entered is correct. Once opening has been entered, the POS Document (Receipt) can be generated.

The opening screen can be accessed from the main screen to modify the amount. However, only the opening amount will be modified; the date and time are unalterable.

7.2 Closure

To close and settle the cash till, the user must access the main 'Cashaudit' menu, where they will find a 'Close' button to access the closing screen. The closing button checks whether there are any documents pending processing. This is intended to avoid closing while there are still missing documents in the central system. If there are still pending documents to be sent, a message will appear to notify the user and show options:

  • Synchronize (Synchronize documents).
  • Continue (Access the closing screen without synchronizing; only for offline terminals).
  • Cancel (Postpone closing).

7.3 Verification

The closing screen header indicates what the opening amount was.

The value declared is entered as cash, credit card, or gift card.

To delete an entered value, its line must be tapped.

If a form of payment is entered more than once, only the last value entered will be recorded.

To modify a previously-entered value, it must be re-entered with the correct value, rather than deleting the first.

Once the declared amounts are entered, the 'Verify' button is pressed. This button will synchronize data with the central system and perform cash settlement, countering the central system's existing payments with the ones declared. Finally, the settlement result will be shown.

There are three possible result options:

  • No Internet connection: Blind settlement

  • Incorrect settlement: There are discrepancies between the theoretical amounts and the amounts declared.

  • Correct settlement: The theoretical amounts and the amounts declared are equal.