---
title: Managing Duplicate Vendor Records
description: "VendorHearth Pro is designed so a vendor can maintain one central profile while participating in multiple events. Creating unnecessary duplicate vendor records can separate applications, payments, communications, and other history that should belong to the same vendor. ## How Duplicate…"
url: "https://vendorhearth.com/docs/managing-duplicate-vendor-records/"
updated: "2026-09-23"
category: Vendors — vendor accounts, profiles, Vendor Dashboard, vendor management
---

# Managing Duplicate Vendor Records

VendorHearth Pro is designed so a vendor can maintain one central profile while participating in multiple events.

Creating unnecessary duplicate vendor records can separate applications, payments, communications, and other history that should belong to the same vendor.

## How Duplicate Vendors Can Happen

Duplicate vendor records may be created when:

- An organizer manually creates a vendor who already exists
- Existing applications are imported
- A vendor registers using a different email address
- A business name is entered differently
- Staff members create records without first checking for an existing vendor

Checking for an existing vendor before creating a new record can prevent many duplicate records.

## Search Before Creating a Vendor

Before manually creating a vendor, search VendorHearth for the business or vendor.

Check information such as:

- Business name
- Vendor name
- Email address
- Phone number

A slightly different business name does not necessarily mean it is a different vendor.

## Check Existing Vendors During Imports

When importing an existing application, VendorHearth can work with an existing vendor or create a new vendor record.

Use an existing vendor when the application belongs to a business already in VendorHearth.

This helps keep the vendor's event history together.

## Business Name Changes Do Not Require a New Vendor

If a vendor changes their business name, update the existing vendor profile when appropriate.

For example:

**Old Name:** Willow Creek Creations
**New Name:** Willow Creek Candle Co.

If this is still the same business and vendor account, a completely new vendor record may not be necessary.

The same applies to changes in:

- Logos
- Product descriptions
- Social media accounts
- Contact information

## Check Email Addresses Carefully

A vendor may accidentally create another account using a different email address.

Before assuming two records represent different vendors, compare their business and contact information.

At the same time, do not combine records simply because two businesses have similar names.

Verify that they actually represent the same vendor.

## Why Duplicates Matter

Duplicate vendor records can split important information between multiple profiles.

For example:

**Vendor Record A**

- Spring Market application
- Payment history
- Agreement records

**Vendor Record B**

- Holiday Market application
- Updated logo
- New contact information

If both records belong to the same vendor, organizers may not immediately realize that the information is divided.

## Do Not Delete Records Without Reviewing Them

If you discover a duplicate vendor, do not immediately delete one of the profiles.

First review whether either record contains:

- Applications
- Payments
- Agreements
- Documents
- Communications
- Booth assignments
- Event history

Deleting a vendor record that contains legitimate history may remove information you intended to preserve.

## Confirm the Correct Account

If duplicate records involve WordPress user accounts, determine which account the vendor should continue using.

Make sure the vendor's active account has the appropriate **Vendor** role and is associated with the correct VendorHearth information.

Do not give the vendor elevated WordPress permissions simply to resolve an account issue.

## Prevention Is Easier Than Cleanup

The easiest way to manage duplicate vendors is to avoid creating them.

Before adding a vendor manually or importing an application:

1. Search for the business.
2. Search for the vendor's email address.
3. Check similar business names.
4. Use the existing vendor when appropriate.
5. Create a new record only when it truly represents a different vendor.

## Keep One Central Vendor Record

Whenever possible, a vendor's applications across multiple events should connect back to the same central vendor profile.

This gives organizers a clearer view of the vendor's history and keeps VendorHearth easier to manage as the number of events and vendors grows.

## Next Step

Continue to **Understanding Vendor Roles and Access** to learn how VendorHearth separates vendor permissions from Organizer, Vendor Relatio