What it actually takes to sell a WordPress theme (and what we no longer do ourselves)
When we started Porto, we assumed the hard part would be the theme itself. Get it fast, make it flexible, keep shipping demos people actually want to build on. We knew how to do that.
Selling it on our own site turned out to be a different job. Once a customer clicks “Buy”, there’s tax to collect, an invoice to send, a license to issue and, a year later, a renewal to chase. This post is about how we deal with all of that now, and which parts we’ve handed off.
Porto in a nutshell
Porto began as a multipurpose WordPress and WooCommerce theme. Over time it turned into a small family: Porto WP, Porto for Magento and the Porto eCommerce HTML template. Our buyers are mostly agencies and freelancers building sites for clients, along with store owners who want a shop that looks finished from day one. The WordPress version has 106 demos, works with Elementor, WPBakery and Gutenberg, and comes with its own builder for headers, footers, product pages and archives.
Porto went on sale on ThemeForest in 2014. More than 200,000 customers have bought it since, and we’re still a team of six. PortoTheme.com now sells seven themes and one plugin: the three Porto editions, Molla, Riode, Wolmart and U-Design, plus Alpus AI Product Review Summary.
For twelve years ThemeForest was basically our only shop, and it still brings in a big share of sales. In July 2026 we opened our own store on PortoTheme.com as well, so now we sell in both places.
The work nobody tells you about
On a marketplace you don’t see most of this. The buyer pays ThemeForest, ThemeForest pays you, and you check purchase codes against the Envato API. Sell on your own site and all of it lands on your desk.
Tax is the big one. Sell digital products worldwide and you’re dealing with sales tax and VAT rules in a lot of countries, and some of them expect you to register after only a handful of sales. Business customers need proper invoices with their VAT number on them, and they tend to ask months later, right before their own tax deadline.
Then there’s the money itself. Cards expire, banks block foreign charges, and renewals fail without anyone noticing. A refund is mostly a support conversation, but a chargeback is a formal dispute with a deadline and evidence you have to pull together. And every month someone has to get the payouts into the company account, in the right currency, with records the accountant can use.
Licensing gave us the most work, because we sell the same themes in two places. A ThemeForest buyer has an Envato purchase code. A PortoTheme.com buyer has a Freemius license key. Either one has to activate the theme without any fuss. We updated our license API so it accepts Freemius keys alongside ThemeForest codes, and the Freemius API helped a lot with that. It checks the keys bought on our site and keeps count of how many sites each license is used on.
How we set up selling
Before we opened the store, we talked through three ways of doing it.
The first was plugging in Stripe ourselves. It’s the cheapest per sale, and we’d control everything. But controlling everything also means handling the tax registrations, the invoices and the failed-payment emails, and we didn’t want to build a billing department inside a theme company.
The second was to stay on ThemeForest only. That’s simple, and it works. The catch is that the customer relationship isn’t really yours, and you can’t run your own renewals or bundles.
The third was a platform that sells on our behalf, and that’s what we chose. Freemius acts as the Merchant of Record, so legally the customer is buying from Freemius, not from us. Collecting tax on each sale, issuing the invoice and processing the payment are their job. We get payouts and a dashboard, and most of the list above stopped being our problem.
We didn’t hand over everything, though. Activation still runs through our own license server, the same one our WordPress themes already used for ThemeForest codes. Nothing had to change in the themes, and customers get the same activation screen wherever they bought. When a PortoTheme.com key comes in, the server rejects it if the license has expired or been cancelled, and otherwise registers the site on that license.
A typical month now
These days most of the billing side runs without us.
Tax is calculated at checkout and collected with the payment. If an EU business enters a valid VAT number, the reverse charge is applied automatically, so nobody here checks VAT IDs by hand. Every order gets an invoice, and when someone asks us for one, we send them to their account page. Renewals go out on schedule and failed payments are retried with reminder emails before a license runs out. When a license expires or gets cancelled, our license server picks that up the next time a site checks in.
What’s left for us is mostly the work that needs a person. Support is the biggest part, and licensing questions are still the most common billing-related tickets we get. Issuing a refund takes one click, but deciding whether a request is fair is still our call. We keep our own books from the payout reports. And pricing is ours too: what we sell, what it costs and what goes into each plan.
One moment where it mattered
The lesson that stuck with us wasn’t about tax. It was a license seat that wouldn’t free up.
A customer moved their site to a new domain. They deactivated the theme on the old site, our server replied “unregistered”, and they went to activate it on the new one. The activation was refused because they had no activations left.
It took us a while to see what was going on. Our server had deleted its own record of the old site, but it never released the seat on the Freemius side first. So as far as we knew the site was gone, while the license still counted it. The customer had done everything right and was stuck, and nothing on screen told them why.
We fixed the order. The seat is now released on Freemius first, and our own record is deleted only after that works. If the release fails, the customer is asked to try again in a few minutes instead of seeing a success message that isn’t true. We also stopped creating a new install every time a site re-checks its license, since that could use up a seat as well.
If you split licensing between your own server and a platform, expect most of the trouble to come from keeping the two in sync rather than from the license check. Freemius’s software licensing best practices are worth reading before you start building.
What we’d tell another maker
If you’re setting up sales for your own theme or plugin, here’s what we’d pass on.
Work out who the seller is before you compare tools. If it’s you, the tax and invoices in every country you sell to are on you. If it’s a merchant of record, they aren’t, and most of your other decisions follow from that.
Look at the full cost, not just the fee on each sale. A plain payment processor costs less per transaction, but add tax registrations, filings, accountant hours and your own time, and the difference shrinks a lot.
Keep licensing simple: one activation flow, clear seat limits, and a way for customers to free a seat without writing to support. Most of our billing-related tickets have been about licenses, not payments. If part of the system stays on your own server, decide which side has the final word and write down the order things happen in. Our seat bug came from getting that order wrong.
Make refunds easy to issue, but keep a person deciding them. It’s one of the places where customers can tell whether there’s a real team behind the product.
There are trade-offs, of course. You pay more per sale than with a bare processor, and you give up some control, since checkout and part of the customer account live on someone else’s platform. For a team of six selling worldwide, that’s a price we’re happy to pay. A solo developer selling mostly in one country might decide otherwise.
We’d also like Freemius to improve a couple of things. Their licensing API could be clearer about which call actually frees a seat. Deactivating a license and deleting an install are separate calls, and we ended up making both just to be safe. And activation should be idempotent, so checking the same site twice can never use up two seats. Neither one stopped us, but both cost us debugging time.
Leave a Reply