WP Sell Services 1.3.0: Money That Adds Up, and a Marketplace That Sells on Day One

If you run a service marketplace on WP Sell Services, version 1.3.0 is not a feature showcase. It is the release where a lot of quiet, structural problems around money, first-run setup and dark-mode rendering got found and closed. That is a good thing to ship, and it is worth explaining plainly rather than dressing it up as something bigger than it is. This article walks through what you can actually do with the plugin pair after updating, organized by outcome rather than by changelog line.

What WP Sell Services actually is

WP Sell Services turns a WordPress install into a Fiverr-style service marketplace. Vendors list services with tiered packages, buyers purchase through a structured order workflow, and the whole thing runs on your own domain instead of a third-party gig platform’s terms. It suits freelance platforms, gig marketplaces, agency storefronts and any service directory where the value is in the ordering and delivery workflow, not just a product catalog.

The free plugin is the marketplace engine. It is not a stripped demo of a paid product; it is a complete, usable service marketplace on its own. Here is what ships in free, without needing Pro:

• A multi-step service creation wizard with live preview, so vendors see the listing take shape as they build it
• Three-tier pricing packages (Basic, Standard, Premium) with independent pricing and feature lists per tier
• Service add-ons and extras, an image gallery (up to four images on free), video embeds, per-service FAQ, and configurable service requirements to collect buyer information up front
• Category and tag organization for the service catalog
• A complete order lifecycle covering 11 distinct order statuses, from initial requirements collection through delivery, revision, approval and completion
• File delivery with buyer approval, built-in per-order messaging with attachments, revision requests, and deadline extension requests
• Vendor registration and approval workflow, plus seller level progression (New Seller, Rising Seller, Top Rated, Pro Seller)
• A standalone checkout supporting Stripe, PayPal and offline payment
• Dispute resolution, buyer reviews, and commission-based vendor earnings

Pro sits on top of that engine and requires the free plugin installed and active; it does not replace it. Pro’s job is to plug the marketplace into the e-commerce and payment infrastructure a growing business actually needs: platform adapters, more gateways, vendor payout rails, and higher operating limits. We will cover exactly where that line sits in the capability table further down.

What 1.3.0 actually delivered

Read the 1.3.0 free release notes and the Pro release notes together and a pattern falls out immediately: this is a correctness and stability release, not a feature drop. Three themes account for almost everything in it. Money now behaves the same way across every gateway and platform. A fresh install is sellable within minutes instead of requiring a gateway first. And the entire frontend, including Pro’s dashboard and analytics, respects dark mode the way your theme defines it, not the way the visitor’s operating system happens to be set.

None of that is glamorous marketing copy. It is the kind of release that matters most if you already have vendors and orders running through the plugin, because it changes what you can trust the numbers to say.

Theme 1: Money now adds up, everywhere

A marketplace plugin’s core promise is that when a buyer pays, the right amount lands with the right vendor, minus the right commission, and stays reconciled through refunds and renewals. Before 1.3.0, that promise had real gaps depending on which payment platform and gateway combination a site used. 1.3.0 closes them. We are not going to soften this: some of these were bugs that could cost a vendor money or pay them twice, and they are worth naming directly.

What was wrong	What it meant for you	Status
Commission splits did not always persist per order across WooCommerce, EDD, SureCart, FluentCart, Stripe Connect and subscription renewals; some orders saved a NULL split	You could not reliably tell what commission was actually taken on a given order, which breaks both vendor trust and your own accounting	Fixed in 1.3.0
PayPal payouts settled outside the wallet ledger	A vendor’s PayPal earnings could be paid out twice, since the payout and the ledger were not the same source of truth	Fixed in 1.3.0
Ledger reversal fired on every refund, regardless of whether the gateway actually reclaimed the money	A refund that failed at the gateway could still zero out a vendor’s ledger balance for money they never lost	Fixed in 1.3.0
Money precision was hardcoded to two decimal places everywhere: refunds, the earnings ledger CSV export, and payouts	0-decimal currencies (like JPY) and 3-decimal currencies (like KWD, BHD) rounded incorrectly, throwing off exported totals and payout amounts	Fixed: rounding now respects the currency’s real precision
Stripe Connect’s application fee and split were computed by divergent math in different code paths	Two orders that should have split the same way could compute slightly different platform fees depending on which path handled them	Fixed: both now run through one canonical commission service and currency converter
Vendor subscriptions could charge nothing on signup, and switching plans could double-bill	You could lose subscription revenue outright, or a vendor could be charged twice for a single plan change	Fixed: subscription billing now runs through hosted Stripe Checkout
A paid subscription plan without a Stripe Price ID attached still granted access	A misconfigured plan silently became a free plan, with no charge and no warning	Fixed: access now requires a valid Price ID
Payment integrations were also supplying the marketplace’s own amounts, currency and delivery deadline, not just processing payment	The payment rail could influence order data it should never have touched, creating a hidden second source of truth	Fixed: payment integrations are now a payment rail only

One more item belongs in this theme even though it is Pro-specific plumbing: Stripe Connect ledger reconciliation is now owned end to end inside Pro, so automated payouts settle directly against the wallet ledger instead of trusting a separate calculation. If you run automated vendor payouts through Stripe Connect, this is the piece that keeps the payout amount and the ledger balance from drifting apart over time.

Practically, if you were running any of the affected combinations, especially PayPal payouts, Stripe Connect splits, or vendor subscriptions, it is worth pulling your commission and payout history for the last billing cycle after updating and spot-checking a handful of orders against what actually settled. That is not because 1.3.0 is unstable; it is because the fixes correct data that may already be sitting in your database from before the update, and reconciling once after an update like this is good practice regardless of which plugin you run.

Theme 2: A marketplace that can sell on day one

The second theme is about the gap between installing the plugin and actually taking a first order. Several rough edges in that path got smoothed out in 1.3.0, and together they change what a brand-new install looks like on day one.

• Fresh installs now come sell-ready out of the box: manual/offline payment is enabled by default, default service categories are seeded, and new services publish without forced moderation getting in the way
• The setup wizard no longer forces you to configure a payment gateway as its first step; offline payment already works, and the wizard guides you toward a real gateway when you are ready for one
• Add-to-cart now goes straight to checkout, so the “Continue to Checkout” button actually does what its label says
• Paused services can no longer be ordered through the service call-to-action button, the order modal, or the cart API; a paused service is paused everywhere
• A buyer could previously get stuck on an order pending requirements with no visible way forward; the flow now always surfaces a next step

Individually these read like small fixes. Together they matter because they are exactly the sequence a brand-new visitor walks through: land on a service, click buy, get asked for requirements, check out. Before 1.3.0, a site owner testing that flow for the first time could hit a forced-gateway wall in the wizard, a mislabeled checkout button, or a stuck order and reasonably conclude the plugin was broken. None of those were data problems; they were friction in the exact path a new marketplace depends on.

If you are evaluating WP Sell Services against building a similar workflow on top of WooCommerce yourself, the comparison is laid out in more detail at WP Sell Services vs. Woo Sell Services, and if you are weighing a fully standalone service platform against a WooCommerce-attached one, see Launch a Freelance Service Marketplace.

Theme 3: Dark mode and a real frontend polish pass

The third theme is visual, and it is the one most visitors will notice first even though it is the least consequential to your bottom line. WP Sell Services now has full dark-mode support across every frontend surface, including Pro’s vendor dashboard and analytics screens.

The detail worth understanding here is which signal dark mode follows. It does not follow the visitor’s operating system dark-mode setting. It follows the toggle exposed by your active theme, whether that is BuddyX, BuddyX Pro, Reign, or another theme with its own light/dark switch. That is a deliberate choice: a marketplace styled to match its own theme’s dark mode looks intentional, while a plugin that flips independently based on OS preference can clash with a theme that has not switched.

Alongside the dark-mode work, 1.3.0 includes a broader consolidation of frontend styling:

• Dark mode no longer renders dark text on dark surfaces, a legibility bug that made some panels effectively unreadable once a theme’s dark toggle was on
• Buyer request cards keep their action buttons on a single line as compact icon controls on mobile and tablet, instead of overflowing the card
• An accessibility pass added visible keyboard-focus indicators, labeled service metabox fields in the admin, and ARIA labels on the frontend search input and category select
• Duplicated service-grid, empty-state and card styles were consolidated into shared components, so the same element renders consistently wherever it appears instead of drifting between screens

That last point is an internal-quality fix with an external effect: before consolidation, the same visual element (a service card, an empty state) could have accumulated slightly different styling in different places because each screen had its own copy. Consolidating them means a fix or a theme-driven style change now applies everywhere at once, rather than needing to be patched screen by screen in a future release.

Also worth knowing about

Beyond the three headline themes, 1.3.0 includes a handful of changes that are easy to miss in a changelog but change day-to-day operation for specific site setups.

• Role-based menu visibility. You can now show or hide marketplace menu items per user role, so a role that should not see vendor-only or admin-only navigation simply does not.
• Frontend dispute messaging. Buyer and vendor can now message each other and attach evidence directly on a dispute, without leaving the order screen to do it somewhere else.
• Display-only multi-currency hint (Pro). Powered by OpenExchangeRates, this shows catalog prices converted to the visitor’s currency as a convenience. Your base currency stays authoritative for all actual charges; this is a display hint, not a checkout currency switch.
• PayPal checkout context. PayPal checkout now sends full checkout context and handles multi-cart orders server-side, closing a path where the Pay button could go dead mid-checkout.
• WooCommerce My Account fixes. The vendor dashboard and notifications endpoints inside the WooCommerce My Account area now render correctly. That provider had never actually been hooked up before, so if you run the WooCommerce integration and rely on My Account for vendor access, this is a real fix, not a refinement.
• Unbuilt options stay hidden. Recurring services and a handful of wizard options that are not fully built yet are hidden and deferred to a future version, rather than appearing in the UI before they actually work.

That last point deserves a moment, because it is a small honesty signal worth naming. It would have been easy to ship a recurring-services toggle that looked like a feature and did not fully function, and let support tickets sort it out later. Instead, the option is hidden until it is real. That is a minor decision on its own, but it is the same instinct behind fixing the money bugs rather than leaving them: show what works, fix what does not, and do not paper over either one.

Free vs. Pro: where the line actually sits

It is worth being explicit about which capabilities are free and which require Pro, because a marketplace plugin’s value proposition lives or dies on that line being clear. Everything in this table reflects only capabilities named in the release material above; nothing here is inferred or assumed.

Capability	Free	Pro
Multi-step service creation wizard with live preview	Yes	Yes
Three-tier pricing packages (Basic, Standard, Premium)	Yes	Yes
Service add-ons, video embeds, per-service FAQ, service requirements	Yes	Yes
Image gallery per service	Up to 4 images	Expanded limits
Category and tag organization	Yes	Yes
11-status order lifecycle, requirements collection, file delivery with approval	Yes	Yes
Per-order messaging with attachments, revision and deadline-extension requests	Yes	Yes
Vendor registration/approval, seller level progression	Yes	Yes
Standalone checkout (Stripe, PayPal, offline)	Yes	Yes
Dispute resolution, frontend dispute messaging with attachments	Yes	Yes
Reviews and commission-based earnings	Yes	Yes
Role-based marketplace menu visibility	Yes	Yes
Display-only multi-currency hint (OpenExchangeRates)	No	Yes
E-commerce platform adapters: WooCommerce (HPOS), EDD, Fluent Cart, SureCart	No	Yes
Razorpay gateway (UPI, cards, netbanking, wallets)	No	Yes
Vendor payout wallets: Internal Wallet, TeraWallet, WooWallet	No	Yes
Stripe Connect ledger reconciliation for automated payouts	No	Yes
Advanced analytics	No	Yes
Cloud storage for delivery files	No	Yes
Expanded service creation limits	No	Yes
Vendor subscription plans	No	Yes
Full dark mode across dashboard and analytics screens	Frontend surfaces	Frontend + Pro dashboard/analytics

The pattern is straightforward: free owns the complete marketplace mechanics, from listing to order to dispute to commission-based earnings. Pro owns the connective tissue to bigger e-commerce infrastructure (WooCommerce, EDD, Fluent Cart, SureCart), a regional gateway (Razorpay), vendor payout automation at scale, and the reporting and storage headroom that matters once you have real order volume.

Which payment setup actually fits your marketplace

Because 1.3.0 touched money handling across every combination, it is worth laying out concretely what each layer does, so you can match your setup to what you actually need rather than installing everything by default.

Gateways

• Stripe (free): card payments, with Stripe Connect available for automated vendor payouts in Pro
• PayPal (free): now with full checkout context and server-side multi-cart handling, and payouts settling on the wallet ledger instead of a separate path
• Offline/manual payment (free): enabled by default on fresh installs, so you can take orders before configuring any gateway at all
• Razorpay (Pro): UPI, cards, netbanking and wallets, aimed specifically at Indian markets

All of these gateways, per the release notes, support sandbox and live modes, multi-currency, and webhook verification.

Vendor payout wallets (Pro)

• Internal Wallet: built-in wallet with full transaction history
• TeraWallet: integration for sites already running TeraWallet
• WooWallet: integration for sites already running WooWallet

If you already standardized on TeraWallet or WooWallet for other parts of your store, Pro plugs vendor earnings into that existing wallet rather than asking you to run a second, parallel balance system.

E-commerce platform adapters (Pro)

• WooCommerce: HPOS compatible, with support for a multi-service cart
• Easy Digital Downloads
• Fluent Cart
• SureCart

None of these are required. WP Sell Services free ships its own standalone checkout, and that checkout is a complete purchase path on its own. The adapters exist for sites that already run one of these platforms for other products and want services sold through the same cart and order system, rather than running two separate checkouts side by side.

Updating: free and Pro move together

Free and Pro 1.3.0 need to be installed together. Given how much of this release is cross-cutting money logic (commission splits, ledger reconciliation, Stripe Connect fee computation) that spans both plugins, running a mismatched pair is not a supported state; update both at the same time rather than staggering them.

A sensible update sequence:

1. Back up the database before updating, as with any plugin update that touches order and payment data
2. Update the free plugin and Pro together, not one and then the other days later
3. If you run WooCommerce, EDD, Fluent Cart, SureCart, Razorpay, or a Pro wallet integration, spot-check a few recent orders’ commission splits after updating against what actually settled
4. If you run vendor subscriptions, confirm a test signup and a test plan change both bill correctly under the new hosted Stripe Checkout flow
5. If your theme has a dark-mode toggle, click it and check the vendor dashboard, service pages and cart in both states

Frequently asked questions

Do I need Pro to take payments?

No. The free plugin ships a standalone checkout with Stripe, PayPal and offline payment, and offline payment is enabled by default on a fresh install so you can take orders immediately. Pro adds Razorpay for Indian markets, plus e-commerce platform adapters and vendor payout wallets for sites that need those specifically.

Which payment gateways are supported?

Free supports Stripe, PayPal and offline/manual payment. Pro adds Razorpay (UPI, cards, netbanking, wallets). All gateways support sandbox and live modes, multi-currency, and webhook verification. Pro also adds Stripe Connect for automated vendor payouts, with ledger reconciliation now owned end to end inside Pro as of 1.3.0.

Do I have to use WooCommerce?

No. WP Sell Services free includes its own standalone checkout that works without any e-commerce platform installed. WooCommerce, along with Easy Digital Downloads, Fluent Cart and SureCart, are optional Pro adapters for sites that already sell other products through one of those platforms and want services to share the same cart and order system.

Should I update both plugins together?

Yes. Free and Pro 1.3.0 must be installed together, and given how much of this release is shared money-handling logic (commission splits, ledger reconciliation, subscription billing) between the two plugins, updating them at the same time is the only supported path.

Does dark mode follow my theme or the visitor’s OS?

It follows your active theme’s own dark-mode toggle, whether that is BuddyX, BuddyX Pro, Reign or another theme with a light/dark switch, not the visitor’s operating system setting. As of 1.3.0 this covers every frontend surface and, in Pro, the vendor dashboard and analytics screens as well.

The bottom line

1.3.0 is not the release to point to if you want a list of new things vendors can do. It is the release that makes the things they were already doing add up correctly: commissions that persist instead of saving NULL, PayPal payouts that settle once instead of twice, and refunds that reverse a ledger entry only when the gateway actually took the money back. Rounding now respects the currency you are actually charging in.

Layered on top of that, a new install now sells on the first visit instead of getting stuck behind a forced gateway step, and the whole frontend, including Pro’s dashboard, renders correctly in whatever light or dark mode your theme is set to.

If you are already running WP Sell Services, the practical next step is the update sequence above: back up, update both plugins together, and spend ten minutes spot-checking commission and payout numbers against what actually settled, especially if you use PayPal payouts, Stripe Connect, or vendor subscriptions.

If you are evaluating the plugin for a new marketplace, start with the free plugin’s download page, confirm the standalone checkout and order workflow fit what you need, and add Pro’s platform adapters, Razorpay gateway or payout wallets only once you know which of those your specific setup actually requires.