The Review requests dashboard (or Requests History dashboard) helps you monitor the performance of your review requests and quickly troubleshoot any issues. Review requests will appear in the dashboard once the related order has been fulfilled.

To access the Review requests dashboard:

Use the Product view and Order view buttons at the top-right of the page to change how the review requests appear on your dashboard.
​

Your choice is remembered in your browser and in the page link. Switching views keeps your search and filters.

A card at the top of the page that summarizes your review requests for a date range you pick, separate from the table below it. Changing this card's date range doesn't filter the table, and filtering the table doesn't change this card.

Range options: Today, Last 7 days, Last 30 days, Last 90 days (default), Last 12 months, Custom.

The card shows 5 tiles (in Order view, the first tile is titled "Orders" and counts orders instead of products — everything else works the same):

Pending + Sent + Not sent always add up to your total (Product line items). Reviews collected is the exception — it's a separate count layered on top, not a slice of the same total.
​

Two more things you'll see on the card:

If the whole card fails to load, you'll see "Could not load metrics" with a Reload button.

By default, the Review requests dashboard shows the most recent requests first, sorted by the fulfilled date (shown in the Date column).

To change the sort order in the Review requests dashboard:

Sorting is available in Product view only — Order view always shows orders by fulfilled date.
​

To find a specific review requests:

If you're not part of the Early user program:

If you're part of the Early user program:

In Order view, a product match returns the orders containing that product.

To limit results in the Review requests dashboard to a specific date range:

To filter the requests by status to focus on requests that were sent, are scheduled to send, or were skipped:

If you're not part of the Early user program:

If you're part of the Early user program:

To immediately send a scheduled or skipped review request:

If you're not part of the Early user program:

If you're part of the Early user program:

A notification ("Request sent") will appear at the bottom of the page. You can then refresh the page to see the updated status of this review request. It may be sent successfully or still marked as Skipped (if conditions prevent sending).

To skip a review request immediately:

To skip all requests for a customer:

This action will add this customer to the Emails blocklist, which will cancel this and all future requests to the customer.

To skip all requests for a product:

This action will cancel this and future requests to this product.

To skip all review requests that have not been sent:

To check the status of your sent review request emails:

Judge.me automatically skips review requests in the following situations to ensure relevance and avoid over-emailing:

The Review requests dashboard shows the current status of each review request so you can track what has been sent, what’s scheduled, and what needs attention.

To see the status of your review requests:

A review request is skipped and marked as "already reviewed" if the customer already left a review for the same product in a different order.

As each customer can only review a product once, if you want them to update their review, you can use the Ask customer to update review action instead.

A review request is skipped and marked as "another variant in the order" if we've already scheduled a request for a different variant of the same product in the order.

If you still want to send this request, you can use the Send request now action.

A review request is skipped and marked as "cannot process Custom line item" when the customer bought a customized version of the original product (e.g. a necklace engraved with their name).

Because the custom item isn’t linked to a specific product page, we cannot match it to a reviewable product and you can’t use Send request now for these cases.

To collect reviews for custom line items, you can manually schedule review requests that point to the original product the customization is based on.

In both cases, be sure to enter the product URL of the original, non-customized product so the review can be correctly attributed.

A review request is skipped and marked as "Email does not accept marketing" if the "Send review requests to customers who have opted out of Shopify marketing emails" setting is disabled and the customer did not subscribe to marketing emails at checkout.

Requests with the “no email found” status cannot be resent with the Send request now action — if you try, you'll encounter the same status.

A review request is skipped and marked as "Email failed to deliver" if:

Review requests are marked as "Event sent to Klaviyo" when you enable "Send trigger when it’s time to send a review request".

This status doesn’t confirm whether the email was sent or delivered by Klaviyo, only that the event was sent successfully from Judge.me.

A review request is skipped and marked as "hard bounce or spam complaint" in these cases:

In either case, our email provider (Postmark) blocks future emails to protect your sender reputation and Judge.me will automatically skip sending new requests to that address.

While we can attempt to reactivate the email address upon request, we generally recommend guiding the customer to leave a review directly on your product page instead.

A review request is skipped and marked as "line item per order exceeded" when the number of products in the order has passed the limit you've set for sending review requests.

For example, if the Collect reviews for this many items per order setting is set to 3 and the order has 5 products:

To avoid this, you can increase the number of review requests to send out for each order.

A review request will be skipped with the status "no email found" if there are no email address or phone number when the order was created (e.g. the customer added their email after checkout).

Requests with the “no email found” status cannot be resent with the Send request now action — if you try, you'll encounter the same error.

Instead, you can manually add a new request to reach out to the customer:

A review request with this status "no engagement in the previous request" is a reminder request. It is skipped if neither the initial review request nor the previous reminder email was opened by the customer. In this case, no further reminders will be sent. This helps prevent over-emailing disengaged recipients.

As this is the expected behavior designed to respect customer engagement levels, no action further action is needed when you see this status.

A review request is skipped and marked as "product not in store" when:

To send review requests for out-of-store products:

A review request is skipped and marked as "request sent for another order recently" if we already sent a review request to the same customer in the last 7 days.

If you still want to send this request, you can use the Send request now action to do so manually.

When the "Send requests for domestic orders" setting is disabled:

If you re-enable the "Send requests for domestic orders" setting:

If you only want to resend one request with the "Review request is disabled for domestic order" status, use the Send request now action.

When the "Send requests for international orders" setting is disabled:

If you re-enable the "Send requests for international orders" setting:

If you only want to resend one request with the "Review request is disabled for international order" status, use the Send request now action.

A review request is skipped and marked as "reviewer's email is in blacklist" if the customer’s email address was added to your Emails blocklist.

If you still want to send the request, remove the customer’s email address from the blocklist first, then use the Send request now action to resend the request.

A review request will be skipped and marked as "unsubscribed email" if the customer has previously clicked Unsubscribe in another review request.

Requests with this status cannot be resent with the Send request now action — if you try, you'll encounter the same error.

To see all customers who unsubscribed from your review requests:

A review request is marked as Waiting for delivery when it's set to send after the order is delivered. This applies whether the request was scheduled under the Delivered order trigger, through the AfterShip integration, or under our older delivery-based scheduling (used before order triggers were introduced).

The request isn't scheduled to send yet — it's waiting for Shopify to confirm that the order was delivered. Once we receive that delivery update, the request is scheduled and the status changes to Will send on.

A request stays in Waiting for delivery while we're still waiting for that delivery confirmation. It gets stuck there indefinitely when the confirmation never arrives — the carrier or tracking app doesn't report it, the tracking details are delayed, or the order is never marked as delivered.

A request can be on this delivery-based schedule for two reasons:

In both cases, the request stays in Waiting for delivery only because the delivery confirmation hasn't come through — not because of the trigger setting itself.

To send a request that's waiting for delivery right away:

If you're not part of the Early user program:

If you're part of the Early user program:

Force-sending a request this way skips its normal reminder cycle, so no reminders will be sent for it.

A review request shows this status right after it's created, before Judge.me has evaluated whether to send or skip it. You'll see it briefly:

This status doesn't last long — Judge.me evaluates the request shortly after and moves it to its real status (e.g. Will send, Skipped, or Waiting for delivery). If a request seems stuck on Will be processed, refresh the page — it's likely already moved on and the dashboard just hasn't updated yet.