Unusual Paypal problem

We have a site which has some code added to the checkout_process page which triggers an email to the manufacturer of the item ordered.

This code is activated when an order has been processed by either Paypal or Protx... except that if the Paypal customer has been returned to the site automatically, then, although the order is complete and appears in ZenCart, that email does not go to the manufacturer.

If the client doesn't wait for automatic return and clicks the manual link, then the code IS activated and that email is sent.

Can anybody suggest why there should be a difference?

As long as the customer is actually coming back to your store after completing the PayPal order, I don't see why there would be any difference between clicking the button vs allowing the automatic return.

If it's breaking because the customer closes their browser and never returns to your store, that's another story ... meaning you probably need to put your extra code in another place.

Thank you DrByte - hadn't occurred to me that people may not bother to come back.

However I've tested the auto/manual myself so even though neither of us can think of a reason, there is definitely different behaviour between the two options.

I'll try moving it to the checkout_success page.

If they don't click to come back to your site, then the checkout-success page won't solve anything.
You'll have to do something in the /ipn_main_handler.php, probably just before this line:```
ipn_debug_email('Breakpoint: 6 - Completed IPN order add.' . ' ordersID = '. $ordersID . ' IPN_id =' . $paypalipnID);

HOWEVER: it's important to note that if the customer makes a payment WITHOUT creating a PayPal account AND closes the browser without choosing "yes or no" to PayPal's invitation to create an account at the end of their order, the IPN is not sent, and your store will never know about the order, and thus it doesn't matter how many hooks you put in or where (you won't get emails from the store, and neither will your manufacturers).  PayPal still hasn't fixed that design flaw.

Thanks for that advice - although the "HOWEVER" part is not the problem here. :D