Skip to main content

Salsify integration

Automatically sync and assign assets to your products

Updated today

This integration ensures that the right, most up-to-date assets from Frontify are automatically assigned to the correct products in Salsify – based on a shared product identifier.

It is designed for product content managers, PIM administrators, and brand/DAM teams who want Frontify to remain the single source of truth for assets, while Salsify continues to manage product data.


What this integration does

Once configured, the integration:

  • Reads assets and asset metadata from Frontify

  • Matches them to Salsify products using a defined product identifier (e.g., sku)

  • Assigns or updates assets in specific Salsify asset properties

  • Runs automatically on a defined schedule (e.g., every 12 hours or daily)

This removes manual asset uploads, reduces errors, and ensures consistency across systems.


How it works (in simple terms)

  1. Each Salsify product has a unique identifier (for example: sku).

  2. The same identifier value must exist on the related Frontify asset (stored as a metadata text field).

  3. The integration looks at specific metadata on the Frontify asset that is being used for Salsify's asset property. Based on your defined mapping, it assigns the asset to the correct Salsify asset property.

Example:

If a Frontify asset has:

  • Identifier (e.g. sku): ABC-123

  • Asset mapping: Additional Images

And in Salsify you have a product with:

  • sku = ABC-123

The integration will:

  • Match the asset to the product

  • Assign it to the Salsify property mapped to Additional Images (for example images)


Where setup happens

Setting up this integration involves three places:

  • Frontify → where you manage assets and metadata

  • Salsify → where you manage products and asset properties

  • Integration configuration → where you connect both systems, define mapping, and set the sync schedule

Please note: The mapping and sync schedule are not configured in Frontify or Salsify, but in the integration configuration.


What you need before setup

Frontify

  • Frontify domain

  • API token

    • The token inherits the permissions of the user who created it

    • Ensure access to all relevant assets and metadata

Salsify

  • Salsify domain

  • API token

  • A product identifier field (e.g., sku)

    • Must be a text field

    • Must contain values that also exist in Frontify

    • Matching is case- and space-sensitive


How to set up the integration

Step 1 – Define your product identifier (Frontify + Salsify)

Choose the Salsify field that uniquely identifies products (e.g., sku).

  • The same value must exist on the corresponding Frontify asset

  • Values must match exactly (including capitalization and spacing)

Step 2 – Prepare your Frontify metadata (In Frontify)

Ensure assets contain:

  • The product identifier (e.g., sku)

  • The metadata values used for mapping (e.g., Main Image, Additional Images)

Metadata names must match your mapping exactly.

Step 3 – Prepare your Salsify properties (In Salsify)

Ensure your product catalog includes:

  • The product identifier field (e.g., sku)

  • The asset properties you want to populate (e.g., images, Main Image)

Step 4 – Define your mapping (In the integration configuration)

Define which Frontify metadata values map to which Salsify properties.

Example:

  • Main Image → Main Image

  • Bottom Image → Bottom Image

  • Additional Images → images

Meaning:

  • If a Frontify asset has metadata Additional Images, it will be assigned to the Salsify property images.

Step 5 – Set your sync schedule (In the integration configuration)

Choose how often the integration should run:

  • Daily (recommended)

  • Every 12 hours

  • Or another interval (minimum: once per hour)

The integration will then automatically:

  • Fetch assets from Frontify

  • Match them to products

  • Assign or update Salsify properties


Capabilities

1. Identifier-based matching

Assets are matched to products using a configurable identifier field (e.g., sku).

  • You can have one or multiple identifiers per asset.

  • Matching is exact (case- and space-sensitive)

2. Flexible property mapping

You decide which Frontify metadata values correspond to which Salsify asset mapping.

Example mapping:

  • Main ImageMain Image

  • Bottom ImageBottom Image

  • Additional Imagesimages

This means when a Frontify asset contains the metadata value Additional Images, the integration writes that asset into the Salsify images property.

3. Handling multiple assets

  • Multiple assets can be assigned to the same product and property

  • New assets are appended, not replaced

4. Scheduled sync

The integration runs automatically on a schedule you define:

  • Daily

  • Every 12 hours

  • Or another configured interval, but not more than once per hour

Each run processes assets and updates assignments in Salsify.

5. One-way sync

Assets flow from Frontify → Salsify.


Frontify remains the source of truth for assets. Changes made directly in Salsify may be overwritten during the next sync.


Error handling

  • Assets without a valid identifier are skipped

  • Assets with no matching product in Salsify are ignored

  • Invalid mappings (e.g. missing Salsify properties) prevent assignment


Limitations

  • Assets without a valid identifier are skipped

    Assets with no matching product in Salsify are ignored

  • Invalid mappings prevent assignment


After setup

Once configured and running:

  • Assets in Frontify are automatically reflected in Salsify

  • Product records stay up to date without manual uploads

  • Teams can manage assets centrally in Frontify while Salsify handles product data

Did this answer your question?