Every existing way to run a service marketplace on WordPress made you pick a compromise.
You could stack WooCommerce with 4-5 marketplace plugins: Dokan or WCFM as the multi-vendor layer, a custom-fields plugin for the requirements form, a chat plugin for buyer-vendor messaging, a withdrawals plugin for payouts, a custom CSS pack to hide the parts of WooCommerce that don’t apply to services. It worked, sort of. Until any of those plugins updated and broke the chain.
You could rent a SaaS marketplace: Sharetribe, Arcadier, ListingHub. Pay $100-500 a month for the privilege of building your business on someone else’s roadmap. Branding limits, data lock-in, no control over the commission engine.
You could commission custom development: six months of agency time and twenty thousand dollars to build what already exists in fragments across other plugins.
Or you could wait for the right tool.
The gap in the WordPress ecosystem
Dokan, WCFM, and WC Vendors are excellent. For physical-product marketplaces. They were designed when “marketplace” meant Etsy clones and multi-vendor stores selling t-shirts. The data model is product, the order state machine ends at completed, and the workflows assume inventory + shipping.
Services don’t have inventory. Services have requirements that need to be collected before work starts. Services get delivered as files, not packages. Services often need revisions. Services sometimes fail and need a dispute system that knows what “fail” means in the context of a 2-week consulting engagement.
Retrofitting product plugins to fit services is the job that consumes thousands of hours across the WordPress community every year. Every freelance marketplace owner ends up reinventing the same patches.
What we decided to build
WP Sell Services was designed from day one for service workflows. The decisions that flow from that:
Requirements collection is a first-class part of the order. When a buyer purchases a service, the order doesn’t proceed until the buyer has filled the vendor’s intake form. That form is built into the service listing. Vendors define their questions once, every buyer answers before any work starts.
The order state machine matches reality. Orders go: payment received → requirements pending → in progress → delivered → revision requested → redelivered → completed. Each state has a different UI on the vendor and buyer dashboard, different notification emails, different available actions. This is how service work actually flows.
Delivery is its own event. Vendors upload deliverable files attached to the order. Each delivery has a timestamp, a file batch, and a note. Buyers see all deliveries in chronological order. The order doesn’t auto-complete on payment. It auto-completes after delivery + a configurable revision window expires without action.
Disputes resolve with full context. When something goes wrong, the dispute UI shows the requirements form, every message, every delivery, every revision request. Admin (you) has everything needed to resolve fairly. No guessing.
Two marketplace modes, both built in. Buyers can browse a catalog and buy a fixed-price package (Fiverr-style) OR post a brief and receive proposals (Upwork-style). Most marketplaces force you to pick one. We ship both because real demand has both shapes.
What we chose to leave for Pro
The free plugin is complete enough to run a production marketplace. We’ve been hard-headed about not crippling it with artificial limits.
The Pro modules solve problems that show up after the marketplace works:
- WooCommerce checkout integration. When you outgrow Stripe + PayPal and need regional gateways without polluting the catalog with physical products.
- Vendor analytics. When vendors start asking you for data you don’t have.
- Automated payouts. When manual withdrawal review is a part-time job.
- Cloud storage. When delivery files exceed your host’s disk limits.
- Recurring services. When retainer engagements need automated monthly billing.
- White-label. When you want your marketplace’s brand instead of ours.
We sell Pro as one-time license plus a year of updates. No SaaS. No per-vendor pricing. No commission on your transactions.
What we’re not
This isn’t a Fiverr competitor. We’re not building a hosted marketplace. We don’t see vendors. We don’t see orders. We don’t have access to your data. We’re a plugin. Installed on your server, owned by you.
We’re also not a marketplace toolkit for everything. If you’re selling physical products, WooCommerce + Dokan is still the right answer. If you’re running a multi-vendor digital products store, Easy Digital Downloads with the front-end submission addon fits better. WP Sell Services is the right tool when the product is a service.
What’s next
The roadmap is in the open at store.wbcomdesigns.com/wp-sell-services/docs/. Active priorities:
- More payment gateway integrations in Pro.
- AI-assisted service creation (auto-generate package copy from a vendor’s portfolio).
- A “vendor marketplace” mode where the platform itself becomes a marketplace of pre-vetted service providers.
If any of those would change your build decision, we want to hear it reach us via support.