VendorHearth Pro separates a vendor’s central business profile from their individual event applications.
This allows the same vendor to participate in multiple events while maintaining one primary vendor record.
One Vendor, Multiple Events #
A vendor does not need a new profile every time they apply for another event.
For example, the same vendor might participate in:
- Spring Market
- Summer Market
- Fall Market
- Holiday Market
Each event can have its own application and participation records while remaining connected to the same vendor.
Vendor Profile vs. Event History #
The vendor profile contains information about the business.
This can include:
- Business name
- Contact information
- Product description
- Categories
- Social information
- Logo
- Product photos
The vendor’s event history comes from their applications and participation in individual events.
Keeping these separate allows VendorHearth to maintain a more complete picture of the vendor.
Application Status Can Differ by Event #
A vendor’s status in one event does not determine their status in another.
For example, the same vendor could be:
Spring Market — Confirmed
Summer Market — Declined
Fall Market — Waitlisted
Holiday Market — Awaiting Payment
Each application maintains its own status.
Payments Belong to the Appropriate Event #
Payment activity is associated with the applicable application and event.
A vendor being paid for one event does not automatically mean they are paid for another event.
This distinction is important when a vendor participates in several events during the same year.
Booth Information Is Event-Specific #
Booth types, booth selections, and booth assignments also belong to individual events.
A vendor assigned to Booth 18 at one event should not automatically be considered Booth 18 at another event.
Each event maintains its own booth configuration.
Category Availability Can Change #
A vendor may generally be associated with a particular category, but category availability and limits are configured by event.
A vendor being accepted within a category for one event does not guarantee availability for that category at another event.
Agreements and Documents #
Agreement and document requirements may also vary depending on your VendorHearth configuration and event requirements.
Historical acceptance or document information should remain connected to the activity that actually occurred.
VendorHearth does not need to fabricate new historical records simply because a vendor participates in another event.
Communications and Activity #
VendorHearth maintains communication and activity information that can provide additional context about interactions with a vendor.
This can be useful when multiple staff members work with the same vendor over time.
Instead of relying entirely on memory, organizers can review the information maintained within VendorHearth.
Avoid Creating Duplicate Profiles #
Creating another vendor profile for every event breaks up the vendor’s history.
Before creating a vendor manually or importing an application, check whether the vendor already exists.
Whenever appropriate, connect new participation to the existing vendor.
Why Vendor History Matters #
Keeping vendor history together makes it easier to understand a vendor’s relationship with your organization over time.
It can help when reviewing:
- Previous applications
- Event participation
- Payments
- Communications
- Agreements
- Documents
- Booth information
VendorHearth provides the records; organizers can use those records as context when managing future activity.
Historical Records Should Remain Accurate #
Avoid changing old records simply to make them match a vendor’s current situation.
For example, if a vendor changed their business name, their central profile may need to be updated—but a legitimate historical payment should not be rewritten as though a different transaction occurred.
VendorHearth history is most useful when it accurately reflects actual activity.
Next Step #
Continue to Managing Duplicate Vendor Records to learn how to avoid unnecessary duplicate vendors and what to check when you believe the same vendor appears more than once.
