Skip to main content
If you use storekit’s built-in feedback requests, each step of the review is also sent to Klaviyo. That lets you send the review request from Klaviyo instead of storekit’s email, thank happy customers, recover unhappy ones, and segment on how people rate specific dishes.

​
Turn On Feedback

Review events depend on the store’s feedback settings, which are separate from the Klaviyo page.
1

Open feedback settings

Go to Stores → your store → Settings → Feedback.
2

Enable feedback

Turn on Enable feedback. Set Notification delay to how long after the order’s estimated ready time the request should go out (the default is 60 minutes).
3

Decide who is asked

Leave Opt-in only off to ask every customer with an email address, or turn it on to ask only customers who ticked the marketing opt-in at checkout.
storekit always sends its own review request email (and a push notification to app users) when feedback is enabled; there is no setting to turn that email off while keeping the Klaviyo event. If you also send a request from Klaviyo, the customer receives two — see Send the review request from Klaviyo below.

​
The Review Lifecycle

The 4-star threshold for positive versus negative is fixed; it cannot be changed in the dashboard. Every review event carries ReviewId, OrderId, OrderCode, Currency, VenueName and VenueSlug. Full property lists are in the Event Reference.

​
Profile properties

Alongside the events, storekit updates three custom properties on the customer’s profile so you can segment without querying event history: Only customers who gave an email at checkout receive review events. A customer is asked at most once per store in any 24-hour period, so a second order the same day does not produce a second Review Requested. Partial or abandoned review forms are not sent; the review must be completed.

​
Send the Review Request From Klaviyo

Build a flow triggered by Review Requested that sends your own email or SMS, and use {{ event.ReviewUrl }} as the button link. The link opens the storekit review form for that order, already tied to the customer, so the review still flows back into storekit and Klaviyo. Because storekit’s own request email cannot be switched off, use this for a follow-up rather than a duplicate: for example, a time delay of one day, then a conditional split on Review Submitted since the trigger, and send the Klaviyo reminder only to customers who have not reviewed.

​
Flows Worth Building

  • Thank positive reviewers — trigger on Positive Review Submitted, send a thank-you with a link to leave a public Google review or a reorder incentive.
  • Recover negative reviews — trigger on Negative Review Submitted, notify your team (Klaviyo can send an internal notification) and send the customer an apology with a voucher. Include {{ event.ReviewContent }} in the internal email so the team sees the comment.
  • Dish-level follow-up — trigger on Reviewed Product with a filter Rating is less than 3, and use {{ event.ProductName }} and {{ event.Reasons }} to act on a specific dish.
  • Segment lapsed reviewers — a segment of profiles where StoreKit Last Review Rating is 5 and Placed Order count is at least 3 gives you your advocates.
Worked examples with property names are on Flows to Build.

Customer Feedback

How storekit’s feedback requests and review form work

Event Reference

Every property on the review events