Klaviyo's revenue cut is a tax you don't have to keep paying

Webhooks. Shopify's native webhook system covers every event you'd want to trigger on — checkouts/abandoned, orders/paid, orders/fulfilled, customers/create, customers/update. You paste the CleverlyBox webhook URL into Shopify Admin → Settings → Notifications, and the flow fires within seconds. No app, no app-store fees, no extra OAuth surface, no Klaviyo-style platform lock-in. Same pattern works for WooCommerce, BigCommerce, and Shopware.

Performance is determined by three things: deliverability (which is better on a dedicated SES IP than on Klaviyo's shared pool), the email itself (yours, copy-pasted across), and the timing logic (which you'll rebuild identically). Most operators see equal or slightly better cart recovery in the first 30 days, primarily because the new dedicated IP improves Gmail inbox placement.

Yes. The webhook payload from Shopify includes line items, prices, and product images. Use them as merge tags directly: {{line_items[0].name}}, {{line_items[0].price}}, {{line_items[0].image_url}}. For broadcast campaigns with dynamic catalogs, you can use the API to inject product data at send-time or pre-render a personalized HTML block per segment.

CleverlyBox is email-first. SMS isn't built in. Most operators either keep SMS on Postscript / Attentive (which is fine those tools earn their keep), or migrate SMS separately to a Twilio-direct setup. The CleverlyBox saving is large enough that the SMS line item becomes irrelevant you're net-positive even with Postscript still running.

CleverlyBox gives you click-through and conversion-event tracking via webhooks back to your store. Revenue attribution is calculated by your store (Shopify's "marketing analytics" report shows email-attributed revenue when you tag campaigns with UTM parameters — which CleverlyBox auto-appends). For more sophisticated attribution, pipe the click webhook into your analytics warehouse and join against orders. This is how the largest operators run attribution anyway Klaviyo's number is a black-box approximation.

SES suspension is rare and almost always preceded by complaints/bounces above AWS's thresholds. CleverlyBox's deliverability dashboard surfaces those signals before AWS does, so you can pause campaigns and clean before AWS notices. As a backup, configure SendGrid or Mailgun as a failover provider (CleverlyBox supports multi-provider sending pools) — if SES ever has an issue, sending switches automatically.

CleverlyBox includes a form builder with embed snippets, popup triggers, and double opt-in. Most operators keep their Klaviyo popups running for 30 days post-migration (they still capture to your Shopify customer DB), then swap the embed to the CleverlyBox snippet at month-end. Both approaches work the swap is a one-line code change.