Dokan plugin review and common issues

Vendor order visibility requires correct vendor assignment. Check: (1) the products in those orders are assigned to the vendor — go to the product edit page and verify the “Vendor” is set to the correct vendor account; (2) in Dokan → Settings → Selling, verify vendors have the correct capabilities to view their orders; (3) orders placed before the vendor was set as the product owner may not be associated with that vendor — only orders placed after proper vendor assignment are visible; (4) the vendor must be logged in with their registered vendor account, not an admin or customer account.

Withdrawal processing depends on the payment method configured. For PayPal withdrawals: (1) the vendor’s PayPal email must be correctly entered in their vendor profile; (2) admin must process withdrawal requests manually in Dokan → Withdraw → Pending; (3) PayPal Adaptive Payments (older Dokan versions) is deprecated — if using Adaptive Payments, migrate to Stripe Connect. For Stripe Connect: (1) the marketplace owner must configure a Stripe Connect account in Dokan → Settings → Payment; (2) vendors must connect their individual Stripe accounts; (3) payouts use Stripe’s payout schedule to vendor bank accounts.

Vendor storefront URLs follow the pattern /store/vendor-name/. 404 errors occur when: (1) the Dokan store base URL conflicts with an existing WordPress page or post slug — check if a page with the slug “store” exists; (2) permalink rules need flushing — go to Settings → Permalinks → Save Changes; (3) in Dokan → Settings → Appearance, verify the Store URL base is configured; (4) if the vendor name contains special characters or spaces, the URL generation may create an invalid slug — check the vendor’s store URL field and correct it to a URL-safe slug.

Dokan Pro supports commission rate overrides at the category level. Go to WooCommerce → Product Categories → [category] → Edit and look for the Dokan commission settings in the category editor. Set a category-specific commission rate and type (percentage or fixed). Dokan applies commission rates in priority order: product-specific → vendor-specific → category-specific → global default. For a marketplace where jewelry earns 15% commission and electronics earn 8%, category-based commission rates avoid setting rates on every individual product.

In Dokan → Settings → Payment → Stripe, enable Stripe Connect and enter your Stripe platform account credentials. Vendors connect their individual Stripe accounts via the vendor dashboard → Withdraw → Connect Stripe. Once connected, Dokan can process payouts automatically according to the configured payout schedule (immediate, weekly, monthly). Each vendor receives money directly in their Stripe account, with the marketplace owner collecting the commission portion. Stripe handles the split payment and currency conversion for international vendors.

Dokan is the better choice for most marketplace projects due to its larger community, better documentation, and more polished vendor dashboard. WCFM provides similar functionality with a more generous free tier — many features that require Dokan Pro are available in WCFM’s free plugin, making WCFM the better value choice for budget-conscious marketplace builders. Dokan’s advantages are developer ecosystem quality, better support infrastructure, and the peace of mind of a well-funded company (weDevs) maintaining the platform.

Yes — Dokan supports WooCommerce downloadable products, which digital product vendors use to sell files. Each vendor can create downloadable products with file attachments managed through WooCommerce’s standard download management system. For software licenses, Dokan integrates with Easy Digital Downloads-style workflows when appropriate add-ons are used. For a marketplace specifically focused on digital products (like CodeCanyon), Dokan’s downloadable product support provides the necessary vendor-side file management.

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.