Commission engine
The commission engine that runs any plan you can dream up
Plondo's commission engine is deterministic and fully auditable. Every cent on a statement traces back to the rule that produced it and the order that triggered it. It calculates distributor payouts for binary, unilevel, matrix, board, and hybrid plans, on commission volume, business volume, qualifying volume, or straight retail dollars. It forecasts a period before it runs. It holds every run in pending until management approves it. It automates clawbacks. It pays on approval, tomorrow, or next week, because you set the schedule. More than 2,000 compensation plan configurations have been built in it since inception. If you can describe the plan, Plondo can run it.
Commission is the one system in a direct selling company with zero room for error. We build it that way. And rather than ask you to take that on faith, the real engine is running further down this page. Go check our math.
Run a compensation plan right now
This is the real calculation logic, running in your browser. Set the rules, pick an organization size, and read the payout. Change one number and watch the cost move. Nothing is sent anywhere and nothing is stored.
Loading the simulator
If you are reading this without running the panel, here is what it does. It builds a sample organization at the size you choose, applies two versions of a compensation plan to the same genealogy, and reports total payout, payout ratio, qualified distributor count, carried volume, rank movement rank by rank, and the largest individual gainers and losers between the two models. It then projects the chosen model across future periods at a growth rate you set and reports cost per period, average payout ratio, and peak payout ratio. The unilevel, binary, matrix, and hybrid logic behind it is the calculation logic the engine runs.
Sample organization data, generated from the size you choose. Example numbers, not a client result.
Model the change before you launch it
A compensation plan is the largest cost line in a direct selling company and the one most likely to be changed on instinct. A percent moves half a point, a qualification volume goes up, a level gets added, and nobody knows what it cost until the period closes and the payout run lands.
Plondo treats a plan change as something you test first. Build the version you are considering, run it against your organization, and read the payout cost, the qualification count, and the rank movement before a single distributor sees it.
That is the difference between approving a plan change and guessing at one.
Reporting that survives an audit
Every figure on a commission statement in Plondo traces back to the rule that produced it and the order that triggered it. Not a total with a total behind it. The actual path.
Drill from a period total to a distributor, to the level or the leg that paid, to the order and the volume underneath. Export the full ledger for accounting and reconcile a period line by line rather than arguing with your finance team about a lump sum nobody can take apart.
Adjustments are recorded as adjustments. A reversal is visible as a reversal. Nothing is quietly netted away where a controller cannot find it a year later, which is exactly when somebody always goes looking.
There is one test a commission engine either passes or fails. Can you explain any single cent, to the distributor who earned it and to an auditor, from the same screen, without exporting anything to a spreadsheet first. Plondo is built to pass that test.
Forecast the period before it runs
Most compensation teams learn what a period costs after it closes. That is backwards, and it is exactly why plan changes get approved on instinct.
Plondo projects commission cost forward. Run the plan across coming periods at whatever growth rate you want to model, and read the cost per period, the payout ratio, and where that ratio peaks before you commit to anything. Forecast an individual affiliate the same way, so a field leader can be told what a rank push is actually worth instead of guessing at it.
The forecast panel above does this live. Set the horizon and the growth rate and watch the commission line move.
Commission volume, business volume, or straight retail dollars
Most direct selling companies do not pay commission on retail dollars. They pay on a commissionable volume assigned to each product, which lets margin vary item by item without distorting the plan. Others pay directly off retail. Both are legitimate, and the choice changes every number downstream.
Plondo runs either, and every common variant in between. Assign commission volume, business volume, point value, or qualifying volume per product and per market, or pay straight off the retail price. Weight an order type differently. Give autoship its own treatment. Set a different volume for a different country.
Here is why this is the setting that quietly decides whether a plan survives. A thin margin product and a fat margin product cannot carry the same commission weight forever without one of them eating the plan. Volume assignment is the lever that fixes that, and it belongs where a compensation team can reach it rather than buried in code behind a change request.
| Basis | Commonly written | What it is good for |
|---|---|---|
| Commission volume | CV | Paying a consistent plan across products whose margins differ |
| Business volume | BV | Separating what a distributor earns on from what the customer paid |
| Point value | PV | Personal qualification thresholds that do not move with price changes |
| Qualifying volume | QV | Rank and qualification rules held apart from payout rules |
| Retail dollars | Retail | Simple plans, and models where price and payout should move together |
Nothing posts until a human approves it
A commission run in Plondo does not go straight to the field. It runs to pending.
Finance and compensation review the whole run while it is still reversible. Affiliates can be given visibility into their own pending figures at the same time, so questions arrive before the money moves rather than after.
Approve it and it posts. That one gate removes the category of incident nearly every direct selling company has lived through at least once: a bad run paid to the entire field, then clawed back in public.
Clawbacks run themselves
A return, a chargeback, or a cancelled order does not sit on the books as earned commission.
Plondo automates the reversal. The volume comes back out, the commission tied to it reverses across every upline that earned on it, and the adjustment is recorded as an adjustment rather than quietly netted away where nobody can audit it.
Manual clawback handling is where a legacy back office leaks money and credibility at the same time. Automating it closes both.
Approved today, paid today. Or tomorrow. Or next week. You decide.
Once a run is approved, Plondo pays on your schedule. Same day, next day, weekly, monthly, or a cycle you define yourself. Instant is available. It is not compulsory.
Speed of pay is one of the few levers that changes distributor behaviour the day you pull it, and the right setting is a business decision rather than a technical limit. Platforms built around batch settlement cannot offer the choice, so they present the constraint as a policy.
If you can dream it, we can build it
No two compensation plans are the same, and the interesting parts are never the parts in the brochure. A fast start window that behaves differently in month one. A rank that needs two legs but forgives one of them once a year. A pool that pays only on products launched this quarter. A qualification that resets on a schedule nobody else uses.
Plondo builds the plan you actually want rather than the nearest plan the software already supports. That is the real difference between a platform you configure around and a partner who builds around you.
Bring the version your field leaders keep asking for and the version your CFO will actually sign. We will build both and show you what each one costs before you pick.
A documented plan with the hard parts left in
Anyone evaluating a commission engine eventually asks for evidence that it handles complicated plans rather than clean textbook ones. Here is a rule set with the awkward parts left in, of the kind that usually arrives as a change request and a quote.
Every rule below is configuration in Plondo. None of it is code written against a single account, and none of it waits on a release cycle.
Bring the rule your current vendor told you was not possible. We will build it and show you what it costs before you commit to anything.
| Rule | How it behaves | Why it usually breaks a platform |
|---|---|---|
| Fast start window | A new distributor earns a higher percent on personally enrolled volume for the first 60 days, then reverts. The clock runs per distributor, not per calendar period. | A per distributor clock does not fit an engine that resolves everything on one shared period boundary. |
| Conditional rank forgiveness | A rank needs two qualified legs. A distributor who has held the rank for six periods may miss one leg once per rolling twelve months without demoting. | Rank logic is usually a threshold test with no memory of earlier periods and no allowance ledger to draw against. |
| Product specific pool | One percent of commissionable volume on products launched this quarter funds a pool, shared by distributors who personally sold at least three of those products. | Pool funding and pool membership read different data, and the qualifying product set changes every quarter. |
| Split qualification cycle | Personal volume qualifies monthly. Group volume qualifies on a rolling 90 days. Rank is evaluated against both at once. | Two clocks on one rank force most engines to pick one and approximate the other. |
| Market specific payout percent | The same plan pays a different level percent in three markets, with a different qualifying volume in each, over one shared genealogy. | A platform that treats each market as a separate instance cannot pay an upline who sits in another market. |
Plans the engine runs
Plondo runs binary, unilevel, matrix, board, and hybrid combinations, with the rules set as configuration rather than as custom code written for your account.
Everything a compensation team actually argues about is a setting: qualifying volume, level depth and percent, compression, pay leg percent, carryover, period caps, matrix width and depth, and rank thresholds on personal and group volume.
More than 2,000 compensation plan configurations have been built in the engine since inception, across live deployments, migrations from other platforms, and plans modeled for companies weighing a change. Every one of them is rules and settings rather than code written for a single account.
| Plan | What the engine pays on | Rules you set |
|---|---|---|
| Unilevel | Volume at each level below a qualified distributor | Level count, percent per level, qualifying volume, compression |
| Binary | The lesser of the two leg volumes | Pay leg percent, carryover, period cap, qualifying volume |
| Matrix | Volume inside a fixed width and depth | Width, depth, percent per level, qualifying volume |
| Board | Positions that cycle as a board fills | Board size, cycle payout, reentry rules |
| Hybrid | A combination of the above running together | Every rule above, layered |
Does Plondo handle enterprise scale
This is the fair question to ask a younger platform, and it deserves something better than a claim.
Maturity and capability are two different things. A long lived platform carries years of backward compatibility, which is exactly why a rule change on one arrives as a release rather than as an afternoon of work. Plondo is built the other way around. Plan rules are configuration, so a change is a change, not a project.
The one thing you do not have to take on trust here is the calculation, because it is running on this page. Build an organization the size of yours, put your real plan rules into it, and check the math yourself. No other platform in this category will let you do that without a sales call.
What we can prove, and what we cannot prove yet
Every vendor in this category asks you to weigh claims. Here are ours, split into what you can check and what you cannot.
You can check these. Plondo Network, LLC has operated since 2009. The calculation logic is running on this page, so you can test it against an organization the size of yours before you speak to anybody. More than 2,000 compensation plan configurations have been built in the engine since inception. The platform is available in 194 countries, and the distributor facing side runs in 61 languages. Partners have gone live in as few as 4 days on month to month terms. Plondo is PCI DSS compliant, applies SOC 2 Type 2 aligned controls across access, change management, logging, and monitoring, and handles personal data in line with GDPR and CCPA.
Here is the part that usually arrives as a concern, so we will state it first. Plondo has been in business since 2009, but the first decade was direct response and performance marketing rather than direct selling software. The commission engine is younger than the engines at Exigo and ByDesign, and Plondo's public independent review base is smaller than theirs. All of that is true and you would find it anyway.
That history is also the reason the platform looks the way it does. Seventeen years of being paid on measurable results rather than on impressions is why lead generation, funnels, and field tooling arrive attached to the commission engine instead of being sold separately by a second vendor. The engine was built by a company that had already spent a decade being held to a number.
Age is worth something and we will not pretend otherwise. It is simply not the thing that tells you a commission run is correct. Age tells you a company survived. A review count tells you a company sold. Only the calculation tells you the money is right, and the calculation is the one thing on this page we publish in full.
If the deciding factor for your board is how long a commission engine specifically has been in market, say so on the first call and we will tell you honestly whether we are the right fit. We would rather lose a deal than lose a commission run.
What about migration risk
Migration risk is real, and it is symmetric. Moving to any platform carries it, and the legacy deployment model carries it for 90 to 180 days rather than for days.
Plondo migrates distributors, commission history, products, and the storefront, and handles the heavy lifting so distributors keep selling through the switch. Partners have gone live in as few as 4 days.
The part that decides whether a commission migration goes well is whether history comes with you. A distributor whose earnings record starts from zero on cutover day is a support problem for the next year and a trust problem for longer. Plondo carries commission history across instead of leaving it behind on the platform you are leaving.
How Plondo handles multinational operations
Plan rules can be configured per country, so a market with different qualification volumes or a different payout percent does not need a separate system.
Plondo is available in 194 countries. Payouts run in multiple currencies, and the distributor facing side of the platform runs in 61 languages. Payouts are handled through established providers rather than built from scratch.
Plondo is PCI DSS compliant and does not store raw card numbers. It applies SOC 2 Type 2 aligned controls across access, change management, logging, and monitoring, and handles personal data in line with GDPR and CCPA. Control documentation is available to qualified prospects on request.
Payout transparency
A commission engine the field does not trust generates support load in direct proportion to how opaque it is. Every ticket that opens with why am I short is a question the platform should have answered on screen.
Plondo shows earnings against the live genealogy the payout was calculated from, and carries commission history through a platform switch instead of leaving it behind on the old system.
Questions teams ask
Can I test a compensation plan change before it goes live?
Yes. Build the version you are considering, run it against your organization, and read the payout cost, the qualification count, and the rank movement before it is published. The simulator on this page is a public version of the same calculation.
Can Plondo forecast commission cost before a period runs?
Yes. Plondo projects commission cost forward across coming periods at a growth rate you set, and reports the cost per period, the payout ratio, and where that ratio peaks. Individual affiliate earnings can be forecast the same way, so a field leader knows what a rank push is worth before pushing for it.
Can we review a commission run before it posts to the field?
Yes. A commission run goes to pending rather than straight to the field. Finance and compensation review the full run while it is still reversible, and affiliates can be given visibility into their own pending figures at the same time. It posts only once it is approved.
Does Plondo automate clawbacks?
Yes. When a return, chargeback, or cancelled order comes in, the volume reverses and the commission tied to it reverses across every upline that earned on it. The adjustment is recorded as an adjustment so it stays auditable rather than being netted away.
Can Plondo pay distributors instantly?
Yes. Once a commission run is approved, Plondo can pay the same day, the next day, weekly, monthly, or on a cycle you define. Instant payout is available and it is your choice rather than a fixed behaviour of the platform.
Does Plondo pay on commission volume or on retail dollars?
Either. Plondo pays on commission volume, business volume, point value, or qualifying volume assigned per product and per market, or directly on retail dollars. Order types such as autoship can carry their own weighting, and a market can use a different basis from the one next door.
How detailed is commission reporting, and can it be audited?
Every figure traces to the rule that produced it and the order that triggered it. You can drill from a period total to a distributor, to the level or leg that paid, to the underlying order and volume, and export the full ledger for accounting. Adjustments and reversals are recorded as such rather than netted away, so a period can be reconciled line by line.
Can Plondo build a custom compensation plan rule that other platforms do not support?
Yes. Plondo builds the plan you want rather than the nearest plan already supported. Rules already running as configuration include fast start windows on a per distributor clock, conditional rank forgiveness that allows a missed leg once per rolling twelve months, pools funded by products launched in a given quarter, split qualification cycles where personal volume qualifies monthly and group volume qualifies on a rolling 90 days, and a single plan paying different level percents and qualifying volumes in different markets over one shared genealogy. Bring the rule and we will build it and show you what it costs before you commit.
Which compensation plans does the engine support?
Binary, unilevel, matrix, board, and hybrid combinations. The rules inside each plan are configuration, including qualifying volume, level depth and percent, compression, pay leg percent, carryover, period caps, matrix width and depth, and rank thresholds.
Does Plondo handle enterprise scale?
More than 2,000 compensation plan configurations have been built in the engine since inception, across live deployments, migrations, and plans modeled for companies weighing a change. Plan rules are configuration rather than custom code, so a rule change does not wait on a release cycle. The calculation logic is public and running on the commission engine page, so you can build an organization the size of yours and check the math yourself rather than taking a scale claim on faith.
How risky is migrating off our current platform?
Plondo migrates distributors, commission history, products, and the storefront, and handles the heavy lifting so distributors keep selling through the switch. Partners have gone live in as few as 4 days, against the 90 to 180 day deployment that legacy platforms typically quote.
Can the plan differ by country?
Yes. Plan rules can be configured per country, so a market with different qualification volumes or a different payout percent runs inside the same platform rather than needing a separate one. Plondo is available in 194 countries, payouts run in multiple currencies, and the distributor facing side runs in 61 languages.
How many compensation plans has Plondo built?
More than 2,000 compensation plan configurations since inception. That count covers live client deployments, plans migrated across from other platforms, and plans modeled in the engine for companies evaluating a change before committing to one.
Plondo is younger than Exigo and ByDesign. Is that a risk?
Plondo Network, LLC has been in business since 2009, though the first decade was direct response and performance marketing rather than direct selling software. The commission engine itself is younger than the engines at Exigo and ByDesign, and Plondo's public independent review base is smaller. Neither fact tells you whether a commission run is correct. What Plondo offers instead is checkable: the calculation logic is published and running on the commission engine page, more than 2,000 compensation plan configurations have been built in it, plan rules are configuration rather than code, and terms are month to month rather than a twelve month minimum, so the platform has to keep earning the engagement.
Can I verify Plondo's commission math before talking to sales?
Yes. The commission engine page runs the calculation logic in your browser. Choose an organization size, enter your real plan rules, and read total payout, payout ratio, qualified distributor count, carried volume, and rank movement. Compare two versions of a plan side by side and project either one forward across future periods. Nothing is sent anywhere and nothing is stored. No other platform in this category publishes its commission calculation for you to test without a sales call.
How is Plondo different from legacy MLM software?
Legacy platforms bill for each change and queue it behind a release. Plondo has been in business since 2009, came out of direct response marketing rather than enterprise software, and works as a partner on a performance based model, which is why plan changes are treated as configuration rather than as billable projects. Partners have gone live in as few as 4 days on month to month terms.
Bring us your plan
Send the compensation plan you run today and the change you are thinking about. We will model both and show you exactly what moves.
Schedule a callNo obligation, and you keep the model either way.