The usual answer treats deliverability as a theme setting you can toggle, but the actual requirements live in sender authentication rules from Google, not in any Shopify theme's code, and confusing the two wastes time a store owner does not have.
Most store owners searching “email deliverability requirements” expect to find a checklist buried somewhere in their theme’s settings, a toggle they missed, a section called “Email Rules” they never opened. That thing does not exist. Deliverability to Gmail and Yahoo is decided by domain-level authentication and sender reputation, and no Shopify theme, however expensive or well reviewed, touches that layer. This article separates what theme code actually contains from what Google’s own sender guidelines actually require, because conflating the two is the single most common mistake merchants make when a campaign starts landing in spam.
A direct search through Dawn’s code finds the word “stores” in 33 of its 351 files, and Horizon’s code contains it in 4 of its 484 files. That sounds like a lead worth chasing until you look at where those matches live. In Dawn, “stores” appears in locale files: locales/bg.json, locales/cs.json, locales/da.json, locales/de.json, which are translation strings for the storefront interface, not mail configuration. In Horizon, the same word turns up in LICENSE.md, assets/scroll-container.js, assets/theme-drawer.js, and snippets/chat-drawer.liquid, which is licensing text, a scroll behavior script, a drawer component, and a chat widget snippet. None of these files sets up SPF, DKIM, or DMARC records, because a Shopify theme has no mechanism to do that. Sender authentication is configured at your domain’s DNS provider and inside whatever email platform sends your campaigns, a layer the theme never touches, as measured against Dawn commit 258f00f and Horizon commit 8b42ace from 2026-08-10 and 2026-08-31 respectively.
Same search, different word. “Rules” shows up in 12 of Dawn’s 351 files and 12 of Horizon’s 484 files, an identical count that might look meaningful until you check the file paths. Dawn’s matches sit in assets/base.css, assets/component-card.css, assets/global.js, and assets/product-info.js, all storefront display code: CSS rule sets, card component styling, and product info logic. Horizon’s matches sit in assets/base.css, assets/product-form.js, assets/volume-pricing-info.js, and blocks/buy-buttons.liquid, which cover product forms, volume pricing display, and buy button blocks. Neither theme has a section, setting, or block dedicated to email sending rules of any kind. If you are hunting for a deliverability control panel inside your theme customizer, stop, because the measured code confirms it is not there.
Google’s sender guidelines are explicit about timing and scope. Starting February 1, 2024, all email senders who send mail to Gmail accounts must meet the requirements described in that document, full stop, regardless of volume. A second, stricter tier applies if you send more than 5,000 messages per day to Gmail accounts, in which case you must meet the additional requirements built for that section. And there is one hard number worth remembering on its own: sending to personal Gmail accounts requires a DKIM key of 1024 bits or longer. That is a specific cryptographic threshold, not a suggestion, and it is the kind of requirement your email service provider configures, not something adjustable from a Shopify admin panel.
| Requirement | What Google’s guidelines say | Applies to |
|---|---|---|
| Baseline sender requirements | In effect starting February 1, 2024 | All senders emailing Gmail accounts |
| High-volume requirements | Stricter section, separate from baseline | Senders over 5,000 messages per day to Gmail |
| DKIM key length | Must be 1024 bits or longer | Sending to personal Gmail accounts |
Core Web Vitals data pulled from real visitor sessions in July 2026, using CrUX rather than a lab test, shows the median theme passing all Core Web Vitals in 85.5% of mobile sessions and 86.2% of desktop sessions. The method here is straightforward: CrUX aggregates field data from actual Chrome users visiting each storefront, not a synthetic run in a testing tool, so the numbers reflect what real shoppers experienced. Among the 247 themes with sufficient mobile data, the best performer hits 98.6% and the worst sits at 46.1%. Among the 199 themes with enough desktop data, the range runs from 99.2% at the top to 30.3% at the bottom. A slow signup form loses subscribers before they ever reach your list, and that is a real cost, but it is a conversion problem, not a spam-folder problem, and the two should not be solved with the same fix.
None of the 329 themes ranked in the market aggregate are sorted by anything related to email. The median theme price is $300 across a $100 to $500 spread, and the average rating across 308 rated themes is 4.53 out of 5 with a median of 23 reviews. These figures describe how a theme is priced and perceived by buyers on a theme marketplace, checked as of 2026-09-04, and they have no documented relationship to inbox placement. A $500 theme with a 4.9 rating authenticates your domain no better than a $100 theme with a 4.2 rating, because authentication happens outside the theme entirely.
If deliverability is your actual problem, go check your domain’s SPF, DKIM, and DMARC records and confirm your DKIM key meets the 1024-bit minimum Google names, rather than opening your theme customizer again. Fix the storefront speed and theme choice separately, based on the Core Web Vitals and pricing data above, because they solve a different problem than the one that put your last campaign in spam.
No. Deliverability to Gmail and Yahoo is decided by sender authentication records like SPF, DKIM, and DMARC, plus sending reputation and complaint rates, none of which live in theme files. A search of Dawn's 351 files and Horizon's 484 files finds the words 'stores' and 'rules' scattered in locale files, CSS, and JavaScript utilities, not in any section that configures outbound mail. If you are troubleshooting spam placement, the fix is in your email platform's domain authentication settings, not your theme customizer.
Google's sender guidelines say that starting February 1, 2024, all senders emailing Gmail accounts must meet the requirements described in that document. Senders who send more than 5,000 messages per day to Gmail accounts must meet an additional, stricter section built for higher volume. Google also states that sending to personal Gmail accounts requires a DKIM key of 1024 bits or longer, which is a specific, checkable number, not a vague recommendation.
No such setting exists in either theme's measured code. The word 'rules' appears in Dawn's assets/base.css, assets/component-card.css, assets/global.js, and assets/product-info.js, and in Horizon's assets/base.css, assets/product-form.js, assets/volume-pricing-info.js, and blocks/buy-buttons.liquid, but in every case it is CSS class naming or JavaScript logic for product display, not mail authentication. Those records are set at the domain's DNS level and inside your email sending platform, entirely outside the Shopify theme layer.
Because a slow or broken storefront hurts the signup and checkout flow that builds your list in the first place, even though it has no direct effect on inbox placement. Across 247 themes with sufficient mobile data, the median share passing all Core Web Vitals is 85.5%, with the best theme in the market at 98.6% and the worst at 46.1%. On desktop, across 199 themes with enough data, the median is 86.2%, the best at 99.2%, and the worst at 30.3%. Those numbers describe page speed and stability for real visitors measured in July 2026, which is a separate problem from whether Gmail accepts your campaign.
There is no data connecting theme price or rating to deliverability. The market's median theme price is $300 across a $100 to $500 range, and the average rating is 4.53 out of 5 across 308 rated themes with a median of 23 reviews, but these figures come from a theme marketplace listing, not from any email sending metric. Treat theme choice and email authentication as two unrelated decisions.