Request product reviews

This page helps you pull the orders that are eligible for Amazon’s Request a Review from your shipped orders, and build a send list. Review count and rating feed directly into conversion, so not missing eligible orders matters. Sending itself happens only after you review the list and approve it.

About this page

Item	Detail
What you can do here	Pull review-request candidates from shipped orders, confirm eligibility one order at a time, and build a prioritized send list
Scope	Amazon orders (shipped). No advertising data is used
Data / connection required	A connected Picaro account (MCP connection)
Extent of execution	Extraction and confirmation only. Sending happens after approval. No advertising settings are changed

There is a cap on how many candidates you can pull at once

Review-request candidates come back with a per-call cap. Above the cap you get the count only, not the list. Candidates cluster toward the longer end of days-since-shipment, so even splitting the range one day at a time can exceed the cap.

That means you often cannot say “this is all of them”. The prompt always reports how many were retrieved and how many were not, so decide based on those numbers. Do not read a result of 0 as “no eligible orders”.

Terms used on this page

• Candidate — an order that matches the days-since-shipment window. Being listed here does not guarantee it can actually be sent.
• Eligibility — the per-order answer from Amazon. Use this, not the candidate list, to decide what goes on the send list.
• Request status — whether a request has already been sent for that order. An empty value means “unknown”, which is not the same as “not sent”.

When to use this

• You want reviews on a new product to build up quickly
• You want to improve conversion on products with few reviews
• You want to check periodically that nothing is being missed

Before you run

• Sending happens after approval — this prompt only builds the send list. It does not send mail.
• No buyer personal data is handled — email addresses and the like are neither retrieved nor displayed.
• Do not send twice — repeated requests on the same order hurt the buyer experience. Always check request status.

Prompt quick reference

What you want to do	What you get	Changes	Prompt
Find the orders you can request reviews for	A candidate list with eligibility, plus disclosure of what was retrieved	No change (extract and confirm only)	Prompt 1

---

Prompt 1: Pull review-request candidates and build a send list

Pulls review-request candidates from shipped orders, confirms eligibility one order at a time, and builds a prioritized send list.

When to use — when you want reviews on a new product, or to periodically check that nothing is being missed.

What you need first — the target account. The days-since-shipment range and the ASINs you want to prioritize are optional.

Check review-request candidates and build a list of orders to send to.
Do not send anything until I approve it.

[State the constraints up front]
- The candidate list has a per-call cap. Above the cap it returns the count only and stops.
- You will filter by days since shipment (<lower bound>-<upper bound>), but candidates cluster
  toward the longer end, so even one day at a time can exceed the cap.
- So you may not be able to enumerate everything. In that case, say explicitly that this is
  "what could be retrieved", and do not write "none found" or "this is all of them".

[Steps]
1. Pull candidates one day at a time. For each day, table
   "candidate count / retrieved count / whether the cap was exceeded".
   For a day that exceeded the cap, record the count only and move on.
2. If you pull the whole range at once, on completion always state
   "windows processed / succeeded / failed / rows retrieved" and the failure reasons.
   If even one failed, it is a partial result. Do not treat it as complete.
3. For the candidates you did retrieve, confirm eligibility one order at a time before sending.
   Being on the list does not mean it can be sent. Put the result (and the reason) on each row.
4. To avoid sending twice, always check the request status on the order list, and distinguish
   "empty (unknown)" from "already requested".

[Priority]
Order the orders confirmed as sendable by:
1. Orders containing <ASINs to prioritize>
2. Order value, descending
If no priority ASINs are given, sort by order value only and say so.

[Output]
- Header: period covered, retrieved count, not-retrieved count (and why), coverage
- List: order ID / ship date / days elapsed / ASIN / product name / quantity / value / eligibility / request status
- The number you recommend sending to, and why

[Guardrail]
- Do not send mail until I approve it.
- Do not handle buyer personal data (email addresses etc.). Do not retrieve it either.
- Exclude orders whose eligibility could not be confirmed from the recommendation, and list them
  separately as "could not confirm".

What you can change — the lower/upper bound on days since shipment, the ASINs to prioritize, the sort order.

What comes back — disclosure of what was retrieved (period, retrieved count, missing count, coverage) and a candidate list with eligibility. The recommended number to send to, with reasoning, is attached.

Changes — none (extract and confirm only). No mail is sent.

Next steps — review the list and approve it to send. After sending, watch the review count and rating on the target ASINs to decide whether to continue.

Related categories

• Manage inventory & sales opportunities — a review request on an out-of-stock product will not convert
• Analyze Subscribe & Save (SnS) — repeat purchase and reviews are both repeat-experience signals
• Connect your advertising account — setup steps if the connection is the problem