What does it mean when multiple records share a KERN ID?
Last updated: June 21, 2026
Short answer
When multiple CRM records share the same KERN ID, Kernel has resolved them to the same real-world entity. That can support duplicate handling, reporting, and matching logic, but it does not automatically mean Kernel will merge the records.
The final merge decision still depends on duplicate rules, safeguards, primary record selection, survivorship rules, and customer configuration.
What to check
- Do the records have the same KERN ID on the same object: Account or Kernel Account?
- Are the records in an active merge group?
- Which record is marked primary or keeper?
- Are any of the records safeguarded or excluded from actioning?
- Is the group a true duplicate group, or are the records intentionally separate operating records?
- Has the action queue been recalculated after the latest configuration changes?
Common causes
- The records are true duplicates and are waiting for review or merge approval.
- The records share identity but are protected by safeguards.
- The records match identity but fail a configured duplicate rule.
- The records are deliberate duplicates that should remain separate.
- The KERN ID is available before the merge/action queue has recalculated.
What to send support
- All Salesforce Account IDs in the group.
- The shared KERN ID.
- Current merge group status, if visible.
- Primary/keeper record, if visible.
- Any safeguard or error shown in the action queue.
- Why the customer expected these records to merge or stay separate.