Follow the instructions below to configure products using the new Cloud UI Product Detail Page.
...
| Note |
|---|
IMPORTANT: The URL path of the calendar page and all transitioned PDP pages will be updated with this release from http://shop.store.com/s/category_path/c/product_path/ to https://shop.store.com/l/category_path/c/product_path/. The domain name will not change. Any deep links from the marketing site must be changed to the /l/ path to take full advantage of the Pricing Calendar on the separate UI in this release, though this is not a hard requirement for Cloud UI 1. 0. Deep links with the /s/ path will still work until the full migration is complete, though they won’t access the refreshed designs on the Cloud UI. |
For the best user experience, it is advised that product detail page deep links on the marketing site and from emails be updated to use the new url path, which uses an /l/ between the host domain and category slug rather than an /s/. See the “important” box above. However, if
If a deep link to a PDP is not updated, or a link is updated to use the Cloud UI url and that product page should continue to render in Legacy, the shop will handle re-directing the user to the correct experience (Legacy or Cloud UI) automatically so that customers have a consistent experience with a given product, regardless of their origination route. This auto-redirection can be enabled and disabled using the setting ‘awcloud.redirectenabled.’‘awcloud.redirectenabled.’ We recommend that resorts update their deep links rather than rely on this failsafe, as there can sometimes be a “blip” when using the awcloud.redirectenabled for redirection.
Commerce Tasks
If the product is configured to show the pricing calendar as the landing page, ensure the Cloud UI Full-Page Pricing Calendar is set in advance.
Configure Product Shell and Product Attributes as usual, but consider the following differences for the Cloud UI PDP.
[Dynamic] and [Conditional] are no longer needed as the Dynamic box is not used for the Cloud UI PDP and conditional logic will be driven off the Conditional Attribute setup described in Section 5 of the Product Attributes Configuration Guide.
Cloud UI offers better coach messaging if an attribute is required but not preselected. Defaults no longer need to be defined unless the product uses the pricing calendar.
Upgrade your Experience is a configurable Language String (see below)
Attribute descriptions are configured differently from what is documented in section 6 of the Product Attributes Configuration Guide. Follow the instructions below for Attribute descriptions.
Meta title text and price from related product’s configuration pulls through on related product cards.
Flag products that are not compatible with Cloud UI so that they continue to render in the Legacy UI. See section 1 below for flagging instructions and a complete list of incompatible product types.
...
Most products are Cloud UI compatible, but there are some exceptions. If a product has any of the following features/configurations enabled on the PDP it should NOT load on the Cloud UI and should be flagged to continue to display Legacy PDP. These products will continue to work if they retain their Legacy configuration and are flagged as noted below in the Setup Guide. :
Radio button date products (section 2 of this guide) (Cloud UI compatibility coming soon!)
Time-based activity products (Cloud UI compatibility coming soon!)
Assigned to attribute with Assignment on the PDP (Cloud UI compatibility coming soon!)
Fenced products that can only be accessed using a valid voucher (Cloud UI compatibility coming soon!)
Fast Flow (Cloud UI compatibility coming soon!)
Payment Plan products (Cloud UI compatibility coming soon!)
Affirm enabled products (Cloud UI compatibility coming soon!)
Reservation products (Cloud UI compatibility coming soon!)
IKON Friends and Family ticket (Cloud UI compatibility coming soon!)
For these listed exception products, there is a new product-level setting that enables some products to continue to load for users in the Legacy UI, and for the majority of products to load in the new Cloud UI. Respecting this routing will work whether a PDP is accessed via the category page, related product link, or cross-sell link. To flag a product so that it continues to load in the Legacy UI:
Find the product from Catalog > Products >Edit
Scroll to the Aspenware Commerce section of the edit page
Locate the new product-level setting called Use Legacy Product Page.
Check the box
Click SAVE ALL SETTINGS
| Info |
|---|
NOTE: Our goal is to make all Product Detail Pages (PDPs) compatible with the Cloud UI, except for Arrive Parking and Retail in the near term. Watch release notes or revisit the Incompatible Products List (detailed in section 1 below) above periodically to check if the 'Use legacy' flag can be removed as new releases become available. |
...
To edit product attribute titles and descriptions:
Go to Catalog > Attributes > Product Attributes
Scroll to the desired attributes and select Edit
Edit the attribute as indicated below
Click Save
Attribute titles and descriptions can also be displayed for add-on product selections, to better explain the add-on, as in the example below.
...
| Info |
|---|
NOTE: If an attribute title isn’t defined, the attribute name will be displayed above the attribute values on the PDP. |
3. Configure Data to Enhance Item Summary and Cart Notice (Optional but Highly Recommended)
...
If a product has attribute combinations defined, admins can define a name for each variant (product attribute combination). This name will be used in the item summary shown to customers before adding to cart on the PDP to describe the selected variant. It will also be passed into Google Analytics 4 as the variant name. If no product attributes are used, the product name will display in the item summary and be passed to Google Analytics 4 as the variant name. If a variant name is not defined, the product name will be displayed.
For a better user experience and effective usage in Google Analytics 4 (GA4) reporting, it's advisable to review and edit all variants used on Cloud UI Product Detail Pages (PDPs). When doing so, aim for clear and concise variant names, keeping in mind that these names are visible to guests.
...
To edit product variant names:
Go to Catalog > Products
Edit the desired product.
Expand the Additional Product Settings section. Within this section, if attribute combinations are defined, each attribute combination will be populated in the table and can be edited.
...
To edit product variant names:
Go to Catalog > Products
Edit the desired product.
Expand the Additional Product Settings section. Within this section, if attribute combinations are defined, each attribute combination will be populated in the table and can be edited.
If you want to configure the max price but not show it to the guest, you can hide savings information on the product or add on product itself within the Aspenware Commerce settings section. To hide savings information from displaying to guests uncheck “Show Max Price” and select Save All Settings. Show Max Price is true by default for all products.
...