WC Vendors plugin review and common issues

WC Vendors Stripe Connect requires: (1) configure Stripe platform account credentials in WC Vendors → Settings → Payment → Stripe Connect; (2) vendors connect their individual Stripe accounts from their vendor dashboard → Payments → Connect Stripe Account; (3) the marketplace admin processes withdrawal requests in WC Vendors → Vendors → Withdrawals, or configure automatic payouts in Stripe platform settings; (4) verify the Stripe account supports Connect payouts for your country — Stripe Connect availability varies by country for the payout destination. Check Stripe documentation for supported countries.

WC Vendors adds vendor information to product pages via hooks. If the wrong information appears: (1) verify the product is correctly assigned to a vendor — in the product edit page, the “Vendor” field should show the selling vendor’s name; (2) check if the theme overrides the product page in a way that bypasses WC Vendors’ vendor information hooks; (3) in WC Vendors → Settings → Display, verify vendor information display is enabled on product pages; (4) theme caching may serve pages with incorrect vendor data — clear all caches.

Check: (1) the user is registered as a vendor (WC Vendors role) — go to WordPress → Users → [user] and verify they have the Pending Vendor or Vendor role; (2) admin must approve pending vendor applications in WC Vendors → Vendors → Pending; (3) the vendor dashboard page is correctly configured in WC Vendors → Settings → Pages with the [wcv_dashboard] shortcode; (4) the vendor dashboard page is published and accessible; (5) a permalink flush may be needed — go to Settings → Permalinks → Save Changes.

Go to WC Vendors Pro → Settings → Commission → Category Commissions. Add commission overrides by WooCommerce product category: select “Electronics” → set 8% commission; select “Clothing” → set 15% commission. These category-specific rates override the global commission for products in those categories. The commission rate priority in WC Vendors Pro is: product-specific → vendor-specific → category-specific → global default. Test with a product in each category to verify commission calculation is correct on a test order.

Vendor coupons require WC Vendors Pro. In Pro settings, enable vendor coupon creation. Vendors access the Coupon section in their dashboard to create discount coupons for their specific products. When creating a coupon, vendors select which of their products the coupon applies to — coupons automatically scope to only that vendor’s products (not the entire marketplace). Commission calculation adjusts to apply the commission to the discounted price rather than the full price. Configure whether vendor coupons affect vendor earnings or marketplace commission in the commission settings.

WC Vendors Pro at $99.50/year provides a feature set comparable to Dokan Starter ($149/year) with better commission flexibility and a cleaner codebase. For small marketplaces where budget is a consideration, WC Vendors Pro delivers a production-capable marketplace at a meaningful cost saving. Dokan’s advantage is its larger ecosystem, more tutorials, and broader Pro module library for advanced use cases. For a straightforward product marketplace without exotic requirements, WC Vendors Pro at $99.50/year is the strongest value proposition in the category.

Yes — WC Vendors Pro supports WooCommerce downloadable products, which vendors use to sell digital files (ebooks, software, music, fonts, templates). Each vendor manages their downloadable products from the vendor dashboard. The marketplace owner configures download settings (download limits, expiry) globally, while vendors set prices and upload files for their specific products. Digital product marketplaces work well on WC Vendors as there is no physical shipping complexity, making commission management and vendor payouts more straightforward.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.