Limitations and methods

This is to draw your attention to certain procedures and performance limits that you may need to consider when planning your POS system. We assume that these performance limits only mean relevant restrictions in absolutely exceptional cases. Please see the following chapters for more details.

Head offices and locations

For systems with a head office and usually several locations, there are many other technical possibilities to maintain the master data centrally and to evaluate the transaction data from the locations in the head office. In this context, further rules and limitations emerge, some of which we deal with in a differentiated way per programme in the section ENTERPRISE Solutions.

Changes during operation

Changes beyond new items or item prices should not be applied without further ado during operation and without restarting the system.

General information on evaluations

If reports or an entire POS system is new, you want to gain confidence in the technology as quickly as possible. This is often done by comparing different reports. This makes the uncertainty all the greater if the results differ from one another. However, this is unavoidable if the bases of the reports on which the result is calculated are different. For example, a static-date report setting may cause misunderstandings compared to a post-opening report with bookings beyond 0:00. Also rounding (in this gross system that you may prefer to use net) may require understanding here. Take a look at this, for example: Rounding and decimal places

Further notes


Further documentation:

Antivirus programmes with Hypersoft systems

Daily closing, daily change and TTA

Number of item data records

Gross and net prices

Postings between clients

Calculate purchase prices

Deleting master data

Disable pop-up blocker

POS boundaries and location systems

Rounding and decimal places

Special price and loss treatment

operation counter

Web browser compatibility

Back to the parent page: Basics