2.13 Release Guide - Inventory Enhancements

In this release, we’re happy to announce many improvements to inventory management.

Eliminated duplicate API calls

The primary cause of performance issues in RTP were the calls to the RTP stored procedure, proc_publicGetProductInventoryPoolInventory. Previously, the sync may have unnecessarily called this stored procedure multiple times with the same criteria on each sync. Now, this stored procedure is only called once for each combination of InventoryPoolCode and InventoryPoolLocationCode.

Eliminated syncs for past dates

Previously, inventory for prior dates in the same season would be updated on each sync. We’ve modified the function in the release as follows: Prior to the start of the season, inventory is synced for the time period between the store-wide “Season Start Date” and “Season End Date” settings.  After the start of the season, inventory is only synced for the current date through the “Season End Date”.

Removed DeleteGuests schedule task

The DeleteGuests ScheduleTask has been removed from the database so it cannot inadvertently be set to Active. The DeleteGuests function, which removes temporary records created by users of the site who never create an an account, has been moved to an Azure function which runs on a scheduled basis (typically once a day, at midnight local time).

New Inventory Frequency Setting

Some inventory pools may have high availability and therefore do not need to be synced as often as products with only a few slots available. For example, if your inventory for lift tickets has 50,000 slots available each day, there’s no need to sync it every 5 minutes. Reducing the amount of inventory that needs to be synced with each execution of the function helps reduce the performance impact on the POS database server.

A new column, Frequency Type, has been added to Inventory Pools administration. The default for this new setting is blank, which means existing sync frequency (every 5 minutes) will be used. The other option is Once Daily. If you select Once Daily, it will execute the sync the first time the function runs after midnight daily, local store time.

IMPORTANT: If more than one row in Aspenware Commerce Inventory Pools administration maps to the same combination of InventoryPoolCode and InventoryPoolLocationCode, and one is set to Once Daily and the other is not, both will sync every time the function runs, and the Once Daily setting will be ignored. The sync will always choose the most frequency syncing option for that combination of InventoryPoolCode and InventoryPoolLocationCode.

Improved Sold Out messaging on Add to Cart

Two configurable language strings will appear in a toast message on the PDP whenever a guest attempts to add inventory to cart when this is none available. The toast message will appear as follows:

The Language strings are: