Release 1.16.5 · Customer reviews you can moderate, newsletter signups you can keep, and clearer contact navigation

Shoppers can leave product reviews on the storefront, but nothing goes public until your team approves it. That keeps low-quality or abusive content out of your catalog pages while still letting you collect honest feedback you can publish when it helps conversion.

The dashboard adds a dedicated queue for pending reviews, with actions wired through server code so moderation stays permission-aware and tied to the right organization. Product pages surface a lightweight teaser that links operators to the workflow, and brand settings include policy controls so each brand can align wording and rules with how you want reviews to work.

Behind the scenes, reviews are stored in a first-class database table with status, moderation audit fields, and indexes that match the common queries: newest pending work for a team, and approved content for a product detail surface. A follow-up migration tightens duplicate protection for reviewer email so repeated submissions are harder to abuse.

Newsletter signups become durable: the shared API contract and persistence layer capture signups in a dedicated table so you can grow your list without losing submissions that only lived in a transient integration path. Footer newsletter UI and related utilities are updated so the storefront experience matches the new backend shape.

Storefront navigation labels for contact are seeded across supported locales via translation defaults, so the contact entry in common navigation reads consistently whether the shopper speaks English, Swedish, Norwegian, Danish, Finnish, German, Italian, or the other locales included in the migration. This is deliberately scoped to the label; the underlying contact route remains stable.

Documentation in the internal architecture library explains the end-to-end product review flow, how storefront kits call the new routes, and how moderation fits into the broader commerce surfaces. That should shorten onboarding time for engineers validating behavior across the template app, the production storefront app, and the dashboard.

If you operate multiple brands under one organization, the org-level queue remains the operational home for review work, while brand-level configuration continues to be the right place for customer-facing policy text and toggles that shape what shoppers see before they submit a review.