Salsify DAM review: fit, pricing model and integrations

What Salsify is

Salsify is a PXM platform, a PIM extended with syndication, enhanced content and digital shelf analytics, and its DAM capability is an asset module inside that platform. Salsify, Inc. was founded in 2012 in Boston. Offices are listed in Boston, Lisbon, Paris and Sydney.

The Salsify entitlement guide lists "Record and Digital Asset management" as a Core Edition capability: import, export, storage and display of product records and digital assets. The guide defines a digital asset as any file stored in the platform, including images and videos, and counts assets separately from records. Salsify markets no standalone DAM product. Its PXM product page names DAM as one of several categories a PXM platform brings together.

Salsify sells these components, according to its own documentation and press releases:

• ProductXM (PXM): product records, digital assets, the Workflow Engine and syndication to channels.
• SupplierXM (Supplier Onboarding): the supplier platform that came with the Alkemics acquisition in 2021.
• Add-ons: Enhanced Content, Catalog Sites, Grocery Accelerator and Digital Shelf Analytics.
• AI: the Intelligence Suite with AI Accelerators in the Workflow Engine, plus SalsifyIQ and AI Image Generation, announced in May 2026.

Ownership is changing. Cinven announced on 22 July 2026 an agreement to acquire Salsify, Inc., subject to regulatory approvals. The ownership table on this page lists the dated history.

Where Salsify fits

Salsify fits the DAMSelection segment for product content, packaging and commerce when the PIM decision comes first and assets mainly serve product pages. Nine DAM vendors document a Salsify connector in the Fit Map, which shows how often large asset estates sit in a separate DAM.

DAMSelection assessment: Salsify suits buyers whose assets are mostly packshots, product documents and short videos tied to SKUs and published to retailers. Keeping those assets in the PIM removes one integration and gives one link between record and image. Brand teams that need campaign workflows, agency sharing and guideline portals fit the brand and marketing DAM segment better, with Salsify receiving approved product assets.

Compare the two-system route on Bynder vs Salsify and the wider vendor directory.

How Salsify covers the core DAM jobs

Salsify documents the basic product asset jobs of upload, product linking, storage and CDN delivery, while documentation for asset rights, versioning and approvals was not found.

Salsify's rendition handling runs through its CDN partner. The sub-processor list names Cloudinary, Inc. and ImageKit Inc for image and video management in PXM.

Product content and PIM integration

Salsify needs no PIM connector for its own asset module, because assets and product records sit in one platform. Integration questions arise when a separate DAM feeds Salsify, and the Fit Map records connectors from nine DAM vendors on that route.

brix Solutions AG also sells a Salsify Connector Service that moves product assets from Bynder into one or more Salsify instances. Check depth levels per DAM in the PIM DAM Fit Map and the Salsify integration guide.

Hosting, security and contract checks

Salsify documents SOC 2 Type II and links an ISO/IEC 27001 certificate that expired in November 2025, and its sub-processor list places PXM hosting on Amazon Web Services in the USA. The security page names no hosting provider or region. Supplier Onboarding runs in the EU on Microsoft Azure, OVH and Scaleway.

The ISO certificate linked from the security page is ISO/IEC 27001:2013, issued by A-LIGN under number ISMS-SA-110822, with expiry on 8 November 2025. Salsify publishes no renewed certificate, so ask for the current one.

Confirm these points in contract, using the contract clauses guide:

1. The region that holds PXM data and asset files, and any EU option for data residency.
2. The current ISO/IEC 27001 certificate and the latest SOC 2 Type II report.
3. Which asset data Cloudinary and ImageKit process, and in which regions.
4. The AI providers that process assets in AI Accelerators and image generation.
5. Change of control terms, given the announced Cinven acquisition.

What to test in a scripted demo

Salsify's demo should prove the asset claims in its documentation on your own SKUs and images. Build the script with the demo script guide.

1. Upload 200 product images named to your convention and show automatic linking to the matching SKUs.
2. Generate three channel renditions from one master and show the delivery URLs and which processor creates them.
3. Run Extract Data from Assets on 20 packaging images and show the human review step before values publish.
4. Expire a licensed lifestyle image and show how Salsify removes it from every connected channel.
5. If a DAM already exists, run its Salsify connector live: replace an asset in the DAM and show the update reach a retailer feed.
6. Show storage and bandwidth usage against the 500 GB entitlements, with the three-month average.
7. Show where asset files and backups are stored, by region.

Pricing questions to ask

Salsify prices by edition and entitlement, and its published guide states limits without prices. Core Edition includes 50,000 records, 500 GB asset storage, 500 GB monthly asset bandwidth and 100,000 API calls per month.

Worked example: a brand with 40,000 SKUs and six images per SKU at 4 MB each holds about 960 GB. That library needs roughly double the Core storage entitlement before any video. Model the five-year effect in the TCO calculator.

• Price per additional 500 GB of asset storage.
• Charges when the three-month bandwidth average exceeds 500 GB.
• Fees or usage caps on AI Accelerators.
• Renewal cap after the ownership change.