Pluggable is a WordPress plugin marketplace that makes it easy for users to discover, purchase, and manage high-quality plugins from independent developers. Here’s a quick look at how it works:

1. Discover Plugins

Browse a wide range of WordPress plugins across various categories like eCommerce, SEO, Membership, LMS, Page Builder, and more. Access all the plugins from the Home or dedicated Plugins page. You can:

  • Filter plugins by category or type (Free or Pro)
  • View plugin details, screenshots, and reviews
  • Compare pricing and feature highlights at a glance

2. View Plugin Details

Click any plugin to visit its dedicated product page, where you’ll find:

  • Description, installation guide, reviews, and changelog
  • Product features and screenshots
  • What’s included (updates, support, money-back guarantee)
  • Pricing variations and Live Demo (optional)

You’ll also see options such as ‘Free Download’ or ‘Buy Now’ to proceed to checkout.

3. Purchase & Download

The next step is to complete the checkout process. When ready:

  • Review your carted products.
  • Optionally priority support option.
  • Coupon code button (If any)
  • Enter personal information like email and name.
  • Enter credit card information.

Agree to the refund policy and complete payment via Visa, MasterCard, Stripe, and more. You’ll receive a confirmation email regarding purchase completion.

4. Manage Licenses & Downloads

Once purchased, get the file from Customer Dashboard (my.pluggable.io/customer). Manage the product licensing part from the same page.

 

All technical issues or bugs within a plugin are the responsibility of the plugin developer to resolve. However, if the developer becomes unreachable or fails to respond within a reasonable time, feel free to contact us. We’ll do our best to help you get in touch with the developer.

Pluggable offers a 30-day money-back guarantee if there’s an unresolved issue that prevents you from using the plugin as advertised. Refunds are considered only when:

  • You’ve contacted the developer but received no solution
  • The issue significantly affects plugin functionality
  • The problem persists despite reasonable efforts to resolve it