Skip to main content
Back to E-commerce Dictionary

Data Lineage

Data management and qualityAdvanced Level

Data lineage is the record of where a piece of data came from, which steps changed it and where it went, from source to final destination.

Image by · CC BY 4.0

What is Data Lineage?

Data lineage is the record of where data comes from, how it changes along the way and where it ends up. For product data, it traces a value such as a price or a description from the supplier file through import, mapping and enrichment to the webshop or marketplace. Lineage answers questions like: which file set this weight, which rule rewrote this title, and which channels received the change. It is close to data provenance, which focuses on the origin of the data, while lineage covers the full path including transformations. An audit trail logs who changed what; lineage connects those events into one flow. It is a core part of data governance, because you cannot fix or defend data you cannot trace.

Why Data Lineage matters for e-commerce

Product data in e-commerce passes through many hands: suppliers, ERP, PIM, enrichment, feed tools and channels. When a wrong value shows up on a product page, lineage tells you where it entered and which step to fix, instead of correcting the symptom in one place. Lineage also matters for compliance. Rules such as the EU Digital Product Passport ask brands to show where product information comes from. A clear record of sources and changes makes those questions easier to answer.

Examples of Data Lineage

  • 1Value: Product weight 2.4 kg, Source: supplier CSV of 3 March, Step: unit converted from grams, Destination: Shopify and Google Shopping
  • 2Value: English title, Source: ERP name, Step: rewritten by a title template, Destination: webshop
  • 3Value: German description, Source: English description, Step: AI translation, Destination: German storefront
  • 4Value: Sale price, Source: base price, Step: channel pricing rule, Destination: marketplace feed
Image by · CC BY 4.0

How WISEPIM Helps

  • Product import keeps your column mapping per source, so you can see which file field feeds which attribute.
  • Operation history lists bulk operations on your catalog, and on paid plans you can undo one.
  • Rollback Import reverses an import that brought in wrong data.
  • Pricing rules per channel and Template Strings make derived values explicit instead of hidden in manual edits.

Common mistakes with Data Lineage

  • Editing values by hand in the channel, so the source and the shop drift apart without a record.
  • Documenting lineage once in a diagram and never updating it.
  • Tracking only who changed a value, not where the value came from.
  • Letting several systems overwrite the same field without a clear owner.

Tips for Data Lineage

  • Name one system as the source for each field, such as ERP for price and PIM for descriptions.
  • Keep import mappings per supplier and store the original files.
  • Avoid manual edits in channels; change the source and let the data flow again.
  • Start lineage with the fields that cause the most errors or legal risk.

Trends around Data Lineage

  • Regulation such as the Digital Product Passport increases demand for traceable product data.
  • AI-generated content raises the question of which text a person wrote and which a model wrote.
  • Data catalogs and lineage tools from data engineering are being connected to PIM and ERP systems.

Tools for Data Lineage

  • WISEPIM (import mapping, Operation history and Rollback Import)
  • Collibra
  • Microsoft Purview
  • OpenLineage with dbt or Airflow

Related Terms

Access Control (PIM)Attribute Dependency ManagementAttribute InheritanceAttribute ManagementAttribute mappingAttribute Scoping

Also Known As

data provenancedata audit traildata flow tracking

Frequently Asked Questions

Data lineage is the record of where data comes from, how it changes and where it goes. For product data, it traces a value from the supplier file through import and enrichment to each sales channel.

Provenance is about the origin of data: who created it and from which source. Lineage covers the whole path, including every transformation and destination. Provenance is the start of the lineage.

No. An audit trail logs individual events, such as who changed a field and when. Lineage connects those events into a flow from source to destination, so you can see how a value was built.

Governance sets owners and rules for data. Lineage shows whether those rules hold in practice, because it reveals which system set a value and which steps changed it.

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

Keep exploring

Hand-picked next steps to go deeper.