Article

Product records and content: how I work with scattered data

From master data to photos and videos: how I organise export, mapping and reimport to keep assets linked to the right product record.

Published 13 November 20264 min readProduct dataPIMDAM

Product information can be scattered across spreadsheets, PDFs, emails and the ERP. But putting the data in the same place does not finish the job: it must also reach the content describing that product. A photo or video without a link to the product record is still a file someone has to interpret. I start with that link, not the button for uploading a spreadsheet.

Before exporting, I establish the reference with you

By master data I mean the reference data for the product. Before designing how it reaches the assets, I ask where it lives and who can confirm it. I do not choose the right file by its name or the attachment date. If the sources disagree, someone who knows the product needs to decide, rather than a hidden import rule.

  • Which product record takes precedence when the spreadsheet and ERP disagree?
  • Who owns the data and who approves a correction?
  • Which fields do you actually need on photos, videos and other content?
  • How do you identify the product each asset belongs to?

Export, enrichment and back to the assets

For BaseCamp Studio I managed and developed the PIM side of the platform. I design the flow starting from the assets in the DAM, the digital content library. From the client's master data I export the structure and mapping: the correspondence between the source data and the fields that need to receive it. Then I enrich the data and reimport it, remapped onto photos, videos and other assets.

The point is to preserve the link to the product record throughout the journey. Reading a column is not enough: the information must return to the asset belonging to the product it describes. That is what makes this process different from a simple file import. Assets need to come out with coherent, usable information, not a disconnected copy of the original data.

The CSV module grew out of manual work

An earlier part of this work is the enrichment module using masterdata CSV files. You upload the file, the system maps columns and values, and it populates metadata on existing assets. No manual file-by-file edits. I built it because I had seen that work happen too often with hundreds of SKUs to align. The spreadsheet feeds the existing content instead of requiring someone to rewrite it by hand.

When organising the flow is worthwhile

I would consider it if you keep aligning product information and content by hand. If there is no agreed reference, I would start there. Choosing the tool is a separate question, covered in when you need a PIM. Likewise, AI asset enrichment is a distinct step, not a replacement for the product record. To work out how to connect your data to your content, we can examine the flow through custom software: write to me with your reference source and where you currently copy data by hand.

Let's talk

Tell me what's blocking you.

30 minutes, free. Afterwards I'll send you, in writing, the first 3 things I'd do. Or email me: the person doing the work reads and replies.