Is there a way to prevent auto opt in for marketing emails from Collective partners? Every time I get a sale for one of my collective partners it opts me in to their email list with a new email address that forwards to my primary email. For example, a partner for which I have made 50 sales for, I get 50 of the same marketing email spammed to my inbox. It’s a real pain to unsubscribe every one of them.
Right now, Shopify Collective doesn’t have a built-in way to stop partners from automatically opting you into their marketing emails. It’s super annoying, and you’re definitely not the only one dealing with it.
Here are the only effective options right now:
1. Turn off “auto-subscribe” on the partner’s side (if they offer it). Some Collective partners have an option in their email/marketing settings to not subscribe retailers.
You can politely ask them to disable it.
2. Create a Gmail filter / Outlook rule. This is the fastest fix you can control. You can filter out all those auto-generated Shopify Collective emails using something like:
to:*@shopifyemail.com or by filtering by the partner’s “from” email.
There isn’t a toggle to stop auto opt-in (sadly), but you can block the emails without unsubscribing 50 times.
Hope this helps!
Collective also auto-creates customer records for each partner order, so every order results in a new “customer email” unless you enable forwarding. A cleaner fix is to direct partner order notifications to a separate alias that doesn’t forward to your main inbox. This will allow you to completely avoid marketing opt-ins without having to edit each email.
Has anyone found a clean workaround for this issue? I am going crazy dealing with the sheer number of Collective partner marketing emails I get daily. I use Gmail. I’ve tried setting up filters but it doesn’t seem to be working, plus so many of the companies I partner with use the same email for their marketing as they do for their support or direct contact…so I am worried important emails will get lost in the mix. It is maddening. Shopify needs to correct this issue. Look at this crap:
