Resolving Cart Recovery Emails Sent After Order Placement

In this article, we provide a step-by-step guide to troubleshoot and resolve the issue of cart recovery emails being sent after an order has been placed.

If you're experiencing an issue where customers receive cart recovery emails even after placing an order, please follow the steps outlined below to ensure your Retainful plugin is correctly configured and your webhooks are properly set up.

Step 1: Update the Retainful Plugin

  1. Log in to your Retainful dashboard.

  2. Navigate to Plugins.

  3. Locate the Retainful plugin.

  4. Ensure the Retainful plugin is updated to the latest version.

  • If an update is available, click on Update Now.

Step 2: Reconnect the Retainful Plugin

  1. Go to your WordPress dashboard.

  2. Navigate to Retainful -> Connection.

  3. Click the Re-connect button.

Step 3: Verify Webhooks Configuration

  1. Go to your WordPress dashboard.

  2. Navigate to WooCommerce -> Settings -> Advanced -> Webhooks.

  3. Ensure you see two webhooks:

  • Retainful Order Created

  • Retainful Order Updated

If the Webhooks Are Missing:

  1. Go to your WordPress dashboard.

  2. Navigate to Plugins.

  3. Find the Retainful plugin.

  4. Deactivate the plugin by clicking Deactivate.

  1. Reactivate the plugin by clicking Activate.

  • This action should recreate the webhooks if they were deleted.

If the issue still persists, please follow the steps below,

Step 4: Adjust Order Status Settings

For the payment options such as “invoice” or “cash-on-delivery”, which result in the order status being marked as “Pending” or “On Hold,” these will be classified as abandoned carts. Therefore, it’s necessary to modify the settings in Retainful accordingly.

  1. In your WordPress dashboard, go to Retainful -> Settings.

  2. Find the “Consider on hold order status as abandoned cart”.

  3. Set this field to NO and Save.

This setting ensures that orders with the status "On Hold" do not trigger the abandoned cart workflow.

If the issue persists, please contact to support team at

Last updated