
Yes, you can publish customer questions and answers on your Shopify product pages, and in most cases simply asking the customer and getting a clear yes is enough. The line that matters is reuse: once you take that Q&A beyond the product page, into ads, email, or social posts, you need separate, explicit permission. The compliance section below covers the legal nuance in full.
TL;DR:
- Product page approval does not cover reuse in ads, email, or social posts; obtain separate written consent that names channels, duration, and revocation method.
- Log each consent with the customer ID, order ID, and timestamp; third party content also needs a product ID to qualify for Shop channel display.
- Since October 21, 2024, FTC rules prohibit suppressing negative Q&A, faking or manipulating answers, and hiding incentives; disclose material connections clearly beside the content.
- Document edits, preserve the original context, and link moderation actions to the consent record; seek legal counsel for incentive programs or cross border campaigns.
Before any question or answer goes live on a product page, run it through a short gate. This keeps your records audit-ready and protects you if a customer later asks why their words appear somewhere they did not expect.
Shopify’s own guidance on user-generated content makes a similar distinction: always ask for explicit permission before repurposing customer content, and credit the person when you share it. Treating “publish on page” and “repurpose elsewhere” as two separate permissions, rather than one blanket agreement, is the single habit that prevents most disputes.
Three practical flows cover most stores, and none require custom development.
That third option matters more than it sounds. Shopify’s sync requirements state that partner-collected reviews need a Customer ID, Order ID, and Product ID before they are eligible to display in the Shop channel. Apps that skip this mapping will have content rejected, so building the ID link into your consent capture from day one saves rework.
Store the consent record itself in customer metafields, your app’s datastore, or a periodic CSV export, whichever your current stack supports. The format matters less than the link: every consent entry should point back to an order ID, because that is what turns a vague “they said it was fine” into a verifiable record if a customer disputes it months later. For store owners who want to add a widget without touching theme code, a step-by-step setup guide walks through placement options.
Pro Tip: Tie every consent record to an order ID from the start. Retrofitting that link after a dispute is far harder than capturing it at checkout.
You do not need a lawyer to write a usable consent line. A few short, honest sentences cover most situations.
The FTC’s Consumer Reviews and Testimonials Rule, effective October 21, 2024, requires that disclosures about material connections be clear and conspicuous, not hidden behind extra clicks or vague language. A disclosure that a shopper has to hunt for does not count as a disclosure. Keep the wording plain enough that a first-time visitor understands the relationship in one glance.
A few rules do most of the work in keeping your Q&A program defensible.
Moderation and consent are often treated as separate tasks, but they are really one record. A Q&A you edited for clarity, without noting what changed, is harder to defend than one you left untouched, even if the edit was harmless.

Most guidance on this topic treats consent as a legal formality, a box to check once and forget. That framing misses the actual risk. The real exposure is not the missing checkbox, it is the gap between what a customer agreed to and what you later did with their words. A shopper who said yes to a product-page question showing up in a retargeting ad six months later did not actually consent to that, even if your form technically covered it in fine print.
The fix is not more legal language. It is narrower, plainer permission requests asked closer to the moment of use. Ask for product-page publishing at the time of purchase. Ask again, specifically, before you ever move content into ads or email. That second ask feels like extra friction, but it is the one step that keeps your Q&A program honest rather than just technically compliant. Store owners who skip it are not saving time, they are deferring a harder conversation to whenever a customer notices and objects.
— Leo
Running consent checks by hand across spreadsheets and email threads gets harder the more Q&A you publish, which is the exact problem we built Peers to solve. Our widget embeds verified shopper Q&A and post-purchase video reviews directly on your product pages, with every submission tied to a real order rather than an anonymous form entry.

If you want to see the Q&A and video review flow before installing anything, our demo store shows the shopper-facing side end to end. When you are ready to add it to your own store, install Peers from the Shopify App Store and start capturing verified consent on your next order.
Yes, you generally need some form of explicit permission, even if it is as simple as a checkbox agreeing to have the answer shown on the product page. Shopify’s own guidance on user-generated content recommends asking before you publish or reuse anything a customer wrote.
You need separate, explicit consent any time you move a Q&A beyond the product page, such as into email campaigns, paid ads, or social posts. Product-page permission does not automatically cover those other channels under Shopify’s repurposing guidance.
The FTC’s Consumer Reviews and Testimonials Rule, effective since October 2024, prohibits suppressing negative content, faking reviews, and hiding material connections like discounts given in exchange for an answer. Disclosures about those connections must be clear and placed where shoppers will actually see them.
Store each consent event with the customer ID, order ID, and a timestamp, whether in customer metafields, your app’s datastore, or an exported file. Tying consent to the order ID matters because Shopify’s sync requirements for partner apps already require verified order and customer identifiers before content can display in the Shop channel.
Yes, apps built for this purpose can tie consent directly to verified orders and keep moderation logs in one place, which reduces manual audit work. Peers, for example, embeds verified post-purchase Q&A and video reviews on product pages with order-level verification built in.