They cannot be deleted or hidden. You can reject a review that breaks the rules (with a reason, logged), and if you enable mediation a very low review can be temporarily — and, if the author does not respond, permanently — excluded from the average. But it always stays publicly visible in a separate, clearly labelled „not counted in the score” section, and the profile shows how many there are. This is deliberate: hiding criticism would destroy the credibility of the ratings.

A verified review comes from a single-use link sent to the address on a specific order. A review from a public link or QR code does not get that label, because we cannot tell whether the author actually bought anything. Both are shown, but they are clearly distinguished.

Product ratings will — the product widget injects structured data, and ratings collected by an independent platform are accepted by Google. A company rating published on the company's own site is ignored by design, which is why we publish it in structured data on the ReviewBasis profile, where we are the third party.

Three days after the order date by default — late enough for the customer to have the product, early enough that they still remember buying it. You control the delay yourself, from zero to sixty days.

New invitations are not created, and the import tells you how many rows were rejected. Everything else — collected reviews, the profile, the widgets — keeps working unchanged. The limit resets at the start of the next month.

The script is small, has no dependencies and loads asynchronously. Widget data is cached, and rendering happens inside a shadow DOM, so it does not recalculate styles for the whole page.