Share
Share
Share
Share
Open two mid-market Shopify storefronts selling comparable goods and the front ends will look like cousins: the same section-based theme conventions, the same sticky add-to-cart, the same review widget below the fold. Open the two admin panels and the resemblance ends. One store runs a bundling app configured in an afternoon. The other runs a build nobody else has, reading a distributor price list, checking a credit limit, routing each line item to the nearest warehouse holding stock.
That second store is where the budget went. Shopify’s second-quarter fiscal 2026 disclosures put gross merchandise volume at $115.57 billion, up 31.6% year over year, with B2B GMV up 76% — the fastest-growing line in the business. Wholesale pricing tables and approval chains do not ship inside a theme.
Key takeaways
Shopify reported B2B GMV up 76% year over year in Q2 fiscal 2026 — the segment whose pricing and approval rules most often outgrow off-the-shelf apps.
Merchant solutions revenue grew 37% against 22% for subscription solutions in the same quarter, per company disclosures.
Shopify reports merchant retention of 92% above $1 million annual GMV and 97% above $10 million; depth of integration is part of the explanation.
“Private app” stopped being a live distribution type in 2022; the current categories are public App Store apps and custom apps.
Shopify ships a new API version quarterly and supports each release for at least twelve months, which sets a hard maintenance cadence for anyone owning app code.
What does Shopify development actually cover in 2026?
Shopify development is the build, integration and optimisation work layered on top of the hosted platform: theme engineering, storefront performance, data modelling through metafields and metaobjects, and the apps that encode a merchant’s own operating rules. The last of those now absorbs a growing share of serious project budgets.
The reason is convergence. Shopify keeps absorbing functionality that once justified a bespoke build — checkout extensibility, native subscription APIs, markets, B2B catalogues, discount logic through Shopify Functions. Each absorption lifts the floor for every merchant, which is good for merchants and awkward for anyone selling differentiation. What stays distinctive is the rule set behind the storefront.
What is the difference between a public app, a custom app and a private app?
A public app is listed on the Shopify App Store, installable by any merchant, and passes Shopify’s app review. A custom app serves one store, distributed by install link or created in the admin, and skips App Store review. “Private app” was the earlier name for single-store apps, retired in 2022.
The distinction bites at procurement. Public apps carry a listing, a support obligation, a review score and the Built for Shopify technical standards, plus every other merchant’s requirements baked into their settings screens. Custom apps carry neither that overhead nor that generality: they authenticate against the Admin API with credentials scoped to one shop, and can ship as extension-only apps injecting UI into checkout, the admin or the theme.
Why are merchants commissioning bespoke apps instead of buying them?
Because off-the-shelf apps must generalise and operating rules do not. A merchant with 400 negotiated account prices, two-step purchase approval above a threshold value, and split fulfilment across three logistics providers is describing a workflow, not a feature. Configuration screens run out before workflows do.
Wholesale is where requirements are least portable between businesses: customer-specific catalogues, credit terms, minimum order quantities, tax exemption handling, reorder logic tied to consumption rather than browsing. Custom Shopify app development is usually what a merchant reaches for after stacking three or four apps plus a spreadsheet to reconcile them.
Which operating rules genuinely justify custom code?
Four patterns recur: pricing that depends on customer attributes rather than product attributes; fulfilment routing that weighs stock location, carrier cost and delivery promise; subscription mechanics tied to real consumption cycles; and B2B approval flows where an order stays a request until somebody signs it. Each is a decision engine, not a display setting.
Everything else deserves scepticism. A merchant who wants custom code to change how upsells look is buying maintenance liability to solve a theme problem.
What does owning app code actually cost after launch?
Ownership is a subscription in disguise. Shopify releases a new API version quarterly and supports each for at least twelve months, so any app touching the Admin or Storefront APIs faces a recurring upgrade obligation. Webhook payloads change, deprecated fields disappear, and theme updates can break theme app extensions that previously worked.
Regression risk is the underestimated cost. Agencies handling Shopify app development (https://www.thegenielab.com/pages/ecommerce-app-development) at this tier increasingly price a retained maintenance window alongside delivery, because an app encoding pricing or fulfilment rules sits in the revenue path and every upgrade needs a staging store, seeded data and a rollback plan. Public apps add a cycle: material changes return to Shopify’s review queue.
When should a merchant not build an app?
Most of the time. The honest sequence is to exhaust the App Store first, then Shopify Flow and native automation, then a Functions-based extension, and only then a commissioned build. Merchants below roughly $1 million in annual GMV rarely have rules complex enough to outrun a $49-a-month subscription.
Two cautions. Custom code duplicating something Shopify is visibly building will be obsolete within a release cycle or two. And a build with no named internal owner goes unmaintained the moment its sponsor changes job.
What should a buyer ask before signing a build contract?
Five questions, in order: who owns the source code and repository; which API version the build targets and who upgrades it; what the test coverage and staging arrangement look like; whether the app is custom or intended for eventual public listing; and what happens to the code if the relationship ends.
The answers separate a deliverable from a dependency. Shopify’s reported 97% retention above $10 million in GMV shows how sticky deep integration becomes. That stickiness runs towards whoever holds the code, not only towards the platform.
Frequently asked questions
Can a custom Shopify app be moved to another store later? Not directly. Custom apps are scoped to one shop, so a second store needs its own installation and credentials. Builds meant for several stores should be scoped as unlisted or public apps from the outset.
Do custom apps go through Shopify’s app review process? No. Custom apps skip App Store review, which shortens delivery but removes an external quality gate. Security review, API scope hygiene and performance testing fall to the merchant and the build partner.
How much of a Shopify development budget should go to the app layer? No published benchmark exists, and any figure quoted as one is invented. Size the app layer against the manual work it removes, then reserve a recurring allocation for API upgrades.
Figures are drawn from Shopify Inc.’s Q2 fiscal 2026 earnings disclosures and Shopify’s published API versioning and app distribution documentation. Editorial brief; not commercial advice.
