Short answer
A SAP Commerce Cloud DAM integration is a connector that turns approved DAM assets into SAP Commerce media items, grouped in media containers and tagged with media formats per storefront use. SAP Commerce Cloud stores media files in Azure Blob Storage. Fact: media items are catalog-aware, so a new or withdrawn image reaches the storefront only after catalog synchronisation.
What a SAP Commerce Cloud DAM integration must do
A SAP Commerce Cloud DAM integration must create the right media items in the right containers and formats, attach them to products, and remove them when rights end.
| Function | Direction | Why it matters |
|---|---|---|
| Create media items | DAM to SAP Commerce | Each file or URL becomes a media item in a catalog version |
| Group formats | DAM to SAP Commerce | A media container holds one image in every format the storefront needs |
| Fill missing formats | DAM or SAP Commerce | Either the DAM sends each rendition or SAP Commerce converts it |
| Attach to products | DAM or PIM to SAP Commerce | Containers in a product's gallery images drive the product page |
| Synchronise | Inside SAP Commerce | Staged changes reach the Online catalog only after synchronisation |
| Withdraw | DAM to SAP Commerce | Expired assets leave the Staged and then the Online catalog |
The DAM integrations guide places commerce platforms among the other DAM connections. SAP Commerce Cloud usually receives product data from a PIM, so read DAM vs PIM before you assign ownership. DAMSelection assessment: decide whether the DAM or SAP Commerce creates the format renditions before the first demo. That one decision sets the connector design, the storage volume and the test plan.
How SAP Commerce Cloud models media
SAP Commerce Cloud models media as catalog-aware media items, each with one media format, grouped in media containers.
SAP Learning describes the media management framework in four building blocks. The table summarises them with the role each plays for a DAM connector.
| Element | What SAP documents | What the DAM connector must handle |
|---|---|---|
| Media item | Holds a URL that points to the physical file, with a unique ID such as 30124_medium | Create one per file and catalog version, with a stable code |
| Media format | Each media item has exactly one; the format labels intended use, such as 96Wx96H | Map DAM rendition presets to SAP media formats |
| Media container | Groups media items with the same content in different formats or encodings | Keep one container per DAM asset |
| Catalog version | Media items belong to a catalog version and synchronise across versions | Write to Staged and trigger or wait for synchronisation |
Fact: SAP states that format names are labels with meaning only to business users. SAP Commerce does not check that a 96Wx96H media item is 96 by 96 pixels. The storefront picks the best matching media item from the container, based on the available space and the assigned format.
Fact: the media file stays in place during catalog synchronisation. Only the media item and its URL synchronise.
Worked example: 10,000 products with four gallery images in four formats need 160,000 media items in the Staged catalog. Synchronisation creates another 160,000 media items in Online, all pointing to the same 160,000 files.
Media storage in SAP Commerce Cloud
SAP Commerce Cloud stores media files in Azure Blob Storage, and the DAM connector writes files there through the platform's media services.
Fact: SAP Learning states that SAP Commerce Cloud supports only the Azure Blob Storage mechanism for media, through the default `azurecloud` extension. The `amazoncloud` and `gridfsstorage` extensions were removed. The general framework lesson lists Amazon S3, Azure Blob and MongoDB GridFS as storage options, and the removals narrow that list for SAP Commerce Cloud.
DAMSelection assessment: count the storage twice in the five-year cost model. The DAM keeps masters and renditions, and SAP Commerce keeps its own copies of every format it serves. Read the image CDN glossary entry for the delivery side.
Media formats and conversion
SAP Commerce Cloud fills missing media formats through conversion groups and conversion media formats, run against a source media item in each container.
Fact: SAP Learning describes the flow in Backoffice. A conversion group defines the required formats. The media container holds the conversion group and the source media, so it can tell which formats are missing. The action "Convert missing Medias" generates the missing files and places them in the container.
- In SAP Commerce Cloud public cloud, conversion needs the `cloudmediaconversion` extension. Without it, the convert action stays disabled.
- An SAP Community article on CCv2 image processing describes a remote image conversion service that runs ImageMagick commands, switched on with `enableImageProcessingService` in `manifest.json`.
- On older on-premises set-ups, the same article describes conversion against a local ImageMagick installation.
- A conversion media format carries a conversion command with ImageMagick options, such as `-resize 300x300`, according to an SAP Community walkthrough.
DAMSelection assessment: two conversion designs work, and each has a different owner.
| Design | Who creates formats | Strength | Watch-out |
|---|---|---|---|
| DAM renders every format | DAM rendition presets | One rendition rule set for all channels | Connector must push four or more files per asset |
| SAP Commerce converts | Conversion group in SAP Commerce | Connector pushes one master per asset | Format rules live in two systems |
| External URLs | DAM delivery layer or image CDN | No file copies in SAP Commerce | Search indexing and storefront code need changes |
The external URL design appears in the same SAP Community article. A DAM supplies asset URLs, the integration creates media and media container models, attaches the container to the product, and adjusts the Solr image value provider. The headless DAM guide covers the delivery architecture behind that design.
What must stay in sync with SAP Commerce Cloud
Four DAM changes must reach SAP Commerce Cloud within a stated time: new versions, rights expiry, deletions and format rule changes.
The mechanisms are a DAMSelection assessment, based on the catalog-aware media model SAP documents.
| DAM change | What must happen in SAP Commerce | Mechanism |
|---|---|---|
| New version of an image | Replace the source and every derived format in the container | Push all formats, or replace the source and convert again |
| Rights expiry | Remove the container from the product in Staged, then synchronise | Connector update plus catalog synchronisation |
| Deletion in the DAM | Remove media items and containers that no product uses | Connector clean-up job |
| New rendition rule | Add or change a media format across all containers | Bulk conversion run or bulk push |
Usage rights need the most care. A removal in Staged leaves the image live in Online until synchronisation runs. DAMSelection rule of thumb: agree a maximum time from DAM expiry to Online removal, and test it with the real synchronisation schedule.
The four depth levels for SAP Commerce Cloud
DAMSelection rates SAP Commerce Cloud integration depth on the same four levels as every other platform, based on who builds and maintains the connector.
| Level | What it means for SAP Commerce Cloud | Evidence DAMSelection accepts |
|---|---|---|
| 4 Native connector | Extension built and maintained by the DAM vendor | Vendor documentation or an SAP Store listing by the DAM vendor |
| 3 Partner or marketplace connector | Extension built by a third party | Marketplace listing naming the developer |
| 2 Documented API pattern | DAM guide for creating SAP media items and containers | Published developer guide |
| 1 Custom build only | No connector or guide | Explicit statement that a custom build is required |
Vendor ratings appear on vendor profiles once verified. The integrations overview explains the scale for all platforms.
What to test in a SAP Commerce Cloud demo
A SAP Commerce Cloud demo tests the full media loop in a development environment with the buyer's products, formats and assets. Add these steps to the scripted demo.
- Show the extension or integration service and the SAP Commerce version it supports.
- Attach four approved images to one product in the Staged catalog.
- Show one media container per image, with a media item for every required format.
- Show which system created each format: DAM rendition or SAP conversion.
- Synchronise to Online and show the product page with the correct formats.
- Replace one image in the DAM and show the new file in every format.
- Expire the rights on one image and time its removal from Online.
- Load 1,000 images in one run and show error handling for a failed file.
- Show the report of products that use a given DAM asset.
The Demo Script Generator formats the steps as a scenario.
Common failure points
SAP Commerce Cloud DAM integrations fail at five points that a buyer checks before signature.
- Format mismatch: DAM preset names that do not match SAP media format codes leave containers incomplete.
- Missing conversion: without `cloudmediaconversion`, missing formats stay missing.
- Synchronisation lag: Staged changes, including rights removals, wait for the next synchronisation.
- Orphaned media: deleted products and replaced images leave media items and files behind.
- Duplicate containers: repeated pushes of one asset create extra containers on the product.
Questions for the DAM vendor
The buyer sends these questions in writing before the demo and asks for documentation with each answer.
- Who builds, hosts and supports the SAP Commerce Cloud connector, and which versions does it support.
- Does the connector push all formats, push one master for SAP conversion, or reference external URLs.
- How does the connector map DAM rendition presets to SAP media formats.
- How does the connector store the DAM asset ID to prevent duplicate containers.
- What happens in Staged and Online when rights expire, and how fast.
- How does the connector clean up orphaned media items and files.
- What does the connector cost, and is it priced per environment, per catalog or per asset.
Frequently asked
Does SAP Commerce Cloud have a built-in DAM?
SAP Commerce Cloud has a media management framework with media items, formats, containers and conversion, managed in Backoffice. DAMSelection assessment: the framework serves the storefront and lacks the rights records, approval workflows and brand portal of a DAM. Most enterprises push approved product media from a DAM into it.
What is a media container in SAP Commerce Cloud?
A media container in SAP Commerce Cloud groups media items that show the same content in different formats or encodings. A product's gallery images hold containers, and the storefront picks the best matching format from each one. A DAM connector usually keeps one container per DAM asset.
Can SAP Commerce Cloud resize images itself?
SAP Commerce Cloud resizes images through conversion groups and conversion media formats, which generate missing formats in a media container. In SAP Commerce Cloud public cloud, conversion needs the `cloudmediaconversion` extension. Test conversion speed and quality on your own masters in the demo.
Why does a new product image not appear on the storefront?
A new product image stays off the storefront until the Staged catalog synchronises to Online, because media items are catalog-aware. Synchronisation copies the media item and its URL, while the file stays in place. Check the synchronisation schedule before you set integration service levels.
Where does SAP Commerce Cloud store media files?
SAP Commerce Cloud stores media files in Azure Blob Storage, through the default azurecloud extension, according to SAP Learning. Support for Amazon S3 storage through the amazoncloud extension was removed. Media items in the catalog hold the URL that points to each stored file.