The product images live in the store, the originals on the photographer’s hard drive and the cut-outs in the agency’s Dropbox folder. Someone built separate versions for Amazon. Nobody knows exactly which license covers the lifestyle shots. This works for a long time. Until the photographer changes, a marketplace introduces new image rules or a legal claim arrives.
A DAM system is supposed to fix this chaos. Most guides on the topic come from DAM vendors. They are written for the marketing departments of large brands and skip one question: does an online store need a DAM at all? This guide is vendor-neutral. It is written for online stores and D2C brands in Europe, with a focus on the DACH region, with €500,000 to €50 million in revenue.
The short answer
What is a DAM system? A DAM system (digital asset management) is a central image and media library for companies. It manages images, videos and documents with metadata, rights, versions and approvals. It delivers the right version to every channel.
Does your store need one? Most online stores with fewer than about 2,000 products and a team of up to five people do not need a separate DAM. The media management in the store or well-organized cloud storage is enough. A PIM with a DAM module pays off when more channels and languages are added. A standalone DAM pays off mainly when many people work with licensed images or you share images with retailers and press.
What does a DAM cost? From zero (included in the store plan) through about €7 to €22 per user for cloud storage to several thousand euros a month for an enterprise DAM. For PIM and DAM, add an implementation of about €5,000 to €40,000.
What is a DAM system?
A DAM system is a central place for digital media with clear rules. Media (“assets”) include product photos, cut-outs, lifestyle images, videos, 3D files, logos, manuals and data sheets.
A DAM mainly does six things a normal folder cannot:
- Metadata: Every image has fields such as SKU, image type, alt text, photographer and license.
- Search: You find images by these fields, often also via AI image recognition.
- Rights: Licenses, expiry dates and model releases are stored with the image.
- Versions and approvals: Everyone sees which version is approved.
- Output per channel: One original produces the right sizes and formats for store, Google and marketplaces.
- Sharing: Retailers, press and agencies get access via a portal.
PIM vs DAM, and where the store fits
PIM and DAM are often confused. Both are “central sources”. But they manage different things.
| PIM | DAM | Store media management | |
|---|---|---|---|
| Manages | product data: copy, attributes, prices, variants | media: images, videos, documents | media shown in the store |
| Key question | What is the product? | What does it look like, and may we use the image? | What does the store show right now? |
| Rights and licenses | no | yes | no |
| Output to several channels | yes, data | yes, images in the right formats | only its own store |
| Typical users | e-commerce, purchasing | marketing, photography, agencies, partners | store team |
Many PIM systems now include a DAM module, for example Plytix, Akeneo, Pimcore and Ergonode. For many online stores this is the best middle ground. Images are attached directly to the product and variant. They flow to all channels together with the product data. When a PIM pays off is covered in the article on PIM for Shopify.
Store media management is not a DAM. Shopify and Shopware store images and deliver them fast. But rights, licenses, approvals and versions for other channels are missing.
Do you need a DAM? The decision guide
Whether a DAM pays off does not depend on revenue. What matters is how many images, channels, languages and people come together. And whether you use licensed images or share them with others.
Projects with online retailers point to four stages:
| Stage | Typically fits when | Running cost | Limit |
|---|---|---|---|
| 1: Media management in the store | under 500 products, store only, 1 to 2 people, only own photos | included in the store plan | no originals, no rights, no channel versions |
| 2: Cloud storage with clear rules | up to approx. 2,000 products, 1 to 2 marketplaces, agency or photographer involved | approx. €7 to €22 per user per month | order depends on discipline, no connection to the store |
| 3: PIM with a DAM module | thousands of products and variants, several channels or languages | approx. €150 to €3,500 per month | brand and campaign assets and portals often limited |
| 4: Standalone DAM | many people involved, licensed images with expiry dates, images for retailers or press, many campaigns | approx. €100 to €3,500 per month, enterprise considerably more | a project of its own, needs an owner |
When you don’t need a DAM
A separate DAM is too big for many stores. You usually don’t need one if:
- you mostly use your own product photos, without licenses that expire
- no more than five people work with the images
- you don’t share images with retailers, press or partners
- the images are only needed in the store and on one or two marketplaces
In that case a clean naming convention does more than new software. A DAM without rules and without an owner just moves the old chaos to a new place.
Your stage in one minute
The decision helper shows which stage fits your store. It also estimates what searching for and recreating images costs you per year.
- Typical tools
- –
- Running cost
- –
- Effort
- –
- Cost of searching for images per year
- –
Your inputs and the result are copied into the contact form.
Guidance from project practice, not a quote. Prices from vendor websites or buyer data, as of November 2026.
The four ways compared
| Criterion | Store media | Cloud storage | PIM with DAM | Standalone DAM |
|---|---|---|---|---|
| Examples | Shopify Files, Shopware media | Google Drive, SharePoint, Dropbox | Plytix, Ergonode, Akeneo, Pimcore | Dash, pixx.io, Kontainer, Bynder, Canto |
| Image linked to product and variant | yes, only in the store | only via file names | yes | via metadata and connector |
| Rights and expiry dates | no | only as a list | limited | yes |
| Versions for channels | no | manual | partly automatic | automatic |
| Portal for retailers and press | no | share links | partly as an add-on | yes |
| Implementation effort | low | low | medium | medium to high |
Cloud storage is better than its reputation. With a fixed folder structure by SKU, a naming convention and a license list, many stores do well for years. What is missing is the connection to the store: every image has to be uploaded by hand.
PIM with DAM is the middle ground for most growing stores. Images and product data live together. A new image is immediately in the store, the Google feed and on marketplaces.
A standalone DAM plays to its strengths when marketing, sales and partners need images that are not tied to individual products. Examples are campaigns, logos, press images or videos.
Why images become mandatory work in 2026 and 2027
Product images are no longer just design. Several rules make managing them an obligation.
| Channel | Key requirement |
|---|---|
| Google Merchant Center | from 31 Jan 2027 at least 500 × 500 pixels; no watermarks, promotional text, borders or placeholders; do not remove AI labeling in the metadata |
| Amazon | main image on a pure white background, product fills about 85 percent, no text and no logo, 1,000 pixels or more for zoom |
| Zalando, OTTO | own formats and backgrounds per category, for fashion usually images on a model |
| Shopify | up to 20 MB and 25 megapixels per image, at most 250 media per product |
| ChatGPT product feed | one publicly accessible main image per variant as a mandatory field |
| Own store | alt text for informative images (European Accessibility Act, in Germany since 28 Jun 2025) |
This leads to a simple rule: one original image becomes many versions. Google wants a different format than Amazon, Zalando a different one than your own store. If you build these versions by hand, you quickly end up with dozens of files per product. This is exactly where a DAM or a PIM with a DAM module helps.
AI image labeling is easy to overlook. Google requires that the source information in the IPTC metadata of AI-generated images is preserved. But many paths to the web strip this metadata: image compression, CDN or the upload to the store.
Good images also reduce returns. According to KPMG and EHI, 60.4 percent of German online shoppers name an inaccurate description or images that differ from the product as a reason for returns (December 2025). According to Bitkom, 41 percent of returns happened because the product did not match the image or description (2023). According to Baymard, 56 percent of users look at the images first on the product page. More on this in the article on product data quality.
Image rights and AI images: what stores need to know
Even simple product photos are protected. Under German copyright law (§ 72 UrhG), photos are protected at least as “simple photographs”. This also applies to plain cut-outs. Using images without a matching license risks cease-and-desist letters and damages.
Licenses have limits. Typical traps:
- The license only covers the store, not marketplaces or ads.
- The license expires after a certain period.
- A model only consented to certain channels.
- Manufacturer images may only be used for that manufacturer’s goods.
A DAM keeps this information right with the image and warns before expiry. In stages 1 and 2 you need at least a license list.
Purely AI-generated images are usually not protected. The prevailing view in Germany is that purely AI-generated images lack human creation. The Munich Local Court took the same view in February 2026. The consequence: competitors may be able to reuse such images. Document which images were created with AI and how people edited them.
Labeling AI images. The transparency obligations of the EU AI Act (Article 50) have applied since 2 August 2026. They mainly affect providers of AI tools. Retailers as users are mainly affected by deceptively realistic content (“deepfakes”). Whether an AI product photo falls under this is still legally open. If in doubt, have it reviewed.
Which DAM? Vendors with prices
The table shows solutions that are relevant for online stores in Europe. Many vendors do not publish prices.
| Vendor | Type | Price | Shopify | Shopware | Data location |
|---|---|---|---|---|---|
| Plytix | PIM with DAM | from €0 / €149 / €699 per month, rises with product count | app | no plugin found | not stated |
| Ergonode | PIM with DAM | €0 / from €5,990 / from €19,990 per year | CSV export | no plugin found | not stated |
| Pimcore | PIM with DAM | Community free; Professional $9,900, Enterprise $29,900 per year | no official plugin checked | integration by shopware AG and partners | self-hosted |
| Akeneo | PIM with DAM | not public | app | partner connector | cloud |
| Dash | DAM | from €99 per month, unlimited users | in all plans | no plugin found | EU (Ireland) |
| pixx.io | DAM | €20 / €40 / €80 per admin user per month, billed yearly, Team from 3, Business from 5 admins | app | no plugin found | Germany per vendor |
| Kontainer | DAM | €430 to €1,995 per month, store plugins extra | plugin | plugin | not stated |
| Bynder | DAM | not public; buyer data: median around $40,000 per year | app | plugin by signundsinn | Frankfurt, EU-only possible |
| Canto, Brandfolder, Frontify, Fotoware, 4ALLPORTAL | DAM | not public | partly app | no plugin found | per vendor |
| Cloudinary | image CDN with DAM | from $89 per month (yearly), Shopify app Pro $999 per month | app | no plugin found | USA, EU only on Enterprise |
Three observations from the market:
- For Shopware, the choice is small. The Shopware Store has practically only one current DAM connector, the one for Bynder. Other DAMs are connected via the vendor’s API, an agency or a PIM in between.
- For Shopify there are many apps, but little track record. Almost all DAM apps in the Shopify App Store have zero to three reviews. Test the integration with real products before you decide.
- Pimcore is no longer classic open source. Since version 2025.1 it uses its own “Open Core” license. Many comparisons still call it open source.
The market leaders according to Forrester (Adobe, Aprimo, Bynder, OpenText, Orange Logic) are usually too big for stores with €0.5 to €50 million in revenue. They tend to pay off for brands with many countries and large marketing teams.
What does a DAM system cost?
The license is only one part. Plan for these cost blocks:
- License or subscription: per user, per storage or flat
- Implementation: define structure and metadata, set up rights
- Migrating the images: review the existing stock, rename, add metadata
- Integration: plugin, app or custom interface to store and PIM
- Operation: one person who maintains structure and metadata permanently
Vendor figures for mid-sized organizations are $5,000 to $15,000 for implementation and migration, plus $3,000 to $10,000 for integrations. A rule of thumb from practice: in year one, a DAM costs about 1.5 to 2 times the annual license.
Be careful with ROI promises. Vendors advertise Forrester studies showing 168 to 434 percent return. These studies are commissioned by the vendor and based on interviews with about four customers each, mostly large companies. They do not transfer to a store with €3 million in revenue. The frequently quoted figures on search time are 14 to 25 years old. Calculate with your own values instead, for example in the decision helper above.
Connecting a DAM to Shopify and Shopware
Shopify
Shopify stores images in “Files” and on products. Depending on the plan, 100 GB (Basic) to 1 TB (Plus) are available for files. Images may be up to 20 MB and 25 megapixels. Shopify delivers them automatically as WebP or AVIF. A product can have at most 250 media. The increase to 2,048 variants did not change that.
DAM apps connect in three ways:
- As a product image: The DAM copies the image to the product or variant. Shopify’s limits still apply.
- As a file with a metafield: Additional images, PDFs or 3D files go into Files and are linked via metafields.
- As a link: The image stays in the DAM and is delivered from there.
Shopware
Shopware 6 has solid media management with folders, thumbnails per folder, alt texts and tags. Rights, licenses and approvals are missing. For connecting a DAM there are two modes, which the Bynder plugin also offers:
- CDN mode: Shopware shows the image directly from the DAM.
- Copy: Shopware stores a copy and generates its own thumbnails.
For every integration, check how quickly changes reach the store. With the Bynder plugin this can take up to an hour.
Implementation in six steps
- Take stock: Where are which images today? How many are there per product? Which licenses apply?
- Define names and metadata: A pattern like
SKU_variant_imagetype_number.jpgand a fixed list of metadata fields (template below). - Record rights: photographer, license scope, channels, expiry date and model release per image.
- Migrate images: best-selling products first, then the rest. Sort out duplicates and outdated images along the way.
- Connect and test: connect store, PIM and feeds. Test with real products and variants, including special cases like bundles.
- Assign ownership: One person is responsible for structure and metadata. Without one, every system decays.
Template: metadata for product images
| Field | Example | Purpose |
|---|---|---|
| File name | TS-1042_blue-M_cutout_01.jpg | assign the image to the variant without a system |
| SKU and GTIN | TS-1042, 4012345678901 | link to store, PIM and feeds |
| Image type | cut-out, in use, detail, scale, model | pick the right images per channel |
| Alt text EN and DE | Blue organic cotton T-shirt, front view | accessibility and image search |
| Channels | store, Google, Amazon | only supply approved channels |
| Photographer and license | Studio Example, license all online channels | prove usage rights |
| Usage right until | 31 Dec 2027 | renew or replace in time |
| Model release | yes, online only | rights of the person shown |
| AI origin | no / AI-generated / AI-edited | labeling for Google and documentation |
| Approval | approved on 12 Oct 2026 | only publish current images |
AI in DAM: what really helps in 2026
Almost every DAM now advertises AI. Three features actually help online stores:
- Automatic tagging: The AI recognizes color, subject and image type and pre-fills metadata. This saves a lot of time with large existing libraries. You still have to check the results.
- Cut-outs and variants: remove backgrounds, create formats for channels, derive color variants.
- Generated images: lifestyle images from cut-outs, for example with Google Product Studio. The notes on rights and labeling above apply here.
For AI search, the image is also a data field. Google AI Mode and ChatGPT Shopping read images from the feed. Make sure the same main image appears in the store, the Google feed, structured data and social media previews. This is easiest with one central source.
Checklist: is your image management ready?
FAQ
What is a DAM system?
A DAM system (digital asset management) is a central image and media library for companies. It manages images, videos and documents with metadata, rights, versions and approvals and delivers the right version to every channel.
What is the difference between PIM and DAM?
A PIM manages product data such as copy, attributes, prices and variants. A DAM manages media such as images, videos and documents including their rights. Many PIM systems include a DAM module, which is enough for many online stores.
Does an online store need a DAM system?
Usually not below about 2,000 products and five people involved. Store media management or well-organized cloud storage is then enough. A standalone DAM pays off mainly with many people involved, licensed images with expiry dates and images for retailers or press.
What does a DAM system cost?
Cloud storage costs about €7 to €22 per user per month. PIM with DAM costs about €150 to €3,500 per month, a standalone DAM for stores about €100 to €3,500 per month. Add an implementation of about €5,000 to €40,000. Enterprise solutions cost considerably more.
Are Google Drive or SharePoint enough as an image library?
For many smaller stores yes, if folders by SKU, a naming convention and a license list are used consistently. But the connection to the store, automatic channel versions and rights management on the image are missing.
Which DAM works with Shopify?
Many DAMs offer a Shopify app, for example Bynder, Dash, pixx.io, Canto, Cloudinary and Air. PIM systems with DAM such as Plytix and Akeneo also have apps. Most apps have hardly any reviews. Test the integration with real products and variants.
Which DAM works with Shopware?
The Shopware Store has practically only one current DAM connector, the one for Bynder. Other DAMs are connected via the vendor’s API, an agency or a PIM such as Pimcore or Akeneo.
Are AI-generated product images protected by copyright?
Under the prevailing view in Germany, not if they were generated purely by AI. Competitors may then be able to reuse them. Document which images were created with AI and how they were edited, and have individual cases reviewed legally.
Is there a free DAM system?
Yes, some vendors have free entry plans, for example Plytix, Ergonode and Cloudinary. Pimcore is available as a free Community Edition for self-hosting. Still, plan for costs for setup, operation and integration.
Conclusion: structure first, then software
Most online stores don’t need a big DAM. They need structure: a naming convention, a home for originals, a license list and an owner. As channels and languages grow, a PIM with a DAM module is often the best next step. A standalone DAM pays off when many people work with licensed images or you share images with others.
More important than the choice of tool in 2026 are the obligations around images. These include Google’s minimum sizes from 2027, alt texts, image rights and the labeling of AI images. If you have these under control, you sell more and get fewer returns.
Sources
- KPMG with EHI: Returns as an opportunity, press release (11 Dec 2025, German)
- Bitkom: Online shopping – one in ten purchases is returned (2023, German)
- Baymard: Product images and descriptive text
- Baymard: Current state of e-commerce product page UX (2026)
- Google Merchant Center: Image requirements
- Google Merchant Center: AI-generated images and IPTC metadata
- OpenAI: Commerce product feed spec
- Shopify Help Center: File uploads
- Shopify Help Center: Product media types
- Shopify Changelog: Automatic image optimization in AVIF
- Shopware Docs: Media
- Shopware Store: Bynder integration (signundsinn)
- Plytix: Pricing (knowledge base, 10/2026)
- Ergonode: Pricing
- Pimcore: Pricing
- Dash: Pricing
- pixx.io: Pricing (German)
- Kontainer: Pricing
- Cloudinary: Pricing
- Vendr: Bynder pricing from buyer data
- Bynder: Hosting and data location
- Sharedien: Forrester Total Economic Impact (06/2025)
- Forrester: Total Economic Impact of Wedia (06/2024)
- Brandlife: DAM pricing guide
- IT-Recht Kanzlei: Image theft online, cease-and-desist and damages (German)
- DFN: Infobrief Recht 4/2026 (Munich Local Court on AI images, German)
- IHK: Accessible websites (German)
- Google Merchant API: Generate images with Product Studio
