Getting to know the Woo Marketplace: A developer’s look

This article is the first part of a two-part series designed to guide you through the process of submitting your product to the Woo Marketplace. In this post, we’ll cover the basics—understanding the marketplace, preparing your product, and navigating the submission process. In Part 2, coming next week, we’ll take a deep dive into the tools and criteria used during the review process, including the Quality Insights Toolkit (QIT).


What is the Woo Marketplace?

The Woo Marketplace is a curated platform where developers like you can list extensions, themes, and other products that enhance the functionality of WooCommerce stores. It’s a trusted destination for merchants looking for high-quality solutions to grow their businesses.

By listing your product on the marketplace, you gain:

  • Exposure: Reach WooCommerce users worldwide.
  • Credibility: Being part of the marketplace signals trust and quality.
  • Revenue potential: Earn income through product sales while reaching a global audience.

The Woo Marketplace is a partnership between you and WooCommerce. While they provide the platform and visibility, you retain control over your product’s development, maintenance, and support.

Preparing your product for submission

Before you hit that “Submit” button, there are a few things you need to do to ensure your product is ready for the marketplace. Here’s a step-by-step guide:

1. Check the eligibility requirements

WooCommerce has a set of guidelines to ensure all products on the marketplace meet their standards. Some key requirements include:

  • Your product must be compatible with the latest two versions of WordPress and WooCommerce.
  • It should not violate the GPL license or include any spammy or malicious code.
  • Your product must provide real value to WooCommerce users.

Checkout the Pre-submission checklist for more details on what to keep an eye on when building a product for the marketplace.

2. Follow development best practices

Quality matters. Here are some tips to ensure your product is up to par:

3. Create thorough documentation

Merchants and developers love clear and detailed documentation. Be prepared to include:

  • Setup and configuration instructions
  • Use cases, comparisons, and video tutorials
  • Developer documentation for seamless integrations

Find more information in this guide about how to write clear and useful information for your product.

4. Test your product

WooCommerce provides a powerful tool called the Quality Insights Toolkit(QIT) to help you test your extension. (We’ll dive deeper into QIT in Part 2 of this series!) Use it to catch any issues before submitting your product.

The submission process

Once your product is ready, it’s time to submit it! Here’s how the process works:

  1. Create a WooCommerce.com Account: If you don’t already have one, sign up for a WooCommerce.com account.
  2. Submit your product: Navigate to Submissions > Submit Product. Fill out the submission form, providing details about your product, its features, and any supporting documentation.
  3. Wait for review: The WooCommerce team will review your product to ensure it meets their standards. This process typically takes up to 30 days.
  4. Address feedback: If the review team finds any issues, they’ll provide feedback. Make the necessary changes for the submission team to review.
  5. Get approved: Once your product is approved, it will be listed on the Woo Marketplace!

Tips for success

What’s next?

Stay tuned for part 2 of this series, where we’ll explore the tools and criteria used to evaluate your product, including the Quality Insights Toolkit (QIT). You’ll learn more about QIT to catch issues early and ensure your product meets WooCommerce’s high standards. Have questions about the submission process? Drop them in the comments below, or join the Woo Community Slack and head over to the #marketplace channel.


7 responses to “Getting to know the Woo Marketplace: A developer’s look”

  1. John Doe Avatar

    Very inflexible, just a tool for you guys to make money!

    1. Hi John Doe, we want our marketplace to be a space of shared opportunity for both Woo and the valued vendors who contribute to the ecosystem. We are working toward improving the marketplace experience for both our vendors and our consumers, and we appreciate any specific feedback you may have.

  2. The Pre-submission checklist makes mention “Compatibility with the top Woo extensions”.

    As all six of the top extensions listed are paid add-ons, is there a way for developers to test against these without having to purchase them?

    1. Hi David,

      Great question! Our team is currently working on a solution to make testing against these paid Woo extensions more broadly available to developers.

      In the meantime, when you’re ready to submit your extension, please mention which specific plugins you need to test compatibility with. We’ll do our best to assist you with the testing process.

      Thanks for bringing this up!

    2. Hi David!

      Just a quick follow up to what Adrian mentioned above, we also include these extensions as one of the tests we run in QIT, mentioned above in the post.

      This test specifically will install the extensions included in the compatibility extension set in the test environment, along with your extension: https://qit.woo.com/docs/managed-tests/extension-sets#available-extension-sets

      The test will report back any PHP errors or warnings and will also include any screenshots of failed steps that could indicate a compatibility issue.

      Let me know if you have any other questions, happy to dive into more details!

      1. Thanks Adrian & Greg!

        Just as a quick follow up — what is the stance on including custom blocks with themes sold on the marketplace?

        1. Adrian L. Avatar
          Adrian L.

          Including custom blocks within the theme is generally discouraged due to portability concerns. If users switch themes, any custom blocks bundled exclusively with your theme would become unavailable, causing loss of functionality or requiring extensive content migration.

          There may be rare exceptions, such as when a custom block is deeply integrated with your theme’s unique styling or layout, and it’s unlikely to be reused elsewhere. However, even in these scenarios, we would strongly recommend providing these blocks via a companion plugin to maintain flexibility for users.

          If you plan to submit such a product, make sure to include a few details about what you have in mind as part of the submission and we’ll do our best to guide you in the right direction as part of the review.

Leave a Reply

Your email address will not be published. Required fields are marked *