> ## Documentation Index
> Fetch the complete documentation index at: https://varaahi.vritservicespro.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Product reviews

> Render real review metafields in a cinematic layout — rating summary, individual reviews, and verified-buyer badges.

# Product reviews

The Product Reviews section reads your review data from product metafields and renders
it in a layout designed to be looked at, not skimmed.

![Product reviews section](https://mintlify.s3.us-west-1.amazonaws.com/vr-it-services-pro-c6bfa2fc/images/placeholder/section-product-reviews.png)

Product reviews with a rating summary and review cards

***

## Setup

VARAHI reads review data from **product metafields**, so you need a review app that
writes to metafields.

| Metafield | Type | Used for |
| - | - | - |
| `reviews.rating` | Rating | The average score and star display |
| `reviews.rating_count` | Number | The review count |
| `reviews.content` | Rich text | The body of an individual review |
| `reviews.author` | Single line text | Reviewer name |
| `reviews.created_at` | Date | When the review was written |

> [!NOTE]
>
> The most common Shopify review apps that write to these namespaces are **Judge.me**
> and **Loox**. If you use a different app, tell us the metafield names and we will
> add support — the rendering layer does not care where the data comes from.

***

## Which product's reviews?

The section uses, in order of priority:

1. The **current product**, when the section is on a product page
2. The **Product handle** setting, for the homepage
3. The **first product in the store**, as a final fallback

> [!WARNING]
>
> Because of that fallback chain, deleting the product you pointed the homepage
> reviews at will silently switch the homepage to reviewing a different product. If
> your homepage reviews matter, re-point the setting after any product deletion.

***

## What it renders

| Element | Source |
| - | - |
| Average score | `reviews.rating` |
| Star display | `reviews.rating` |
| Review count | `reviews.rating_count` |
| Individual review cards | `reviews.content`, `reviews.author`, `reviews.created_at` |
| Verified badge | Rendered when the review carries a verified-purchase flag |

> [!NOTE]
>
> If your review app stores the verified flag in a different metafield, the badge will
> not appear. The theme renders it when `reviews.verified` is truthy; otherwise it
> renders nothing rather than an empty badge.

***

## The empty state

When a product has no reviews, the section renders a considered empty state rather than
disappearing — a heading, a line of copy, and a muted placeholder. This is deliberate:
a missing section shifts the page layout, and a visible but honest empty state reads
as "no reviews yet" rather than "something is broken".

> [!TIP]
>
> Do not seed fake reviews to fill the space. Every major marketplace treats seeded
> reviews as a policy violation, and it is a fast way to get a store delisted.

***

## Best practice

> **Put reviews on the homepage and the product page**
>
> Social proof above the fold reduces hesitation; social proof next to the buy box
> closes the deal. Having it in both places is the single most common high-impact
> arrangement.

> **Match the review app's styling**
>
> VARAHI's review cards are minimal by design. If your app also injects its own
> review markup, disable the app's frontend output and let the theme render.

> **Keep the count accurate**
>
> The review count is the number shoppers trust. If your app's metafield is stale
> relative to the app's own count, fix the metafield — a mismatched count reads as
> manipulation.

***

> **[Main product](https://varaahi.vritservicespro.com/sections/main-product.md)**
>
> Where reviews sit next to the buy box.

> **[Feature overview](https://varaahi.vritservicespro.com/features/overview.md)**
>
> Every capability in one table.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.