Shopify DAM integration

What a Shopify DAM integration must do

A Shopify DAM integration must place the right approved asset on the right product and variant, in the right order, and remove it when the asset is withdrawn.

The DAM integrations guide explains where commerce platforms sit among the other DAM connections. Shopify is a commerce platform with product data inside it, so the integration often runs next to a PIM feed. DAMSelection assessment: decide which system owns the link between asset and product before the first demo. Two systems that both write product media create duplicates.

How Shopify models product media

Shopify models product media as files in a store-wide file library, attached to products and optionally linked to variants.

Fact: Shopify recommends 2,048 by 2,048 pixels for product images. Fact: apps can create up to 1,000 videos per store per week. A DAM master often exceeds the image limits, so the connector must send a rendition in a supported size and format.

The Shopify Admin GraphQL API handles media through a small set of mutations.

• `fileCreate` creates files from a public URL or from a staged upload, up to 250 files per batch.
• `stagedUploadsCreate` returns upload targets for direct uploads.
• `productSet`, `productCreate` and `productUpdate` attach files to products through the `media` field.
• `productVariantsBulkUpdate` links media to variants. A variant can reference only media already on its product.
• `fileUpdate` changes alt text, filename, content and product references.
• `productReorderMedia` changes media order as an asynchronous job, with position 0 as the primary image.
• `fileDelete` removes files permanently.

Fact: Shopify processes files asynchronously, and `fileStatus` moves through UPLOADED, PROCESSING, READY and FAILED. A connector must poll for READY before it links media to variants.

Integration patterns for Shopify

Shopify DAM integrations follow three patterns, and the pattern decides who serves the files and where the merchandiser works.

Fact: Shopify generates several image sizes on its CDN and transcodes video to 480p, 720p and 1080p in HLS and MP4. Fact: the Liquid `image_url` filter resizes images up to 5,760 pixels per side and never above the original size. A push connector therefore sends one high-quality master rendition and lets Shopify create the sizes.

The external URL pattern keeps one delivery layer for all channels. The headless DAM guide covers that architecture. Fact: Shopify documents that collection images can use Shopify CDN URLs or external image URLs. Product galleries, variant images and 3D viewers in standard themes rely on Shopify media, so most stores combine the push pattern with external URLs for campaign content.

Worked example: a catalogue of 2,000 products with six images each needs 12,000 files. At 250 files per `fileCreate` batch, the initial load takes 48 batches, plus polling for READY and one product update per product.

What must stay in sync with Shopify

Five changes in the DAM must reach Shopify within a stated time: updates, rights expiry, deletions, alt text and media order.

Fact: removing a file from a product deletes it from the product's media gallery and clears the image from variants that used it. A rights expiry run can therefore leave variants without an image. Fact: `fileUpdate` replaces content of videos and 3D models only for alt text and product references. A new video version needs a new file.

Usage rights need the most care. The rights management guide explains expiry handling in the DAM. The Shopify connector must turn each expiry into a removal and log it. Alt text needs the same discipline, and the accessibility and alt text guide covers the source side. Fact: Shopify's file mutations show one alt field per file, so buyers with several storefront languages ask how translated alt text reaches the store.

The four depth levels for Shopify

DAMSelection rates Shopify integration depth on the same four levels as every other platform, based on who builds and maintains the connector.

Vendor ratings appear on vendor profiles once verified. The integrations overview explains the scale for all platforms.

What to test in a Shopify demo

A Shopify demo tests the full product media loop on a development store with the buyer's own products and assets. Add these steps to the scripted demo.

1. Connect the DAM to a development store and show the access scopes the app requests.
2. Attach six approved images to one product from the DAM, including one master above 4,472 pixels.
3. Confirm the connector sends a supported rendition and the files reach READY.
4. Link two images to colour variants and set the primary image.
5. Replace one image with a new version in the DAM and show the same Shopify URL with the new file.
6. Upload a video and a GLB model and attach both to the product.
7. Change alt text in the DAM and show the change on the Shopify file.
8. Expire the rights on one image and show its removal from the product and variants.
9. Delete an asset in the DAM and show the Shopify result and the log entry.
10. Load 500 files in one run and show error handling for a failed file.
11. Show the report of products that use a given DAM asset.

The panel scores each step pass or fail against criteria written before the demo. The Demo Script Generator formats the steps as a scenario.

Common failure points

Shopify DAM integrations fail at six points that a buyer checks before signature.

• Oversized masters: images above 20 MB or 4,472 pixels fail without automatic renditions.
• Asynchronous processing: a connector that links variants before files reach READY creates errors.
• Duplicate files: repeated pushes of the same asset fill the Files library with copies.
• Variant gaps: removing a file clears variant images, so expiry runs need a fallback image rule.
• Video versions: videos and 3D models cannot have their content replaced, so update logic differs per media type.
• API versions: Shopify releases a new API version every quarter and supports each stable version for at least 12 months. A connector that falls behind stops working.

Questions for the DAM vendor

The buyer sends these questions in writing before the demo and asks for documentation with each answer.

1. Who builds, hosts and supports the Shopify connector, and which API version does it use today.
2. Which pattern does the connector use: push to Shopify media, external URLs or both.
3. How does the connector choose the rendition for each media type and limit.
4. How does the connector store the DAM asset ID in Shopify to prevent duplicates.
5. What happens in Shopify when rights expire, and how fast.
6. How does the connector handle alt text for several languages.
7. How many files per hour can the connector load, and how does it retry failures.
8. What does the connector cost, and is it priced per store, per product or per call.