Shogun vs. Theme Sections: Buy the Builder or Build the Library?
Building an OS 2.0 section library beats Shogun once dev support exists: one $20,000–$45,000 build (Deploi estimate, illustrative) ends the subscription, and pages persist as JSON in your theme, not app structures. Shogun's own 2025 move, unbundling A/B testing into a paid add-on, shows how rented feature sets shift underneath you (July 2026 research). Buy Shogun only with zero dev support, and price the add-ons before signing.
Your profile — see how the verdict shifts
- Confidence
- High — Dev support decides the lane structurally, and Shogun's 2025 repackaging added measured feature volatility to the buy side of the scorecard (July 2026 research)
- Reference scenario
- $20M–$100M GMV · in-house marketing team · agency dev support · single storefront
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| No reachable dev support (any revenue) | BUY | Shogun keeps marketing shipping pages with nobody touching the theme. Price the A/B add-on separately if testing matters; the 2025 unbundling moved it out of core plans (July 2026 research). |
| Dev support · single storefront | BUILD | The reference scenario: a section library gives marketing theme-editor self-serve while every page stays portable JSON. The subscription would buy a canvas you no longer need. |
| Multi-store brand standardizing one builder | CUSTOMIZE | Shogun's cross-store consistency pitch is real, but a shared theme carrying one section library syncs the same system as owned code. Fence the builder to stores with no dev coverage. |
| Testing program that assumed bundled A/B | BUILD | The bundled-testing argument died with the 2025 unbundling. Run experiments through a dedicated testing tool on owned section pages instead of paying a builder plus an add-on. |
What Shogun vs. an OS 2.0 theme section library Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Paid traffic converts on landing pages, so speed and message-match there move ROAS directly; the builder runtime taxes those exact URLs. |
| Operational efficiency | High | Both lanes remove the dev-ticket queue between brief and live page; the matchup decides whether that capability is rented monthly or owned outright. |
| Data & insight | Medium | Owned pages are versionable JSON any future stack can read; builder pages answer only to the vendor's editor. |
| Revenue — indirect | Medium | Evergreen landing pages compound as SEO assets when they live as fast theme pages on your own URL structure. |
| Customer experience | Medium | Presets and locked tokens keep self-serve pages consistent; a free canvas trades consistency for speed unless someone polices it. |
Spend ceiling: Pay for exactly one thing: marketing shipping pages without dev tickets. Once the theme editor delivers that through owned sections, a builder subscription plus add-ons is rent on a solved problem.
What buying enables (top apps)
- + Pages live within days, across one store or many, with no theme work required
- + A managed editor: breakpoints, widget fixes, and platform compatibility on the vendor's sprint, not yours
- + One page workflow for multi-store teams before any shared theme exists
- + Zero-dev self-serve for marketing, the builder category's honest core promise
What building additionally unlocks
- + Pages as portable JSON that survive redesigns, replatforms, and every vendor decision
- + A feature set no renewal can repackage; the 2025 A/B unbundling can't happen to code you own (July 2026 research)
- + Server-rendered speed on the exact URLs where ad spend lands
- + One design system serving landing pages, homepage, and PDPs, beyond the builder's page scope
Find Your Verdict in 3 Questions
Does marketing have reachable dev support, agency retainer or in-house?
Yes: Go to question 2.
No: Your verdict: BUY — Shogun is how pages ship this quarter; price the A/B add-on separately and cap the page count for the eventual exit.
Is an A/B testing program part of why you'd pay for a builder?
Yes: Your verdict: BUILD — the 2025 unbundling broke that bundle; run tests through a dedicated tool on owned section pages instead of builder plus add-on.
No: Go to question 3.
Are you standardizing page production across multiple storefronts without a shared theme?
Yes: Your verdict: CUSTOMIZE — keep Shogun on stores with no dev coverage, and build the shared section library as the end state.
No: Your verdict: BUILD — a single storefront with dev support is the library's home turf; every page stays yours.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | Shogun publishes pages the week you install it; the section library needs an estimated 6–10 weeks of design and build before marketing self-serves (Deploi estimate, illustrative). | ||
| Recurring fees | Mid-market builder tiers plus the now-separate A/B add-on stack into a real annual line; the library has no subscription at all. | ||
| Maintenance & upgrades | The vendor maintains the editor, but widgets breaking at theme updates and breakpoints stays a community-documented pattern; the library moves with the theme at ~15–20% of build cost per year (Deploi estimate). | ||
| Switching & exit | Shogun pages live in app structures, so exit means a page-by-page hand rebuild; JSON templates survive redesigns and vendor changes untouched. | ||
| Risk | |||
| Vendor risk | The 2025 A/B unbundling is this page's receipt: features you priced into a plan can move to add-ons at renewal (July 2026 research); the owned lane has no renewal. | ||
| Security & compliance surface | Builders handle storefront content rather than customer data; the surface is modest, but still one more script on paid-landing URLs. | ||
| Platform-deprecation exposure | OS 2.0 sections and JSON templates are the sanctioned surface Shopify keeps investing in; a builder tracks every platform change from a layer above the theme. | ||
| Value | |||
| Fit to requirement | Honest split: Shogun suits teams standardizing page production across stores; the library suits teams standardizing the brand system itself. | ||
| Time to market | Days against 6–10 weeks; the builder's genuine, unarguable win, and worth paying for exactly as long as it stays true. | ||
| Performance & scale | Builder markup and runtime carry the documented app-bloat speed tax where ad spend lands (July 2026 research); sections render server-side with nothing attached. | ||
| Data ownership & AI-readiness | Section settings live as versionable JSON in your theme and repo; builder pages are readable only through the vendor's editor. | ||
| Focus & opportunity cost | The library consumes a design-and-dev quarter; Shogun frees that attention, which is the honest argument for renting while the team is small. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shogun | Live — Unbundled A/B testing to a paid add-on in 2025: the category's feature volatility on display (July 2026 research) | Mid-market tiers; A/B testing now an add-on | Multi-store teams that want one page workflow everywhere |
| PageFly | Live — The category's volume leader on the App Store | Free tier + slot/page-tiered | Price-checking the builder lane before committing |
| GemPages | Live — PageFly's closest peer, with template-library depth | Tiered | Template-first teams comparing builders |
| Theme section library (Online Store 2.0) | Build lane — The other column on this page: 12–20 owned, flexible sections in your theme | $20,000–$45,000 one-time (Deploi estimate, illustrative); no subscription | Owning the page system, the pages, and the renewal-proof feature set |
The Build Path
- Flexible section library on Online Store 2.0: A designed set of 12–20 flexible sections with presets and locked brand tokens. Marketing composes pages in the theme editor, saved as JSON templates you own.
- Owned test surfaces for experiments: Run A/B experiments with a dedicated testing tool on section-built pages, so testing capability never depends on a builder's plan bundling again.
- Staged Shogun exit: Audit the live page list, archive dead campaigns, and rebuild evergreen winners as sections first; the rest expires in place and never gets rebuilt.
- Effort band
- $20,000–$45,000 section library, Deploi estimate (illustrative); usually the $25–75K contact-form band
- Typical timeline
- 6–10 weeks (Deploi estimate, illustrative), tokens and core sections first so early pages ship before the full library lands
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate), about $3,000–$9,000/yr (illustrative) for theme-update compatibility and new sections. No subscription, no add-ons.
- What you own — and what you take on
- You own: the pages as JSON, the design system, and a testing stack independent of any builder plan. You take on: section requests arriving as dev work, plus the upkeep above.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$3,500 (install + initial builds) | $20,000–$45,000 |
| Years 1–3 (recurring) | $5,400–$14,400 (subscription, add-on excluded) | $9,000–$27,000 (maintenance) |
| 3-year total | ≈$5,400–$17,900, plus kept pages rebuilt at exit | ≈$29,000–$72,000, pages stay yours |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: a Shogun mid-market tier held flat, A/B add-on excluded; adding it raises the app line.
- † Build path: 12–20-section library with staged migration and marketing enablement; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Feature repackaging at renewal: the 2025 A/B unbundling moved a bundled capability to a billed add-on (July 2026 research); re-quote your stack yearly
- — No export path: leaving Shogun means rebuilding every kept page by hand as sections (community-reported pattern)
- — The speed tax: builder markup and runtime weigh on the paid-landing URLs that fund growth (documented recurring pattern)
- — Widgets break at theme updates and breakpoints, and fixes queue behind vendor support (community-reported theme)
On the build path
- — Scope creep: the library becomes a design system; lock tokens and the section list up front or the estimate doubles
- — Adoption risk: an unloved library sends marketing back to a builder trial within a quarter
- — Testing isn't free on the owned lane either; budget the dedicated testing tool as its own line
- — ~15–20% of build cost per year in upkeep (Deploi estimate): cheaper than subscription plus add-ons, not zero
What Merchants Say
The 2025 repackaging stories share one arc: a feature the team had priced into the plan reappeared as a billed add-on at renewal, and the whole stack got re-quoted mid-year.
Builder widgets misbehaving after theme updates and at odd breakpoints remains the category's standing complaint, with fixes waiting on vendor support.
If You Change Your Mind Later
If you bought and outgrow it
Budget the Shogun exit as a project: pages live in app structures with no path into sections, so every kept page is rebuilt by hand. Keep the bill small from day one. Audit the page list quarterly, archive dead campaigns, and rebuild evergreen winners into the theme while the subscription still runs. Re-verify plan bundling at each renewal so add-on creep never surprises you.
If you built and want out
Nothing strands: sections and JSON templates ride in your theme through redesigns and replatforms with no vendor in the loop. Retreat is cheap too. A store that later needs cross-store page production can re-add a builder for that lane while the library keeps the brand system; all the owned work survives.
When This Answer Changes
We're watching for:
- ▸ Further Shogun repackaging after the 2025 A/B unbundling; re-verify what your tier includes at every renewal (July 2026 research)
- ▸ Shopify's theme editor absorbing more builder features; each flexible-section release shrinks the builder's delta
- ▸ Your live Shogun page count crossing roughly 30–50 pages; past that line the exit rebuild bill starts driving the decision
Verdict change log:
- 2025-01-01Date anchored to the year of the repackaging (2025; exact month varies by plan). The unbundling matters here as evidence: features inside a subscription can move to separate line items at renewal, a risk owned sections never carry.
Common Questions
Is a theme section library a real Shogun alternative?
Yes: a 12–20-section OS 2.0 library gives marketing the same self-serve page assembly inside Shopify's theme editor, with every page stored as portable JSON you own. Experiments move to a dedicated testing tool instead of a builder add-on. The trade is the blank canvas; teams working inside brand guidelines rarely notice, and the pages render server-side.
What did Shogun's A/B testing unbundling change?
Shogun moved A/B testing out of its core page-builder plans into a paid add-on in 2025 (July 2026 research). Teams that bought Shogun as builder-plus-testing in one line now price two. The lesson for this matchup is structural: rented feature sets can be repackaged at renewal, while a section library's capabilities can't be moved behind a new invoice.
When does Shogun beat building a section library?
Shogun wins with zero reachable dev support, and for multi-store teams that need one page workflow across storefronts before any shared theme exists. Speed is the other honest case: pages ship within days of install, against 6–10 library build weeks (Deploi estimate, illustrative). With a dev bench and a single storefront, the library wins the three-year math.
Your Next Steps
If you're going with BUILD(matches your selected profile)
- Audit live Shogun pages; tag each as evergreen, campaign, or dead, and archive the dead ones now
- Price your testing stack on its own; since the 2025 unbundling, builder and experiments are separate line items anyway (July 2026 research)
- Design the 12–20-section library against locked brand tokens, presets over free inputs
- Rebuild evergreen top performers as sections first for the paid-traffic speed win
- Schedule marketing enablement before cutover; success is marketing never opening Shogun again
If you're going with BUY
- Get current plan bundling in writing, A/B add-on included, before signing
- Cap the page count and audit it quarterly; every live page is future rebuild work
- Check mobile Core Web Vitals on builder pages before scaling spend into them
- Book a re-decision at renewal or the day dev support arrives, whichever lands first
Official Docs & Sources
- Theme architecture — shopify.dev
- Blogs — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Shopify Landing Page Builders: Buy an App or Build a Section Library?
Landing page builders win only below the mid-market band; with dev support, a section library keeps every page in your theme.
Should You Go Headless on Shopify or Stay on Your Theme?
A headless storefront pays off for a small minority of mid-market Shopify merchants; a well-built theme delivers most of the gains without the replatform.
Shopify Theme Sections: Buy Premium or Build a Section Library?
A custom theme section library wins at mid-market campaign tempo; below the floor, a premium theme is the right call.
Should You Build or Buy Your Blog and Editorial Hub on Shopify?
An editorial hub favors building: a headless CMS rendered into your theme turns content into structured, citable data; builder apps trade layout for lock-in.
Build or Buy Performance Monitoring & App Audits on Shopify?
Measurement is free on Shopify; storefront speed comes from an audit-and-remediation program, not a speed app.
Ready to stop renting your page system?
We build section libraries that replace builder subscriptions: Nudestix runs on a custom Shopify 2.0 theme we built on native features to cut third-party apps. We'll scope your library, stage the Shogun migration, and price your testing stack honestly. If Shogun still fits your team, we'll tell you.
Contact us todayVerdict scored for the reference scenario above. This page decides the named Shogun matchup; the category-wide landing page builder decision is its own page. Estimates are not quotes; Shogun pricing and bundling are banded re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.