Retail Review Management: Store Reviews, Product Reviews and the FTC Rule That Now Covers Both

Retail review management is usually described as a store problem: dozens of Google profiles, dozens of managers, one brand voice to keep consistent. That is half of it. A retailer also collects reviews on its own product pages, and often in a shopping app on the App Store and Google Play, and since the Federal Trade Commission’s rule on consumer reviews took effect, the way a retailer asks for, filters and displays reviews in every one of those places is governed by the same federal text. This guide covers both halves: the rules first, because they decide what the workflow is allowed to do, then the store-level operation that makes replies fast without making them risky.

What retail review management covers that other industries do not

A restaurant or a dental practice has one kind of review: a customer describing a visit. A retailer has at least three, and they behave differently. Store reviews on each Google Business Profile describe staff, queues, stock and returns at one address. Product reviews on the retailer’s own site describe the thing that was bought, wherever it was bought. App reviews on the App Store and Google Play describe the shopping app, its checkout and its delivery tracking.

Each has a different owner inside the business. Store reviews belong to store and district operations. Product reviews belong to ecommerce and merchandising. App reviews belong to whoever ships the app. The most common failure in retail review management is not a bad reply, it is a review that nobody owns, because it arrived on a surface that sits between two teams.

• Store reviews. Google profiles per location. Themes are staff helpfulness, wait times, stock availability, returns and parking. Owner: store manager, escalating to district.
• Product reviews. Your own site, usually through a review widget. Themes are fit, quality, sizing, damage in transit. Owner: ecommerce. These are first-party reviews, and you control what is displayed, which is exactly why the FTC cares about them.
• App reviews. App Store and Google Play. Themes are checkout failures, login problems and delivery tracking. Owner: the app team, with customer service for anything about an order.

The FTC rule now governs how retailers collect and show reviews

On 14 August 2024 the FTC announced a final rule banning fake reviews and testimonials, approved 5-0, which lets the agency “seek civil penalties against knowing violators”. The rule is codified at 16 CFR Part 465, read on 30 September 2026. Its definition of a consumer review covers an evaluation “of a product, service, or business” published to “a website or platform dedicated in whole or in part to receiving and displaying such evaluations”. That is a store’s Google profile and a product page’s review widget alike.

Four sections matter to a retailer day to day. Section 465.4 bans buying reviews of a particular sentiment: it is a violation “for a business to provide compensation or other incentives in exchange for, or conditioned expressly or by implication on, the writing or creation of consumer reviews expressing a particular sentiment, whether positive or negative”. Section 465.5 bans reviews written by an “officer or manager” of the business without a clear disclosure of that relationship, which is the store manager who leaves a five-star review of their own store. Section 465.7(a) bans groundless legal threats, physical threats and intimidation used to stop or remove a review. And section 465.7(b) bans the practice that caught a retailer before the rule even existed.

“According to the FTC’s complaint, Fashion Nova used a third-party online product review management interface to automatically post four- and five-star reviews to its website and hold lower-starred reviews for the company’s approval.”

— Federal Trade Commission, press release, 25 January 2022

The Fashion Nova settlement cost the retailer $4.2 million, and the FTC described it as “the FTC’s first involving a company’s efforts to conceal negative customer reviews”. The complaint said that from late 2015 until November 2019 the company never approved or posted “the hundreds of thousands of lower-starred, more negative reviews”. The FTC also wrote to 10 companies offering review management services, putting them on notice that avoiding the collection or publication of negative reviews violates the FTC Act.

Section 465.7(b) turns that case into a standing rule. A business may not misrepresent that the reviews displayed on its site “represent most or all the reviews submitted” when reviews “are being suppressed (i.e., not displayable) based upon their ratings or their negative sentiment”. The rule is also clear about what is not suppression: withholding reviews on criteria “applied equally to all reviews submitted without regard to sentiment”, such as reviews containing abusive or obscene content, another person’s personal information, content that is “clearly false or misleading”, reviews the seller reasonably believes are fake, and reviews “wholly unrelated to the products or services” offered. A moderation queue is allowed. A moderation queue that only ever releases four and five stars is the Fashion Nova pattern.

Where the FTC rule and Google’s policy disagree, and which one wins

The two rulebooks overlap, and the gap between them is where retail loyalty programmes get into trouble. The FTC rule bans incentives tied to a particular sentiment. Google’s prohibited and restricted content policy, read on 30 September 2026, goes further on its own platform and forbids merchants to “Offer incentives – such as payment, discounts, free goods and/or services - in exchange for posting any review”. Ten percent off your next visit for any honest review is not a sentiment-conditioned incentive under section 465.4. It is still a breach of Google’s policy on a Google profile.

The practical rule is short. On Google, ask every customer and reward nobody. On your own site, publish every review that passes a moderation rule you would be happy to read aloud, and apply that rule without looking at the stars. Asking only the customers who looked pleased is review gating, and Google names it outright.

The same reasoning applies when a retailer embeds its Google reviews on product or store pages. Choosing which reviews to show is a display decision, and a carousel labelled as what customers say that only ever shows five stars invites exactly the reading section 465.7(b) is aimed at. The mechanics of embedding, and the honest ways to select, are in embedding Google reviews on your website.

Store reviews: who replies, who escalates, and how fast

With the rules settled, store reviews are an operations problem. A regional chain with forty stores receives reviews every day, and the store manager is the only person who knows whether the Saturday queue was really forty minutes. The manager should draft. The district should see everything and step in only on the reviews that carry risk. That split is the core of multi-location review management, and retail is its purest case.

1. Assign every store profile to a named manager and a named deputy. A profile with no owner during a manager’s holiday is how a week of reviews goes unanswered.
2. Write a complaint taxonomy with retail categories: staff, wait time, stock availability, returns and refunds, pricing at the till, cleanliness, parking. Tag every review with one.
3. Set escalation triggers that move a review from the store to the district automatically: any mention of injury, discrimination, theft accusations, a refund dispute over a set amount, or a threat of legal action. The escalation matrix playbook covers how to write these without flooding the district.
4. Set a publish target by severity rather than one clock for everything. The response time SLA playbook sets out targets that survive a Saturday.
5. Give managers two or three approved openings per category and let them finish the reply with the store detail. Consistency comes from the opening and the offline route, not from identical paragraphs.

One retail-specific rule for the reply itself: never argue stock or pricing in public. A reviewer who says an item was out of stock three times is describing a replenishment problem, and a reply that insists the item was on the shelf is a reply the next hundred readers will judge the store on. Acknowledge, say what the store is checking, and give a named person to ask for.

Review generation that stays inside both rulebooks

The fastest honest way to more store reviews is to ask everyone, at the moment the experience is freshest, without any reward. For retail that means the receipt, the order confirmation email for click-and-collect, and a short follow-up after delivery. A receipt QR code that points to the store’s own review link converts at the till; the setup is in the Google review link and QR code guide.

Email is the scalable channel for retailers with a customer list, and it is also where review gating creeps in, because it is easy to send the request only to customers who rated a survey highly. Send it to every eligible order. The mechanics of timing, suppression lists and follow-ups are in the review request email campaign playbook, and ReviewMankey’s email campaigns send the same request to every eligible customer rather than a filtered list.

Staff incentives deserve a separate sentence because they are common in retail. Rewarding a store team for the number of reviews collected is a different thing from rewarding customers, but it creates pressure to review on a customer’s behalf, or to ask a friend. Section 465.5 and Google’s conflict of interest clause both land on that outcome. If you run a staff incentive, tie it to response quality and time, which staff control, not to review count.

The retail app is a third review surface

Most retailers with a loyalty programme run an app, and its store listing collects ratings that shoppers see before they install. App reviews are rarely about the app alone: a one-star review about a missing order is a customer service case that happened to arrive through Google Play. Route those to the same queue as store complaints about orders, and reply as the retailer rather than as the development team.

The reply mechanics on the App Store and Google Play differ from Google profiles, including how edits and updated ratings work. The App Store review response workflow covers them. The point for a retailer is only that the app is not a separate reputation. A shopper deciding between two chains sees the store rating, the product ratings and the app rating as one brand.

What to count, per store and per district

Average star rating is the slowest number a retailer has. These move sooner and point at something a district manager can change.

• Response rate and time to publish by store. The district view should rank stores, because the slowest two usually account for most of the gap.
• Review velocity by store. New reviews a month. Falling review velocity at one store while the district holds steady usually means the request stopped being made at that till.
• Top three complaint categories by store. Stock availability clustering in one district is a supply problem, not a reputation problem.
• Escalation rate. The share of reviews that moved to district. Rising means either the stores are having worse weeks or the triggers are too sensitive.
• Product reviews withheld, and why. For the ecommerce team, a monthly count of withheld reviews by reason is the evidence that moderation is rule-based rather than rating-based.

For context when presenting to leadership, the review management statistics page collects the published consumer research with each figure attributed to its source. Google’s own guidance on how local results are ranked, read on 30 September 2026, states that “More reviews and positive ratings can help your business’s local ranking”, which is why store-level velocity is worth a line on the district report.

Retail review management done well is mostly plumbing: every store owned, every surface routed, one moderation rule for product reviews applied without looking at the stars, and a district view that ranks stores by the numbers they control. ReviewMankey brings store reviews on Google together with App Store and Google Play reviews in one queue, with drafting, assignment and approval built for exactly this store-to-district shape. The retail review management use case shows how the pieces fit for a store network.