Product Reviews: Must Customers Leave Stars, Written Feedback or Both?
Decide whether a product review needs a star score, written feedback or both before adding the form to your shop. A missing rating is not a low rating, and a written-review count need not be the same as the number of ratings. The product page should explain the information it actually has.
This guide concerns the review data and its public summary on your own shop. It does not determine legal verification duties, approve review-request marketing or describe reviews on Google or an app store. Have the applicable policy and legal requirements reviewed separately.
Specify the permitted combinations
Write down whether a customer can submit stars without text, text without stars, or only a combined contribution. Then show what happens when they leave everything empty. Do not silently turn an untouched star control into a score merely to satisfy a required database field.
The WooCommerce product-review documentation distinguishes enabling star ratings from requiring them. It also describes a separate order-review page under a feature labelled beta: for each product the customer chooses to review there, stars are required while written text is optional. Do not assume the standard product form and that order-specific route have identical rules.
For your implementation, test every route customers will actually use. A helpful requirement is that the confirmation and the resulting product page agree about what was submitted, without manufacturing a written review from a rating alone.
Explain the numbers beside the product
Ask the developer to define the population behind the displayed average and count. Does it include only published star ratings? What happens to a text-only contribution? Does an unpublished contribution change the summary? These are requirements to agree and demonstrate, not calculations established by the cited WooCommerce settings.
Keep missing scores outside any numeric calculation unless an explicitly justified alternative is approved. A text-only comment should not become a zero-star judgment. If the interface shows both “ratings” and “written reviews”, use labels reflecting their actual populations rather than displaying different numbers under the same name.
A hypothetical shop might allow stars without text. Its page could therefore have more ratings than written reviews without either number being wrong. The problem is an unexplained label, not necessarily a missing comment.
Keep replies and changes understandable
An owner's reply is a response, not another customer rating. WooCommerce documents replies grouped with the original review. Agree how your display distinguishes the two so a conversation does not look like several independent product opinions.
Decide what happens when a customer is allowed to revise a rating or add text later. Must the revised contribution be reviewed again? Which version contributes to the public summary while that happens? Preserve the agreed relationship rather than accidentally counting an edit as another reviewer.
Where approval is required, tell the author the contribution is pending. The documented beta WooCommerce order-review route explicitly provides that pending state under manual moderation; it does not promise instant public appearance.
Demonstrate the form and summary together
Use fictional contributions: stars only, text only if allowed, neither, a pending entry, an approved entry, an owner reply and an authorised revision. Inspect the form, the author's receipt and the signed-out public summary after each permitted transition. No fabricated ratings should be posted to a real shop for testing.
Record the chosen combinations and counting rules in your acceptance criteria before commissioning the shop. A review feature is ready when readers can understand its evidence, not merely when a row of stars looks complete.