Klaviyo Pricing Guide for 2026

The billing model in one paragraph

Klaviyo charges for active profiles, meaning contacts who may receive marketing, with monthly email allowances attached to each profile tier, while SMS and newer AI products draw on separate credit-style meters. The model assumes commerce reality: a store's list is its asset, dormant profiles included, and the platform prices the asset while metering the channels that touch it. Exceeding free limits pauses sending until the next cycle or an upgrade, so growth forces explicit tier decisions rather than silent overages.

This shape rewards revenue-per-recipient thinking and punishes list hoarding. A store with 40,000 profiles but only 9,000 engaged buyers pays for storage of the unengaged, which makes suppression, sunset flows, and profile hygiene direct profit levers rather than deliverability niceties. SMS multiplies the stakes because carrier costs pass through on top of platform fees, so every phone number captured must earn its carrying cost in expected revenue.

Real list-size examples

The following email-only examples use the profile selectors shown by Klaviyo. They are monthly list costs, before any SMS, service, analytics, or AI line selected in the calculator.

These are bands, not a per-contact equation: a store at 501 profiles moves to the 1,000-profile selector rather than paying a fraction of the $30. Keep a forecast row for the next band, then add the SMS commitment only after estimating opted-in phone volume and message cadence. That prevents an agent from treating the email price as the whole bill.

Plan tiers, verified

The free plan is a complete commerce starter kit under tight caps: up to 250 active profiles and 500 email sends monthly, with reporting, web forms, templates, segmentation, and revenue attribution. Integrations with major commerce platforms are included rather than gated, so a new Shopify store can connect its catalog, build abandon flows, and prove cart-recovery math before paying.

Paid tiers scale price against active-profile count with larger send allowances per step, and the page structures email, SMS, service, analytics, and AI agent products as selectable lines that compose each account's total. Because the vendor page renders paid tiers through an interactive builder, this guide states the mechanism rather than snapshotting transient numbers: pick the profile band matching mailable contacts, add the SMS commitment matching message volume, and add Composer or agent products only where their output measurably beats human-built flows. Record every selected line before approving the subscription.

Limits, overages, and the fine print

Klaviyo's limits bite as pauses rather than surprise invoices: exceed 250 profiles or 500 sends on free and sending stops until the next cycle or an upgrade. That behavior protects budgets but threatens launches, so any store approaching either ceiling during a sale season must upgrade ahead of the spike rather than during it. Paid tiers convert the pause into a larger allowance with the same logic at higher scale, which keeps forecasting honest but demands attention to growth inflection points.

Support tapering is the overlooked limit. Free accounts receive full email support only for the first sixty days, then fall back to community and self-service resources, so operational questions in month four meet a thinner channel. Deliverability consequences follow list growth automatically: larger profile counts demand warmer sending discipline, sunset automation, and spam-complaint vigilance, costs paid in attention rather than dollars but very real in revenue terms.

What the free tier really proves

Two hundred fifty profiles and five hundred sends prove unit economics, not scale. A new store can run welcome flows, two cart-recovery variants, and a post-purchase cross-sell to its first customers, then read revenue attribution per flow and decide whether email earns its keep. The small mobile and Composer allowances let a team test SMS and AI-assisted flow building before committing to larger meters.

The honest boundary is the profile ceiling's speed of arrival. A single successful month can triple a new store's list past 250 profiles, converting a free evaluation into a paid decision mid-momentum. Founders should enter the free tier already knowing which paid profile band follows, and should treat support tapering after day sixty as a reason to document their own runbooks early.

Who Klaviyo is for

Klaviyo fits commerce sellers where carts, catalogs, and repeat purchase drive revenue: Shopify and WooCommerce stores, wellness and apparel brands, restaurants with ordering flows, and any business whose data model centers on SKUs rather than seats. Predictive churn and lifetime-value models, product recommendations, and back-in-stock alerts earn their keep fastest where purchase frequency is high and margins absorb platform cost.

Klaviyo is a weaker fit for SaaS and product-led teams. Subscription trials, seat expansion, dunning, and usage-based segmentation map awkwardly onto a commerce profile model, and contact-based pricing taxes the dormant free-user lists SaaS products naturally accumulate. Those teams should compare our Mailchimp guide if beginner-grade breadth matters more than commerce depth.

Agent and MCP fit

Agents meet Klaviyo through conventional APIs and an expanding set of AI products such as Composer for auditing and building flows from prompts and customer-facing agents powered by store data. Practical agent work includes segment analysis, flow performance audits, product-recommendation tuning, and draft campaign generation, all under scoped API access with human approval on anything customer-facing. The platform's own AI features compress the drafting loop while leaving judgment calls, discount depth, send frequency, and brand voice, firmly human.

Governance must bound two risks commerce agents amplify: discount-trained audiences and over-messaging. Agents optimizing open rates can learn to recommend perpetual discounts or daily sends, quietly trading margin and deliverability for engagement metrics. Approval gates should therefore review commercial terms and cadence, not just copy, with frequency caps and margin floors set as locked configuration. Our discussion scenarios on thresholds, brand voice, and cost attribution apply almost verbatim to commerce agent programs.

Where Klaviyo fits

Klaviyo wins commerce retention: catalog data, cart flows, predictive models, and SMS orchestration are purpose-built for stores. Product teams should choose a lifecycle platform whose event model matches trials and subscriptions instead of forcing commerce profiles to carry that state.

Choose by business model, not by feature checklist. Stores should shortlist Klaviyo first and verify paid profile-band pricing for their list size. SaaS teams admiring Klaviyo's polish should recognize the commerce-shaped data model underneath and pick the SaaS-native stack instead.

Verdict and checklist

Choose Klaviyo when commerce revenue depends on carts, catalogs, and repeat purchase. Prove flow-level ROI inside free 250 profiles and 500 sends, test SMS and Composer against their $5 allowances, know your next profile band before growth forces it, upgrade ahead of sale spikes since limits pause rather than flex, and lock discount and frequency policy outside agent reach. Re-verify every figure at Klaviyo pricing, then return to the pricing index for the full verified set.