Binary vs matrix vs unilevel MLM plans explained

The short answer

Binary, matrix and unilevel are three common ways of arranging a direct selling network and paying commission on product sales. A binary plan gives each member two positions below them. A matrix plan fixes how wide and how deep each member's team can be. A unilevel plan lets each member have any number of people directly below them and pays on a set number of levels.

None of them is "best" for every business. The right structure depends on your products, your margins and how you want to reward selling. Whatever you choose, the software must calculate commission exactly as your written plan says, every time, and keep a clear record of how each payout was worked out.

Who this guide is for, and an important note

This guide is for founders and managers of direct selling businesses in India who are planning a new compensation plan (the rules for how members earn), moving from spreadsheets to software, or replacing a system they no longer trust.

Direct selling in India is regulated, including under the Consumer Protection (Direct Selling) Rules, 2021. Broadly, a genuine direct selling business earns from selling real products or services to consumers. Schemes where people mainly earn by recruiting others or by joining fees — often called pyramid or money circulation schemes — are not allowed. This guide explains plan structures and software, not the law. Before you launch or change a plan, take advice from a lawyer who understands direct selling.

Common terms in plain English

These words appear in almost every plan document.

• Sponsor (the person who introduced a new member).
• Upline and downline (the people above you and below you in the network).
• Genealogy tree (a diagram of the whole network showing who sits where).
• Leg (one branch of a member's downline; in a binary plan there is a left leg and a right leg).
• Business volume or BV (a points value attached to each product, used to calculate commission instead of the selling price).
• Payout cycle (how often commission is calculated and paid, such as weekly or monthly).
• Rank (a level a member reaches by meeting sales targets, which can unlock extra bonuses).
• Wallet (a running balance inside the system showing earnings, deductions and withdrawals).

How each plan works and what the software must handle

Each structure needs different rules in the software. These are the main ones to confirm.

• Binary — every member has two positions below them, left and right. Commission is usually based on matching sales volume from the two legs. The software must handle placement (where a new member goes, sometimes chosen by the sponsor, sometimes automatic), matching of left and right volume, carry forward (unmatched volume kept for the next cycle), and any limits on earnings per cycle. Because one leg can grow much faster than the other, the rules for carry forward and limits must be written very clearly.
• Matrix — the network has a fixed width and depth, for example a set number of people on each level and a set number of levels. When a member's front line is full, new members are placed lower down, which is called spillover. The software must place members automatically in the right order, know when a matrix is complete, and pay only on the levels your plan allows.
• Unilevel — each member can have any number of people directly below them, and commission is paid on sales from a fixed number of levels, often at a different rate per level. The software must calculate level-wise commission, apply rules such as a minimum personal sales requirement to stay active, and handle compression (skipping inactive members so commission passes to the next active one), if your plan uses it.
• Rank and bonus rules — in any structure, ranks and one-off bonuses add their own conditions, such as personal sales, team sales or the number of active members below. The software must check these conditions at the right moment and show members what they still need to qualify.
• Hybrid plans — many businesses combine elements, such as a unilevel base with rank bonuses. The software should let these rules be set up clearly rather than hidden in code nobody can explain.

Checks every direct selling system needs

Whatever the plan, these checks help keep the business transparent and easier to defend if questions are ever asked.

• Commission linked to real product sales, with each order, invoice and GST record traceable to the payout it created.
• Member KYC (identity checks) and a clear joining process with your terms shown before someone signs up.
• Returns and refunds that automatically reverse the commission earned on that sale.
• Clear deduction records, such as tax deductions where applicable — confirm the details with your accountant.
• A payout report that shows each member exactly how their earning was worked out.
• An audit log (a record of who changed what and when), especially for any manual change to a member's position or payout.
• Role-based access so only authorised staff can approve payouts or edit the tree.
• A way to test a plan change on sample data before it goes live.

Common mistakes and limits

The biggest mistake is building software around a plan that has not been checked legally and financially. If a plan only works when recruitment keeps growing, software will not fix that, and it may create serious trouble later.

Another mistake is a plan document that is vague. Phrases such as "balanced legs" or "active member" must be defined exactly, or the software developer will have to guess, and members will dispute payouts. Write down worked examples for each rule.

Also be careful with manual overrides. A system where staff can quietly move members or edit payouts loses trust quickly. Keep changes rare, approved and logged.

Finally, remember that large networks mean a lot of calculation. Ask how the system handles payout runs as the network grows, and test with realistic sample data.

Software also has limits on what it can prove. It can record that commission came from product sales and keep a clean trail, but it cannot make an unsound plan compliant. Compliance depends on the plan itself, your product pricing, how members are recruited and trained, and how you deal with complaints and returns.

Practical next steps

A careful start saves a lot of rework.

• Write your full compensation plan in plain language, with a worked example for every type of earning.
• Have the plan reviewed by a lawyer and your accountant before any software is built.
• List your products, their prices and business volume, and how returns are handled.
• Decide what members need on their phone: their tree, orders, earnings and payout history.
• Ask for a test run of a full payout cycle on sample data and check the numbers by hand.
• Plan how existing member and order data will be moved in, and check it carefully.
• If useful, H1Cloud can review your written plan from a software point of view and tailor a system to it.