Prepared POS Reloads

Usually when POS needs data files it will connect to Merchant Central Server and download the required information. If you have lots of POS or lots of items, this can have a real impact on the system, especially if the reloads are all done at the same time.

The idea of prepared POS reloads is to help alleviate this impact and give you more control over when the data for POS is extracted.

The concept is as follows:

Safety Precautions

There are some checks the system will do when POS requests a Prepared Reload to ensure the data is valid.

When the POS asks for the prepared data, the system will check the age of the data file. If it older than a certain period of time, the system will do a full reload. This prevents the POS from getting data that could be considered too old. The allowed period of time is defined in the Max Age Of Prepared Data (Hrs) option in System Settings.

The system will do a check to ensure the data is for the required version. When the prepared data is actually created, the system will check the expected file version of the system (by checking the FILEVERSIONS table). This is recorded along with the actual data. When POS asks for the data, the system will check the version of the POS compared to the expected version recorded with the data. If the two are different, a full reload is done. The implication here is that you must update the file versions (see Upgrading Client Programs for more details).

When Does POS Do A Prepared Reload Started?

Preparing Files For A New Version Of POS

Because of the file version checks, you can prepare POS data for the new version of POS and avoid the full reloads normally associated with a version upgrade.

Converted from CHM to HTML with chm2web Pro 2.85 (unicode)