Your Money-Back Guarantee Wording Is a Claim

which guarantee wording did fda quote as a claim?

FDA quoted BergaMet's guarantee wording because it promised a measurable cholesterol outcome, not merely a refund process. In the BergaMet North America warning letter, FDA cited the money-back language “if they do not improve your LDL levels” alongside the product name and direct LDL-reduction claims as evidence of intended use.

That sentence does the same work as a headline saying the product improves LDL. We checked the letter for the usual escape routes: the guarantee was not treated as a neutral commercial term, and FDA did not isolate it from the surrounding cholesterol copy. It sat in the claim stack because LDL improvement is the condition for getting the buyer's money back.

A refund condition can be the claim.

That is the point buyers miss when they audit headlines, VSLs, and bottles while leaving the guarantee box to the ecommerce team. If your refund promise says the customer gets paid back when the promised health result fails, you have restated the health result in a place regulators still read.

why does a refund promise establish intended use?

A refund promise establishes intended use when the condition for the refund describes what the product is meant to do. FDA's intended-use analysis looks at objective marketing context, so a guarantee, checkout promise, product page, marketplace listing, social reply, or ingredient tab can all become evidence that the product is intended for a disease use.

For cholesterol, FDA's 2000 final rule is unusually blunt: “lowers cholesterol, however qualified, is an implied disease claim.” That matters because a guarantee keyed to lower LDL or improved cholesterol is not administrative language. It tells the buyer the product's intended outcome, and for this vertical FDA treats that outcome as disease territory.

We counted the guarantee as claim copy because the buyer reads it that way: not as warranty mechanics, but as proof that the seller expects the result. That is also why designing the refund policy belongs in compliance review before launch, not after payment processing is already wired.

how did the product name factor into the same letter?

The product name mattered because FDA cited “Cholesterol Command” as evidence before it reached the guarantee. Under 21 CFR 101.93(g)(2)(iv)(A), the name of a dietary supplement can create a disease claim by itself when it conveys an effect on disease.

FDA had already drawn the cholesterol line in the 2000 final rule, writing that elevated cholesterol is a disease itself, not merely a risk-factor number. The same rule says an appropriate structure/function claim is “helps to maintain cholesterol levels that are already within the normal range,” which is much narrower than most cholesterol offers want to say.

Most operators would argue that the guarantee is lower-risk than the headline because it appears in customer-service copy; BergaMet shows the opposite. A guarantee can be more damaging than a headline because it turns the outcome into a purchase condition, and it is often repeated again in cart, terms, and email copy.

what did a third-party walmart listing contribute as evidence?

The Walmart listing contributed outside-the-site corroboration that the product was being marketed for high cholesterol. FDA cited a third-party listing describing the item as “a bergamot supplement for high cholesterol,” which showed that the claim environment extended beyond BergaMet's owned product page.

We could not verify from the fact pack whether BergaMet wrote that Walmart listing, a reseller wrote it, or a marketplace data feed generated it. The settlement fact would be the listing's source record: seller account history, content-management logs, feed submissions, or Walmart marketplace revision history.

That uncertainty does not make the evidence harmless. The enforcement lesson is operational: if the product is being sold through a marketplace, your compliance perimeter includes the marketplace title, bullets, badges, Q&A, reviews, category mapping, and any reseller text that describes why the product is bought.

do marketplace listings you did not write count against you?

Marketplace listings can count against you when they help establish the product's intended use in the real sales environment. FDA has cited Amazon, Walmart, Facebook, Instagram, and brand-owned blogs in other supplement warning letters, so the source of the text is less important than whether it sits in the promotional path.

That does not mean every stray reseller sentence creates liability in the same way. It means you cannot build a campaign assuming the owned landing page is the only document in scope. We would review marketplace copy before scale, then archive screenshots after corrections so there is a record of what changed and when.

The same principle applies outside cholesterol. In memory, absentmindedness can be allowed while memory loss is not, but an Amazon bullet or affiliate review that drifts into dementia language can drag the funnel into disease territory even if the main page stayed disciplined.

how should a guarantee be worded to avoid restating the claim?

A guarantee should describe the purchase remedy, not the biological result. The clean version says what the customer must do, when the window closes, what is refunded, and what exclusions apply; it does not say the product improves LDL, lowers blood sugar, relieves pain, restores memory, or produces any other health endpoint.

For a supplement refund policy, the safer construction is procedural: “Try one bottle for 60 days; if you are not satisfied, request a refund under the return terms.” That still needs ordinary consumer-law review, payment-processor review, and consistency with the checkout page, but it avoids making the refund contingent on a disease or structure/function outcome.

This is where operators need to separate guarantee strength from claim strength. You can offer a strong refund window without promising a health result. If the niche is constipation, for example, the claim review belongs beside the refund review because occasional constipation wording carries its own condition.

• Avoid: “Refund if your LDL does not improve.”
• Avoid: “Refund if your blood sugar remains high.”
• Avoid: “Refund if pain is not reduced.”
• Prefer: “Refund available if you are not satisfied, subject to the posted return terms.”

which checkout and terms pages need the same review?

Every page that repeats the guarantee needs the same claim review: product page, cart drawer, checkout, order-confirmation page, subscription terms, FAQ, refund policy, email flows, SMS flows, marketplace listings, and affiliate copy. FDA and FTC both read across the funnel when the text helps show what the product is being sold to do.

The FTC's health-products guidance says health-benefit substantiation generally needs randomized, controlled human clinical testing, and the FTC also treats testimonials as claims the advertiser must substantiate. That means a guarantee box, review widget, and “risk-free trial” module can each create separate problems even when the headline has been softened.

We changed our audit order after reading the BergaMet letter: guarantees now get reviewed before checkout QA, not after. The old workflow treated refund wording as retention copy. The better workflow treats it as a claim surface, because that is how FDA used it.

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For external context, readers should compare advertising and research decisions against authoritative primary references such as FTC health claims guidance, Meta advertising standards, and Meta Ad Library. Daily Intel adds the proprietary direct-response layer: blackhat, greyhat, and whitehat campaign pattern comparison across VSL-heavy niches and 14+ language markets.

For deeper evaluation, continue through Nutra niche intelligence directory, Supplement Advertorial Examples: 7 Working Layouts, Nutra Seasonality Calendar: When Every Niche Peaks, Is the Weight Loss Niche Saturated? What Ad Data Shows, Next Big Nutra Niches: Early Scaling Signals (2026), and GLP-1 affiliate marketing intelligence. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.