London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

Best practice when structuring Catalog Content

Vote:
 

Hi,

We're planning to restructure one of our catalogs to improve performance of our web app.

We have set up multiple sites in our web app (around 200+). Currently, all of the categories and products imported from an external ERP system are saved under one catalog called "General", which has around 251150 children. Loading the catalog UI would take more time and can potentially crash the entire web app.
 
We have thought of the following options to improve performance:
- creating a catalog under Catalog Root for each of our sites. However, we do have a case where the same product can belong to multiple sites.
- clean up products and categories under the "General" catalog that are duplicates or not needed. We have identified around 29,000+ products that are duplicate relations, and currently determining more content that needs to be cleaned up.

What are the best practices or recommendations you can suggest for how to restructure our catalog? Which of the best practices might be the easiest to implement?
#338478
May 21, 2025 11:00
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.