VendorHearth Pro includes settings that control organization information, vendor-facing pages, payment configuration, email behavior, licensing, and other system features.
Most settings are configured during initial setup and only need occasional changes afterward.
Accessing VendorHearth Settings #
From your WordPress dashboard, open the VendorHearth menu and navigate to the appropriate settings area.
Available options are organized by their purpose so you can manage different parts of VendorHearth without changing individual vendor or event records.
Organization Information #
VendorHearth stores basic information about the organization using the system.
This may include information such as:
- Organization or market name
- Vendor contact information
- Email sender information
- Branding-related settings
Review this information if your organization’s name or contact details change.
Vendor Portal Settings #
VendorHearth uses front-end WordPress pages to provide vendors and staff with access to appropriate features.
Depending on your configuration, these may include:
- Vendor Registration
- Vendor Login
- Vendor Dashboard
- Vendor Event Packet
- Vendor Check-In
- Vendor Relations Portal
- Organizer Portal
VendorHearth needs to know which WordPress pages are being used for supported portal functions.
Vendor Dashboard Page #
The Vendor Dashboard page can be configured within VendorHearth.
The Vendor Dashboard uses:
[cmn_vendor_dashboard]
This page provides vendors with access to their VendorHearth information without requiring access to the WordPress administration area.
Registration and Login Pages #
VendorHearth provides front-end shortcodes for vendor registration and login.
Vendor Registration
[cmn_vendor_register]
Vendor Login
[cmn_vendor_login]
These pages allow vendors to create or access their accounts through the front end of your website.
Payment Settings #
VendorHearth’s payment settings contain the configuration required for supported payment processing.
For Square, this includes information such as:
- Environment
- Application ID
- Location ID
- Access Token
- Webhook configuration
- Signature Key
Payment credentials should be treated as sensitive information.
Never share your Access Token or Signature Key with vendors.
Email Settings #
VendorHearth allows you to configure information used when sending system emails.
This includes settings such as:
- From Name
- From Email
- Email templates
- Test email functionality
Your WordPress website must also have functioning email delivery for VendorHearth messages to reach vendors reliably.
Category and Event Settings #
Some VendorHearth configuration is managed at the individual event level rather than through global settings.
For example, events can have their own:
- Booth types
- Booth capacity
- Vendor categories
- Category limits
- Maps
- Spotlight scheduling options
- Operational information
Changing one event does not necessarily change your other events.
License Settings #
VendorHearth Pro includes license settings for activating your installation.
Your license provides eligibility for VendorHearth Pro updates and support during the applicable license period.
VendorHearth licenses do not automatically renew.
If you want continued update and support eligibility after the license period ends, you must manually renew your license.
What Happens if a License Expires? #
An expired VendorHearth Pro license does not delete your vendor data or automatically disable the installed system.
Your existing installation and functionality remain available.
However, an active license may be required for continued access to new VendorHearth Pro updates and support.
System Readiness #
After changing important settings, review:
VendorHearth → System Readiness
System Readiness can help identify problems involving areas such as:
- VendorHearth version and database
- Portal pages
- User roles
- Setup status
- Uploads
- Scheduled automation
- Payment configuration
This is especially useful after moving your site or making significant configuration changes.
Be Careful With Production Settings #
Avoid changing important settings simply to experiment on a live site.
Use particular care when changing:
- Payment credentials
- Portal pages
- User roles
- Email configuration
- License information
Incorrect settings can affect vendor access, payments, or communications.
Settings vs. Event Configuration #
Not everything in VendorHearth is a global setting.
A useful distinction is:
VendorHearth Settings control how the overall system operates.
Event Settings control how an individual event operates.
If a change should only affect one event, check that event’s configuration before changing a global VendorHearth setting.
Next Step #
Continue to Configuring Organization and Portal Settings to learn how to manage your organization information and VendorHearth’s front-end portal pages.
