woo-marketplace-submission

Generate WooCommerce.com Marketplace submission content and packaging guidance for plugin vendors.

Updated Sep 22, 2024
One-click install
npx skills add https://github.com/WordPressBugBounty/plugins-woocommerce-for-japan --skill woo-marketplace-submission
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: woo-marketplace-submission
Source: https://github.com/WordPressBugBounty/plugins-woocommerce-for-japan/tree/main/woocommerce-for-japan/.claude/skills/woo-marketplace-submission
Command: npx skills add https://github.com/WordPressBugBounty/plugins-woocommerce-for-japan --skill woo-marketplace-submission

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you avoid costly submission mistakes by guiding you through the full WooCommerce.com Marketplace process: writing review-ready English for every Vendor Dashboard Submit Product field, packaging and versioning correctly for ZIP upload, passing the staged Business/Code/UX reviews, and staying compliant after launch with update and documentation obligations.

Core Features & Use Cases

  • Write compliant WooCommerce.com submission form English: Produce natural, review-friendly text for fields like Name, Short description, Best features, Benefits, Rationale, Competitive comparison, Testing instructions, and reviewer notes.
  • Prepare submission packaging and changelog: Ensure ZIP naming/folder structure correctness and enforce strict version consistency across the plugin header, changelog.txt, and upload version entry.
  • Navigate review stages effectively: Use targeted guidance for automated tests (Activation/Security/Malware), Business review expectations (70/30 revenue share, pricing alignment, trademark constraints, uniqueness, prohibited practices), Code review standards (originality/security/WordPress-Woo compatibility, sanitization, HPOS readiness), and UX review requirements.
  • Design business model and freemium correctly: Apply rules for annual vs monthly (SaaS Billing API requirement), revenue split, and two-track freemium submissions (WordPress.org free + WooCommerce.com paid).
  • Run post-release operations: Meet update cadence (at least every 6 months, quarterly major releases recommended), handle version upload workflow, and maintain buyer support and documentation.

Quick Start

Use the woo-marketplace-submission skill to generate the complete set of WooCommerce.com Vendor Dashboard Submit Product form text in English and a correctly formatted changelog/ZIP submission plan for your plugin’s current version.

Frequently Asked Questions about woo-marketplace-submission

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit a plugin to the WooCommerce.com marketplace?

To submit a plugin to the WooCommerce.com marketplace, you must complete the Vendor Dashboard Submit Product form, package your ZIP file correctly, and pass staged Business, Code, and UX reviews. Ensure version consistency across your plugin header and changelog.

What are the WooCommerce.com marketplace review stages?

The WooCommerce.com marketplace review stages include automated tests for activation, security, and malware, followed by manual Business, Code, and UX reviews. These stages check pricing alignment, code originality, WordPress-Woo compatibility, sanitization, and HPOS readiness.

How does the WooCommerce.com revenue split work for plugin submissions?

The WooCommerce.com revenue split operates on a 70/30 revenue share model. During the Business review stage, your submission must align with pricing rules, trademark constraints, and marketplace uniqueness requirements to remain compliant.

Can I submit a freemium plugin to WooCommerce.com?

You can submit a freemium plugin to WooCommerce.com using a two-track approach: hosting the free version on WordPress.org and the paid version on WooCommerce.com. Monthly billing requires SaaS Billing API integration, while annual pricing follows standard rules.

What are the post-release update obligations for WooCommerce.com plugins?

Post-release update obligations for WooCommerce.com plugins require maintaining an update cadence of at least every 6 months, with quarterly major releases recommended. Vendors must handle version upload workflows, buyer support, and documentation maintenance.

Why does my WooCommerce.com submission fail version consistency checks?

WooCommerce.com submissions fail version consistency checks when the version number in the plugin header does not match the changelog.txt and the upload version entry. Strict version alignment across these files is required for ZIP packaging approval.