Klaviyo

Klaviyo is worth considering when an online store needs its email program to respond to what customers buy, browse and stop buying. Its appeal is the connection between customer records, segments and automated messages. That connection also creates work: someone has to keep the events, permissions and billing population accurate as the store changes.

Start with the number of billable active profiles, not the number of people who received the last newsletter. On 17 October 2026, the public estimator displayed USD 100 per month for 5,000 active profiles and 50,000 emails, with optional products unselected. That is an email-plan observation, not a quote for every part of the Klaviyo platform.

> Distinctive strength: Store events can inform segments and email flows. > > Where it stops being an advantage: Event quality and profile growth need an owner.

BenPicks reviewed public pricing and documentation. We did not connect a store, send campaigns or measure revenue. The calculations below are original planning examples with stated assumptions.

Does your store need this level of customer data?

A large integration directory does not prove that a particular field arrives with the right meaning. For example, a refunded order and a paid order should not produce the same follow-up merely because both contain a transaction identifier. Write down those distinctions before evaluating a template library.

Pricing: profiles and sends are two separate constraints

The selected 5,000-profile email estimate included 50,000 monthly sends. Composer, mobile messaging, Customer Hub and other optional products were not added. A promotion visible for the 500-profile first month was excluded from the recurring example. Confirm the billing currency, tax, regional offer and exact order before buying.

Klaviyo's free allowance is much smaller: up to 250 active profiles and 500 monthly emails. It can support a limited evaluation; it does not cover the 5,000-person scenario here. Support entitlements and paid features also differ.

The important accounting distinction comes from the active-profile documentation ↗. Active profiles can include people who supplied an email during general store activity without explicitly subscribing to marketing. Suppressed profiles do not count toward the email billing population. Neither a billable record nor a purchase gives you permission to send marketing.

Profile compliance and message overages follow different rules. The billing-preference guide ↗ describes profile-based upgrades at renewal, plus separate choices for handling message limits. Inspect those preferences rather than assuming unused sends protect you from a profile-driven increase. We have not inspected a buyer's private account or negotiated contract.

An original 5,000-recipient workload

Assume the account has exactly 5,000 billable active profiles, all permitted recipients for the relevant campaigns. The 500 people entering the example flow are already inside that population.

The basket uses 42% of that send allowance. It leaves no assumed profile headroom at 5,000. Extra checkout records, a second store or a broader import can change the billable population even if email volume barely moves. That is why a per-email calculation alone would be misleading.

Download the scenario worksheet. For a wider cost model, use the email platform cost guide; the existing calculator does not contain a newly verified Klaviyo tariff table.

What happens during a real migration?

Treat migration as a sequence of acceptance checks, not a single CSV upload.

1. Inventory the data. Separate marketing permissions, suppression reasons, customer identifiers, store events and optional custom properties. Record where each came from.
2. Choose one identifier strategy. Check what happens when the same customer arrives through a store sync, a form and an old email export. Do not assume every integration merges them as intended.
3. Rebuild a small flow first. Verify entry, delay, exclusion and exit rules, especially after a purchase or refund.
4. Check audience counts before launch. Explain any difference between source subscribers, imported profiles, billable active profiles and eligible recipients.
5. Retain an exit copy. Klaviyo documents list/segment CSV export ↗, including selectable consent details. Confirm which fields you need; an export file is not proof that another platform can reproduce a flow or attribution model.

Keep the previous system available for reconciliation where the contract permits. Reusing a template is faster than discovering that an exclusion rule was lost, but no time saving has been measured for this profile. The migration checklist covers the broader handoff.

Data, access and reporting questions that deserve an answer

An ecommerce integration can connect purchase history and browsing-related activity to contact records. Before a real import, confirm the required permissions, retention arrangements, subprocessors and deletion process for the services you enable. Klaviyo publishes a data-request guide ↗; that is procedural documentation, not an independent compliance assessment.

Create a role for the person maintaining flows and decide who may export customer data or change billing. A public product page cannot establish the permissions in your actual workspace.

Also keep reported campaign revenue separate from incremental revenue. A platform's attribution settings can assign an order to an email without proving that the order would not have happened otherwise. Reconcile a small set of permitted test orders with the store ledger before using attributed revenue to justify a larger subscription.

Which alternatives belong beside it?

Compare Omnisend when the same ecommerce communication job is central. Read Drip for a different approach to contact-based email automation and the same 21,000-send planning basket. Consider MailerLite if the job is mainly newsletters, forms and a smaller set of automations.

Avoid choosing from entry prices at different list sizes. Normalize active records, consent, monthly sends, channel selection, operators and migration work. None of these profiles establishes a deliverability or revenue winner.

A bounded evaluation before moving the whole store

Use permitted test records representing a subscriber, a non-subscribing purchaser, a suppressed person, a refunded order and a repeat customer. Check what enters the account, what becomes billable and which messages would be eligible. Start with a draft flow; do not activate live marketing merely to inspect the rules.

For the buyer's own authorized evaluation, record expected versus observed segment membership, event delays, accidental duplicates, operator time and export completeness. Set hard gates in advance: no suppressed person receives marketing, purchase/refund exits behave correctly, and the billable population reconciles to your inventory. Review the applicable terms and permissions before any test using real data.

Klaviyo belongs on the shortlist when the store can use customer events reliably and someone owns their upkeep. If the evidence for those two conditions is missing, a more elaborate flow builder will not answer the buying question.

Sources and limits

Checked 17 October 2026: public pricing and estimator ↗, active profiles ↗, message limits and billing preferences ↗, CSV export ↗, and data requests ↗. Pricing redirected to the UK page with USD selected. Estimates are dated observations; private contract terms, actual deliverability and migration outcomes remain untested. BenPicks affiliate approval is unconfirmed, and the product link is an ordinary official destination.