---
title: Understanding System Readiness
description: "System Readiness is VendorHearth Pro's built-in installation and configuration check. It helps identify problems that could prevent VendorHearth features from working correctly before you begin accepting vendor applications. Access it from your WordPress Dashboard by going to: **VendorHearth Pro →…"
url: "https://vendorhearth.com/docs/understanding-system-readiness/"
updated: "2026-09-22"
category: "Getting Started — installation, activation, Setup Wizard, System Readiness, first-time configuration"
---

# Understanding System Readiness

System Readiness is VendorHearth Pro's built-in installation and configuration check.

It helps identify problems that could prevent VendorHearth features from working correctly before you begin accepting vendor applications.

Access it from your WordPress Dashboard by going to:

**VendorHearth Pro → System Readiness**

We recommend checking System Readiness after initial setup, after moving VendorHearth to another website, and whenever you experience a system-wide problem.

## What Does System Readiness Check?

VendorHearth evaluates several important parts of your installation.

### VendorHearth Version

VendorHearth verifies information about the currently installed version of the plugin.

Keeping VendorHearth updated helps maintain compatibility with WordPress, PHP, payment services, and other system components.

### Database and Schema

VendorHearth uses its own database tables to store information such as applications, events, payments, agreements, communications, and other operational records.

System Readiness checks that the required database structure is available.

A database-related warning may indicate that installation or an update did not complete correctly.

### VendorHearth Pages

VendorHearth uses WordPress pages for its front-end portals.

These can include:

- Vendor Registration
- Vendor Login
- Vendor Dashboard
- Vendor Check-In
- Vendor Event Packet
- Vendor Relations
- Organizer Portal

System Readiness checks that the pages required by VendorHearth are available.

Do not permanently delete VendorHearth portal pages unless you understand how that page is being used by the system.

### User Roles

VendorHearth creates specialized WordPress roles so users can access the appropriate parts of the system without receiving unnecessary WordPress permissions.

These include roles for:

- Vendors
- Vendor Relations
- Event Staff

System Readiness checks that VendorHearth's required roles are installed and configured.

### Role Isolation

VendorHearth also checks that its specialized roles remain appropriately separated from WordPress Administrator access.

This is important because vendors and limited staff users should not receive administrative control over your WordPress website simply because they have access to VendorHearth.

### Setup Status

System Readiness checks whether the initial VendorHearth setup has been completed.

If setup is incomplete, return to:

**VendorHearth Pro → Setup Wizard**

and review the remaining configuration.

### File Uploads

Several VendorHearth features rely on your WordPress website's ability to accept uploaded files.

Uploads may be used for items such as:

- Vendor logos
- Product photos
- Vendor documents
- Event materials
- Vendor maps

System Readiness checks that the necessary upload environment is available.

### Automation and WordPress Cron

VendorHearth uses scheduled WordPress processes for automated tasks.

These processes support features such as reminders, deadline processing, event archiving, waitlist processing, and other scheduled VendorHearth operations.

System Readiness checks whether the environment needed for these scheduled processes is available.

If WordPress cron is disabled or unable to run, some VendorHearth automation may not occur when expected.

### Payment Configuration

If your organization accepts online payments, VendorHearth checks relevant payment configuration.

A payment warning does not necessarily mean the rest of VendorHearth is unusable. However, you should resolve payment configuration issues before asking vendors to make live payments.

For detailed payment setup instructions, see the **Payments** documentation.

## What Should I Do If a Check Fails?

A failed readiness check identifies an area that needs attention. It does not necessarily mean VendorHearth is completely unusable.

Start by reviewing the message shown with the failed check.

Depending on the issue, you may need to:

- Complete an unfinished setup step
- Restore or recreate a required VendorHearth page
- Correct a WordPress role or permission problem
- Verify that file uploads are enabled
- Check WordPress cron
- Complete payment gateway configuration
- Review your hosting environment

For more technical information about your installation, open:

**VendorHearth Pro → System Information**

System Information provides additional details that can help diagnose a problem.

## When Should I Check System Readiness?

We recommend checking System Readiness:

- After installing VendorHearth Pro
- After completing the Setup Wizard
- Before opening your first event for applications
- After migrating your WordPress website
- After making significant server or hosting changes
- After a major WordPress or PHP change
- When multiple VendorHearth features unexpectedly stop working

You do not need to check System Readiness every time you use VendorHearth.

## Is Every Warning an Emergency?

No.

Some readiness messages identify configuration that only affects a particular feature.

For example, an incomplete payment configuration is important if you plan to accept online payments, but it does not mean your vendor records suddenly disappear or that every other VendorHearth feature has stopped functioning.

Read the specific message and address the affected area before relying on that feature.

## Before Going Live

Before opening VendorHearth to real vendor applications, review System Readiness and resolve any problems that affect the features you plan to use.

You should also complete at least one test of your vendor workflow before launch.

## Next Step

Once your VendorHearth installation is ready, continue to **Creating Your First Event**.
