Skip to main content

Modules overview

A Growthify module is a unit of capability that can be independently gated by plan, switched on or off by the merchant, and — when it renders on the storefront — lazy-loaded as its own runtime. Modules are the organising idea behind the whole product: they are what a plan grants, what the loader fetches, and what a merchant reasons about.

Two module lists, and why both are correct​

Documentation elsewhere quotes "16 modules" and "15 modules". Both are accurate, and they are not the same list.

The 16 entitlement module ids​

These are what the application actually gates on. Each becomes an Entitlement row when a shop installs, each has a required plan, and each has a default on/off state.

Module idNameRequired planOn by default
popupPopup BuilderFreeyes
reviewsProduct ReviewsFreeyes
wishlistWishlistFreeyes
cookieCookie ConsentFreeyes
marketingMarketing & ConversionFreeyes
merchandisingMerchandisingFreeyes
complianceCompliance & GatingFreeyes
bundlesProduct BundlesProno
cartSmart CartProno
fulfillmentFulfillmentProno
i18nInternationalizationProno
seoSEO SuiteProno
reportsAdvanced ReportsGrowthno
aiAI AssistantGrowthno
b2bB2B & WholesaleGrowthno
loyaltyLoyalty & RewardsGrowthno

The 15 numbered module specifications​

These are the engineering documents, numbered 00–14: platform, loader, analytics-errors, popup, reviews, wishlist, bundles, cart, consent, upsells, reports, analytics, OTP/COD, page builder, sourcing.

The two lists diverge for good reasons. The specs include infrastructure that no plan can withhold — the platform and the loader are not features you can sell or revoke. The entitlement list includes capability groups such as marketing, merchandising and b2b that span several specs and several admin screens. Whenever this site quotes a number, it names which list it means.

Who this page is for​

  • Merchants deciding which modules to enable and what their plan includes.
  • Agencies planning a rollout across client stores with different tiers.
  • Developers who need to know what the gating unit is before reading the entitlement code.

The module map​

#ModuleWhat it doesPrimary surface
00PlatformOAuth, billing, webhooks, sessions, the entitlement systemAdmin + server
01LoaderThe lazy module loader booted by the app embedStorefront
02Analytics-ErrorsEvent tracking and error-reporting plumbingCross-cutting
03PopupsEmail capture, spin-to-win, exit intent, announcementsStorefront
04ReviewsStar ratings, moderation, verified-purchase badgesStorefront + admin
05WishlistSave for later, shareable lists, recently viewedStorefront
06BundlesQuantity breaks, BOGO, mix-and-matchStorefront + checkout
07CartCart drawer, free-shipping bar, cross-sell, add-onsStorefront
08ConsentGDPR cookie banner, language packs, audit logStorefront + compliance
09UpsellsPost-purchase and thank-you-page offersCheckout extension
10ReportsThe report engine and exportsAdmin
11AnalyticsUsage meters, funnels, trendsAdmin
12OTP / CODPhone verification and cash-on-delivery controlsStorefront + admin
13Page BuilderSection-based landing pagesStorefront
14SourcingProduct sourcing and supplier syncAdmin

How a module becomes visible to a shopper​

Four things must all be true. Missing any one is the cause of nearly every "it is not working" report:

  1. Your plan includes it — otherwise the toggle explains which plan does.
  2. You have enabled it in the Modules hub.
  3. The Growthify Embed app embed is on in your theme.
  4. The module's theme block is placed where you want it to render.

Steps 1 and 2 are two separate facts, and the Merchant API reports them separately as hasAccess and isEnabled. A module can legitimately be available and switched off.

Beyond the modules: 51 admin feature screens​

The embedded admin also ships 51 feature screens covering SEO, marketing, merchandising, fulfilment and operations — seo-optimizer, email-marketing, sms-marketing, loyalty-rewards, subscriptions, wholesale-b2b, store-locator, tax-calculator, sales-forecasting and more. Each is a real route with a loader, an action and persistence.

A feature screen is a configuration surface; a module is the gating and loading unit. Several screens often configure capabilities belonging to one entitlement module — which is exactly why the screen count and the module count are different numbers measuring different things. See Admin features.

What modules do not do​

  • Enabling a module does not place its block. Except for site-wide surfaces such as consent and popups, you still add the block in the Theme Editor.
  • Modules are not separate apps. They share one install, one subscription, one database and one admin.
  • A module cannot be bought individually. Access follows the plan tier, not an à-la-carte purchase.
  • Disabling a module does not delete its data. Reviews and wishlist items persist; they stop rendering.
  • Some modules depend on your Shopify plan for their checkout-level surfaces, independently of your Growthify tier.

FAQ​

Why are there 16 modules in one list and 15 in another?​

Because they are different lists — 16 entitlement module ids the app gates on, and 15 numbered engineering specifications. The specs include ungateable infrastructure; the entitlement list includes capability groups spanning several specs. Both lists appear in full above.

Do I have to use every module?​

No. Modules toggle independently, and a disabled module ships no storefront JavaScript. Most stores run a handful. Turning one off removes its cost rather than hiding its settings.

Which modules are available on the Free plan?​

popup, reviews, wishlist, cookie, marketing, merchandising and compliance — all available from Free and on by default. bundles, cart, fulfillment, i18n and seo need Pro; reports, ai, b2b and loyalty need Growth.

What is the difference between a module and an admin feature screen?​

A module is the unit of plan gating and runtime loading. A feature screen is a configuration surface. There are 51 screens, and several often configure one module's capabilities.

Does enabling a module immediately change my storefront?​

Not by itself. Enabling makes it available and lets its runtime load, but most modules render through a theme block you still place. Consent and popups are the usual exceptions, since they render site-wide.

Can a module be available but switched off?​

Yes, and that is an ordinary state — hasAccess and isEnabled are reported as two separate facts.

What happens to a module's data if I downgrade?​

The data remains; access to the module locks on the next request after the subscription webhook updates your plan. Re-upgrading restores access to the same data.