...
| Tip |
|---|
This feature is supported for RTP|One Inventory Pools and Siriusware Max4Sale |
| Warning |
|---|
This feature is NOT supported for Sirusware Points4Sale, Siriusware locations |
Key Terms
| Excerpt |
|---|
Inventory FunctionRTP|ONE Inventory pool slots and Siriusware Max4Sale slots are synced to Aspenware Commerce inventory tables by an Azure function. The sync timer is configurable and is typically set to run to every 5 - 20 minutes. On this interval, the function obtains the latest inventory numbers from the POS and writes them to the Aspenware Commerce inventory table for each component code or DCI configured in Aspenware Commerce’s Inventory Pool administration. (Note: when newly added setup is input into AWCAspenware Commerce, the sync takes up to one hour to fully sync and initially appear on the PDP). Inventory LockingInventory Locking is a mechanism that prevents another guest from “stealing” inventory if they are faster at checking out. It also eliminates the possibility that inventory can oversell if the order processor is delayed. When a customer adds a product to the cart, they “lock” in their inventory and are guaranteed their spot for as long as the lock timer allows. (The duration of the lock timer is configurable.) When a guest completes their order, the system checks inventory levels again and attempts to get an order lock upon order complete. If the product in their cart is still available after the cart lock time expires, they will obtain an order lock and be able to check out. If the product in their cart sells out and is no longer available, they will be prevented from buying that product. The order lock holds the inventory until the inventory is decremented in the POS and the inventory sync runs again, at which point the order lock is released. Inventory Pools (RTP|One only)This is RTP|One’s One’s term for their inventory control mechanism. In RTP|One inventory is pooled, meaning multiple product headers can pull from a common inventory pool and all decrement the same inventory, so if the inventory pool is sold out for a date, it will be sold out for all products using that inventory pool. Max4Sale (Siriusware only)This is one of two inventory control mechanisms in Siriusware, the other being Points4Sale which Aspenware does not yet support. In Siriusware, Max4Sale inventory is configured at the Department level, or the Department + Category level, or the Department + Category + Item (DCI) level, meaning multiple DCIs cannot pull from a common inventory grouping and all decrement the same inventory unless these items are also in the same Category and Department. If Max4Sale is configured at the DCI level, each DCI has its own Max4Sale allotment, and when it's sold out for a date, only that single DCI will be sold out. |
...
First, redundant calls that could occur when multiple products point to a single RTP|One inventory pool and inventory location or Sirisuware Max4Sale pool are reduced to a single call.
Second, only dates from today’s date through the end of the season are called. If today’s date is outside of the season, only dates within the upcoming season are called.
There is a ‘StoreId’ setting in the function app settings. This means if you have multiple stores, work with your Aspenware Representative to define which store’s season start and end dates the inventory function should use as parameters for dates that it gets inventory for. The current default is 0, which is “All Stores.”
For products that do not need their inventory to be synced at regular intervals and have high availability, there is an option to only sync inventory for these once daily, which limits the regular syncs to only get inventory for products that could reasonably sell out.
The function to Update Inventory Pool Codes, which looks for changes to the configuration in Aspenware Commerce inventory pools, can be set to run on a different frequency from the overall Inventory Sync function.
The inventory sync function was re-written to use Azure Durable function architecture and function chaining to increase performance.
...
By utilizing this feature, resorts have control of capacity across any of their products. In turn, this will promote increased control and allow resorts to plan proper staffing for upcoming arrivals. In the case of COVID-enforced limitations, resorts can ensure they are adhering to capacity limitations.
Inventory Display in AWCAspenware Commerce
On the PDP, If inventory is sold out the date will be displayed with a strikethrough and on mouse-hover a “sold out” message will show.
...
*Important: For resorts using RTP|Connect order processing, in this scenario, the order may fail in the order queue. In this case, inventory will not be oversold, but the failed order will need to be handled. For resorts using Unity order processing, the Aspenware order will process successfully, which will overbook inventory for the applicable slot or slots.
...
Scenario 1: If a shopper books the last remaining slot in inventory when only 1 slot remains for an inventory group for the selected date, checks out, and returns to the shop to buy that product for the same date again before the order is processed and the lock expires, the shopper might see that date/slot as available and add it to cart, but be unable to check out with that product, if the lock has expired by the time he attempts to complete the order.
| Child pages (Children Display) | ||
|---|---|---|
|
Other Interesting Reads
Configuration Links
| Child pages (Children Display) | ||||||
|---|---|---|---|---|---|---|
|
Insert excerpt
...