Page Comparison

Inventory Function

RTP|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 AWC, the sync takes up to one hour to fully sync and initially appear on the PDP).

Inventory Locking

Inventory 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 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.