If a potential customer abandons an order, but then comes back and successfully places a new order before the followup message was sent, the original abandoned cart will still trigger a follow up email.

It would be great to have an option for this module to check if the same customer (matching on email address, I assume) has since completed an order before the email is sent out.

Comments

m.stenta’s picture

Status: Active » Closed (won't fix)

I'm not sure if there's an easy way to handle this within uc_followup. There are a lot of possible scenarios where a duplicate order could be created for a customer. For example, if a customer clicks the "back" button during checkout review and then continues, you're left with 2 orders in the system: 1 in_checkout and 1 pending (see #841862: Revisiting the checkout review form multiple times creates a new order each time).

And there may be scenarios where a customer wants to create multiple orders, and one or more of them end up as duplicates along the way. It would be very hard to determine which ones are which.

It seems that it should be up to the shop manager to maintain the orders in Ubercart, by setting bad orders to "Cancelled" to avoid followup emails. There may be a way to automate that process, as well.

I'm going to close this and set it to "won't fix" for now, unless a good solution presents itself.

Neo13’s picture

Would it be possible to check before sending follow-up if there is another completed order for the user? I would like to send user email if he hasnt ordered anything for 3 months for example.

m.stenta’s picture

Here's an idea: what if there was a checkbox in the followup set-up form that said "Only send a followup for the latest order that matches these criteria."

Checking the option would only check ONE order (the latest one by that customer) for matching criteria, so it would only send out one email. As opposed to looking through ALL of the customer's past orders and potentially sending multiple emails, as it's doing right now.

Neo13’s picture

That would be really great. Lots of new possibilities.

Neo13’s picture

Status: Closed (won't fix) » Needs work
m.stenta’s picture

Status: Needs work » Patch (to be ported)

This is done in the latest 7.x-1.x branch.

Now I just need to port it to the 6.x branch...

m.stenta’s picture

Version: 6.x-1.1 » 7.x-1.x-dev
Status: Patch (to be ported) » Closed (fixed)

Alright! Backported it to the 6.x-1.x-dev branch also!

This is done!