VendorHearth Pro allows organizers to duplicate an existing event instead of rebuilding a similar event from the beginning.
This is especially useful for recurring events or when several events use similar configurations.
Why Duplicate an Event? #
Duplicating an event can save time when a new event will use settings similar to an existing one.
For example, you may want to reuse an event as the starting point for:
- The next year’s version of the same event
- A recurring seasonal market
- Another event using similar booth options
- An event with similar vendor categories and limits
The duplicated event becomes a separate event that can be edited without changing the original.
Duplicate an Existing Event #
From your WordPress Dashboard:
- Go to VendorHearth Pro → Events.
- Locate the event you want to use as your starting point.
- Select Duplicate.
- VendorHearth creates a new event based on the selected event.
- Open the duplicated event and update its information.
- Save your changes.
Review the New Event #
A duplicated event should always be reviewed before it is opened for applications.
At minimum, verify the new event’s:
- Event name
- Event date or TBA status
- Location
- Application availability
- Booth types
- Booth pricing
- Booth capacity
- Vendor categories
- Category limits
- Application questions
- Agreements
- Paid Add-Ons
- Event map
- Vendor Spotlight settings
Do not assume every setting from the original event is appropriate for the new event.
What Happens to Vendor Applications? #
Duplicating an event is intended to duplicate the event’s configuration—not turn the vendors from the original event into applicants for the new event.
Vendor applications and participation records belong to their original event.
Vendors who want to participate in the new event should enter through the appropriate application or Season Pass workflow.
This keeps the history of each event separate.
Payments Are Not Duplicated #
Payment records from the original event do not become payments for the duplicated event.
Payments remain associated with the application and event for which they were originally recorded.
Agreement Acceptances Are Not Duplicated #
Historical agreement acceptance records are evidence of what a vendor accepted as part of a particular submission.
Duplicating an event does not create new agreement acceptance records for vendors.
When an agreement is required for a new application, the vendor should complete the appropriate acceptance process.
Update the Event Date #
Pay particular attention to the event date after duplication.
Date-dependent VendorHearth features can rely on this information, including:
- Automatic event archiving
- Vendor Spotlight scheduling
- Event operations
If the new event date has not been finalized, use TBA instead of leaving an old or inaccurate date in place.
Review the Event Map #
If the original event has an event map, verify whether that map is still appropriate for the duplicated event.
A venue or layout may change even when the event itself returns each year.
Replace outdated maps before distributing event information to vendors.
Review Pricing and Capacity #
Booth prices and capacities can change between events.
Before opening applications, confirm that the duplicated event reflects the pricing and space actually available for the new event.
Keep Applications Closed While Reviewing #
Do not open the duplicated event to vendors until you have reviewed its configuration.
This gives you time to correct inherited settings without vendors submitting applications based on outdated information.
Duplicating vs. Creating a New Event #
Use Duplicate when the new event will share a substantial amount of configuration with an existing event.
Create a completely new event when the events are significantly different.
Either method creates an independent event record that can be managed separately in VendorHearth.
Next Step #
Continue to Adding and Updating an Event Map to learn how VendorHearth handles event map images.
