Binary MLM software
Binary MLM software with exact pairing, carryover and flush rules
Binary plans fail in software when the pairing math is close enough. We build binary engines where the weaker leg match, carryover balance, cycle caps and flush rules are your rules, with a ledger that proves every payout.
Typical binary build: 3 to 5 months including parallel run against your current payouts.
genealogy / binary placement
sample dataD. Alvarez
root
K. Nguyen
4,180 BV
S. Patel
2,240 BV
M. Ross
1,940 BV
J. Coleman
9,640 BV
A. Brooks
5,120 BV
T. Silva
4,520 BV
How it works
How the binary plan works in our software
Two legs, tracked separately from sponsorship
Every distributor holds exactly two placement slots, left and right. Sponsorship and placement are separate records, so spillover placement under a non sponsor works correctly, and matching bonuses still pay on personally sponsored people wherever they sit. The placement queue follows your rule: weakest leg first, preferred side, or manual placement with an override screen for operators.
Pairing on the weaker leg
The engine walks each period’s orders, attributes business volume up both legs, then matches the weaker leg against the stronger one at your ratio (commonly 1:1, 2:1 or 3:2). Matched pairs pay the pairing bonus you define; unmatched stronger leg volume waits. The back office shows both leg volumes, the matched amount and the bonus side by side.
Carryover, caps and flush
Your plan decides what happens to unmatched volume: carry the weaker leg forward indefinitely, expire it daily or weekly, or cap pairings per cycle. We configure all three and test each: carryover balances must survive rank changes, mid-period enrollment and refunds, and flush events must appear as explicit ledger lines so support can answer "where did my volume go".
| Legs per distributor | Exactly 2 (left and right placement slots) |
|---|---|
| Match ratio | 1:1, 2:1, 3:2 or custom per rank |
| Pairing bonus | For example 10% of matched business volume |
| Cycle cap | Per day or per week, for example 5,000 BV |
| Carryover | Weaker leg carries; flush rules configurable |
| Rank requirements | Personal volume plus paired volume thresholds |
| Refunds | Clawback reduces next run or draws down carryover |
What we build
What we build into binary MLM software
- Placement engine with weakest leg, preferred side and manual override modes.
- Real time leg volume cards in the distributor back office, with carryover balance and flush history.
- Pairing ledger: every match shows the orders, legs and volumes that produced it.
- Cycle caps enforced per period with explicit capped-amount reporting for corporate.
- Spillover transparency: distributors see exactly where each placement landed and why.
- Rank engine layered on paired volume, personal volume and active leg counts.
- Reconciliation reports that tie commission run totals to order volume to the cent.
- Migration from your current binary platform with placement data intact, not just sponsorship.
Every build ships with locked, reproducible commission runs and statements that show the math behind every payout. See the full delivery scope on the development page.
Edge cases
The details that break generic platforms
These are the rules we write tests for before your launch, because they are the ones support tickets are made of.
| Scenario | How we handle it |
|---|---|
| Refund after a run closes | Clawback posts against the next run and, if configured, draws down the carryover balance with a ledger line. |
| Rank change mid period | Pair ratio changes apply from the rank effective date; volume matched earlier keeps the prior ratio. |
| Manual placement override | Operators can move a placement before the period closes; the change is versioned and audited. |
| Terminated distributor | Their subtree compresses or holds per your rules; paired volume is recalculated and documented. |
| Cap reached mid cycle | Excess stronger leg volume holds or flushes per plan; the capped amount reports separately from paid pairs. |
| Cross leg volume from a shared customer | Attribution follows the referring distributor placement leg exactly once, with the order ID on the ledger line. |
Fit
When a binary plan fits your company
Products with an enrollment moment
Starter kits and high margin one time purchases generate the enrollment velocity binaries reward. If your pitch includes "join now, my team places under you", the software must show spillover honestly, which ours does by design.
Cultures that watch two numbers
Binary distributors monitor left and right volume daily. That focus drives recruiting activity, and the back office is built for it: leg volumes and next pair progress are the first screen.
Not ideal for pure reorder businesses
If 80 percent of revenue is subscription reorder with low recruiting, unilevel usually pays the field more evenly. Model both plans at 1,000 distributors before committing; we do this with you during plan specification.
Compare structures in the plan explorer, or read the buyer checklist before deciding.
Related
Other compensation plan software
Frequently asked questions
What is spillover in binary MLM software?
Spillover happens when your upline placement pushes new distributors into one of your two legs. Our back office shows each placement event, the leg it landed in and the rule that put it there, so distributors can verify spillover claims.
Can the software carry unmatched binary volume forward?
Yes. Carryover is a configurable rule: carry the weaker leg forward indefinitely, expire it daily or weekly, or cap total carryover. Every carry and flush event writes an explicit ledger line.
How do you handle binary plan migration?
We extract placement data (not just sponsorship), rebuild both legs, then load your carryover balances. A parallel commission run reconciles our payouts against your current platform before cutover.
Do you support daily binary cycles?
Yes. The pairing engine can run daily, weekly or monthly, with separate cap windows per frequency and a consolidated monthly statement for distributors.
How much does binary MLM software cost?
A binary build typically starts around 15,000 dollars because placement and carryover logic adds scope. Most binary projects land between 15,000 and 45,000 dollars depending on integrations and apps.
Discuss your compensation plan with an engineer
Bring your draft plan. In a 30 minute call we map it to software modules, flag the edge cases that break generic platforms, and give you a delivery estimate with timelines and costs.