DAM (Digital Asset Management)
A DAM (digital asset management system) is the system of record for product media files — packshots, lifestyle photos, 360 spins, video, CAD models, spec sheet PDFs, safety data sheets. It stores the master file, generates channel-specific renditions, tracks usage rights, versions replacements, and serves stable CDN URLs. A PIM stores attributes about the SKU; a DAM stores the files attached to it. The two link by SKU.
What a DAM does
A DAM is a system of record for files. It takes in the original image, video, CAD drawing, or PDF, keeps the master, and hands out the right rendition to whoever asks for it.
The work it does that a shared drive does not:
- Renditions on demand. One master packshot becomes a 3000px white-background JPEG for Amazon, a 600px WebP for your PDP, and a 100px thumbnail for search results — without anyone opening Photoshop.
- Metadata on the file. Shot type, photographer, color profile, capture date, alt text, embargo date.
- Rights tracking. Which supplier photos are licensed for resale listings only. Which co-op images expire when the program ends.
- Versioning. Replacing the 2024 packshot of a UL listed 600V wire connector without orphaning the URL already syndicated to a dozen channels.
- Delivery. A stable CDN URL you can drop into a feed row.
The unit of a DAM is the asset. The unit of a PIM is the SKU. That one difference decides where every field lands.
DAM vs PIM: where the line sits
Both systems store things about products. They answer different questions.
| Dimension | DAM | PIM |
|---|---|---|
| Unit of record | The file (asset ID) | The SKU (product ID) |
| Typical content | Packshots, lifestyle shots, 360 spins, video, STEP/CAD files, spec sheet PDFs, SDS | Thread pitch, voltage rating, GTIN, MPN, UNSPSC code, UOM, long description |
| Publish rights | Yes — license, rights window, embargo | No |
| Channel crop and size | Yes | No |
| Missing primary image | No | Yes — as fill rate on an image-URL attribute |
| GTIN of a given bolt | No | Yes |
| What it versions | File versions and renditions | Attribute values and workflow state |
| What it sends downstream | Asset URLs | The feed row that references them |
The practical rule: if the answer lives inside a file, it belongs in the DAM. If the answer is a value you could sort, filter, or validate a rule against, it belongs in the PIM.
Some PIMs include a media module, and some DAMs carry enough product metadata to look PIM-shaped. A module does not move the line — it puts both sides of it under one login.
Where the line blurs, and what breaks there
Three failure modes show up over and over in B2B catalogs.
The attributes are inside the assets. The thread pitch, torque spec, and plating callout for a 3/8-16 Grade 8 hex bolt are printed on a supplier PDF sitting in the DAM. The DAM stores that PDF perfectly and knows nothing about what's in it. The PIM has an empty thread_pitch field. Nobody is wrong; the data is just trapped in a file.
Nobody owns the link. The DAM holds tens of thousands of assets; the PIM holds more SKUs than that. The join is a filename convention that broke three suppliers ago, so image_url_1 on the PDP points at a 2019 rendition of a discontinued part.
Coverage is invisible. A DAM reports on assets it holds. It cannot tell you which SKUs in your fastener category have zero images, because those SKUs never had an asset for it to hold. That gap only surfaces on the PIM side, as fill rate — and only if someone modeled image count as an attribute.
All three are completion problems, not storage problems. Buying a second system doesn't close them.
Where Anglera fits
The PIM stores your product data. The DAM stores your product files. Anglera does the work of completing what's in both.
That work looks like:
- Reading the assets. Pulling the voltage rating, wire gauge range, and UL file number out of a supplier spec sheet PDF and writing them into PIM attributes as structured values with a source citation.
- Finding the gaps. Reporting which SKUs are missing a primary image, an SDS, or a CAD file for the channels they're listed on — so the photo shoot and the supplier chase get prioritized by revenue, not alphabetically.
Anglera is not a DAM and not a PIM. Keep both. Anglera reads from them, does the enrichment work, routes the judgment calls to a human reviewer, and writes the results back where your channels already read from.
Frequently asked questions
What is the difference between a DAM and a PIM?
A DAM manages files — images, video, CAD models, spec sheet PDFs — including renditions, usage rights, and versioning. A PIM manages attributes about the SKU: GTIN, MPN, voltage rating, thread pitch, UOM, descriptions. The DAM's unit is the asset; the PIM's unit is the product. They link by SKU, and the PIM usually holds the asset URL as an attribute.
Do I need both a DAM and a PIM?
If your channels require rich media at scale — 360 spins, video, CAD downloads, controlled brand imagery — a DAM earns its place. Smaller catalogs with a handful of images per SKU often get by storing asset URLs in the PIM and files on a CDN. The deciding factor is rights management and rendition volume, not SKU count.
Can a PIM replace a DAM?
A PIM holds the asset URL as an attribute, which covers a catalog with a few images per SKU. The DAM-shaped work is license and rights windows, video, large CAD binaries, and dozens of renditions per master. If your channels need that, check whether your PIM's media module covers it before buying a second system. If it doesn't, a dedicated DAM is worth pricing out.
What is a rendition?
A rendition is a derived copy of a master asset, sized and formatted for one destination. One master packshot yields a 3000px white-background JPEG for Amazon, a 600px WebP for your PDP, and a 100px thumbnail for search. The master never changes; the DAM generates and serves each rendition from it, so replacing the master updates every downstream copy at once.
Where do spec sheets and safety data sheets belong?
The file belongs in the DAM. The facts inside it belong in the PIM. A supplier PDF for a UL listed 600V wire connector holds the voltage rating, wire gauge range, and UL file number — values your PDP filters and your channel feeds require as fields. Store the PDF, extract the values, and keep both linked to the SKU.