Every agency pitch deck seems to include a line about custom Shopify app development being the key to unlocking your brand's full potential. It sounds compelling. It also tends to come with a five-figure price tag and a six-month timeline.
Here's the honest reality: most CPG brands don't need a custom app. They need someone to properly configure the tools they already have access to. But that nuance rarely makes it into an agency sales conversation.
That said, there are genuine scenarios where native Shopify features and third-party apps hit a wall. Subscription models tangled up in regulatory compliance, loyalty programs that go far beyond simple point accumulation, and B2B portals built for wholesale complexity are all situations where custom development earns its cost.
This post is designed to help you tell the difference. We'll walk through what Shopify already handles well for CPG brands, share a practical framework for deciding whether to build or configure, and break down the three narrow use cases where a custom app is actually the right answer. Knowing which camp you're in can save you a serious amount of budget.
If you've been pitched a custom Shopify app after a single discovery call, you're not alone. That upsell happens to CPG founders, DTC directors, and ecommerce managers regularly.
The financial gap is real. Custom Shopify app development runs meaningfully higher than configuration work, and that gap grows when you factor in ongoing maintenance, API updates, and the cost of onboarding a new developer if your original agency becomes unavailable. Understanding what working with a Shopify partner actually costs is a useful starting point before any build conversation begins.
We're Basis, a Shopify-focused agency that works almost exclusively with CPG brands: skincare, beauty, health foods, snacks, and beverage. Every recommendation we make is one we're accountable for. We've built custom apps when the situation genuinely required it. We've also told clients they didn't need one, and steered them toward smarter configuration instead. Both outcomes matter to us equally.
Before assuming you need something built, it's worth taking stock of what Shopify already handles natively.
Metafields alone solve a lot. Shopify's native metafields and custom product fields let you store and display ingredient lists, allergen flags, certifications, and regulatory disclosures directly on your product pages. No custom code, no developer required. For most CPG brands, that covers the core product data problem cleanly.
Checkout extensibility goes further than most brands realize. On Shopify Plus, checkout extensibility lets you add custom form fields, conditional logic, upsells, and purchase flow modifications without touching a custom app. If you're not on Plus and wondering whether it's worth the move, what CPG brands specifically get out of Plus is worth reading before you make that call.
The third-party app ecosystem has genuinely matured. Subscription, loyalty, and B2B wholesale apps have closed a lot of ground in the last few years. The gap between what a well-chosen app can do and what custom Shopify app development can do is narrower than most pitches imply.
Here's what we see repeatedly: a brand gets quoted for custom Shopify plugin development, and when we dig in, the real issue is a misconfigured app or a tool that was never the right fit to begin with. That's a configuration problem, not a build problem.
A configuration-first audit, reviewing what your actual stack supports before scoping anything custom, should always be the starting point.
Here's the real question to ask before anyone starts scoping a custom build: is this requirement genuinely unique to your business, or does it just feel unique because you haven't found the right configuration yet? That distinction is worth thousands of dollars.
Signals that point toward configuration:
The need is functionally similar to what other Shopify stores do
A third-party app covers 80% or more of the use case
The requirement is stable and doesn't change often
The cost of a workaround is low
Signals that point toward custom Shopify app development:
The logic must enforce regulatory compliance
The requirement involves real-time data exchange with an external system
No existing app handles the core function without significant compromise
The use case will scale as your business grows
If you're checking more boxes in the second list, a custom app may be justified. But here's the ROI math agencies rarely walk you through: custom development cost plus annual maintenance plus rework every time Shopify updates its API terms versus the cost of a well-configured app stack. The break-even point is almost always further out than the initial pitch implies.
Dependency risk compounds this. Every custom app creates a maintenance obligation that grows as Shopify's platform evolves, and that obligation lives with whoever built it. If that relationship changes, so does your ability to keep the app functional. That's not a hypothetical; it's a recurring reality we see across the CPG brands we talk to.
If your brand sells subscriptions in a regulated CPG category, like skincare products now subject to expanded FDA oversight under MoCRA, topical treatments, or age-restricted formulations, your subscription model carries obligations that generic billing tools simply weren't built for.
The specific compliance gaps that matter:
State-level SKU restrictions. A product legal to ship in most states may be restricted in others. A subscription that auto-renews doesn't automatically know that, and a fulfillment workaround is not the same as enforcement at the platform level.
Persistent age verification. Verifying age at initial signup doesn't mean that verification follows the customer through every renewal cycle. For age-restricted products, that gap is a liability.
Ingredient disclosure acknowledgments. MoCRA has increased transparency requirements for cosmetics. If a customer needs to acknowledge a disclosure at each order, standard subscription apps have no mechanism for that.
Generic subscription apps do recurring billing well. That's the job they were designed for. Bolting compliance logic onto them through workarounds creates patchwork enforcement, not reliable enforcement.
This is a case where custom Shopify app development earns its cost. The logic is genuinely category-specific, and getting it wrong carries real legal and financial consequences.
One scoping note before you build: work with legal counsel to determine what must be enforced at the platform level versus what can live in documentation or internal process. That conversation will right-size the build considerably. You can find additional thinking on Shopify strategy for CPG brands in our resources section.
Standard loyalty apps are engineered for a universal model: spend money, earn points, redeem for discounts. That works fine for general retail. It starts breaking down for CPG brands with more specific mechanics, like tiered rewards that treat skincare purchases differently from supplements, earning logic tied to skin type quiz completions or ingredient preference data, or promotional multipliers with complex seasonal eligibility rules that change quarter to quarter.
Loyalty program usage increased 28% in 2024, and CPG brands are increasingly treating these programs as first-party data infrastructure, not just discount engines. That ambition frequently outpaces what off-the-shelf apps can execute.
The honest test: configure your loyalty app to its documented limits. If your core program mechanic still requires manual workarounds to function, that's a legitimate signal to consider custom Shopify app development. Not a maybe, an actual signal.
Custom loyalty development is justified when the program mechanics are central to how customers experience the brand, not just a retention layer sitting underneath it. If your loyalty program is genuinely differentiated, customers should feel that in every interaction.
Where brands get hurt is building custom loyalty infrastructure before validating that customers actually want the program. Expensive custom code maintaining a program with low engagement is a real outcome, and it happens more often than agencies advertising custom builds will tell you.
CPG brands running both D2C and wholesale channels can hit a real ceiling when managing dozens of retail accounts, each with their own replenishment cycles, regional pricing tiers, and documentation requirements. In our experience, the gaps that most often push CPG brands toward custom development include: real-time inventory visibility by warehouse location, compliance documentation delivery tied to individual orders (SDS sheets, ingredient certifications), ordering windows customized to each retailer's restock schedule, and tiered pricing that varies by account, region, and volume simultaneously.
Third-party B2B apps have improved, but in practice they often cover one side of the problem, buyer-facing UX or back-office order logic, but rarely both with equal depth. The result is usually a stack of two or three tools with fragile connections between them, and someone on your team manually filling the gaps.
A custom retailer portal makes sense when wholesale is a meaningful revenue driver and the operational friction is visibly costing you orders or straining account relationships. That's a real bar worth clearing before commissioning a build.
Before scoping anything, answer this first: is this a portal problem or an ERP problem? If retailers struggle to interact with your brand, a custom Shopify app integration may be the right answer. If your internal systems struggle to talk to Shopify, the fix likely lives in your back-office infrastructure instead.
Maintenance is almost never scoped into the original build proposal, and the build cost is only the starting point.
Shopify releases new API versions quarterly, and deprecated versions eventually stop working. The REST Admin API was fully deprecated in October 2024, with custom app migration deadlines hitting in early 2025. That's not a hypothetical risk, it's active rework cost landing on brands right now. Shopify's API versioning documentation is public and transparent about this cycle, which means there's no excuse for a proposal that doesn't account for it.
Annual API compatibility reviews, growth-triggered updates, and bug fixes as Shopify's platform shifts are real line items that appear later, not upfront. The total cost of ownership on a custom app is meaningfully higher than the build invoice suggests.
The staff dependency risk compounds this. If the team that built your app isn't available when something breaks, a new developer inherits unfamiliar code under time pressure. That's expensive in ways that are hard to predict in advance.
Scale creates its own rework cycle. A custom app built for your current SKU count and order volume may need significant architectural changes as you grow. That rework is yours to fund, not Shopify's.
The honest framing: a custom Shopify app is an ongoing asset, not a one-time purchase. If that ongoing investment doesn't fit the ROI model, the build decision needs to change. Factor it in from day one, or be surprised by it later.
Basis is a small, focused team working entirely on Shopify ecommerce. Every recommendation we make is one we're personally accountable for. We don't have the project volume to absorb a bad call and move on. When we tell a CPG client they need a custom app, we mean it, and when we tell them they don't, we mean that too.
Our default starting point for any custom Shopify app development inquiry is a configuration audit. Before anyone talks about scoping a build, we want to know what your current setup actually supports. Most of the time, there's meaningful headroom in your existing stack that hasn't been fully tested. That process reflects everything covered above about maintenance obligations and total cost of ownership: if smarter configuration avoids those obligations entirely, that's the right outcome for the client.
When a custom build is the right call, we scope it with maintenance costs included from the start. We document API dependencies, write for readability, and build with the assumption that someone other than us may eventually need to work on the code. That's respect for the client's long-term investment.
If you're weighing whether your use case genuinely justifies custom Shopify plugin development or whether better configuration is the answer, that's a conversation we're specifically set up to have. You can review our terms of service and engagement expectations before reaching out if you'd like to understand how we work.
So here's the short version: always audit before you build.
If your current Shopify setup and app stack can handle the requirement with smarter configuration, that's your answer. Custom Shopify app development earns its cost in exactly three CPG scenarios: subscription logic that has to enforce regulatory compliance, loyalty mechanics that are genuinely central to your brand and too differentiated for any app to replicate, and wholesale B2B portals where the operational complexity is real and measurable.
Everything else is probably a configuration problem waiting to be solved.
When a custom build is the right call, go in with clear eyes on total cost of ownership, including maintenance, API compatibility updates, and developer continuity, all of which compound over time.
An agency that tells you which conversation you're actually in, including when the answer is "you don't need a custom app," is demonstrating the judgment you want making technical decisions for your business.
Custom Shopify app development is a powerful tool, but only when the problem genuinely demands it. The brands that get this right share a few habits: they audit before they build, they quantify the operational pain before approving a scope, and they choose partners who will push back when a simpler solution exists.
If you take one thing from this post, let it be this: complexity is not a reason to build custom. It is a reason to ask harder questions first.
When you have exhausted configuration options and the business case still holds, a custom build can unlock real competitive advantage. Getting there requires honesty at every step of the process.
Ready to figure out which conversation you are actually in? Start with an honest audit of your current stack. If you need a second opinion, we are here for that.
