4 results found

1. Optimize Wishlist Updates: Refresh Line Item Only, Not Entire Page

   Optimize Wishlist Updates: Refresh Line Item Only, Not Entire Page.

   Current Behavior (for customers using live inventory and price via API):
   In Configured Commerce, when a user updates a product within a list or quote (e.g., changing quantity or removing an item), the entire list page refreshes. This results in longer load times and a less efficient experience, particularly for large lists.

   Requested Enhancement:
   Modify list/quote functionality so that updates apply only to the specific line item being changed, rather than forcing a full list refresh (must also adjust the product total). Ideally, this would be handled via an asynchronous update (API call / AJAX request) that re-renders just the affected line item instead of all items in the list/quote.

   Business Impact:

   Enhances customer experience by making lists more responsive and user-friendly

   Especially beneficial for B2B users managing long or complex lists

   Outcome:
   A smoother, faster, and more modern list interaction that aligns with best practices seen in cart and order management on other eCommerce platforms.

   Optimize Wishlist Updates: Refresh Line Item Only, Not Entire Page.

   Current Behavior (for customers using live inventory and price via API):
   In Configured Commerce, when a user updates a product within a list or quote (e.g., changing quantity or removing an item), the entire list page refreshes. This results in longer load times and a less efficient experience, particularly for large lists.

   Requested Enhancement:
   Modify list/quote functionality so that updates apply only to the specific line item being changed, rather than forcing a full list refresh (must also adjust the product total). Ideally, this would be handled via an asynchronous… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  1 comment  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. PIM - User Roles Don't Work

   Optimizely confirmed the existing PIM roles do not work but asked me to enter it as feedback instead of a bug. A user must be an Admin to update an image, which is not optimal. There are existing PIM roles with Edit permissions for items and images, but they do not work. Fix the existing roles, or custom roles and permission so a user doesn't have to have full admin authority to edit an image or an item field.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Fraud prevention

   We are working to resolve ongoing issues with fraudulent ecommerce orders. Frequently, bots have placed orders using stolen credit card information with valid bill-to addresses but random ship-to addresses. Unfortunately, these orders were shipped before we received dispute requests, which forced us to issue credits to customers and resulted in unrecoverable product losses.

   We attempted to implement the DataDome solution; however, it was not compatible with Optimizely. I also understand that Optimizely currently uses the Spreedly gateway for credit card processing, and I’m aware that Spreedly provides a fraud prevention solution that is not included with Optimizely.

   Could you please let me know if Optimizely has plans to introduce fraud prevention features within its ecommerce platform to help customers reduce the risk of fraudulent orders and financial losses?

   We are working to resolve ongoing issues with fraudulent ecommerce orders. Frequently, bots have placed orders using stolen credit card information with valid bill-to addresses but random ship-to addresses. Unfortunately, these orders were shipped before we received dispute requests, which forced us to issue credits to customers and resulted in unrecoverable product losses.

   We attempted to implement the DataDome solution; however, it was not compatible with Optimizely. I also understand that Optimizely currently uses the Spreedly gateway for credit card processing, and I’m aware that Spreedly provides a fraud prevention solution that is not included with Optimizely.

   Could you please… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. PIM - Improve validation with trailing space characters

   The current PIM import process automatically strips trailing space characters from all fields before validating the import. This causes frustrating behavior when a category is named (accidentally or otherwise) with a trailing space character in it.

   The import validation strips the space characters from the file, which causes the import to fail with the "Category Name not found" error. The PIM admin then has no good way of identifying that the trailing space character is what is causing the issue since the error does not specify which category is the one not found.

   In order to avoid this, I would propose two potential solutions:

   A) Improve the category import validation to specify which category name is the one not found

   B) Add a system setting for the import process to accept trailing space characters as-is and not automatically remove them from the file before performing the validation

   The current PIM import process automatically strips trailing space characters from all fields before validating the import. This causes frustrating behavior when a category is named (accidentally or otherwise) with a trailing space character in it.

   The import validation strips the space characters from the file, which causes the import to fail with the "Category Name not found" error. The PIM admin then has no good way of identifying that the trailing space character is what is causing the issue since the error does not specify which category is the one not found.

   In order to avoid this, I would… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating