When many enrichment pipelines touch the same employer, the question is not only what changed — it is who said so. This release tightens change-history labeling so map applies, registry sync, identity peels, and registry merges read clearly in admin CRM timelines across languages.
Source labels you can trust
Company and contact change-history timelines now include consistent source labels for public registries, OpenStreetMap apply, identity peels, cross-border repairs, and registry dedup merges — in English, German, French, Italian, and Polish.
What you will notice:
- Map and registry events no longer fall back to a generic “System” label
- Merge and peel reasons stay readable when two sources disagree about identity
- Locale parity so DE/FR/IT/PL admins see the same source vocabulary as EN
Why it matters for research
Whether you are validating a store phone filled from OpenStreetMap or an officer contact from a public registry, the timeline should name the pipeline. That keeps Platform CRM auditable when enrichment and human edits share the same record.
Admin timelines stay multilingual
Source and merge-reason strings ship in every UI locale so a German or French admin does not fall back to English labels for the same enrichment event.
What you will notice:
- Consistent vocabulary for OpenStreetMap apply, registry sync, peels, and merges
- Fewer “unknown source” fallbacks in non-English admin sessions
What day-to-day users notice
You may not see admin timelines every day — but denser, better-attributed employer records mean company pages and contact maps stay more honest when enrichment runs in the background.
What you will notice:
- Employer pages that accumulate clearer history over time
- Fewer mystery “system” edits on shared research records
- Locale-consistent labels when you switch admin UI language
Built for multi-source honesty
Enrichment only helps when you can reconstruct it. This release makes the changelog side of Platform CRM match the breadth of sources already writing into it.