Settings:
| Empty | Not Active |
| At Start |
At the start of a transaction (or when the interval has expired, if you are using the interval) it loads all active offers. If there is a combination of new transaction and interval, when the interval expires it starts after the first new transaction. |
| By demand | It loads into memory (temp table in the POS) and is accessed when needed, on demand. It expands the memory bulk of offers on demand. |
You need to decide which works depending on the business:
If there are few offers with many lines you would likely choose to load them at the beginning.
If there are many offers with few lines, it loads those that are the most active on demand as they come into play. This is more typically used because it is the best of both worlds.
Offer Load Interval:
This sets the intervals for how long you let the data stay without loading, even though you are creating new transactions.
If offers are not changed often, then you can up it to 30 minutes; 1 hour; or even to run only outside of the opening hours of the store.
Note: You can override this by logging in and out.