Platforms Marketplaces
Product marketplaces on Dokan, WCFM and WC Vendors. Service marketplaces, paid directories, and marketplaces that live inside a community. Each one makes money differently, which is why each one is a different build.
No integration required Export what is owed, pay it however you already pay people, mark it paid.
Why this matters
Someone says marketplace, an agency hears Dokan, and a product marketplace gets quoted to a business that was actually describing a service marketplace or a paid directory. The engine is chosen before anyone establishes how the thing makes money, and since the revenue model is what decides the build, the scope is wrong before a line is written. Settling that first is the cheapest hour of the project.
Four shapes
Not with the plugin. The revenue model decides the engine, the data model and most of the cost, so it is the question worth answering before any of the others.
Commission per sale
Many sellers listing goods, one cart, one checkout, commission split at the point of sale. This is what most people mean by marketplace and what most agencies quote for. Dokan, WCFM and WC Vendors are the three engines worth considering, and we ship a Reign integration for each.
Reign Dokan AddonReign WCFM AddonReign WC Vendors Addon
Multi-vendor development in depthCommission per order
Buyers book work rather than a product with a SKU. That means briefs, requirements, revisions, delivery and messaging between the two sides, none of which a product cart has. We build these on our own plugins, so the seam between listing and delivery is ours to fix.
Paid placement, not transactions
Vendors pay to be listed and to be seen, and the transaction usually happens off the site entirely. The build is search, claims and verification rather than checkout. Listora is ours, and Listora Pro is the part that makes it a business: credit-based plans, paid featured listings and verification badges.
Commission, discovery through the feed
Selling inside a social network, where people find listings through profiles and activity rather than a catalogue. The commerce is conventional; the discovery surface is not, and that is what a standard marketplace build gets wrong here.
Community platform developmentThe hard part
Every marketplace looks like a catalogue and behaves like a payments system. These are the parts that decide whether it still reconciles in year two.
Rules
A flat percentage is easy. Per-vendor rates, per-category rates, tiered rates and a minimum fee are where the arithmetic starts disagreeing with the payout report. The rules have to be one implementation, not one per screen.
Set the rules once, read them everywhere.
Payouts
Automated rails are worth having, but the day-one requirement is that you can pay every vendor without any integration at all: export what is owed, pay it, mark it paid. Automation is an upgrade on top of that, never the only path.
No integration should be able to block a payout.
Reversal
A refund after a payout means the vendor has been paid for a sale that no longer exists. Either the platform absorbs it or it nets against the next payout, and that has to be decided in the build rather than discovered in month four.
Decide it before the first refund, not after.
Vendors
Registration, verification, payment details, tax information and a dashboard they can work in without being trained. Vendor drop-off during onboarding is the quietest way for a marketplace to fail, because nobody files a bug for it.
Measure how many finish, not how many start.
Discovery
Filters and facets that stay fast at fifty thousand listings, not five hundred. This is a database and indexing problem, and retrofitting it after launch usually costs more than building it correctly at the start.
Design for the catalogue you want, not the one you have.
Trust
Two-sided businesses generate arguments the platform has to arbitrate. Order states, evidence, a hold on the money and a decision trail. Without it, the owner arbitrates by hand in an inbox and it does not scale past the first month.
A queue and a paper trail, not an inbox.
3 of 3
major WordPress multi-vendor engines we ship products for
Dokan, WCFM and WC Vendors, alongside our own service marketplace and directory platforms. Which engine we recommend is not decided before you call.
What it costs
A single-category marketplace on a standard engine and a multi-currency platform with custom commission rules are the same sentence and very different projects. Here is what moves the number.
What moves the number
Small, well-defined work is usually better handled as an hourly block than scoped as a project, and we will say so rather than inflate it into one.
Rough idea to delivery
Quick enquiry
Tell us roughly what you have in mind, including how you expect it to make money. That one line changes most of the answer.
Prefer the full form? Start a project
Common questions
Dokan, WCFM and WC Vendors are the three worth considering, and the honest answer depends on your commission model, how much the vendor dashboard matters and what your payout rails need to be. We ship a Reign integration for all three, so our recommendation is not decided before the call. The multi-vendor page goes into the comparison properly.
No, and this is the most common mis-scope in this category. A product marketplace assumes a SKU, a cart and a fixed deliverable. Selling services adds briefs, requirements, revisions, delivery and buyer-seller messaging, which a product cart has none of. We build these on our own service-selling plugins for exactly that reason.
Both are legitimate businesses and they are different builds. Commission per sale needs the whole money layer: splits, payouts, refund reversal. Paid placement needs plans, credits, featured slots and renewals, and often no checkout for the transaction at all because that happens off the site. Choosing between them is the first thing worth settling.
The rule we hold to is that an owner must be able to pay every vendor with zero integrations: export what is owed, pay it however you already pay people, mark it paid. Automated rails such as Stripe Connect sit on top of that as an option. Building it the other way round means an integration outage becomes a payout outage.
Yes, and the listings are the straightforward half. Carrying vendors, their order history, outstanding balances and payout records across is the part that decides whether vendors stay, and it is where these migrations usually go wrong.
Marketplace builds are estimated against scope rather than sold at a list price. A single-category marketplace on a standard engine and a multi-currency platform with custom commission rules and automated payouts are very different projects. The section above sets out what moves the number.
Where to go next
Next step
A discovery call is free and usually settles which of the four shapes you are actually building. The written proposal follows within a week.
WBComDesigns is amazing. The WP plugins and themes are of top notch quality with lots of features and updated very frequently. Supports are very responsive and helpful. I use Reign with TutorLMS, and the experience is surprisingly smooth.…