Requests flow through a pipeline: an order qualifies, a trigger fires, a delay passes, an email sends. When nothing is going out, one stage is stuck, and the Requests queue tells you which.

Open Reviews, then Requests. The stat cards narrate the pipeline: orders processed, waiting for fulfillment, requests in queue, requests sent. Scheduled requests with future dates mean the system is working and the delay simply has not elapsed. An empty queue means orders are not qualifying, read on.

[SCREENSHOT: Requests queue stat cards]

In Settings, then Collect & publish, confirm your trigger matches reality. The classic miss: the trigger is After fulfillment but orders are not being marked fulfilled, so the countdown never starts. The "Waiting for fulfillment" card catches this red-handed. Likewise, After delivery needs delivery confirmation to fire, that is what the AfterShip integration provides.

The Manual review requests strip on the Requests page shows how many sends you have left this cycle and the reset date. At the limit, requests pause until the month resets or you upgrade, and Quoli emails you at 80 and 100 percent so this never arrives as a surprise.

Addresses on the blocklist in Settings, then General never receive requests, which is exactly right until your own test address is on it. Testing with a team email that was blocklisted on day one is the most common ghost in this machine.

If the queue says sent and inboxes say otherwise, check the delivery rate in email performance. A healthy rate means the email is landing in spam or promotions on the recipient side, and a branded sender domain is the durable fix.

💡 Tip: Place one real test order, fulfill it, and watch it move through the queue with a short delay. Ten minutes, and you have verified every stage with your own eyes.