Page Comparison

Q: How do I configure a product that is only available on one or a couple of days of the season with inventory? (i.e. camps, seasonal programs, events, etc.)

• When setting up camps, events, we recommend adding only “start” dates to a front-load inventory pool. Then use radio button date inventory configuration for these most likely. We did this for Camps at a resort where the camp runs from July 4 – 7, but all guests book the 4^th, so the only date added to the inventory pool is the 4^th.

  • When doing seasonal programs, we often do a similar setup to the above, and just add the first day of the program to the inventory pool and use this radio button date functionality, but will hide the date on the product on the product detail page so the guest doesn’t see it, but this allows us to restrict online sales when the product is sold out.

  • If you need all of the dates for accounting and instructor management purposes, our recommendation is to create a separate component and inventory pool to accomplish this. This separate component will decrement inventory for all of the dates of the program and inventory should be set to auto-assign. Don’t configure this component code in the Aspenware Commerce Inventory plugin, instead use the component configured with the aforementioned steps, but this component can be used for RTP fulfillment purposes.

...

A: Setting up your product as a time-based activity, which has time-slots throughout the day, is one option, but does not work for products with many variants (attribute combinations) or products that need to be booked as a rental, etc. What Aspenware has worked with resorts to setup are separate products for each time slot that are each mapped to their own inventory pool or Max4Sale inventory. The time selection would be an attribute with values for each time-slot and the product attribute combination table would include entries for each time and variant with associated SKUs. For examples of products setup like this, see Woodward Park City’s Hub Products.

Q: I setup inventory limits in the Dynamic pricing module, but it’s not properly blocking out dates.

A: Dynamic pricing inventory is only meant to control how many products can be booked at a tiered price point before increasing the price and is not meant to be a true inventory control mechanism. Setup your product using POS inventory (inventory pools for RTP and Max4Sale for Sirisuware) and map them using the steps in the configuration guide if you wish to truly restrict guests from buying more than allowed quantities for a particular date.

...

A: The inventory sync should be set to run no more frequently than every 5 minutes, so first check whether the sync is set to run < every 5 minutes. In addition to this, if you unpublish products that are no longer being used, the sync job will be less beefy as it will only be calling back to the POS for published products. Aspenware also recently released the ability for products that have high inventory levels to only be synced once daily, which is a configurable setting and will reduce the load to the db if it is calling for less data for regular syncs. Also, check your configured season start and end date. If the season start date is not this season’s start date, adjust it so the time frame that the inventory sync is checking your POS for is isolated ot to this season. Finally, Aspenware put in measures to reduce load on the db during this sync. Learn more here. Reach out to your AW rep via support@aspenware.com if this issue is not mitigated by these recommendations.

...

A: The inventory function is set to run every 5 to 20 minutes, so you will not immediately see inventory that is manually changed in the POS update in the shop until this function runs on it’s schedule. The frequency is configurable, but setting it more frequently than 5 minutes can have adverse effects to the POS performance as this is a “heavy” job.

Inventory was re-architected so that while the inventory limits available on the shop rely on POS available inventory, it is not called every time a guest navigates to an inventoried product, but rather on a configurable basis. This re-architected The inventory syncing method both improves shop performance and eliminates reduces the possibility of overbooking inventory. The inventory that the shop reads from is fully contained within Aspenware and accounts for inventory from the POS (based on the last sync which runs every x minutes) and active items that are in carts where the lock is not expired and items that are in orders that are completed but not “processed” through to the POS.

...

A: If a shopper books the last remaining slot in inventory when only 1 slot remains for a inventory pool 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.

Q: I’ve recently added inventory to a product, but the inventory levels aren’t coming across. It looks like my sync ran for other products, what gives?

A: Newly added inventory mappings in admin are checked and updated every hour (frequency may differ by store) and synced to the POS. This is on a different interval from other already configured products, which checks inventory levels in the POS every N minutes. Typically it runs at the top of the hour. This change was made In an effort to improve the performance of the inventory sync on the POS DB and the overall efficiency of the inventory job.

If the time interval has passed that you expect to see inventory updating and you still don’t see the inventory update, check your season start and end date. If the date that inventory is configured for is outside of the season start and end date range, the inventory will not be pulled from the POS.

Q: Why I am not seeing my amount remaining on the PDP despite having set the language string properly?

Displaying the amount remaining beneath the shopping cart depends on whether the inventory threshold has been met. This can be adjusted by going to Settings > All Settings > and searching for catalogsettings.dynamicpricingcalendar.inventorymessagethreshold

Q: I’m trying to update a component code or delete an entry in the inventory pools pulgin, but I’m getting an error with red triangles (see below). What’s wrong?

...

A: In order to prevent errors, you are not be able to update a component code while there are orders that are unprocessed or in an active lock in a shopping cart. You will also be unable to delete an entry in the Inventory Pool plugin when the entry is part of a ready, failed, or processing order. The red triangles are there to prevent admins from editing a configuration where orders are either in process or failed.  Once the failed order is cleared out and the inventory sync runs again, the red triangle will go away. You may need to refresh your page to see the update, however.