How to run a software reseller program: subscription and pay-per-key models, debt limits and reseller panels

At some point, other people want to sell your software for you. They run communities, speak languages you don't, or already have customers you would never reach on your own. A software reseller program turns those people into a sales channel that works in markets, time zones and payment habits you can't cover yourself.

Done badly, it also turns into spreadsheets of keys sent over chat, partners who pay late or never, and licenses nobody can trace. This guide explains the reseller models that work for software, how a debt model lets partners sell before they pay without putting you at risk, and how to keep every reseller key under the same control as your own sales.

What is a software reseller program?

A reseller program lets third parties sell licenses for your software to their own customers. The reseller usually pays a reseller price per key or a fee for access, sells at your retail price or their own, and handles the first line of contact with the buyer. You keep the product, the licensing system and the final say over who can use it.

Resellers are not the only kind of partner, and it helps to be clear which one you are building for:

Resellers make most sense for software that sells through communities: Discord servers, forums and local groups where buyers trust someone they already know, who speaks their language and accepts the payment methods common where they live. If you are still setting up your direct sales, start with how to sell software licenses online and add resellers once that path runs on its own.

Why sending keys in bulk breaks down

Many sellers start by generating a few hundred keys and sending them to a partner. It feels simple. It also creates problems that grow with every batch.

The underlying issue is that a pre-generated key is a liability from the moment it exists. If the partner's chat history leaks, or the partner disappears, those keys keep working and you can't tell which of them were ever paid for. Reconciling a batch means asking the partner for a list and trusting it. A panel reverses all of that: no key exists until a sale happens, and every key carries the name of the reseller who created it.

Subscription vs pay-per-key: choosing a reseller model

PapelShip lets you create reseller accounts in two models, Subscription or Pay-per-Key. In a subscription model, the reseller typically pays a recurring fee for the right to generate keys, usually within a quota. In a pay-per-key model, each key they generate adds its reseller price to their balance. They suit different partners, and you can run both at once.

As a rule of thumb, start new partners on pay-per-key. It costs them nothing to begin, and you learn how much they really sell. Move a partner to a subscription once their volume is steady enough that a fixed fee is a better deal for both sides: they pay less per key, and you get revenue you can plan around.

Whichever model you choose, set the reseller price by working backwards from your retail price. The gap has to cover the reseller's payment costs, their support time and a margin worth their effort, while still leaving you more than it costs to serve the key. Too thin a gap and resellers raise their prices or quietly stop selling. Too wide, and they can undercut your own store while still making money.

How to set up a reseller program step by step

1. 01

   Write down the terms first

   Before creating any accounts, decide which products partners may sell, the reseller price for each, a minimum retail price, who handles support and how quickly balances must be paid. A one-page agreement prevents most disputes.

2. 02

   Create a reseller account

   Invite each reseller to their own account instead of sharing your login. They work in a reseller panel that shows only what you allow, and you can remove their access at any time.

3. 03

   Choose products and durations

   Decide exactly which products and license durations each reseller may sell. A new partner might start with one product; a trusted one can carry your whole catalogue.

4. 04

   Set reseller pricing and margins

   Set the price the reseller pays per product so every key they generate is charged correctly, and leave enough room below your retail price for their margin.

5. 05

   Set quotas and generation limits

   Cap how many keys a reseller can generate and how much debt they can carry. Quotas limit volume; the debt limit limits the money at risk.

6. 06

   Switch on automatic debt collection

   Let the panel assign debt as keys are generated and collect it through your PapelShip commerce account. Reseller revenue routes to your PapelShip balance.

Reseller panels are part of the paid plans, alongside staff panels that give your own team restricted support and key-generation access without sharing the owner account. Pricing lists the current limits for each plan.

How the reseller debt model works

In a debt model, the reseller doesn't prepay. Each key they generate adds its reseller price to their balance, and PapelShip assigns that debt automatically and collects the payment through your commerce account. You don't chase invoices by hand. You don't just grant access; you get paid even when you're offline.

The limits are what make credit safe. A quota caps how many keys a reseller can create; once they reach their debt limit, they can't generate more keys until the balance is paid. Keys already sold keep working, so their customers aren't punished for a late payment. Your maximum exposure to any partner is a number you chose in advance, not whatever they happened to sell before going quiet.

Credit is a design choice, not the only option. If you'd rather carry no risk at all, ask partners to pay before they sell. The trade-off looks like this:

Keeping reseller keys under control

Keys generated by resellers are ordinary licenses in your qPapel Auth system. Everything that protects your direct sales protects theirs too:

• –HWID binding locks each reseller key to the first machine that activates it, so one sale can't become a shared key. See what is HWID locking.
• –Bans work on any key, whoever generated it. A banned key stops working at its next check.
• –Device visibility. The Computers page shows which machines use which keys, including keys sold by resellers.
• –Attribution and logs. Every key records the reseller who created it, so a problem can be traced back to the right partner.
• –Leak tracking. If a build turns up somewhere it shouldn't, Binary Trace helps identify the license it came from.

Reseller customers also benefit from your customer panel. They can check their key's status and remaining time and request a hardware reset without contacting the reseller or you. That keeps reseller support light, which matters: a reseller who drowns in tickets soon stops selling. More in a customer portal for software licenses.

Reseller delegation with a debt model is common among licensing services, and KeyAuth offers one too. The difference with PapelShip is that the panel, the licenses and the payments sit on the same platform as your store and checkout. The PapelShip vs KeyAuth comparison lists the details row by row.

Rules that keep a reseller program healthy

A reseller program is a relationship as much as a system. The panel enforces the limits; these habits keep the program working after the first few months:

• –Publish a minimum retail price so resellers don't undercut your own store, or each other, until nobody makes money.
• –Start small. One product and a modest limit for every new partner, whatever volume they promise.
• –Review monthly. Look at volume, payment behaviour, refunds and HWID mismatches per reseller. Abuse usually shows up in the numbers before it shows up in complaints.
• –Make support explicit. Agree who answers the customer first, how fast, and when an issue escalates to you.
• –Keep products consistent. Reseller keys should come from the same products and durations as your store, so customers get the same experience whoever sold to them.
• –Remove access cleanly. When a partnership ends, close the reseller account. Keys already sold keep working; new ones can't be created.

Grow through partners, not spreadsheets

A reseller program should feel like adding salespeople, not adding bookkeeping. Give each partner a panel, choose the model that fits their volume, cap your exposure with quotas and a debt limit, and let the debt collect itself.

Every key stays traceable, every partner stays accountable, and your software reaches customers you would never have found on your own.