What Is a Shopify Newsletter? An Operator's Definition

A Shopify newsletter is a broadcast marketing email — a launch announcement, a sale, an editorial note — sent to a store’s subscribed customer list, either through Shopify’s native Shopify Email app or through a connected platform such as Klaviyo. That is the dictionary answer, and it is also where most explanations of a Shopify newsletter stop.

What does “Shopify newsletter” actually mean?

A Shopify newsletter is one of two things a merchant sends by email: the other is a flow, which triggers automatically off a customer action — an abandoned cart, a first purchase — rather than off a decision to hit send. Shopify Email, built into the admin, lets a merchant build and send a newsletter at no extra cost up to a monthly volume; a connected ESP does the same job with more segmentation and testing options attached.

The distinction matters because the two systems are graded differently. Klaviyo’s own benchmark data across 183,000+ brands attributes 41% of total email revenue to automated flows (Klaviyo, vendor-reported), despite flows being a small fraction of total send volume — the newsletter earns its keep on reach and timeliness, the flows earn theirs on relevance. Treating a Shopify newsletter as the whole of your email programme, rather than the broadcast half of it, is the first mistake operators make with the term.

What changes for an operator running one at $3M–$30M?

Here is the part the dictionary definition leaves out. The revenue point at which a typical brand starts running both a newsletter and a set of behavioural flows side by side is — metric to confirm, because no platform or research firm publishes adoption by revenue band. What is observable without a published figure is simpler: once a store runs both, which is standard practice by the time it reaches Shopify Plus, those two things frequently live on two different suppression lists that do not talk to each other.

Shopify Email keeps its own subscription and suppression state inside Shopify. Klaviyo, Recharge’s own messaging, or any other connected platform keeps a separate one. A customer who clicks unsubscribe on a Klaviyo flow email has opted out of Klaviyo’s list. They have not touched Shopify Email’s list at all, and depending on how the store is set up, they may still be marked as subscribed there. On a Tuesday, that customer gets the newsletter blast anyway — not because anyone made a mistake, but because “unsubscribed” is a fact recorded in one system and not propagated to the other.

The consequence is not abstract. A spam complaint from a customer who genuinely believed they had opted out is a deliverability event that affects every subsequent send, newsletter and flow alike, because sender reputation is shared across a domain regardless of which tool fired the email. The fix is a reconciliation step between whichever platform runs the newsletter and whichever runs the flows — checked on a schedule, not assumed to be automatic — and it is the same category of unglamorous, necessary system as the one that keeps flow data itself trustworthy.

When does Shopify Email stop being enough for a $3M–$30M store?

Shopify Email stops being enough once a store’s automation needs outgrow its trigger set, not at a single fixed revenue point — the pricing scales cleanly with volume, but the tool’s capability ceiling does not move with the plan. Every store on the Basic Shopify plan and above gets 10,000 free marketing emails at the start of each calendar month, shared across every campaign sent that month, and unused emails do not carry over to the next one. Past that allowance, Shopify charges $1 per 1,000 additional emails up to 300,000 emails a month, $0.65 per 1,000 from 300,000 to 750,000, and $0.55 per 1,000 beyond 750,000 (Shopify Help Center, 2026). Emails are billed per unique recipient, not per campaign, so one newsletter sent to a 40,000-name list uses 40,000 of that allowance in a single send.

That arithmetic is one an operator can run without us: multiply list size by planned sends per month, subtract 10,000, and price the remainder against the tier it falls in. Abandoned checkout automations are the one exception to all of it — they send free and uncounted regardless of volume, so a store leaning heavily on cart-recovery messaging will not see that cost reflected in its newsletter bill at all.

Cost, though, is rarely the reason a $3M–$30M Shopify Plus operator actually migrates off Shopify Email. Shopify Email ships welcome-series, first-purchase-upsell and abandoned-checkout automations at no charge, but the automation set stops there: there is no conditional branching inside a workflow, no built-in A/B testing on subject line, send time or content, and segmentation is limited to Shopify’s own customer segment builder rather than the layered, event-based segmentation a dedicated ESP such as Klaviyo builds around. An operator running post-purchase cross-sell, win-back, replenishment reminders and browse-abandonment alongside a newsletter is describing a job a dedicated ESP is built for — not a limit any Shopify Email pricing tier removes.

The practical trigger is a checklist, not a list-size number: the operator needs conditional logic a single linear workflow cannot express, needs to test more than one subject line without hand-splitting the list, or needs segmentation finer than Shopify’s native customer tags support. Exactly how far into the free-email allowance a typical $3M–$30M store gets before hitting one of those triggers is metric to confirm against your own automation backlog — it depends on catalogue depth and campaign cadence, not list size, so no single figure describes every store. That uncertainty is itself the point: send volume alone is a poor proxy for the migration decision, because a store comfortably inside the second pricing tier can still need to migrate on the first campaign it wants to run, if that campaign needs a branch Shopify Email has no way to build.

What return should a $3M–$30M operator expect from a newsletter send?

No published benchmark breaks email revenue down by list size or revenue tier, so the honest answer is to compute it from your own send history using the one figure that is measured industry-wide: revenue per recipient (RPR). Klaviyo’s 2026 benchmark data, measured across 183,000+ brands, puts average campaign RPR at $0.11 and average flow RPR at $1.94 — an 18-times gap — with top-decile performers reaching $0.95 per recipient on campaigns and $7.79 per recipient on flows (Klaviyo, vendor-reported).

That figure is not segmented by list size or revenue tier — it is a blended average across every Klaviyo customer, most of whom run smaller lists than a $3M–$30M Shopify Plus store. Whether a $3M–$30M operator’s own campaigns should land above or below the blended average — metric to confirm against your own history, not something the published data can answer for you.

The method that does travel, though: take your own recipient count for a planned send, multiply by $0.11 as a conservative floor, and compare that estimate against what Shopify Email actually charges for that volume — free for the first 10,000 recipients each month, then $1 per 1,000 up to 300,000. If a single average-performing campaign clears its own sending cost by a wide margin, Shopify Email’s price is not the constraint on your programme — the missing conditional branching, A/B testing and layered segmentation are. If it does not clear that floor, the newsletter itself, not the platform it runs on, is what needs fixing first. The top-decile figures — $0.95 per recipient on a campaign, $7.79 on a flow — are the number worth aiming a segmented, well-targeted programme at, since they describe what operators this size are capable of rather than the blended average that includes every hobby store on the platform.

The same 2026 dataset gives the two components that produce a low RPR, which matters because it tells you where to look before assuming the platform is the problem. Klaviyo’s all-vertical campaign average is a 31% open rate against a 1.69% click rate; flows average a 42%+ open rate and a 5.58% click rate, with top-performing flows reaching around 10.48% clicks (Klaviyo, vendor-reported). A newsletter posting a click rate near the 1.69% campaign average with an RPR well under $0.11 has an engagement problem — subject line, send time, list health — not a platform ceiling. A newsletter clicking above that average but still earning little per recipient has an offer or landing-page problem downstream of the email entirely, and no amount of platform migration fixes either one.

What deliverability risk does Shopify Email carry at Shopify Plus volume?

Shopify Email’s deliverability risk at scale comes from two mechanics working together: authentication that is largely automatic, and a sending reputation pool a merchant does not fully control on their own. Shopify authenticates a store’s sending domain by adding CNAME records that configure both SPF and DKIM for the sender address, so there is no separate SPF TXT record to manage by hand (Shopify Help Center, 2026). If the domain was purchased through Shopify, authentication — including DMARC — is configured automatically; for a domain hosted elsewhere, including Cloudflare, GoDaddy or IONOS, Shopify can configure the DNS records on the merchant’s behalf, though the change can take up to 48 hours to propagate.

Gmail and Yahoo require a DMARC record and an authenticated sending domain before they will deliver bulk marketing mail from a branded address at all. A store’s existing DMARC record can silently break this: if it sets strict alignment — adkim=s or aspf=s — Shopify’s own authentication can fail validation against it, and Shopify’s own guidance is to relax those settings to adkim=r and aspf=r rather than leave them strict.

This is not a hypothetical threshold for a $3M–$30M Shopify Plus operator — it is one most of them clear without noticing. Google classes anyone sending more than 5,000 messages a day to Gmail accounts as a bulk sender, a bar a weekly newsletter to a five-figure list crosses on send day alone, and bulk senders face rules general senders do not: SPF and DKIM are both mandatory rather than either-or, a DMARC record at a minimum policy of p=none is required, and Google’s own guidance is to keep the spam-complaint rate reported in Postmaster Tools below 0.10% and never let it reach 0.30% (Google, official documentation, 2026). Bulk senders must also support one-click unsubscribe — the List-Unsubscribe and List-Unsubscribe-Post headers, not just a link in the footer — and honour an unsubscribe request within two days. None of this is Shopify-specific; it is the mail a Shopify newsletter has to clear regardless of which tool sends it, and it is why “the newsletter went to spam” at this volume is a compliance-and-reputation question first, not a copywriting one.

Above 1,000 subscribers, Shopify Email also switches on Smart Delivery automatically, which throttles and paces a send based on the recipient list’s own engagement history rather than firing every message at once (Shopify Help Center, 2026). Turning it off is possible but Shopify’s own guidance is that doing so raises bounce rates over time, and a list of any size a $3M–$30M store runs will already be past that 1,000-subscriber threshold on its first campaign. Shopify’s List Health setting automatically excludes anyone who has unsubscribed, bounced, or marked a previous message as spam from every future campaign. That protection is scoped to Shopify Email’s own records only: it cannot see a suppression event recorded inside Klaviyo or another connected ESP, so the same two-list mismatch persists even with List Health switched on — it is enforced inside one system’s list, not reconciled against the other’s. Sustained spam complaints, independent of Smart Delivery or List Health, can lead Shopify to temporarily limit or pause a store’s access to Shopify Messaging entirely — a platform-level consequence a dedicated ESP’s own onboarding and warm-up process is built specifically to avoid.

Where Shopify Email diverges most from a dedicated ESP is whose reputation a send actually carries once authentication is correctly configured. Shopify does not offer a dedicated sending IP for Shopify Email the way Klaviyo offers on its higher tiers — sending infrastructure is shared, and a store’s deliverability is affected by every other sender using the same pool. A merchant with a clean list and strong engagement has no lever to isolate their own reputation from unrelated stores having a bad month on the same infrastructure, which is the opposite of the control a dedicated ESP’s own-IP option is sold on.

Shared-pool deliverability risk and the two-suppression-list mismatch reinforce each other rather than sitting apart. A spam complaint generated because Shopify Email and a connected ESP disagree about who is subscribed does not just cost that one send — it degrades a shared reputation pool the store cannot isolate itself from, so the same customer-level consent gap that causes an unwanted send also does lasting damage at the infrastructure level. Reconciling subscription and suppression state between whichever platform sends the newsletter and whichever runs the flows is not optional at Shopify Plus volume for exactly this reason: the failure mode is not one unwanted email, it is a shared sending reputation that every future send, from either platform, then has to overcome.

Where do people get “Shopify newsletter” wrong?

Two mix-ups come up constantly. The first is calling the signup form the newsletter — the pop-up or footer field that captures an email address is the collection point, not the message. Consent captured there needs to land in whichever system actually sends the campaign, and a form wired to the wrong integration produces a list of addresses nobody ever emails.

The second is assuming Shopify Email and a connected ESP are the same list wearing two names. They are not. A merchant who migrates from Shopify Email to Klaviyo, or runs both in parallel during a transition, needs to explicitly export and reconcile subscriber status rather than trusting that Shopify’s own customer record carries it across. This is where the metric-to-confirm caveat matters most: exact export behaviour and default consent handling change between Shopify and app releases, so verify the current mechanics in each platform’s own documentation before relying on them for a live migration — figure to confirm against your account’s current settings.

What is a Shopify newsletter confused with?

The term gets used loosely to cover three separate things: the broadcast campaign itself, the automated flow that looks similar in the inbox, and the signup mechanism that feeds both. Keeping the three concepts distinct in how a store builds and reports on them is what prevents a newsletter platform, a flow platform and a signup form from disagreeing about who is subscribed where — the same mismatch that turns a legitimate unsubscribe in one system into an unwanted send, and a spam complaint, from another.

That reconciliation, and the broader question of which flows exist, what triggers them and whether their suppression logic actually matches your newsletter platform’s, is a lifecycle flows problem rather than an email-marketing-tool problem. It is the same system-design work — mapping every trigger, every suppression rule and every metric across the tools a store actually runs — that determines whether a Shopify newsletter and the flows sitting next to it reinforce each other or quietly work against one another. That is what a lifecycle flows engagement audits first, and the flow revenue calculator is a fast way to see how much of your current email revenue already depends on getting it right.