Compliance benchmarks: the network marketing risk flags that matter

What to take away

The six flags: income claims, earnings disclosure, recruiting, autoship, classification, retention

Most state attorney general and FTC actions against direct selling companies trace back to a short list of failures. These compliance benchmarks are the flags worth testing. Each one has a named source, a test, and a stop rule.

Income claims. Any statement about what a distributor earns, or could earn, needs the FTC Income Disclosure Guide test: is the claim typical, and can you show it? The FTC 2018 business guidance on multi-level marketing says earnings claims must be truthful and not misleading. The flag is a claim with no disclosure attached.

Earnings disclosure. The income disclosure statement itself. The FTC guidance asks for a clear, conspicuous statement of typical earnings. The DSA Code of Ethics also requires truthful income representations. The flag is a disclosure that is stale, buried, or missing the median.

Recruiting language. Scripts and social posts promising a lifestyle. The FTC Endorsement Guides, 16 CFR Part 255, require disclosure of material connections such as distributor status. The flag is a recruitment script that promises income without qualification.

Autoship. The flag is an autoship rate that props up volume the retail side cannot support. ROSCA, 15 U.S.C. 8401 to 8405, and California's automatic renewal law require clear consent and a simple way to cancel. A 71 percent autoship share is a test case, not a passing grade.

Classification. 1099 or W-2. The IRS common-law factors, including behavioral and financial control, decide it, not the contract label. IRS Form SS-8 asks for a formal determination. State tests, such as California's AB 5 and Dynamex, can be stricter.

Retention math. The flag is a distributor count that only grows because recruitment outpaces attrition. The FTC and state attorneys general treat recruitment-heavy growth as a pyramid risk when retail demand is thin. Track recruits against active buyers each month.

Thresholds that make each flag testable

What a failed flag costs

The FTC has settled two large direct selling cases on these flags. In 2016, Herbalife agreed to pay $200 million and to reorganize its United States business so that retail customers were tracked apart from distributors.

In 2019, AdvoCare agreed to pay $150 million to settle FTC charges over its compensation plan and earnings claims. FTC civil penalties for rule violations are set per violation and adjusted for inflation each year.

Income claims and earnings disclosure appear in nearly every FTC count. Recruiting language draws advertising counts under 16 CFR 255 and state consumer protection acts.

Autoship draws ROSCA counts and state auto-renewal penalties. Classification draws IRS assessments and state wage claims with back taxes attached. Retention math decides whether a case is framed as a pyramid scheme, where the remedy is a restructuring order and not a fine alone.

Test the flag before you trust it

A benchmark you cannot reproduce is a line in a policy document and nothing more. Take a typical case: an autoship threshold of 60 percent has been in the policy since 2021, but nobody has run the volume query since it was written.

This quarter's autoship share is 71 percent, and no one saw it. That is the escalation stop rule: fix the test before you expand.

For each flag, state the population, period, measure, and decision threshold. Recalculate one figure by hand. The NIST experimental design selection guidance starts design choice with the objective and the practical constraints, which is the right order here. Descriptive reporting and a controlled effect estimate are different jobs.

Evidence limits: what records do not prove

The W3C Privacy Principles statement gives system designers shared privacy concepts and warns against shifting privacy work onto individuals. The CISA business-system logging guidance explains why organizations retain and review event records.

The NIST Privacy Framework starting guide describes a voluntary process for identifying privacy risk, assigning owners, and recording responses. All three are management aids. None is legal clearance for a marketing use, and none replaces a flag test.

Worked example: the autoship flag at 71 percent

Take a company with 4,000 active distributors and a monthly autoship rate of 71 percent. Retail volume is the remainder. If you cut autoship, does the business still stand?

Set V, total monthly volume, at $2 million. A, the autoship share, is 71 percent of V, or $1.42 million. R, retail volume, is V minus A, or $580,000. Fixed monthly costs are $700,000 for payroll, software, fulfillment, and compliance staff.

R of $580,000 does not cover $700,000 in fixed costs. The $120,000 gap is covered by autoship volume alone, so the retail side is not carrying the business. Under the 60 percent threshold, the 71 percent figure fails twice: the share sits above the line, and R does not cover fixed costs.

Record the case, the inputs, the unresolved limit, and the next review date. If the case exposes a gap between the written rule and the data, stop and fix the test.

Common questions

What is the first decision in benchmarking compliance risk?

Define the compliance owner, the audience, the outcome, and the evidence that would stop the work. Keep a network marketing compliance register that names each flag, its owner, and its test date. Pick the flag whose number you can pull this week and set its threshold first.

Before that register is complete, work through the network marketing compliance questions nobody wants to ask out loud, because the flags teams skip are usually the ones enforcement finds first. The first test to run is the one with the widest gap between the written rule and this month's data.

How often should these benchmarks be reviewed?

Review findings, incidents, and closure time against cost and quality on a fixed cycle, usually quarterly. Record exclusions, source limits, and failures with a dated decision. If a flag has never been tested, that is the finding.

What should a team avoid?

Avoid marking a flag as met because the policy says so. Avoid quoting an external benchmark as your own threshold.

For tax and classification questions, confirm with the IRS, CRA, or a licensed CPA. For claim rules, confirm with the FTC and your state attorney general. If a flag still has no test date, treat it as untested and hold expansion until it has one.