Design Principles

PearlPOS is designed to be a light and easy maintainable cloud-based application, based on three key design principles.

The first key design principle in PearlPOS is the use of the ARTS Operational Data Model (ODM) defined by the Association for Retail Technology Standards. The ARTS Operational Data Model (ODM) identifies, defines and describes retail entities and relationships. For PearlPOS, ARTS ODM defines the data structure and the system interfaces. The data structure of PearlPOS is built on the principles defined through the model.

The second key principle is division of functionality between PearlPOS and backend ERP solutions. Since all major retailers have an extensive backend system(s) controlling articles, prices, promotions, ordering, accounting and multiple other processes. PearlPOS is built to work with backend systems without duplicating functionality in backend ERP solutions like stock, accounting or store ordering. The second key principle is to reuse already established data sources and services in the organisation, to avoid duplicate functionalities and duplicate data.

The third key design principle in PearlPOS is to be cloud-based. PearlPOS can be hosted almost anywhere and should run on nearly any device. It should be easy to integrate with any new technology using APIs. To achieve this, PearlPOS is built on the Neptune Planet9 development platform.

1.1 Product Overview

Since the first mechanical cash register was invented by James Ritty in 1876, systems that control payment in stores have existed. In the 1970s, the first computerized point-of-sales (POS) systems appeared. In the 1990s, PCs took over and client/server technology started to dominate the POS solutions.

Today, cloud-based IT solutions are replacing these technologies, and PearlPOS is built around this idea. The main advantages of such solutions are scalability, reliability and speed. Furthermore, PearlPOS delivers almost zero footprint in the stores, ease of integration through APIs and rapid innovations.

PearlPOS is a complete point-of-sales solution tailored to the requirements of medium to large retailers.

2 Compliance

When selling goods or services in return for cash payments the use of a certified cash register and to provide customers with receipts is required.  The specific requirements will differ from market to market, and PearlPOS will comply with relevant cash register laws and regulations.

Normally the cash register must be registered with the supervising authority (e.g. tax administration) and follow detailed specifications on functions allowed (or not allowed), reporting- and receipt requirements. The tax administration has powers to make inspections to verify that transactions are registered, and receipts are provided to customers.

This system documentation describes how the cash register system works, including how it can be checked and the functionality in the system. The documentation is delivered with the cash register system.

3 Development and Maintenance Plans

As part of a valid license Agreement, the customer will be entitled to download and install patches, releases or new versions of the Product, which is made generally available. The product will be supported for one year after release of current/last version.

Release plans of the product are mainly dependent on new functionally added to the Product, needs to correct errors, needs to update due to infrastructure, or changes in legislations, but not limited too.