1. Home
  2. Product Information Management (PIM) Software
  3. Salsify Reviews
  4. User Review of Salsify
Improving e-commerce with Salsify
August 18, 2023

Improving e-commerce with Salsify

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Salsify

I assist in synchronizing assets from DAM to Salsify through API connectors, allowing assets such as images, catalogs, spec sheets, brochures, videos instruction sheets and others to show up in different platforms and e-commerce sites. I could either tag the assets from a different asset management system, or link the URL within Salsify irnupload directly to Salsify. Doing so allows uniformity of assets across different channels as well.
  • Integration of assets across channels
  • Application of analytics to see which products are most viewed
  • Manual override in case API connectors faces an issue
  • API connectors sometimes fails, and in my experience usually takes a while for assets to be uploaded/updated
  • Linking of assets to commerce pages
  • Know which products and assets users find most valuable based on their views/sessions
  • Users are able to view updated assets
Their support/purpose is different from each other

Do you think Salsify delivers good value for the price?

Yes

Are you happy with Salsify's feature set?

Yes

Did Salsify live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Salsify go as expected?

I wasn't involved with the implementation phase

Would you buy Salsify again?

No

In my experience, I had an issue with Salsify lately wherein tagged assets did not pass through the API connector. In my opinion, this is probably because of the recent site domain change that we had. However, I believe this could have been avoided if there were occasional “error messages” being received by users for easier troubleshooting. In my opinion, the new products apparently inherited old assets due to the API failure, which as a quick workaround had to be manually removed and link the proper assets.