One Taxonomy, Two Systems: Aligning DAM and PIM Before You Integrate

Most digital asset management (DAM) and product information management (PIM) integrations don’t fail because of the connector. They fail because the two systems were never describing the same things in the same way. The DAM calls a product “Trail Runner 2 Navy.” The PIM knows it as SKU 40418-NVY. A person can tell those are the same shoe. An integration can’t.

We’ve written before about why DAM and PIM so often stop talking and what that gap costs. This post is the practical follow-up. Conversations about DAM keep turning to integrations, content supply chains and AI. All of it depends on the groundwork below. Here’s a checklist to work through before anyone writes a line of mapping logic.

1. Choose one shared identifier, and decide what level it lives at

Every integration needs a key that both systems trust. For most brands, that’s a stock keeping unit (SKU) or a Global Trade Item Number (GTIN). The choice matters less than the agreement. Pick one, document it and make it a required field on every product-related asset.

The harder question is level. Does an image belong to a style, a color variant or a single size? A lifestyle photo of a jacket might apply to every size in a color. A swatch applies to one color only. A spec sheet might apply to the whole product family. If your identifier only exists at one level, some assets will always be linked to the wrong thing, or to nothing at all.

Checklist:

• One identifier named as the integration key
• A clear rule for which product level each asset type attaches to
• The identifier required on upload, not added later

2. Agree on naming standards both systems can read

File names are often the first place a DAM and PIM disagree. Creative teams name files for people (“jacket_front_final_v3.jpg”). Integrations need names that machines can parse.

You don’t have to invent a standard. The GS1 Product Image Specification defines a structure that starts with the 14-digit GTIN and adds codes for image type, facing and state. A file named 09504002100016_A1N1 tells any system which product it shows, that it’s a primary web image and that it’s a front view of the packaged item. Even if you don’t adopt GS1 naming in full, borrowing the idea of a fixed, position-based pattern saves a lot of cleanup.

Checklist:

• A written naming convention, with examples, that starts with the shared identifier
• Codes for view or angle, asset type and version
• A decision on whether file names or metadata fields are the source of truth (metadata is usually safer)

3. Decide who owns each field

This is the step teams most often skip, and it’s the one that causes the most arguments later. When a field exists in both systems, one of them has to win. Aprimo puts it simply in its guide to DAM integrations: the DAM should own governed digital assets, and the PIM should own product attributes.

That rule covers most fields. The gray areas are where you need a decision in writing. A starting point:

Checklist:

• A field-by-field ownership list signed off by both the DAM and PIM owners
• One-way sync for every shared field, from the owner to the other system
• A named person to settle new gray-area fields as they come up

4. Line up your vocabularies

Two systems can share an identifier and still disagree on meaning. The PIM says “Navy.” The DAM says “Dark Blue.” One system uses “US” and “CA” for markets. The other uses “North America.” Each of those mismatches breaks a filter, a sync rule or a search.

Controlled vocabularies fix this. Start with the fields that will actually be mapped: color, category, market, language and product line. For each one, agree on a single list of allowed values and decide which system maintains it. If your category tree lives in the PIM, the DAM should reference it rather than keeping its own version.

Checklist:

• Pick lists, not free text, for every mapped field
• One maintained list per field, owned by one system
• A crosswalk for legacy values you can’t clean up right away

5. Define what moves, and when

An integration isn’t one big sync. It’s a set of rules about which assets move under which conditions. Without those rules, unapproved drafts reach retailers and expired images stay live long after their rights end.

Write down the triggers. A common set: an asset moves to the PIM when it’s approved, linked to a valid identifier and within its rights window. It’s removed or flagged when rights expire or the product is discontinued. Product lifecycle status in the PIM (new, active, discontinued) often drives the second half of that rule.

Our earlier post on where digital asset transformations should happen covers a related decision: whether resizing and format changes for each channel happen in the DAM or the PIM. Settle that here too.

Checklist:

• Clear conditions for an asset to sync (approved, linked, in rights)
• Clear conditions for removal (expired, discontinued, replaced)
• A decision on where channel-specific renditions are created

6. Test on one product family first

Once the rules are written, try them on a small, messy slice of your catalog. Choose a product family with several variants, a few older assets and at least one rights restriction. You’ll find gaps in the ownership list and vocabulary faster than any planning meeting would.

Track a few simple measures before and after: how many assets are linked to the right product, how many sync errors come up, and how long it takes a new product’s images to reach the PIM. Those numbers make the case for the full rollout.

Build the agreement, then build the connection

A connector moves data. It can’t decide what the data means. When the identifier, naming, ownership and vocabulary decisions are made first, the integration itself becomes the easy part. That’s true whether you’re connecting Bynder or Aprimo to Salsify, Akeneo, or Syndigo, and whether you use a native connector or a managed integration like Plezio Fuse.

Ready to get your DAM and PIM speaking the same language before you connect them? Contact us to talk with Sitation’s DAM Implementation and PIM & PXM teams about taxonomy, field ownership and integration planning.