# How to Sell WordPress Plugins and Themes: The Complete 2026 Guide > Learn how to sell WordPress plugins and themes online with the right licensing, pricing, delivery, and payment setup - without marketplace commissions. - **Author**: Ayush Agarwal - **Published**: 2026-04-06 - **Category**: Digital Products, WordPress, How-To - **URL**: https://dodopayments.com/blogs/sell-wordpress-plugins-themes --- WordPress powers over 40% of the web. That audience represents millions of site owners actively looking for plugins and themes to solve real problems. If you have built something useful for that ecosystem, you are sitting on a genuine revenue opportunity. But selling WordPress plugins and themes is not as simple as uploading a zip file and waiting for orders. You need to think through licensing, pricing structures, update delivery, support tiers, and payment processing before you launch. Get these wrong and you either leave money on the table or create a customer support nightmare that burns out your team. This guide covers everything you need to know to sell WordPress plugins and themes successfully in 2026, from choosing where to sell to setting up a payment system that handles global taxes automatically. ## Where to Sell WordPress Plugins and Themes The first decision you will make is where to list your product. There are two main paths: marketplaces and direct selling. Each has real trade-offs. ### WordPress.org Plugin and Theme Directory The WordPress.org directory is free to list on, and it comes with built-in discovery from users searching inside the WordPress admin dashboard. But there is a significant limitation: you cannot charge for plugins or themes on WordPress.org. The directory only accepts free (or freemium) products. If you list on WordPress.org, your monetization strategy has to live outside the directory. The common approach is to offer a free "lite" version on WordPress.org and sell a premium version from your own site. This freemium funnel works well because it gives users a low-friction way to try your product before committing to a paid plan. ### CodeCanyon and ThemeForest (Envato Market) Envato's CodeCanyon (for plugins) and ThemeForest (for themes) are the largest marketplaces for premium WordPress products. The exposure can be significant, particularly if your product ranks well in their search results. The downsides are meaningful. Envato takes a commission that starts at 37.5% for exclusive authors and goes up to 55% for non-exclusive authors on items priced above a certain threshold. You also do not own the customer relationship - Envato does. When a customer buys through CodeCanyon, you get a payment but you do not automatically get their email address or a direct channel to communicate. Additionally, Envato handles licensing through their own system, which means you are dependent on their infrastructure for validating licenses and delivering updates. ### Selling Directly Selling directly from your own website gives you the highest margin, full control over the customer relationship, and the flexibility to set your own pricing, terms, and support structure. You keep the customer email, you define the licensing rules, and you are not subject to a marketplace's changing policies. The challenge is that you need to handle payment processing, license key generation, update delivery, and tax compliance yourself, or at least through tools you choose and control. This is where most plugin and theme developers land once they have some traction. The marketplace provides initial discovery; the direct channel is where you build a real business. For a broader look at this decision, the guide on [how to sell software online](https://dodopayments.com/blogs/how-to-sell-software-online) covers the full landscape of options for digital product developers. ## Understanding GPL Licensing for WordPress Products Before you set up any pricing or licensing system, you need to understand how the GPL applies to WordPress products. This is not optional - it affects what you can legally do with licensing. WordPress itself is released under the GNU General Public License (GPL) v2 or later. Because WordPress is GPL-licensed, any code that runs as part of WordPress, including plugins and themes, must also be GPL-compatible. This is the "viral" nature of the GPL. **What this means in practice:** - Your PHP code (the plugin or theme logic) must be GPL-licensed - Users who receive your plugin have the legal right to redistribute it, modify it, and run it for any purpose - You cannot legally restrict redistribution of the PHP portions of your plugin or theme **What the GPL does not require:** - Your JavaScript, CSS, and images can be under a different license (this is called a "split license") - Your support services, update access, and cloud-connected features are not covered by the GPL - Your trademarks and branding are separate from the GPL requirements The practical implication for your business model is that you cannot sell a license to use the plugin code itself in the way traditional software licenses work. Instead, you are selling access to updates, official support, cloud-connected services, and the convenience of receiving future versions directly from you. This is exactly why the annual license model has become the industry standard for premium WordPress products. Customers pay annually for access to updates and support, not for the code itself. The code is GPL-licensed; the services around it are what you can restrict and charge for. ## Pricing Models for WordPress Plugins and Themes There are three main pricing models in the WordPress ecosystem. Your choice depends on your product type, update frequency, and support requirements. ### One-Time Purchase The simplest option. A customer pays once and receives the current version of the plugin or theme. No recurring billing, no renewal reminders. This model works reasonably well for products that are highly stable, rarely need updates, and require minimal support. A one-time price also lowers the psychological barrier to purchase. The problem is that it creates a revenue cliff. You are constantly dependent on new customer acquisition because you have no recurring revenue from your existing base. If your product requires compatibility updates with new WordPress or PHP versions (which most do), you are providing ongoing value that you cannot monetize. For a detailed comparison of how one-time versus recurring revenue models affect your business over time, the guide on [one-time vs subscription pricing](https://dodopayments.com/blogs/one-time-vs-subscription-saas-pricing) is worth reading before you decide. ### Annual License This is the dominant model in the premium WordPress plugin and theme market. A customer pays an annual fee and receives updates and support for 12 months. After the first year, they can renew to maintain access to new versions and support. Annual licenses create predictable recurring revenue while fitting the mental model of "paying for support and updates" rather than "renting the software." This works within the GPL framework because you are selling services, not access to code. Most developers offer multiple tiers within the annual license model: - Single site license (one domain) - 3 or 5 site license - Unlimited or developer license Tiered site limits are a clean way to capture more value from agencies and developers who deploy across many client sites. For a deeper look at subscription-based pricing structures, the guide on [subscription pricing models](https://dodopayments.com/blogs/subscription-pricing-models) covers the mechanics of designing tiers that convert well. ### Lifetime License A lifetime license is a one-time payment that grants permanent access to updates. Many plugin developers offer these as a premium tier, often at 3 to 5 times the annual price. Lifetime licenses appeal to customers who hate recurring costs. They can help you raise cash quickly, especially at launch. The downside is that you take on an unbounded support obligation. A customer who paid once five years ago expects their plugin to keep working, which means you are supporting them indefinitely without further revenue. Experienced plugin developers tend to cap lifetime license sales or phase them out once they have a stable annual license base. If you offer lifetime licenses, price them high enough that you can sustainably support those customers long-term. ## Setting Up License Key Management License keys are how you control access to premium features, validate active subscriptions, and gate update delivery. Even though the GPL prevents you from using licenses to restrict the plugin code itself, you can use license keys to control access to your update server. A license key system typically works like this: 1. Customer completes a purchase and receives a unique license key 2. The plugin checks in with your server when activated, validating the key against the purchase record 3. Your server returns an authorized status (and can include site URL binding to limit where the key works) 4. Updates are delivered through the WordPress update mechanism only to validated, active licenses > License key infrastructure is one of those things that looks simple until you actually build it. You need generation, validation, domain binding, expiration handling, and revocation on refund - all of which need to stay in sync with your payment events in real time. Most plugin developers underestimate this by an order of magnitude. > > - Ayush Agarwal, Co-founder & CPTO at Dodo Payments Building this from scratch is possible but time-consuming. The core components you need are: - A key generation system that produces unique, non-guessable keys - A validation API endpoint that the plugin can call - A database that maps keys to purchases, expiration dates, and allowed domains - A system to revoke keys when licenses expire or refunds occur For a practical walkthrough of implementing this infrastructure, the guide on [how to set up a license key system](https://dodopayments.com/blogs/set-up-license-key-system) covers the technical and operational details. The [license keys documentation](https://docs.dodopayments.com/features/license-keys) from Dodo Payments also explains how payment-linked license generation works when you sell through a modern platform. For a broader view of how license management fits into a software business, [software license management](https://dodopayments.com/blogs/software-license-management) is a useful reference. ## Delivering Updates Update delivery is where many plugin developers underestimate the complexity. WordPress has a built-in update mechanism that checks a central server (wordpress.org) for available updates. For premium plugins not hosted on wordpress.org, you need to replicate that mechanism using your own update server. The standard approach uses a combination of two WordPress filters: - `plugins_api` - handles requests to check if a new version is available - `pre_set_site_transient_update_plugins` - intercepts the update check and injects your plugin's version data When WordPress runs its standard update check, your plugin can intercept that process and query your own server for the latest version info. If the customer has a valid, active license, your server returns the new version details. WordPress then offers the update through the standard "Updates" screen in the admin. For themes, the mechanism is similar but uses `pre_set_site_transient_update_themes`. **What your update server needs to handle:** - Version metadata in the format WordPress expects (package URL, version number, changelog) - License validation before serving the download URL - Rate limiting to prevent abuse - A CDN or reliable file hosting for the plugin zip files themselves If you are selling through [Dodo Payments](https://dodopayments.com), you can use [webhooks](https://docs.dodopayments.com/developer-resources/webhooks) to keep your license database synchronized with payment events. When a subscription renews or expires, a webhook fires and your system updates the license status accordingly, automatically gating or restoring update access. ## Support Tier Setup Support is often what customers are really paying for with an annual license. How you structure your support tiers directly affects your margins and your team's workload. **Common support structures:** - **Free users (WordPress.org version):** Community support only, via the WordPress.org forums. You or a team member monitors and responds selectively. Response time expectations are low (days to a week is acceptable). - **Standard (single or multi-site license):** Email or help desk support with a defined response time, typically 1 to 3 business days. Access to knowledge base documentation and video tutorials. Does not include configuration help or custom development. - **Agency or Developer (unlimited sites):** Priority support with faster response times (often same-day or next business day). Access to Slack or Discord channel for direct communication. May include a limited number of onboarding calls per year. - **Priority Add-on:** Some developers offer priority support as a paid upgrade to any license tier, giving customers who need faster responses the option to pay for it without forcing everyone into a more expensive tier. **What to document before you launch:** - Scope of support (bug reports, installation help, configuration guidance) - What is out of scope (custom development, third-party plugin conflicts, hosting issues) - Response time commitments by tier - Support channels (help desk ticket system, dedicated Slack, email) - Escalation process for critical bugs Documenting scope aggressively protects you. Support is where small plugin businesses lose the most time, and without clear boundaries, customers will ask for custom feature development and call it "support." ## Payment Processing for WordPress Plugins and Themes Accepting payments is where you need to think carefully about two things: the mechanics of checkout and the compliance requirements of selling globally. ### What to Look for in a Payment Processor WordPress plugin and theme customers are distributed worldwide. Your payment setup needs to handle: - Multiple currencies with localized pricing - International payment methods (not just credit cards) - Automatic VAT and GST calculation and remittance for digital goods - Annual and lifetime (one-time) billing in the same system - License key delivery triggered by successful payment Tax compliance for digital products sold internationally is the piece that surprises most developers. The EU requires VAT collection on digital goods sold to EU consumers, regardless of where your business is incorporated. Similar rules apply in the UK, Australia, Canada, and a growing list of other jurisdictions. > WordPress plugin developers have a global customer base by default - the platform is used in every country. That means your tax obligations span dozens of jurisdictions from day one, even if you are a solo developer working from your apartment. A Merchant of Record is not a nice-to-have for plugin sellers; it is the only practical way to stay compliant without hiring a tax team. > > - Rishabh Goel, Co-founder & CEO at Dodo Payments This is where using a [Merchant of Record](https://dodopayments.com/blogs/what-is-a-merchant-of-record) becomes valuable. When you sell through an MoR, they become the legal seller of record for tax purposes. They calculate, collect, and remit VAT and GST on your behalf, in every jurisdiction where your customers are located. You receive your net revenue without touching a single tax return. ### Setting Up Checkout For direct selling, your checkout flow should feel native to the rest of your marketing site. Embedding the checkout inline or as an overlay performs better than redirecting customers to an off-site payment page. Dodo Payments offers an [overlay checkout](https://docs.dodopayments.com/developer-resources/overlay-checkout) that can be embedded directly into your plugin sales page. Customers complete the purchase without leaving your site, which reduces abandonment. After a successful payment, a webhook fires and your system generates and delivers the license key automatically. This end-to-end flow, from checkout to license delivery, should be fully automated. A customer who buys at 2am should receive their license key within seconds, not when someone checks their inbox the next morning. For a full walkthrough of the digital product selling setup, [how to sell digital products](https://dodopayments.com/blogs/how-to-sell-digital-products-online) covers the checkout and delivery mechanics in detail. ### Dodo Payments for WordPress Plugin Sellers [Dodo Payments](https://dodopayments.com) is built specifically for digital product sellers who need a full Merchant of Record with transparent pricing. At 4% + 40c per transaction with no monthly fees, it is significantly cheaper than alternatives like Paddle or Lemon Squeezy for most volume levels. The platform handles: - Global tax compliance (VAT, GST, sales tax) across 180+ countries - Payment methods including cards, PayPal, UPI, Pix, and local wallets - One-time and annual subscription billing in the same account - Webhook delivery for post-purchase automation (license key generation, email delivery) - Native license key management For plugin developers selling across multiple tiers (single site, multi-site, agency), you can create separate product listings with different pricing and attach license key generation to each. [Dodo Payments pricing](https://dodopayments.com/pricing) is published and straightforward, with no custom quotes required to get started. ## Launch Checklist Before you publish your plugin or theme for sale, verify that you have covered these items: - GPL licensing applied to your PHP code, with a split license for non-PHP assets if applicable - A defined pricing structure (annual vs lifetime vs one-time) with clear site tier limits - A license key system set up and tested, including expiration and renewal handling - An update server configured and responding to the WordPress update mechanism - Support documentation covering scope, channels, and response time commitments - Payment checkout live and tested with a real transaction - Tax compliance handled (via MoR or manual registration, depending on your revenue levels) - A post-purchase email sequence delivering the license key and getting started instructions - A refund policy published clearly on your sales page ## FAQ ### Can I charge for a WordPress plugin if it is GPL-licensed? Yes. The GPL allows you to charge for the software itself and to charge for services around it. Most premium plugin developers charge for access to official updates, priority support, and cloud-connected features rather than for the code itself. Because the PHP code must be GPL, customers technically have the right to redistribute it, but they cannot redistribute your update server access or your support services. The annual license model works precisely because it monetizes those services rather than the code. ### What is the best wordpress plugin marketplace to sell on? CodeCanyon is the largest dedicated WordPress plugin marketplace by volume. However, the commission structure (up to 55% for non-exclusive authors) means you keep less than half of each sale. WordPress.org is free but does not support paid products. Most developers who want to maximize revenue eventually move to direct selling or use a marketplace for initial discovery while building a direct sales channel alongside it. ### How do I handle taxes when selling WordPress plugins internationally? If you sell to customers in the EU, UK, Australia, or many other countries, you are required to collect and remit VAT or GST on digital products, regardless of where your business is located. The practical way to handle this is to sell through a Merchant of Record like Dodo Payments. The MoR becomes the legal seller for tax purposes and manages all collection and remittance automatically. This means you never have to register for VAT in individual countries or file foreign tax returns. ### Should I offer a lifetime license for my plugin? Lifetime licenses can be a useful tool at launch to generate upfront cash, but they carry long-term risks. You are committing to support a customer indefinitely on a single payment. If your plugin requires ongoing maintenance (WordPress compatibility updates, security patches, new features), a lifetime license customer is receiving ongoing value that costs you time and money. If you offer lifetime licenses, price them at least 3 to 4 times the annual price, and consider capping the number you sell or phasing them out once you have sufficient recurring revenue. ### How do I deliver updates to customers who bought directly from my site? You need a custom update server that integrates with WordPress's built-in update mechanism. Your plugin hooks into the `plugins_api` and `pre_set_site_transient_update_plugins` filters to intercept WordPress's standard update checks and query your own server instead. If the customer has a valid, active license, your server returns the download URL for the latest version. WordPress then handles the actual update installation. This setup requires a reliable hosting environment for your update files and a license validation API that the plugin can call at update check time. --- Selling WordPress plugins and themes direct is one of the highest-margin paths in the digital products space once you have the infrastructure in place. The key is to solve licensing, update delivery, and tax compliance early so that the operational overhead stays low as revenue scales. Start with a simple annual license structure, automate delivery through webhooks, and use a Merchant of Record to remove the tax burden entirely. --- - [More Digital Products articles](https://dodopayments.com/blogs/category/digital-products) - [All articles](https://dodopayments.com/blogs)