Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Add feedback Subscribe
Status Future consideration
Product Customized Commerce
Categories Catalogs
Created by Guest
Created on Nov 28, 2022

RELATED FEEDBACK

Add ability to delete language versions for individual commerce content

As a developer, I want to develop code that will delete language versions for individual commerce content to minimize the amount of data stored in commerce.

Once language data has been added for a commerce item (e.g. product) there is no way to remove it.

We have lots of extraneous language data for a client because they wanted English placeholders for each language (28 different languages). This has caused bloat in the commerce catalog and affects the ability to run the Find Indexing job, and the Personalization feed, and is causing memory issues as well.

  • Post comment
  • Optimizely
    Tom Bramley
    Reply
    |     Apr 19, 2024

    Thank you for your recommendation. After investigating, we anticipate this would create breaking changes so we are marking as a 'Future Consideration' as it will be something to consider for Commerce 15 but not planned for the current version

  • Guest
    Reply
    |     Jan 4, 2023

    In Commerce (all versions), any item in a catalog will get all of the languages set at the catalog level. While there is fallback functionality in Commerce 14 it is less useful when there is so much forced extraneous language data.