AfieldIn this article
Similar names and a shared logo do not establish that two records represent the same buying team. Resolve the website relationship first, then record what you know about purchasing and outreach.
Build the entity register before merging
Demo: the Northline organizations below are fictional. An inspection-software campaign needs the team responsible for a factory’s quality process.
| Observed record | What the source says | Decision | Still unknown |
|---|---|---|---|
| Northline Group | About page lists several operating companies. | Keep as the parent record. | Whether it qualifies vendors centrally. |
| Northline Components | Own catalogue and plant address; identifies Northline Group as parent. | Keep the operating record and link it to the parent. | Who owns software procurement for the plant. |
| Northline regional URL | Redirects to a language version of the group website. | Record as an alias of the group website rather than another prospect. | Whether regional purchasing differs; the redirect does not answer that. |
Keep the captured URL and the page that establishes the relationship. Removing a tracking parameter may help compare addresses; it does not establish that two legal or operating entities should merge. A different language, shared domain or plant address is also insufficient on its own.
Coordinate contact without deleting the account structure
If both sites direct supplier inquiries to the same form, prepare one approach naming the relevant components business. If the operating company has its own supplier route, record that route and the campaign owner so another teammate does not independently send a conflicting group-level pitch.
Campaign: Inspection-report software
Operating account: Northline Components
Parent: Northline Group
Approach owner: Avery
First route: Shared supplier inquiry form, naming Components
Related-account action: Group-level outreach on hold pending routing reply
Next question: Does Components qualify software vendors independently?Use a reversible merge record for actual duplicates
A different spelling of the same operating account may be a genuine duplicate. Before merging, retain enough information to undo the decision:
Original records: DEMO-014 “Northline Components”; DEMO-027 “Northline Comp.”
Primary record: DEMO-014
Reason: Same operating entity and site; second name is an abbreviation
Preserve: Both source URLs, contacts, notes and message history
Do not merge: Parent record DEMO-001
Reviewer and date: Avery, 10 October 2026If a later reply establishes separate vendor qualification, correct the relationship and review affected drafts. Do not erase the earlier research trail. In a spreadsheet or CRM, use the available export or history mechanism before making an irreversible merge; the example above describes the information to retain, not a claim that every tool can restore it automatically.