Binary vs Unilevel MLM Plans: What Is the Difference and What Should Your Software Support?

Compensation-plan terminology should be translated into precise rules

Binary and unilevel are two common ways of describing distributor-network structures. The names sound simple, but the actual compensation rules can vary significantly between companies.

A binary plan generally organises a participant's structure into two placement branches. A unilevel plan generally allows multiple directly sponsored members on the first level, with additional levels beneath them according to the plan rules.

Those descriptions explain the structure, not the entire compensation calculation. Qualification, commissionable volume, payout caps, carry-forward rules and eligibility conditions are defined separately by each plan.

If a business is selecting MLM software, it should not stop at asking whether the platform supports “binary” or “unilevel”. The software provider needs the complete written compensation specification.

1. What is a binary MLM structure?

In a binary structure, each participant is placed into two main branches, often described as a left leg and a right leg. Additional members are placed beneath those branches according to the organisation's placement rules.

This creates a two-branch structure for viewing team placement. A company may use volume from one or both branches as part of its commission rules. Some plans may use weaker-leg calculations, carry-forward volume, weekly or monthly periods, caps or qualification requirements. These details are not universal and should never be assumed from the word “binary” alone.

For software, the important requirements may include:

• Recording the sponsor and placement relationships correctly.
• Enforcing the company's placement rules.
• Calculating eligible volume for each branch.
• Applying the exact qualification and payout rules.
• Tracking any permitted carry-forward or expiry.
• Handling refunds and commission reversals.
• Producing statements that explain the calculation period and source transactions.

The system should make it possible to review why a commission was calculated and which rule was applied.

2. What is a unilevel MLM structure?

A unilevel structure generally allows a participant to sponsor multiple members directly on the first level. Those members may then sponsor additional participants, creating further levels beneath the original member.

The company defines how many levels, if any, contribute to particular commission types. It may also define level qualifications, personal activity requirements, group-volume conditions, rank rules or other criteria.

For software, important requirements can include:

• Recording direct sponsorship and downstream relationships.
• Calculating eligible volume by level.
• Applying the plan's depth and qualification rules.
• Showing which activity contributes to each commission type.
• Handling status changes, refunds and adjustments.
• Producing reports for member activity and payout review.

A unilevel structure does not mean every downline transaction automatically generates a commission at every level. The plan document must specify which transactions qualify and under what conditions.

3. Binary vs unilevel: structural comparison

The comparison is about structure. It is not a statement that one plan pays more, is easier to succeed in or is automatically more suitable for a particular company.

4. The compensation rules matter more than the plan label

Two companies can both describe their model as binary and still have different commission logic. One may define a particular period, cap or carry-forward treatment that another company does not use. The same is true of unilevel plans.

Before software configuration, document each commission type separately:

Eligible transaction. Which product or service sales count? Are taxes, shipping, discounts or refunded quantities included or excluded from commissionable volume?

Eligibility. Must a member be active, verified or meet a personal sales condition before a commission is calculated?

Measurement period. Is the calculation performed daily, weekly, monthly or according to another defined cycle?

Levels or branches. Which relationships contribute to the calculation, and how is placement or sponsorship determined?

Caps and thresholds. Are there minimums, maximums or rank conditions? How are they applied?

Carry-forward and expiry. If volume is not used in one period, does it carry into another period, expire or follow a different rule?

Reversals. What happens when an order is refunded, cancelled or charged back after a commission has been calculated or paid?

These details should be written in plain language, reviewed by the business and its advisers, then translated into testable calculation rules.

5. What a software demonstration should prove

A provider may show a network tree and a commission dashboard, but those screens do not prove that the system implements the plan accurately.

Ask the provider to demonstrate a controlled example using test members and sample orders. The example should show the source transactions, placement or sponsor relationships, calculation period, applicable rules, resulting commission entries and any adjustments.

Then test an exception. Refund an eligible order, change a member status or introduce an order that does not qualify. Confirm that the system produces the expected result and preserves the audit trail.

A useful software demonstration should explain not just the final number, but why that number exists.

6. Reporting and transparency for distributors

Members need statements they can understand. A commission report should identify the period, commission type, eligible volume and relevant adjustments. Where appropriate, it should explain why an expected commission was not generated, such as an unmet qualification condition.

Administrators need a broader view: total eligible volume, commission liability, pending approvals, paid amounts, refunds, exceptions and reconciliation differences.

Clear reporting reduces disputes and helps the company investigate problems. It should not expose personal or financial information belonging to unrelated members.

7. Plan design, legal review and responsible implementation

A software platform should implement an approved business model, not decide whether the model is legally or commercially appropriate. In Malaysia, Act 500 governs aspects of direct-selling licensing and prohibits pyramid schemes or arrangements. A compensation-plan label alone does not establish compliance. Businesses should obtain qualified legal and compliance advice before launching or changing a plan. The official legislation is available from KPDN.

The company should also review its product value, sales practices, disclosures, customer rights, refund policy and distributor agreements with appropriate advisers. Software can support transparent records and consistent processes, but it cannot replace that review.

8. How to brief an MLM software developer

Provide a written plan document and a set of test scenarios. Include sample network structures, sample orders, qualification states, commission periods, refunds and expected calculation outcomes.

Ask the developer to return a configuration or technical specification that describes how each rule will be implemented. Review that specification before accepting the build. Use a test environment to compare system outputs against independently calculated examples.

Also confirm whether the plan can be changed by configuration, whether changes require development work and how historical periods are protected from accidental recalculation.

Final thoughts: choose rules you can explain and systems you can audit

Binary and unilevel describe different network structures, but the compensation rules determine how the business actually operates. Choosing software based on the plan name alone can lead to gaps, assumptions and disputes later.

Start with the complete written plan, define every rule and test normal cases as well as exceptions. The right platform should make relationships, transactions and calculations traceable to authorised users.

Lucianize develops MLM and distribution platforms around defined business requirements. Contact our team to discuss your system scope and compensation workflow.

Sources / further reading

• KPDN — Direct Sales and Anti-Pyramid Scheme Act 1993 (Act 500)