To be listed on WPBay, a product must meet a set of minimum standards to ensure it is functional, secure, and clearly presented to customers. These requirements help maintain a consistent level of quality across the marketplace and provide buyers with the confidence that the product has been properly prepared and documented.

A WPBay-ready product must include the following components:

1. Complete and Working Code
The plugin or theme must be fully functional and installable on a standard WordPress installation. It should follow WordPress coding standards and not rely on deprecated functions or insecure practices. Products that cause errors, warnings, or break site functionality will be rejected or disabled.

2. Readme File
Every product must include a readme.txt or README.md file containing basic usage instructions, installation steps, and a changelog. This file should clearly explain what the product does, any dependencies it has, and how users can get started.

3. License Declaration
You must include a license file such as license.txt that clearly states the licensing terms under which the product is distributed. This must comply with WPBay’s licensing policy and accurately reflect whether the product is GPL, MIT, proprietary, or under another approved license. Products without a license will not be accepted. Also, you must have the rights to sell the product (the product must be developed by you or you must own selling rights for it).

4. Screenshots or Demo Images
At least one screenshot is required to visually communicate the product’s functionality. High-quality images showing the frontend, backend, or key features are strongly encouraged. Screenshots should be relevant, unbranded, and ideally in JPG or PNG format.

5. Product Description and Metadata
A clear product title, description, and relevant tags must be provided during submission. The description should outline what the product does, who it is for, and what problems it solves. If your product has multiple plans or versions (e.g., Free vs. Pro), these differences should be clearly documented.

6. Version Number
All submissions must include a defined version number. This helps track updates and ensures users know what version they are installing. The version should follow semantic versioning when possible (e.g., 1.0.0, 1.1.1).

7. Compatibility and Requirements
You should specify the minimum WordPress version, PHP version, and any plugin or theme dependencies required for your product to function properly. Products that are incompatible with current WordPress versions or that rely on unlisted third-party components may be rejected.

8. No Malicious or Obfuscated Code
Code must be clean and human-readable. Obfuscated, encrypted, or malicious scripts are strictly prohibited. Submissions are scanned for such issues, and violators may be banned from the platform.

Meeting these baseline requirements does not guarantee approval, but it is the first step toward becoming a verified WPBay seller. Additional review may be performed to assess usability, security, and overall quality.

For a full list of guidelines and best practices, sellers are encouraged to consult the WPBay Seller Documentation or reach out to the WPBay review team.