Page Comparison

Q: I’m getting an inventory related error in the order queue but the product the guest purchased doesn’t have inventory mapped to it in AW commerce.

...

A: If mapping multiple products to POS inventory codes in a single session, refresh the admin screen between each addition. There is currently a bug that can cause erroneous combinations when inventory assignments are added back to back without the page being refreshed.

Q: I want to support timeslots on my products that each have different inventory levels, how do I do this

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.

...

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.

Q: Can I add inventory to an add on product?

A: While adding inventory to an add on product is not technically a supported feature of Aspenware Commerce, there is a work around that allows you to prevent adding to cart if a guest selects an add on and the date they have selected is sold out for the selected add on product. To set this up, inventory mapping should NOT be done on the add on product itself, but rather on the core product with the add on attribute selected along with the other core . When setting this up, you’ll want to add the inventory code for the core product AND the add on product in a comma separated list. For example, notice below that the core variants for the product are selected, which map to code 76638, and the add on is also selected, so it needs an inventory code as well, the MISSING LIFT COMPONENT CODE should be replaced with an inventory code for the add on product. When setting this up, you would want to have a row with the age, ability and discipline and NOT the add on lift that was only mapped to 76638 and a second row that had age, ability and discipline AND add on lift with codes for BOTH the core product: 76638 AND the winter lift inventory code.

...

Q: The inventory sync is taxing my POS DB, what do you recommend?

A: Aspenware can set the function to run less frequently. 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. Reach out to your AW rep if you see this happening.

Q: A product was sold that has inventory online and I am not seeing the inventory decrement in my POS until several minutes after the order was placed.

A: Aspenware’s order processor runs every 30 seconds picking up orders to place to the POS. Under heavy load, the order processor may get backed up and take several minutes between when an order completes and it shows up in the POS. Thankfully, this back up won’t result in overselling because the inventory for that processing order remains “locked” until the order successfully makes it to the POS.

Q: I zeroed out inventory for a day in the POS and it took several minutes to show up as sold out in the shop.

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 inventory syncing method both improves shop performance and eliminates 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.

...