Email and SMS
Klaviyo agency for ecommerce brands
Klaviyo holds every order, product view and profile a store has, which makes it the natural place to run replenishment, win-back and post-purchase logic. Most accounts we open use a fraction of that: a welcome series, an abandoned cart flow and a weekly campaign. We build the flows around how the product is actually bought, segment from the data Klaviyo already has, and report the channel on revenue the store can reconcile.
Klaviyo
Email and SMS · by Klaviyo. A text wordmark, not a logo: we are not affiliated with the vendor and make no claim to its trademarks.
What we do with it
The work inside Klaviyo
Flow architecture from the purchase cycle
We map how each product category is bought and used, then build the flows to match: replenishment timed to product size, post-purchase education before the first review request, browse and cart abandonment split by product value, and win-back triggered by the category's real reorder gap rather than a fixed ninety days.
Segmentation from store data
Klaviyo's segments can read order history, product properties, predicted values and site behaviour. We build the segments a store's campaigns need, such as one-time buyers of a consumable, subscribers due to lapse, high-value customers who have not bought this season, and use them to send fewer, more relevant campaigns.
Deliverability and list hygiene
Dedicated sending domain and authentication set correctly, sunset flows that stop mailing profiles who never open, double opt-in decisions made per market, and campaign sending shaped so a promotion does not spike complaint rates. Inbox placement is checked before a peak, not after.
SMS inside the same account
SMS consent captured separately and compliantly, quiet hours and frequency caps set per country, and SMS reserved for the messages that justify the interruption: shipping, restocks, replenishment reminders and time-limited offers to customers who asked for them.
Integration and data quality
Shopify, WooCommerce and BigCommerce integrations checked for product catalog sync, order and refund events, and subscription data from Recharge or the platform's own subscriptions. Reviews and support tools feed the profile so flows can react to a bad review or an open ticket.
Reporting against orders
Klaviyo's attributed revenue uses its own windows for opens and clicks. We reconcile it against store orders, report flow and campaign revenue on a consistent click-based basis, and show the share of total revenue the channel actually influenced.
When it fits
Klaviyo is the right tool when
Stores on Shopify, WooCommerce or BigCommerce with real order history
Klaviyo's value comes from the data the integration feeds it. A store with a year of orders and product properties in the catalog can segment and trigger in ways a newer store cannot yet.
Consumable, replenishable or seasonal catalogs
Products bought again on a cycle give flows a schedule to work with. Skincare, supplements, coffee, pet food and printer consumables all benefit more than a one-off purchase category.
Brands ready to run SMS and email as one program
Keeping both channels in one profile prevents the customer receiving the same offer twice and lets quiet hours, consent and frequency be managed in one place.
Teams that want the tool built out, not just connected
The integration takes an afternoon. The flows, segments and reporting that make it pay take structured work, and that is the part we do.
What to watch
Where accounts drift
Facts about defaults and costs, not criticism. These are the settings we check on every account.
Attributed revenue is generous by default
The default attribution window credits opens as well as clicks. Read Klaviyo revenue next to store orders and switch reporting to click-based before making budget decisions on it.
Profile counts drive the bill
Pricing scales with active profiles, so suppressed and never-engaged profiles cost money every month. A sunset policy is a financial control as much as a deliverability one.
Flows drift when the catalog changes
A product-triggered flow keeps referencing a discontinued item, a new collection never gets a browse-abandon path. Flows need a quarterly review against the live catalog.
Consent rules differ by country
Email and SMS consent, quiet hours and unsubscribe requirements vary between Canada, the United States and other markets. The account needs settings per market, not one global default.
Do you set up Klaviyo from scratch or take over an existing account?
Both. A new account gets the integration, sending domain, core flows, segments and reporting built in a defined order. An existing account gets an audit first: which flows are live, which fire, where deliverability stands and what revenue reconciles, then a rebuild plan that keeps what works.
How many flows should a store run in Klaviyo?
As many as the purchase cycle justifies and no more. Most stores need a welcome series, cart and browse abandonment, post-purchase, replenishment or win-back, and a sunset flow. Consumable and subscription catalogs add more. A flow with no clear trigger and no measurable revenue should be switched off.
Can Klaviyo replace a separate SMS platform?
For most stores, yes. Running SMS inside Klaviyo keeps consent, frequency and profile data in one place. A separate SMS platform is worth keeping only when it offers something specific the store depends on, such as a conversational support workflow.
How do you report Klaviyo revenue honestly?
We set attribution to click-based, reconcile flow and campaign revenue against store orders each month, and report email and SMS as a share of total revenue with new versus returning customers separated. Open-attributed revenue is shown only as a secondary figure.
Does Klaviyo work with subscriptions?
Yes. Recharge and Shopify Subscriptions send subscription events to Klaviyo, so flows can react to an upcoming charge, a skipped order, a failed payment or a cancellation. Those flows are usually where subscription retention is won.
Works alongside
Find the leak.
A free Growth Analysis ranks what your store should fix first, by revenue at stake.