Avoid Omnisend for WooCommerce

  • grishinan

    (@grishinan)


    1 month, 1 week ago

    I’ve been using Omnisend for about a year, and honestly, I strongly advise against it. Out of the blue, they discontinued WooCommerce support without any clear communication. When I tried reconnecting, I kept getting errors and contacted their customer support — which turned out to be an absolute disaster.

    We were in touch for over a week. Different agents kept rotating in the same chat, asking me the same questions again and again. One of them (Maria) told me to disable automations inside Omnisend and then completely disappeared — now my automations cannot even be reactivated, leaving my email flows broken.

    Other agents repeatedly suggested the same “solution”: disable Jetpack, which is a critical plugin for WordPress. After involving WordPress support to disable/re-enable Jetpack, my WooCommerce settings got corrupted — I now need to reinstall WooCommerce payments, shipping, and more. Despite all this, Omnisend still throws the same connection error.

    The worst part is that the Omnisend team clearly does not understand their own product, nor how WooCommerce actually works. They wasted my time, broke my site’s setup, and never fixed the original issue. Extremely unprofessional and unreliable.

    If you’re on WooCommerce or WordPress, avoid Omnisend at all costs.

    • This topic was modified 1 month, 1 week ago by grishinan.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support supportomnisend

    (@supportomnisend)

    1 month, 1 week ago

    Thank you for taking the time to share your experience. We’re truly sorry to hear about the difficulties you’ve encountered and completely understand how frustrating this must have been — especially after investing time and effort into setting everything up.

    After reviewing the case, our team found that the potential issue might be caused by your store’s API rate-limiting requests (429 – Too Many Requests), which prevented Omnisend from maintaining a stable connection. While your credentials were correct, the store’s system was temporarily blocking further requests to avoid overload. This is why reconnecting resulted in recurring errors.

    We realize how disruptive this situation was for your business and regret that it led to temporarily paused workflows. Our team has shared a few potential next steps with you directly in the ongoing communication, and we’d be happy to continue working with you or your developer to get your connection restored.

    We appreciate your patience throughout this process and remain committed to helping you get things back on track.

    Plugin Support supportomnisend

    (@supportomnisend)

    4 weeks, 1 day ago

    We wanted to provide an update regarding the issue you experienced. After further investigation and collaboration with your hosting provider, we identified that the problem was related to hosting limitations on the /wp-json/wc/v3/ endpoint. The necessary adjustments were made on their end to ensure Omnisend’s requests are now processed successfully.

    According to the latest logs, the 429 (Too Many Requests) errors are no longer occurring, and the connection issue has been fully resolved.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this review.