Submitting your product to the Woo Marketplace

We look forward to reviewing your extension, theme, or integration for listing in the WooCommerce.com Marketplace. Before getting started, make sure you have signed up for a vendor account, and are logged into your vendor dashboard.

Pre-submission checklist

<details> <summary>Business review</summary>

This includes an analysis of the product's business model and revenue share structure with Woo, as well as product rationale, competition, and developer/company history.

• Mutually beneficial partnership: Products must share revenue with Woo, exclude spam links, affiliate links, or links to upsell products outside of the Woo Marketplace. See our monetization expectations.
• Trademark compliance: Ensure that product names do not violate Woo's trademark guidelines. Select a unique name that builds your brand and sets your product apart from others. Review our product name guidelines.
• Competitive pricing: Is the proposed price equal to or less than the price of the product sold in other environments? Select a suggested price that matches the price you sell elsewhere.

</details> <details> <summary>Development guideline compliance</summary>

• Products must follow security best practices.
• Products must support PHP 7.4+ as a minimum (PHP 8.3+ strongly recommended).

:::warning PHP 7.4 End of Life PHP 7.4 reached End of Life (EOL) in November 2022. Using it may expose sites to security vulnerabilities. :::

• Products must support the two latest major releases of both WooCommerce and WordPress.
• Products must adhere to foundational guidelines outlined in our developer hub.
• If your pricing model is based on a standard, tiered monthly subscription, you will be required to implement the SaaS Billing API before launch. API keys and sandbox access are granted manually after products are submitted for Marketplace consideration.
• Products must be able to pass the following Quality Insights Toolkit (QIT) tests:
  • API
  • End-to-end (E2E)
  • Activation
  • Security
  • PHPCompatibility
  • Malware
  • Validation

</details> <details> <summary>User experience compliance</summary>

• The product review includes a deeper analysis of the product's user experience (UX) and user interface (UI).
• Ensure that your product's critical flows have been thoroughly tested. See an example of critical flows in the core WooCommerce plugin.
• Extensions must adhere to development best practices and UX guidelines.
• Themes must adhere to design, and UX guidelines. If you are submitting a block theme, also review theme development.
• Accessibility: It is important that all customers can use the stores where your extension is installed. Extension submissions must meet the WordPress Accessibility Coding Standards. For more information, review WordPress's accessibility quick start guide.
• Does the product have a single core purpose and use WooCommerce features as much as possible?
• Can the product function "out of the box" without much configuration?

</details> <details> <summary>Compatibility with top Woo extensions</summary>

Products should not cause issues with widely-used Marketplace extensions. If your product is found to break any of these extensions when installed alongside them, it may be rejected or removed from the Marketplace.

Popular extensions include:

• WooCommerce Bookings
• WooCommerce Subscriptions
• Product Add-Ons
• Product Bundles
• Min/Max Quantities
• Shipment Tracking

</details> <details> <summary>Compatibility with core WooCommerce features</summary>

Visitors expect the WooCommerce.com Marketplace to be the leading source of extensions and themes for the optimal ecommerce experience. This means we only accept submissions which are compatible with the latest enhancements to the core WooCommerce platform and overall merchant experience.

Review Woo's public roadmap for primary initiatives and expectations.

<details> <summary>Block editor compatibility</summary>

As we evolve within the WordPress ecosystem, we're placing a strong emphasis on block editor compatibility for WooCommerce extensions. While we continue to support classic and hybrid approaches, prioritizing block editor compatibility ensures your extensions align with the latest trends and offer users a more intuitive and cohesive experience.

• Cart and Checkout blocks: The block-based Cart and Checkout is now the default experience in WooCommerce, offering a more streamlined and visually cohesive shopping experience. As a developer, prioritizing compatibility with these default blocks ensures your extensions and themes seamlessly integrate with the enhanced default shopping flow. Review Cart and Checkout block architecture.
• Extensions: Eliminate shortcode dependency. Many plugins/extensions still rely on shortcodes to output content. To enhance block editor compatibility, it is essential that these shortcodes are provided as blocks. This not only future-proofs your product but also allows users to leverage the full potential of the block editor's capabilities.
• Themes: While we continue to accept classic and hybrid themes, we are prioritizing block themes for the Woo Marketplace. Block themes are designed to fully leverage the capabilities of the block editor and provide users with a more intuitive and flexible content creation experience.

</details> <details> <summary>HPOS compatibility</summary>

High-Performance Order Storage (HPOS) is the default experience for new WooCommerce stores. It moves order data from the WordPress post and postmeta tables to dedicated order tables to improve scalability and reliability.

:::info All new extension submissions must be HPOS-compatible. View our HPOS recipe book for ways to support HPOS in your product. :::

</details> </details>

Submitting a product for review

From your vendor dashboard, navigate to Submissions > Submit Product and select the product type you're planning to submit:

• Extension
• Theme
• SaaS
• Business Service

:::note Freemium products Freemium products — products with both free and paid versions — require two separate submissions, one for each model. These will later be merged into a single product page where users can choose between versions. :::

File upload and submission info

The information required varies slightly depending on the submission flow selected. To help streamline the submission process, we only ask for critical details:

• Product upload
• Business details
• Testing instructions

Next, address any submission test failures noted in the discussion dialog. In the event of failures — marked as Failed — please click the View link beside the failed test to review the results and upload a modified version of your submission.

If necessary, replace the previously uploaded file to test again. When tests fail, the submission status updates to Changes required.

To proceed, click the Replace button to replace the current .zip file with a corrected version. This will automatically restart the testing process.

:::tip If your product is at a stage other than Changes required, you will not be able to replace this file. Please comment within the submission to request a status change from the Marketplace team. :::

Review process

Once the submitted product passes automated code tests, it moves to our review queue. Once it has been reviewed, the reviewer will share feedback (if any) with you.

A review consists of the following steps:

1. Business review: to ensure your product is a good fit for the Marketplace, and that there is a business model to share revenue.
2. Code review: to ensure the submitted product's code is original, secure, and aligned with overall WordPress and WooCommerce quality standards.
3. User experience (UX) review: to ensure the product works as expected and its look and feel aligns with our UX guidelines.
4. Launch preparations: once a submission successfully passes these review phases, it will be formally approved and proceed to onboarding for launch.

FAQs

<details> <summary>How long will it take for my product to be reviewed?</summary>

Once the submission is in business review, you can expect a formal decision from a reviewer within 30 days. Throughout the review process, we may provide feedback and request changes before rejecting or approving a submission.

</details> <details> <summary>Can I resubmit a previously rejected product?</summary>

Yes. You are welcome to resubmit products, providing the previously-received feedback was incorporated and your product was improved to comply with our guidelines and quality standards.

</details> <details> <summary>Why does my QIT test result link show "Invalid URL" or say it has expired?</summary>

• QIT test result links are temporary signed URLs. They expire after a short period of time. This is expected and not an error.
• To get fresh results, re-run the test from the submission in your Vendor Dashboard. New links will be generated with the updated results.

</details>

Submission support

For additional questions related to your submission, please use the discussion box below the Submission Bot results table in the Submission progress tab within your vendor dashboard.