On this page
A customer who already earned a purchase reward should not have to guess whether an unfavorable review will put that benefit at risk. The merchant may intend to ask for honest feedback, yet the sequence of messages, buttons and staff replies can create a different impression. Review the whole journey, not only the campaign’s written eligibility clause.
Consider a fictional kitchenware store offering an approved $15 purchase reward. After the order is delivered, a review app sends a message asking the shopper to “share a five-star experience and unlock your reward.” The original campaign did not require a review. The later automation has nevertheless linked the benefit to a favorable rating in the customer’s eyes.
Identify explicit and implied review conditions
The FTC’s Consumer Reviews and Testimonials Rule guidance says businesses may not condition review incentives, expressly or implicitly, on a particular sentiment. Disclosing the incentive does not make a five-star condition acceptable. This is a specific review-incentive issue; it should not be confused with ordinary eligibility conditions for a purchase reward.
Begin the audit at the customer’s first exposure to the offer. Capture the product-page promise, purchase confirmation, claim invitation, review request and relevant support instructions. Record the version and the sequence. Two messages that appear independent in separate administrative screens can feel connected when they arrive together.
In the fictional store, the audit might contain these findings:
| Touchpoint | Observed example | Problem to resolve | Proposed correction |
|---|---|---|---|
| Campaign page | $15 after the disclosed qualifying purchase | Purchase condition is the intended basis | Preserve approved eligibility wording |
| Review email | Five-star feedback presented as the way to unlock value | Favorable rating appears required | Stop and replace the solicitation |
| Claim page | Review submission shown before access | Optional feedback looks like an access gate | Remove the review dependency |
| Support reply | Agent asks for a review screenshot before helping | Service appears contingent on public praise | Correct the support instruction |
| Reminder audience | Only positive reviewers receive access reminders | Operational selection may reinforce pressure | Review against earned-award status instead |
These are fictional audit observations, not allegations about a particular review application. Their purpose is to show that pressure can arise from workflow design as well as explicit offer text.
Inspect how a shopper could decline the review request. If the next step for an earned award becomes hidden or unavailable, an “optional” label is not doing enough work. Also ask what happens to the customer who submits criticism. Their access and service path should be evaluated under the approved purchase program rather than their review sentiment.
Check platform policies and required relationship disclosures
Identify where the review will appear. A merchant-hosted review page and an external review platform may apply different participation policies. Record the current policy URL, the proposed activity and the person who checked the fit. Do not assume that a sentiment-neutral incentive is permitted simply because it avoids a positive-rating condition.
The FTC guidance also distinguishes the rule from disclosure obligations that can arise under the FTC Act. Keep the disclosure question in the audit, but do not treat a disclosure as a universal cure. The reviewer needs to understand the actual relationship, the incentive being offered and the intended publication context before approving the request.
For the fictional store, the $15 benefit belongs to the purchase campaign, not to a new arrangement paying for a review. The audit should document that fact and check whether the review request creates a misleading connection. If the merchant also proposes a separate incentive for feedback, that proposal needs its own review and must not be smuggled into the earned-benefit workflow.
Use an evidence record that distinguishes three items: what the customer was promised, what the review request now asks for and what the destination platform permits. A statement that “the app allows this template” answers none of those questions conclusively. Software configuration and permission under applicable rules are different matters.
A difficult case is a partner agency reusing a template across several merchants. One retailer may have approved a purchase-only reward while the agency’s template assumes a review-linked benefit. Require the agency to identify the exact approved offer version and review destination. A shared template should not silently establish a new condition for every program that uses it.
Remove pressure without changing earned purchase benefits
Correct the defective solicitation and preserve the purchase history needed to answer affected customers. Stopping the review automation is not a decision to cancel rewards that were earned under the original offer. Keep those workstreams separate, with named owners and records of the correction.
For the fictional store, the corrective action has three parts. Marketing withdraws the five-star message and checks the other placements. Operations confirms that access decisions use the published purchase criteria. Support receives a clear explanation that customers do not need to supply a favorable-review screenshot to obtain help with an earned reward.
An affected customer may reasonably ask whether a negative review caused a delay. The support team should inspect the actual award state and explain the applicable next step. It should not ask the customer to edit or remove criticism as the price of investigating the issue. Preserve the relevant conversation so the team can identify whether the flawed instruction was used elsewhere.
Test the corrected journey with two fictional customers who made equivalent qualifying purchases: one leaves no review and one leaves critical feedback. Compare the information and access each receives. This is a process check, not a fabricated customer experiment or a claim that their award outcomes must always match regardless of other legitimate facts.
Close the audit only when the offer, messages, interface and staff instructions tell the same story. Record which templates changed, which audiences were affected and who confirmed the corrected behavior. That evidence makes the separation durable when a different campaign or agency later reuses the journey.
A purchase reward should remain understandable as a purchase reward. A request for feedback should remain a request that can be evaluated honestly, without hidden pressure over a benefit the shopper was already promised.
Discuss purchase-based eligibility for a rebate program with clearly defined customer conditions.
Source references
This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.
