Bluestone PIM DAM integration: which DAM platforms connect best

What a Bluestone PIM DAM integration does

A Bluestone PIM DAM integration keeps the master file and its rights in the DAM, and keeps the decision about which product uses that file in Bluestone PIM.

Bluestone PIM is a product information management system built on MACH principles, according to its Cloudinary partner listing. The DAM owns the original file, its renditions, its descriptive metadata and its usage rights. Bluestone PIM owns product attributes, product structure and the publication of product data to channels. The integration carries identifiers, links and a selected set of metadata between the two systems.

The split matters because Bluestone PIM also ships its own asset module. A buyer must first decide which files live in Bluestone PIM and which stay in a DAM. Without that decision, teams upload the same packshot twice and the two copies drift apart within one season.

DAMSelection assessment: DAM and PIM form one product content supply chain, so buyers agree the shared data model before the first demo. The DAM vs PIM guide sets out the ownership split, and combined PIM and DAM selection covers running both selections at once.

How Bluestone PIM models assets and media

Bluestone PIM models media in two ways: native assets stored in Bluestone PIM and served through its media service, and external assets held as links in an External assets library.

Native assets

Facts from the Bluestone PIM help centre:

• Fact: native assets are typed as Image, Audio, Video, Document, Text or Other, with a maximum file size of 128 MB.
• Fact: every upload becomes a version, and Bluestone PIM marks the current version.
• Fact: an asset carries a name, description, labels and an availability setting, plus read-only file data such as dimensions and uploader.
• Fact: each asset takes at most 10 attributes, and compound, column and matrix attribute types are unsupported on assets.
• Fact: an asset can link to many products, and to catalogues or categories.

Availability decides publication. Public assets are available for channels. Automatic, the default, publishes the asset when a linked product is published. Internal assets are never published.

Media service

Fact: Bluestone PIM serves public assets through a media service on Amazon CloudFront, with URLs that follow the pattern media.bluestonepim.com/orgID/PID/filename. Query parameters resize, crop, trim and convert images, with output formats JPG, PNG, GIF, WebP and AVIF. The service upscales small images by default unless the request adds the only-shrink-larger flag. Media fetched from the CDN counts toward a monthly data transfer quota, and overages are billed under the contract.

External assets library

Fact: Bluestone PIM's External DAM Connector, listed on the Bluestone PIM Extension Hub and built by Bluestone PIM, connects external DAM libraries to the PIM. The help article states that the External assets library stores links to assets hosted elsewhere, with no file upload. Each entry holds a title, URL, description, asset type, labels, source and status.

Fact: only active external assets are available in channels. Deleting an entry removes the link and leaves the file in the DAM untouched. The Public API exposes external media under a metadata entry named external-media, with fields such as url, status, mediaType and sortIndex.

Integration patterns for Bluestone PIM

Bluestone PIM's External assets library favours the reference pattern, in which Bluestone PIM stores a DAM URL against the product and the DAM keeps the file.

DAMSelection assessment: the reference pattern suits most buyers who already run a DAM, because the file, its versions and its rights stay in one place. The trade-off is that Bluestone PIM sees only a URL, a status and labels. Renditions then come from the DAM, and the Bluestone media service resizing and cropping apply to native assets only, as far as the documentation shows.

The push pattern suits teams without a separate DAM, or with a DAM that only holds campaign material. It gives one delivery URL pattern and one transfer quota to manage. The DAM integrations guide compares the patterns in more detail, and the image CDN entry explains URL-based delivery.

What the integration must keep in sync

A Bluestone PIM DAM integration must keep five things aligned: renditions, metadata, the asset-to-product link, rights expiry and deletions.

Rights expiry is the item most likely to fail silently, because a URL stays valid in Bluestone PIM until someone sets the entry inactive. The rights management guide explains the licence exposure, and the metadata mapping guide gives a template for field ownership.

Worked example: a manufacturer with 5,000 products and 4 external images per product holds 20,000 links in the External assets library. A storage move in the DAM that changes 5% of URLs breaks 1,000 product images at once. Permanent delivery URLs remove that risk before go-live.

How to read the Bluestone PIM depth table

The Bluestone PIM depth table holds two sourced cells on 14 October 2026: Cloudinary and Tenovos at level 3.

Fact: Cloudinary lists Bluestone PIM in its integrations directory as a technology partner in the PIM category, with the integration type partner-supported. The listing describes keeping an existing DAM and searching its content in Bluestone PIM by name, URL and description, which matches the External DAM Connector.

Fact: the Bluestone PIM Extension Hub showed 45 extensions on first load, and the External DAM Connector was the only DAM item. That connector is built by Bluestone PIM and names no DAM vendor, so DAMSelection scores no DAM vendor on it alone. Fact: a Bluestone PIM blog post of 27 November 2025 names Tenovos as an example DAM. Tenovos lists a Bluestone connector in Tenovos Connect without naming the builder, so DAMSelection scores the cell at level 3.

Every DAM vendor without a cell shows "Not verified". That status makes no claim about project-built integrations. The full grid sits in the PIM and DAM Fit Map, and the DAM integrations by platform index links every PIM page.

What to test in a Bluestone PIM DAM demo

A Bluestone PIM DAM demo proves the integration on your own products and assets, with Bluestone PIM and the DAM open side by side.

1. Connect 50 product images from your DAM to Bluestone PIM products through the External assets library, matched on a real product identifier.
2. Show the same products through the Public API and confirm the external-media entries carry the right URL and sort order.
3. Replace one image with a new version in the DAM and show whether the Bluestone PIM link still resolves to the current file.
4. Move one asset to a new folder in the DAM and confirm the URL in Bluestone PIM still works.
5. Set a rights expiry date on one asset to tomorrow, then show the external entry switch to inactive and leave the channel output.
6. Delete one asset in the DAM and show what Bluestone PIM displays, and who receives the alert.
7. Request a channel rendition, such as a 1,200-pixel WebP, and show which system generates it.
8. Show the delivery transfer volume for one month of channel traffic, if native assets serve any channel.

Script these steps in the demo script and repeat them during integration testing before go-live.

Common failure points

Bluestone PIM DAM integrations fail most often on URL stability, status handling and duplicate storage.

• DAM URLs that change on a storage move or rename, which breaks every linked product image.
• Expired assets that stay active in the External assets library, because nothing updates the status.
• Files uploaded both as native assets and as external links, with no rule for which one channels use.
• Channel renditions expected from the Bluestone media service for external links, where the DAM must supply them.
• Asset attributes planned beyond the limit of 10 per native asset.
• CDN transfer overages on native assets, discovered at the first busy sales season.