> For the complete documentation index, see [llms.txt](https://hollow-peak.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hollow-peak.gitbook.io/docs/store/reviews.md).

# Reviews

Verified-purchaser reviews and moderation.

**Store → Reviews**

## Who can review

{% hint style="info" %}
**Only customers who actually bought the product.** Not visitors, not people with an account who browsed it — the platform checks for a paid, fulfilled order containing that product before the form is even offered.

That check happens again on submission. Hiding a form has never stopped anybody posting to it.
{% endhint %}

One review per customer per product. Editing an existing review is allowed; adding a second is not.

## Moderation

Reviews arrive **pending** and are invisible until approved.

| Action      | Effect                                   |
| ----------- | ---------------------------------------- |
| **Approve** | Published, and counted toward the rating |
| **Reject**  | Hidden, and not counted                  |

Only approved reviews affect the average rating, so a pending or rejected review cannot move it.

## The verified badge

Approved reviews carry a **verified purchase** badge.

If the order is later refunded, the badge is withdrawn while the review remains. A refund does not silence a customer, but a refunded purchase should not vouch for a product.

## Displaying them

Reviews appear on the product page automatically. Two blocks put them elsewhere:

**Product reviews** — one product's reviews with a rating breakdown.

**Review showcase** — your best approved reviews anywhere, filtered by minimum rating.

## Switching them off

Site Management → Features → Reviews. Existing reviews are hidden, not deleted.

## Good practice

* Approve promptly; a review sitting pending for a week is a customer who thinks you ignored them
* Publish critical reviews. A product with only five-star reviews reads as filtered
* Reject abuse and spam, not disagreement


---

# 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://hollow-peak.gitbook.io/docs/store/reviews.md?ask=<question>&goal=<user_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.
