> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/reviews/managing-reviews/review-rewards-and-limits/review-submission-limits.md). # Review submission limits Control how many reviews a customer can submit for the same product — per order (subscription-friendly) or per product (strict cap). By default, a customer who orders the same product on two separate orders can leave a review on each — useful for subscription customers, who repurchase frequently and may have new feedback every cycle. If you'd rather hold customers to one review per product ever, the **Review limit** setting lets you change that. This article covers the two review-submission limit options and how Roadmap decides whether a review is verified when there's no order ID in the URL. #### Where to find the setting In Roadmap, open **Reviews**, then **Settings**. Scroll to **Review limit** under the **Auto Publish** setting.

The Review limit section on the Reviews Settings page — radio choice between 'One review per product per order' (default) and 'One review per product'.

#### The two options | Option | What it means | | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **One review per product per order** (default) | A customer can leave one verified review for each order containing the product. Repeat-buyers and subscription customers can leave a new review each cycle. Unverified reviews across products the customer hasn't ordered are not capped. | | **One review per product** | A customer can submit one review per product across their entire history, regardless of how many times they've ordered it. Repurchasing the product does not let them review again. Unverified reviews are also capped at one per product. | Most stores leave it on the default — repurchase reviews give you fresher feedback and a higher review count over time. Switch to **One review per product** if you want a stricter cap, for example to avoid the appearance of a customer "padding" your reviews via repeat orders. #### How a review is marked verified A review is verified when Roadmap can tie it to an order containing the reviewed product. There are two paths to verification: * The review request link includes the order ID. Roadmap reads the order ID from the URL, confirms it contains the product, and marks the review verified. * The review came in without an order ID — for example, a customer used the PDP review block or a generic submission form. Roadmap then looks up the customer by email, scans their order history, and verifies if any order contains the reviewed product. If yes, the review is marked verified. If no order is found containing the product, the review stays unverified. This means a customer who buys from you via a subscription, then submits an organic review later without clicking the email link, still gets verified status — provided their email matches a real order. #### Duplicate submissions If a customer tries to submit a second verified review for the same product under **One review per product**, or for the same product+order combination under **One review per product per order**, the duplicate is rejected at submission time.\
#### How this interacts with rewards Both Roadmap rewards methods that fire on reviews — the loyalty points **Leave a verified review** method and the Discount Code Generator's **When review is published** trigger — have their own reward frequency settings, configured independently of this one. The **Review limit** setting decides whether the review can be submitted at all. The reward frequency settings decide whether a successfully submitted review earns its reward. The two are stacked: a customer first needs to clear the submission limit, then clear the reward frequency rule. See: * [Discount codes for reviews](/reviews/managing-reviews/review-rewards-and-limits/discount-codes-for-reviews.md) — frequency options on the Discount Code Generator's review trigger * [Loyalty points for reviews](/reviews/managing-reviews/review-rewards-and-limits/loyalty-points-for-reviews.md) — frequency options on the loyalty review-points method #### Common scenarios **"I sell subscriptions and want customers to be able to review each delivery"** Leave the setting on the default, **One review per product per order**. Each cycle creates a new order. Each new order unlocks one more verified review for the customer on that product. **"I'm a one-off purchase store and don't want repeat reviewers padding the count"** Switch to **One review per product**. Every customer is capped at one review per product across all their orders. **"Why did a customer's organic review get marked verified — I didn't send them a link?"** Because their email matches an order containing the product. Roadmap looks up the customer's order history at submission time to verify. This is intentional — it gives organic reviews proper verified status without needing every customer to come through your email flow. #### Frequently asked questions
If a customer is blocked from submitting a duplicate, do they get an error message? Yes — they're told they've already reviewed this product, and for the per-order variant, on this order. The submission isn't silently dropped.
Does changing the setting affect reviews that have already been submitted? No. The setting applies to new submissions only. Existing reviews stay where they are.
What's the difference between verified and unverified reviews? A verified review is one Roadmap could tie to a real order containing the reviewed product, either via the order ID in the link or via email lookup. An unverified review is one where no matching order was found — for example, a customer reviewing a product they haven't bought from you. Most stores choose to display the verified badge on storefront reviews so shoppers can tell them apart.
Can I let unverified reviews earn rewards too? For loyalty points, no — loyalty rewards always require purchase verification. For discount codes, you can enable rewards on unverified reviews via the **Every review (unverified and verified)** option on the Discount Code Generator. See [Discount codes for reviews](/reviews/managing-reviews/review-rewards-and-limits/discount-codes-for-reviews.md).
#### Related guides * [Discount codes for reviews](/reviews/managing-reviews/review-rewards-and-limits/discount-codes-for-reviews.md) * [Loyalty points for reviews](/reviews/managing-reviews/review-rewards-and-limits/loyalty-points-for-reviews.md) * [Review submitted but no points](/reviews/troubleshooting/review-submitted-but-no-points.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.roadmap.so/reviews/managing-reviews/review-rewards-and-limits/review-submission-limits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.