Skip to main content
Talk to an expert
Salsify logo

Salsify integration for ecommerce product data

Governed product data published to every channel cleanly. iWeb integrates Salsify with your storefronts and marketplaces so enriched product data, images and completeness rules flow to every selling surface with clear ownership. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: product data connector, plugin, extension, workflow.

SalsifyiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a Salsify integration gives you.

Product data stays governed and complete

Teams know what product content is complete, approved and channel-ready. Salsify becomes the single source of truth for enriched product data, and approval workflows enforce quality before content reaches the storefront.

Channel-specific content publishes automatically

Product feeds to each marketplace, affiliate channel and storefront are built on demand, mapped to each channel's taxonomy and required fields. No manual export, no spreadsheet reconciliation, no stale channel listings.

Images and assets flow to all surfaces

Product images, documents and media are managed once in Salsify and syndicated to storefronts, DAM systems and channels with proper metadata, sizing and focal points. No duplicated asset workflows, no missing images on launch day.

Translations and localisation scale across regions

Product content is translated and localised in Salsify, then published to region-specific storefronts and marketplace feeds with country-specific attributes and compliance data. Multi-geography launches work at scale without manual country-by-country effort.

Launch risk and data drift reduce

Integration failures, stale product data and orphaned assets are caught before they reach the storefront. Exception queues and approval workflows mean teams act on data quality issues in real-time, not after customer complaints.

02 · When it's worth it

Where a Salsify integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Publishing enriched product attributes and editorial copy to multiple storefronts
Synchronising product images, documents and digital assets across commerce channels
Enforcing channel-specific content readiness and required-field validation
Managing product families, variants and relationship hierarchies across languages
Triggering approval workflows when product data reaches channel-publication thresholds
Maintaining taxonomy, translations and localisation rules across geographies
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Multi-language and localisation workflows

Salsify supports translation management, but complex multi-language approval workflows, regional variants and country-specific content rules often require custom field logic and automation outside the standard interface.

Channel-specific taxonomy and classification mapping

Each marketplace and channel uses different category hierarchies, required fields and attribute formats. by default, Salsify can store multiple taxonomies, but mapping logic and conditional field publication to each channel typically needs custom ETL or middleware.

Dynamic asset transformation and image resizing

Salsify can store and link assets, but channels often demand specific image dimensions, formats and focal-point crops. Without a connected DAM or asset transformation layer, these adjustments need custom handling outside Salsify.

Real-time product variant reconciliation with ERP

Salsify enriches variant data, but syncing variant creation, deletion and structural changes back to ERP in real-time requires careful mapping. Manual variant creation in Salsify that ERP does not know about creates data drift.

Fallback and exception handling for failed publishes

If a product publish to a channel fails, Salsify logs the error but does not automatically queue the retry or notify teams. Failed data often sits unnoticed until someone manually checks the integration logs.

04 · The real work

Product enrichment and ecommerce platform ownership easily drift apart when channels publish at different times and approval workflows are not enforced clearly.

05 · Where it sits

Where this integration sits in your estate.

Salsify holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Built for your platform, not a specific one. Salsify integrates with any ecommerce core through the same contract.

System of record
Source / owner
Salsify
System of record for enriched product data and channel-readiness governance
  • Product attributes, descriptions and editorial copy
  • Product images, documents and digital assets
  • Variant enrichment and channel-specific content
  • Completeness rules and channel-readiness criteria
  • Translations, localisation and regional content
  • Category taxonomy and syndication rules
  • Approval workflows and publication status
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Product display and merchandising on storefronts
  • Checkout and cart logic
  • Customer-facing product search and navigation
  • Local pricing and promotion display
  • Customer reviews and ratings
  • Order capture and handoff to OMS / ERP
Connected neighbours
Integration layer
ERP
Provides product master, SKU structure, families and variant hierarchy; Salsify enriches on top and does not create structural variants
Integration layer
DAM or asset system
Stores and transforms product images and documents; Salsify links and governs asset syndication to channels
Integration layer
Storefront platforms
Consume enriched product feeds from Salsify and display products, images and content to customers
Integration layer
Marketplace connectors
Ingest Salsify feeds and publish products to Amazon, eBay and other channels with mapping to marketplace taxonomies
Integration layer
OMS / order management
Receives order data from storefronts; does not interact directly with Salsify product data
Integration layer
Analytics and reporting
Consumes product completeness, publication and approval events from Salsify to track data governance health
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (SAP, NetSuite, Sage)
  • DAM or asset management systems
  • Marketplace connectors (Amazon, eBay)
  • Order management system
  • Analytics and BI platforms
  • Email and marketing automation
  • Search and merchandising engine
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into COMMERCE & SALES CHANNELS & REPORTING
←From ERP
↔BOTH WAYS
Product attribute and content publish: Enriched product attributes, descriptions, images and metadata flow from Salsify to storefronts and product detail pages
Channel-specific required fields and readiness rules determine what content is published and when.
Marketplace and channel feeds: Product data, images, variants and channel-specific content export from Salsify as feeds to marketplaces, comparison sites and affiliate channels
Each channel receives data tailored to its listing requirements and taxonomy.
Product master and hierarchy updates: Core product identifiers, families, variants and basic attributes flow from ERP systems into Salsify as the foundation for enrichment
Salsify maintains the enriched layer; ERP remains the transactional source for SKU and structure.
Asset management and syndication: Product images, documents and video assets are authored and managed in Salsify, then syndicated to storefronts, DAM systems and channels
Asset metadata, alt-text and transformations are governed in Salsify and flow out to all consumers.
Completeness and approval workflow: Salsify tracks product completeness against channel-specific rules
Approval workflows trigger when products meet readiness thresholds, and approvals flow back to mark content as channel-ready and publish-eligible.
Product data quality and governance events: Data completeness metrics, approval events, asset updates and publication history flow to reporting and analytics systems
Teams can track which products are channel-ready, what content is missing and when data was last updated.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Design product data flows from ERP through Salsify to channels

    We map how core product data, families and variants come from ERP into Salsify, and how enriched data flows out to storefronts, marketplaces and other channels. We define who owns what at each stage.

  2. 02
    Build multi-channel export and taxonomy mapping

    We build the feeds, ETL logic and attribute mapping that take Salsify enrichment and convert it into channel-specific catalogue exports. Each marketplace or storefront gets the attributes, categories and content it needs, without manual work.

  3. 03
    Set up completeness rules and approval workflows

    We define what makes a product 'channel-ready', configure Salsify completeness checks and approval workflows, and connect them to governance dashboards so teams know what is ready to publish and why products are blocked.

  4. 04
    Integrate assets and DAM systems

    We connect Salsify with DAM platforms or CDN systems so product images, documents and videos are managed once and syndicated with proper metadata, transforms and focal points to all downstream surfaces.

  5. 05
    Monitor and handle exceptions in real-time

    We set up observability and alerting so failed product publishes, completeness regressions and missing assets are surfaced immediately. Exception queues and runbooks ensure teams respond before data drift spreads.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataProduct attributes and metadata
Source / ownerSalsify
Maintained byProduct team, merchandisers
NotesCore attributes, descriptions and editorial copy are authored and enriched in Salsify. ERP provides the structural baseline (SKU, family, variant IDs); Salsify owns all enrichment.
DataProduct images, documents and digital assets
Source / ownerSalsify (or integrated DAM if present)
Maintained byAsset and content teams
NotesAssets are uploaded, tagged and managed in Salsify or a connected DAM. Syndication to storefronts and channels is governed by asset metadata and transformation rules.
DataProduct families and variant hierarchies
Source / ownerERP (structural) + Salsify (enrichment)
Maintained byERP team for structure, merchandisers for enrichment
NotesERP owns variant creation and deletion; Salsify enriches variant attributes, images and channel-specific content. Changes must flow in both directions with clear ownership of each field.
DataCompleteness rules and channel-readiness criteria
Source / ownerSalsify
Maintained byProduct and channel ops teams
NotesCompleteness thresholds, required fields and channel-specific publication rules live in Salsify. Teams define what 'ready to publish' means for each channel and enforce it via approval workflows.
DataTranslations and localisation content
Source / ownerSalsify
Maintained byLocalisation and regional merchandising teams
NotesTranslated attributes, region-specific content and local variants are managed in Salsify. Publication rules determine which content goes to which country storefront.
DataCategory taxonomy and syndication rules
Source / ownerSalsify
Maintained byCategory and channel operations teams
NotesProduct taxonomies, marketplace category mappings and syndication rules are configured in Salsify. Each channel feed is built from these rules to ensure consistent categorisation.
DataApproval workflow and publication status
Source / ownerSalsify
Maintained byGovernance and approver roles
NotesApproval status, completeness tracking and publication history are managed in Salsify. Integration systems consume this status to decide when and where to publish data.
10 · Experienced integrator

Built this before

iWeb has built and supported Salsify integrations for brands selling across multiple channels and geographies. We understand how enrichment, approvals and channel-specific publication rules sit in the ecommerce estate.

We know how to map product data flows so ERP owns structure, Salsify owns enrichment, and storefronts stay in sync without drift.
We have built multi-channel export feeds that convert Salsify completeness and taxonomy rules into channel-specific catalogues.
We understand how approval workflows, completeness rules and governance dashboards keep teams accountable for data quality.
We can design asset syndication from Salsify or connected DAM systems to storefronts and marketplaces with proper transforms and metadata.
We know how Salsify sits alongside ERP, OMS, search, CRM and analytics systems, and where to prevent data ownership collisions.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Product attribute completeness is calculated correctly for each channel; missing fields are flagged and prevent publish.
Images and assets export with correct metadata, alt-text and sizing rules to each channel; no missing or broken links.
Variant hierarchies and family inheritance work as expected; variant-level overrides do not pollute family-level attributes.
Approval workflow blocks unprepared content and alerts approvers; approved products publish within the SLA window.
Failed publishes to any channel are logged, queued and retried; teams are alerted within 15 minutes of failure.
Translations and localisation content route to the correct region-specific storefronts without language or field mismatches.
Product deletions in ERP are flagged in Salsify; orphaned enrichment is identified and can be cleaned up without accidental republish.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Variant structure drift between ERP and Salsify

Teams enrich variants in Salsify that ERP does not know about, or delete variants in ERP without removing them from Salsify. This creates orphaned enrichment and confuses storefronts about which variants are actually saleable.

Channel-specific content blocking a general publish

A product is rich with global attributes but missing one channel-specific required field. The product gets stuck, and teams do not know whether to fill the field, skip the channel, or lower the completeness threshold.

Asset transforms and image sizing not applied to all channels

Storefronts and marketplaces need different image dimensions and focal points. If asset transforms are not applied consistently, channels receive raw or incorrectly sized images, leading to poor search visibility and checkout abandonment.

Translation and localisation workflows not enforced

Content is enriched in one language, but region-specific storefronts need translated attributes, compliance statements and local variants. Without localisation rules, products go live in wrong languages or with missing regional data.

Failed product publishes sit unnoticed

A feed export to a marketplace fails silently, and no one knows until customer complaints arrive or inventory gets out of sync. Without alerting and exception queues, data drift spreads unchecked.

Approval workflows become a hidden bottleneck

Approvers are overwhelmed by too many products to review, or approval rules are unclear and change ad-hoc. Bottlenecks delay launches and teams bypass the workflow, destroying data governance.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Salsify integrations.

How do we stop enrichment in Salsify from drifting away from ERP product structure?

We establish a clear handoff: ERP owns SKU creation, variant structure and family hierarchy. Salsify imports these as read-only anchors, then enriches on top. Any variant created only in Salsify is flagged as a governance violation and blocked from publication until ERP acknowledges it.

What makes a product 'channel-ready' and who decides?

We define completeness rules for each channel in Salsify (e.g. title, description, image, price, shipping weight). These rules are owned by channel and merchandising teams. A product only publishes when all required fields are filled for that channel; approvers then gate the final publish.

How do we handle products that are complete for the website but missing marketplace-specific fields?

We split completeness rules by channel. A product can be 'website-ready' and 'marketplace-ready' independently. If a product is missing an Amazon-specific field, it stays blocked from the Amazon feed but still publishes to the website. The integration prevents partial publishes and alerts teams to missing channel data.

Can we publish to multiple storefronts and marketplaces from one Salsify instance?

Yes. We build separate export feeds for each storefront and marketplace, each with its own attribute mapping and taxonomy conversion. A single product is published to multiple surfaces, but each feed is tailored to that channel's requirements. Publishing to one channel does not block another.

How do images and assets get to all the channels?

Assets are managed in Salsify (or a connected DAM), and we build syndication rules that push images, alt-text and metadata to storefronts and marketplace feeds. We also handle image resizing and transformation if channels need specific dimensions or formats. Assets are published along with product attributes in each channel feed.

What happens if a product publish fails to a marketplace?

We set up alerting and exception queues. If a feed export fails, the integration logs the error, marks the product as 'publish failed', and notifies the team. Failed products stay in a queue until the error is resolved and a retry is triggered. No silent failures.

How do translations and localisation work across regions?

Salsify can store translated attributes and region-specific content. We set up publication rules that send German translations to the German storefront, French to France, and so on. Region-specific fields (compliance text, local measurements) are conditionally published based on storefront locale.

Who owns the approval workflow and how does it stay enforced?

Approver roles are defined in Salsify; approval rules are set per channel or product family. We integrate with your governance and team structure so approvals happen without bottlenecks. If an approver is overloaded, we set up dashboards to show which products are waiting and why.

Can we see which products are approved, which are blocked and why?

Yes. We build governance dashboards showing each product's completeness, approval status and publish history for each channel. Teams see at a glance which products are ready, which are waiting for approval, and which fields are missing on blocked products.

What happens to enrichment in Salsify when we delete a product or variant in ERP?

We define a deletion workflow. When ERP deletes a product, we flag it in Salsify so merchandisers can clean up enrichment and assets. Orphaned enrichment (content for products that no longer exist) is tracked and alerted. We do not auto-delete to prevent accidental data loss.

How do we manage product family and variant enrichment?

Salsify supports inheritance hierarchies where family-level attributes (brand, size guide, materials) cascade to variants, and variant-level attributes (colour, SKU) override them. We configure these rules so teams enrich once at the family level and variants inherit, reducing duplicate work.

Can Salsify feed multiple different storefront platforms at the same time?

Yes. We build separate feeds to Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts, each tailored to how that platform ingests product data. One Salsify instance supplies all storefronts; each gets the data it needs in the format it expects.

What happens if we need to change completeness rules or add a new required field?

Rule changes are made in Salsify by the product or channel team. When a rule changes, existing products are re-evaluated against it. We flag products that no longer meet the new standard and alert teams, giving them time to fill the new field before republishing.

How do we prevent channel feeds from going stale?

We set up scheduled feeds that export from Salsify on a defined cadence (hourly, daily) and monitor for changes. If a product is updated in Salsify, the next feed export includes the change. We track publication timestamps and alert if no exports have succeeded in the expected time window.

Next step

Have a Salsify integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →