Reporting & research on Shopify and ecommerce
Merchants ask this because they want to know if paying once means owning something forever, and the honest answer is that the purchase itself is one-time but the setting nobody names on a details page is code, not licensing, so this piece checked the theme files instead of the marketing copy.
Most people typing “are Shopify themes a one-time purchase” are really asking something narrower: is there a hidden subscription buried in a settings panel, a recurring toggle labeled something like “purchase term” that will start billing them later. That specific setting does not exist in the two themes checked at the code level for this piece, Dawn and Horizon, and the word “purchase” barely shows up in Dawn at all. What follows is what the code and the market data actually say, instead of what a sales page implies.
Across a combined ranking of 329 themes, the median price is $300, with prices running from $100 to $500. That’s a purchase price, paid to unlock the theme file for a store, and nothing in Shopify’s published Theme Store requirements describes a recurring theme fee. The requirements instead set performance and accessibility floors: a minimum average Lighthouse performance score of 60 across a theme’s product, collection, and home page for both desktop and mobile, and a minimum average Lighthouse accessibility score of 90 across those same three page types, also for both desktop and mobile. Those are one-time gates a theme clears before it’s even listed, not billing terms a merchant needs to track month to month.
So when someone asks if the purchase is one-time, the pricing side of the answer is yes, sitting somewhere in that $100 to $500 band with $300 as the market midpoint. The part worth checking further is whether “one-time purchase” is also a phrase living inside the theme’s actual settings, controlling something a merchant can configure. It is not, at least not in the two themes inspected here.
This is the part a details page won’t show. In Dawn, at commit 258f00f from 2026-08-10, the word “time” appears in 73 of the theme’s 351 files. That sounds like a lot until you see where: README.md, assets/cart-drawer.js, assets/cart.js, and assets/component-rating.css. Every one of those is either documentation or code that manages cart timing behavior and star-rating display, not a licensing or purchase-frequency setting. There is no dedicated section in Dawn for anything resembling a one-time-purchase configuration.
Horizon carries more surface area for both words. “Time” appears in 125 of Horizon’s 484 files, at commit 8b42ace from 2026-08-31, spread across README.md, assets/anchored-popover.js, assets/announcement-bar.js, and assets/cart-icon.js. Those are popover positioning, announcement bar scheduling, and cart icon behavior. Separately, “purchase” appears in 25 of Horizon’s 484 files, and here the trail runs through assets/standard-events.d.ts and a stack of locale schema files: locales/ar.schema.json, locales/cs.schema.json, locales/da.schema.json. That’s purchase-event tracking for analytics and translated schema labels, not a licensing toggle a merchant would ever open in the theme editor.
The honest way to say this: neither theme has a settings section built around one-time purchase logic. The words exist because cart code and event tracking naturally use them, and that’s the whole explanation.
| Theme | Word checked | Files containing it | Where it actually lives |
|---|---|---|---|
| Dawn (commit 258f00f) | “time” | 73 of 351 | README.md, cart-drawer.js, cart.js, component-rating.css |
| Horizon (commit 8b42ace) | “time” | 125 of 484 | README.md, anchored-popover.js, announcement-bar.js, cart-icon.js |
| Horizon (commit 8b42ace) | “purchase” | 25 of 484 | standard-events.d.ts, ar.schema.json, cs.schema.json, da.schema.json |
Method: each theme’s full repository was searched file by file for the exact word, counted against its total file count, with the source commit and date recorded so the count can be reproduced later against the same snapshot.
Since price doesn’t predict what happens after checkout, it helps to look at what does vary. Real visitor data from July 2026, drawn from CrUX rather than a lab test, shows the median share of mobile visits passing all Core Web Vitals sits at 85.5% across themes with sufficient data, 247 of them. The best-performing theme in the market reaches 98.6% on mobile, the worst sits at 46.1%. Desktop tells a similar story with a wider low end: the median is 86.2% across 199 themes with enough data, the best theme hits 99.2%, and the worst drops to 30.3%.
Ratings show a comparable spread without matching to price. The market average rating is 4.53 out of 5 across 308 themes, with a median of 23 reviews per theme. A merchant paying the $300 median price has no guarantee of landing near the 98.6% mobile pass rate rather than the 46.1% one, because nothing in these datasets links price tier to performance outcome. Categories like Home, Clothing, Electronics, Jewelry & Access., and Food and drink all draw from this same combined pool, and none of them carry a separate pricing model tied to purchase frequency.
UTD is one vendor among the 329 themes in this combined ranking, and its presets appear in the same rating and pricing pool as everyone else’s, with the storefront listing browsable directly at themes.shopify.com/themes?q=utd. Nothing in the facts gathered here breaks out UTD’s individual Core Web Vitals pass rate or review count separately from the market figures already cited, so no theme-specific claim beyond its presence in the ranking can be made about it.
If a listing anywhere claims a theme has a “one-time purchase setting,” open the theme’s actual files or ask the vendor for the specific file path before paying, the way this piece traced Dawn’s word count to cart-drawer.js and Horizon’s to standard-events.d.ts. Then judge the theme on the numbers that actually move after checkout, the Core Web Vitals pass rate and the review count, not on a phrase that doesn’t correspond to any setting either theme actually ships.
The theme itself is typically a one-time charge, and the median price across 329 themes tracked is $300 within a $100 to $500 range. Shopify's own store requirements don't mention recurring theme fees at all; they set a minimum average Lighthouse performance score of 60 and a minimum average Lighthouse accessibility score of 90 across product, collection, and home pages, for both desktop and mobile. Those are one-time gates a theme has to clear to get listed, not billing terms. Your recurring Shopify plan cost is separate from whatever you paid for the theme file.
No. In Dawn, checked at commit 258f00f from 2026-08-10, the word 'time' appears in 73 of 351 files, but every instance lives in README.md, assets/cart-drawer.js, assets/cart.js, and assets/component-rating.css, none of which touch licensing. In Horizon, checked at commit 8b42ace from 2026-08-31, 'time' appears in 125 of 484 files and 'purchase' appears in 25 of 484 files, concentrated in assets/anchored-popover.js, assets/announcement-bar.js, assets/cart-icon.js, assets/standard-events.d.ts, and locale schema files like locales/ar.schema.json and locales/cs.schema.json. None of these are a licensing section; they're cart timing and purchase-event tracking code.
Because a one-time price says nothing about ongoing quality. The market-wide average rating sits at 4.53 out of 5 across 308 themes, with a median of 23 reviews per theme, and that spread reflects how a theme performs after purchase, not what it cost to buy. Two themes both priced in the $100 to $500 range can differ sharply in real-world speed, since mobile Core Web Vitals pass rates alone range from 46.1% to 98.6% among 247 themes with sufficient data.
The facts here don't establish that link. What's known is the median price is $300, the median mobile pass rate is 85.5%, and the median desktop pass rate is 86.2%, each drawn from a separate dataset. There is no fact tying price tier to Core Web Vitals outcome, so any claim that spending more guarantees a faster theme would be invented, and this article won't make it.
Check the actual code rather than trust the phrase. In both Dawn and Horizon, the words 'time' and 'purchase' exist in the codebase but only inside cart, popover, announcement, and event-tracking files, never inside a discrete licensing or purchase-model section. If a theme's documentation claims a dedicated one-time-purchase setting, look for the actual file path before believing it, the same way this piece did with Dawn's cart-drawer.js and Horizon's standard-events.d.ts.