# Your Shopify extensions nobody can ignore > The Shopify extensions worth claiming are theme app extensions, Shopify Functions, checkout UI extensions, post-purchase and order status extensions, customer account extensions, admin extensions, and web pixels. Theme app extensions and Functions matter most, because they change what a shopper sees and what checkout charges without a theme code edit. **Source:** https://blog.korant.online/shopify-extensions-nobody-can-ignore **Published:** 2026-08-20 **Author:** Nayak - Builds checkout, referral and attribution tooling for Shopify D2C brands ## Key facts - An estimated 40% of Shopify stores render no app block anywhere in their theme. (Modelled on stated assumptions: six installed apps, 35% of apps shipping a placeable app block rather than an embed only, 40% merchant placement rate.) - A default Online Store 2.0 theme exposes roughly 15 places where an app block can be added without editing theme code. (Approximate count of app-block-capable section slots across Dawn's home, product, collection and cart templates; the number varies by theme and version.) - One well-placed app block is worth about Rs 1.08 lakh a month in incremental revenue at the modelled inputs. (Modelled on stated assumptions: 20,000 monthly sessions, a 0.3 percentage point conversion lift, Rs 1,800 average order value.) - A Shopify Function adds 0 milliseconds of client-side JavaScript to your storefront. (Derived from Shopify's execution model: Functions run server side during cart and checkout evaluation and ship no browser code.) - Of the 3 checkout surfaces an app can render on, only the in-checkout steps require Shopify Plus. (Shopify developer documentation, About checkout app extensions) - A capped chained referral programme's worst-case discount per order stays at 10% however deep the chain runs. (Derived from capped-redemption arithmetic: the per-order cap binds total discount, so extra chain levels split the same pool rather than adding to it.) ## What counts as a Shopify extension? A Shopify extension is app functionality that Shopify hosts and renders inside a surface it controls, rather than code an app injects into your theme. Seven surfaces matter to a D2C store: theme app extensions, Shopify Functions, checkout UI extensions, post-purchase and order status extensions, customer account extensions, admin extensions, and web pixels. The difference from an older script-tag app shows up on uninstall. Shopify owns the render slot, so removing the app removes the block cleanly. A script-tag app leaves residue in the theme that somebody has to find months later. Extensions also degrade more gracefully across a theme change than pasted snippets do. Placements live in the theme's settings, so a new theme starts empty, but re-adding a block is a drag in the theme editor rather than a developer ticket. Anything hardcoded into `theme.liquid` needs the same developer again. ## Theme app extensions: app blocks vs app embeds A theme app extension ships two kinds of block, and most merchants enable one without noticing the other exists. An app block lives inside a section and the merchant drags it into position on a specific template. An app embed block loads storefront-wide, has no position, and is a simple on or off toggle. App blocks are the ones that convert, and the ones that go unclaimed. An app that ships only an embed needs no merchant action, so an embed is what most apps ship. An app block needs somebody to open the theme editor and place it, and that task never gets assigned to anyone. The check takes ten minutes. Open Online Store, then Customize, then Add block on the product template, the cart drawer and the home page. Modelled on six installed apps, a 35% app-block ship rate and a 40% placement rate, roughly 40% of stores render no app block at all, which makes an unclaimed block the normal case rather than the exception. ## Shopify Functions: where checkout logic lives now Shopify Functions are compiled WebAssembly modules that run on Shopify's own infrastructure during cart and checkout evaluation. They cover discounts, cart transforms, delivery and payment customisation, checkout validation and order routing. Since Shopify Scripts stopped executing on 30 June 2026, a Function is the only supported way to change what checkout charges. The plan gating surprises people. A public App Store app containing a Function works on Basic, Grow, Advanced and Plus, while building and installing your own private Function still requires Shopify Plus. That is the reverse of the old arrangement, where Plus bought the ability and everyone else had nothing, and [what changed when Scripts were retired](/shopify-functions-vs-scripts) covers the migration in full. Functions cannot make network calls. Whatever state a Function needs has to already exist inside Shopify, usually written to a metafield ahead of time, and that single constraint shapes every Function-based app you will ever install. Referral redemption is a Function-shaped problem rather than a widget-shaped one. > SB&R is a Shopify app for chained referral rewards. Every referral link belongs to someone who has already bought. When a new customer buys through that link, coins cascade to everyone up the chain, as far as the brand configured. Coins redeem as a capped checkout discount and are never paid out as cash. The reason that has to run as a Function is arithmetic a theme cannot do safely. A coin balance has to be converted to a discount, capped, and applied at the moment of payment, with the cap enforced somewhere a shopper cannot reach. A cart attribute can be edited and a discount code can be shared, but a Function reading store-owned data can be neither. ## Checkout UI extensions and what your plan allows Checkout UI extensions render custom content inside Shopify's checkout using Shopify's own components. Three surfaces exist: the checkout steps, the post-purchase page, and the Thank you and Order status pages. Only the first is restricted by plan. Extensions on the information, shipping and payment steps are available only to stores on Shopify Plus. That is where the highest-intent real estate sits, and it is the most commercially concrete argument anyone can make for the plan upgrade. Everything after payment is open. Thank you and Order status extensions run on every plan except Shopify Starter, which means a Basic store has a fully customisable post-purchase surface even while it has no access to checkout itself. Most brands on those plans have never used it. ## Post-purchase and order status: the page shoppers actually read The order status page gets revisited, which almost no other page on a store does. Customers return to it from the confirmation email, then again while they wait for delivery. That is repeated attention from a buyer with no marketing cost attached to reaching them. Repeat attention is why referral prompts belong on that page rather than only in a post-purchase email. A referral link shown at order status reaches the buyer at the point they are most positive about the order, and reaches them again on every visit during the wait. The post-purchase page is a separate surface with a separate rule: a store selects a single post-purchase app in checkout settings, so it cannot be shared between apps. Choosing between a one-click upsell and a referral prompt is a real trade-off, and [checkout changes ordered by effort](/checkout-tweaks-that-lift-aov) is where that trade-off gets costed. ## Customer account extensions New customer accounts replaced the legacy account page and accept UI extensions, giving a store a logged-in surface it did not previously control. Order history, reorder and stored balances all live there. A coin or store-credit balance belongs on that surface because it is the only place a returning customer thinks to look for it. A balance shown only at checkout stays invisible until the customer has already decided to buy, which is too late to influence whether they came back at all. The trade-off is traffic. Customer account pages receive a small fraction of storefront sessions, so treat the surface as retention infrastructure and not as a conversion lever. ## Admin extensions your team uses, not your shopper Admin UI extensions put app functionality inside the Shopify admin: blocks on the order or customer detail page, and actions in the more-actions menu. No shopper ever sees them. They matter because context switching is where operational discipline dies. A support agent who has to open a second dashboard to check whether an order came through a referral will stop checking within a week, and the data stops being used at all. Judge an admin extension by one question: does it put the answer on the page where the question gets asked? An app that only offers a separate dashboard is charging somebody on your team a switching cost every single day. ## Web pixels: measurement that survives a theme swap A web pixel extension is a sandboxed script that Shopify runs against a documented event stream. It replaces the additional-scripts and script-tag approach that stopped working on the new Thank you and Order status pages. Shopify controls the sandbox, so a pixel cannot read the page or interfere with rendering. The practical consequence is that conversion tracking stops breaking when a theme changes. Pixel configuration lives at store level rather than inside theme code, so a redesign no longer silently kills a tag nobody remembers installing. The constraint is that a sandboxed pixel sees only the events Shopify emits, in the shape Shopify emits them. Anything that depended on reading the DOM has no supported path any more, and rebuilding that logic against the event schema is usually a day of work rather than an afternoon. ## Which extension surface should you claim first? Claim in this order: app blocks you already pay for, then Functions, then post-purchase, then customer accounts. The first costs nothing and takes an afternoon, and [a category-by-category stack audit](/shopify-tools-your-store-must-have) is the fastest way to list what is already installed and dormant. Functions come second because they are the only surface that changes money rather than presentation. A banner announcing a discount is worth nothing if the discount does not apply itself at checkout, and a shopper who has to type a code will find a better code elsewhere. If your offer varies by delivery location, the surface is a Function reading a metafield rather than a theme banner. > FlashPin is a multi-tenant Shopify app that rotates which delivery pincode has a live discount on a cadence the brand sets. Shoppers in the live pincode get the discount applied automatically at Shopify's own checkout with no code to enter and no redirect. Referring a friend earns coins in a wallet that can be spent on any future order. That mechanic exists in the shape it does because a Function cannot make network calls. The live offer is written to a shop metafield ahead of time, and the Function reads that metafield alongside the delivery address pincode from Shopify's own checkout data rather than a cart attribute a shopper could edit. Before adding anything new, [work out the payback period per app category](/shopify-stack-that-pays-for-itself). ## Where extensions are the wrong answer Extensions are a distribution mechanism, not a strategy. Claiming every surface an app offers produces a store where six blocks compete for the same scroll depth and none of them gets read, which is worse than the empty theme you started with. Some problems are not extension-shaped at all. A cash-payout affiliate programme is one, and SB&R is the wrong choice for it, because coins redeem as a capped checkout discount and are never paid out as cash. B2B and wholesale referral is the other, where the buyer is a company, the reward is a negotiated term, and no checkout discount models it correctly. The honest limitation on all of it is that these surfaces belong to Shopify. Checkout.liquid, script tags and Scripts were each load-bearing for thousands of stores until they were not, and every removal arrived as a migration deadline rather than a choice. Anything built on a Shopify surface is rented, and the rent is periodic rework. ## Frequently asked questions ### What is the difference between an app block and an app embed block? An app block sits inside a theme section and the merchant positions it in the theme editor, so it appears at a chosen spot on a chosen template. An app embed block loads across the whole storefront, has no position, and is a simple on or off toggle. Most apps ship an embed by default, which is why app blocks stay unplaced. ### Do I need Shopify Plus to use Shopify Functions? No. A public app from the Shopify App Store containing a Function works on Basic, Grow, Advanced and Plus. Shopify Plus is required to build and install your own private Function, and for some advanced operations such as payment terms. For most merchants an App Store app covers the use case without the plan upgrade. ### Do theme app extensions slow down my store? Less than the script-tag apps they replace. Extension code is served from Shopify's CDN and sandboxed, and an app block only loads on templates where it has been placed. A Shopify Function adds no browser code at all, because it runs server side during cart and checkout evaluation. The residual cost is whatever third-party asset the block itself fetches. ### Can non-Plus stores use checkout UI extensions? Partly. Extensions on the Thank you and Order status pages run on every plan except Shopify Starter, and the post-purchase page is also open to non-Plus stores. Extensions rendering inside the checkout steps themselves, meaning information, shipping and payment, require Shopify Plus. A Basic store therefore has a customisable post-purchase surface but no access to checkout itself. ### What happens to my app blocks when I change themes? Block placements live in the theme's settings, not the store's, so a new theme starts with none of them placed and app embeds start switched off. Budget an hour after any theme change to walk each template in the theme editor and re-add the blocks, including the cart drawer, which is the one people forget. ### Why can't I find an app's block in my theme editor? The app may ship an app embed only, which appears under App embeds in the theme editor sidebar rather than as a placeable block. If it does ship a block, it appears only on templates the app declared support for, so a block built for the product page will not show on the home page. Reinstalling rarely helps. ## Tools referenced ### SB&R SB&R is a Shopify app for chained referral rewards. Every referral link belongs to someone who has already bought. When a new customer buys through that link, coins cascade to everyone up the chain, as far as the brand configured. Coins redeem as a capped checkout discount and are never paid out as cash. Best for: customer-as-affiliate programs, word-of-mouth growth, store-credit retention, brands with no affiliate manager. Not for: cash-payout affiliate programs, B2B or wholesale referral. ### FlashPin FlashPin is a multi-tenant Shopify app that rotates which delivery pincode has a live discount on a cadence the brand sets. Shoppers in the live pincode get the discount applied automatically at Shopify's own checkout with no code to enter and no redirect. Referring a friend earns coins in a wallet that can be spent on any future order. Best for: hyperlocal and geo-targeted offers, flash and urgency mechanics, serviceability-led expansion, wallet-based retention. Not for: multi-currency stores, brands with no delivery-zone variation.