How SuiteCommerce Handles Data-Driven Fields
Because prerendered HTML may not always reflect the latest item data or shopper-specific state, SuiteCommerce applies targeted safeguards to fields that are more likely to change during the transition to interactivity.
SuiteCommerce focuses on fields that can negatively affect the shopper experience if an outdated value briefly appears. For example:
-
Price - SuiteCommerce temporarily obscures a price by blurring it until the latest value is available. This approach helps avoid displaying a price that immediately changes after the page becomes interactive.
-
Out-of-stock messaging - SuiteCommerce temporarily hides out-of-stock messaging until the availability status is ready on the client. This approach helps avoid briefly showing an out-of-stock message for an item that's available.
Other fields, such as an item name or description, can also become outdated between prerendering and the client-side update. However, these fields usually have less immediate impact on the shopper experience, so SuiteCommerce doesn't apply a default safeguard to every possible field.
Because themes and extensions can introduce many different customizations, SuiteCommerce focuses on the fields that are most crucial to buying. Developers can apply similar techniques to other custom fields when needed.
For custom content, you can apply similar protections when needed. For example, you can add the .blur class to a template element to use the same blur treatment SuiteCommerce uses for price content.