Costs
Part of Direct selling: a focused business guide for 2027
A direct selling checklist built around real audits
A direct selling audit checklist records who checked each claim, what evidence backed it, and which gaps stopped a release before it reached recruits.
What to take away
- Every objective claim in a recruiting script, income disclosure or product page needs a reasonable basis on file before it goes out, per the FTC advertising substantiation policy.
- Recruitment volume is not customer demand. Track retail orders, refunds and complaints separately from sign-ups, or the checklist proves nothing.
- A blank field is a failed check, not an assumed pass. Name the owner and the date on every line.
- Retest anything that changed. An old approval does not carry forward to a new script, price or compensation claim.
- Keep the completed checklist with the version it released, so an auditor can match decision to document.
Direct selling companies fail audits for two reasons: a claim nobody can substantiate, and a distributor treated as a customer when the orders say otherwise. A checklist that records both is the only kind worth keeping.
Build the evidence file first
Start with the claims a distributor actually repeats: earnings potential, product results, time to rank, the cost to join. Each one needs a source, a date and a stated limit. The FTC's substantiation standard applies to objective claims before they are disseminated, which means the file exists before the script does.
Claim evidence review fields
- Claimexact wording, audience, where it appears
- Basisstudy, disclosure, or internal data
- Recruitmentsign-ups, kit orders, autoship volume
- Retailcustomer orders, refunds, complaints
- Decisionpass, fail, exception, or block
| Review field | What to record | Acceptance test |
|---|---|---|
| Claim | Exact wording, audience, and where it appears | Source document on file |
| Basis | Study, disclosure, or internal data behind it | Dated and limited |
| Recruitment | Sign-ups, kit orders, and autoship volume | Separated from retail sales |
| Retail | Customer orders, refunds, complaints | Reconciled to the same period |
| Decision | Pass, fail, exception, or block | Named owner and date |
A claim with no basis does not get a softer version. It gets pulled.
Acceptable and unacceptable wording
Earnings. Unacceptable: "Earn $10,000 a month from home, guaranteed." Acceptable: "Earnings depend on sales, effort and market. Our income disclosure reports the share of participants who earned nothing and the median for those who did."
Product results. Unacceptable: "Cures arthritis and replaces your prescription." Acceptable: "Supports joint comfort. Not intended to diagnose, treat, cure or prevent any disease."
Copy this checklist
Copy one per release.
| # | Check | Owner | Date | Result |
|---|---|---|---|---|
| 1 | Wording matches the approved source | |||
| 2 | Basis dated and limited | |||
| 3 | Sign-ups split from retail orders | |||
| 4 | Refunds and complaints reconciled | |||
| 5 | Plan version matches the live script | |||
| 6 | Disclosure page passes an access check | |||
| 7 | No blank field without an owner |
Separate recruitment from demand
The number that hides a problem is total volume. A distributor who buys the starter kit and never sells to anyone outside the business still counts as a recruit and still generates an order. That order is not demand.
Pull three figures for the same period: retail orders from non-participants, refunds and returns, and complaints. If retail orders are flat while recruitment climbs, the growth is inventory moving into the field, not product moving to customers. The direct selling model only works when the second number is real.
Run this check monthly. Quarterly is too slow when a rank promotion depends on the gap.
Put the page check on the checklist
A compliance review that reads the copy and stops there misses half the exposure. The W3C information and relationships explanation sets out that visual structure and relationships must also be available programmatically. Apply that to the actual income disclosure table, the sign-up form, and the commission report a distributor downloads.
If a screen reader cannot tell which column is rank and which is payout, the disclosure is not delivered. That is an access failure and a disclosure failure at once. Put the page test on the checklist, with the tool, the person and the date.
Keep audit records you can hand over
Any CRM, autoship or back-office platform you adopt will hold distributor records, downline data and payment history. The GOV.UK technology selection guidance asks the questions worth copying: can you export your data, who controls it, what does it cost to run over time, and what happens at renewal.
Read the answers as retention requirements. An audit file needs the record, a usable export, and the version history that shows which script was live on which date.
Set the retention period in writing. Four things determine it: the limitation period for claims in your state, the compensation plan cycle, tax record rules, and the life of any open complaint. A platform that cannot export your downline is a platform that owns your business.
Retest on a schedule and on triggers
Set the interval in writing. A full claim file review is typically annual, every 6 to 12 months, with the monthly retail check in between. A trigger overrides the calendar.
Triggers that force a re-audit:
- New or edited recruiting script, income claim or testimonial.
- Price change, new kit, or a change to the compensation plan.
- New product with structure or function claims.
- A rise in refunds, returns or complaints within one period.
- Regulator inquiry, state attorney general letter, or platform migration.
Record the trigger, the date and the owner.
A worked release audit
Take one recruiting script and one income disclosure and trace them end to end.
- Pull every approval, version and supporting record attached to each.
- Treat any unexplained blank as a control gap with a named owner.
- Compare the finding against retail orders, refunds and complaints for the same period.
- Check that the compensation plan version in the script matches the one in force.
- Record the safeguard, the correction owner and the next review date.
The outcome you want is customer transactions you can count and seller conduct you can defend. Treat early numbers as diagnostic, not as proof. Expansion should wait until the result reproduces with the people, systems and budget you actually have.
For privacy risk specifically, the NIST Privacy Framework starting guide describes a voluntary process for identifying risk and assigning owners. It is a management aid, not legal clearance. Record the source date and its limits beside your decision.
Common questions
What is the first decision in a direct selling audit?
Define the owner, the audience, the outcome, and the evidence that would stop the work. Without a named owner, a failed check has nobody to correct it.
How often do I retest?
On the cycle you set, and immediately when a trigger fires. Record the date and the owner either way.
What should the checklist never do?
Never let a blank field pass as approval, and never release a claim without a dated basis on file. Preserve the affected record and correct the output where the error appeared.
Who sets the rules I have to follow?
Income and product claims are policed by the Federal Trade Commission, which also applies its Business Opportunity Rule to many seller-assisted programs. State attorneys general enforce separate consumer protection and business opportunity statutes, and their filing, disclosure and cooling-off requirements vary by state.
Verify with your state attorney general's office and the FTC's business guidance pages.
