Shopify private apps no longer exist. They were deprecated in April 2023, and any guidance you find about them — including older posts on this site — describes a feature that has been removed from the platform. If you're looking to extend Shopify's functionality beyond what's available in the app store, the current answer is a custom app. This post explains what changed, what custom apps are, and where they genuinely add value for DTC brands.
What happened to Shopify private apps
Private apps were a way for merchants to create API credentials tied directly to a store, giving a specific integration or custom tool access to Shopify's Admin API without going through the Shopify app review process. They were simple to create and useful for lightweight internal tooling — connecting a third-party warehouse system, pulling order data into a spreadsheet, or building a small internal dashboard without publishing a full app.
Shopify deprecated them as part of a broader shift toward a more secure, scalable app infrastructure. The replacement is the custom app — which covers the same use cases but operates within Shopify's modern API framework, uses access token authentication rather than legacy API keys, and integrates with Shopify's admin interface rather than existing as an invisible credential in the background.
What Shopify custom apps are
A custom app is a Shopify app built for a single store, not listed in the Shopify App Store and not available to other merchants. It can access Shopify's Admin API, use Shopify Functions to customise checkout logic, add embedded UI within the Shopify admin, and interact with orders, products, customers, and fulfilment data in whatever way the merchant needs.
The key difference from a public app is scope: a custom app is built for one specific purpose, for one specific merchant, without the overhead of supporting multiple stores or maintaining a general-purpose product. That makes custom apps the right tool for operational problems that are unique to a brand's fulfilment model, product range, or subscription architecture — things that no app store product covers well because no app store product was designed for exactly that problem.
When a custom app makes sense for a DTC brand
Most DTC brands don't need a custom app. The Shopify app ecosystem is large enough that off-the-shelf solutions cover the majority of requirements well. Custom apps earn their place when the operational problem is specific to the brand's model in a way that an existing app can't solve cleanly — usually where the product structure, fulfilment logic, or subscription mechanic creates complexity that a generic tool handles badly or not at all.
The most common use cases Tribe sees: custom fulfilment dashboards for brands with complex production requirements, bespoke reporting tools that aggregate data across Shopify, subscription platform, and third-party logistics in a format the team can actually act on, and operational tooling that sits between the subscription platform and the warehouse where the native integration doesn't cover the full requirement.
A real example: production aggregation for a subscription meal brand
One of the clearest examples of a custom app earning its place is a production dashboard Tribe built for a subscription meal prep brand. The brand sells build-a-bundle subscriptions — customers pick their meals and flavours through a Skio dynamic box, choosing from a range of options delivered on a recurring basis. The fulfilment challenge is what makes this operationally complex: the kitchen team needs to know the total quantity of each flavour required across all orders for a given day, not just a list of orders. A standard Shopify fulfilment view shows orders; the kitchen team needs an aggregated production list.
The custom app solves this by reading the Skio build-a-bundle line item data — which records individual flavour selections per box — and aggregating them across all unfulfilled orders into a single production list. The kitchen can see that they need to make 47 units of one flavour and 23 of another before they start packing, rather than working through orders individually. The dashboard also shows which flavours belong in each individual box, removing ambiguity at the packing stage. It handles legacy product mappings where older SKU structures differ from the current build, and flags orders with missing data rather than silently misrepresenting them.
None of this was possible through a standard Shopify fulfilment app. The problem was specific to how the subscription bundle worked, how flavour data was structured in the line items, and what the kitchen team actually needed to see. A custom app was the only solution that fitted the requirement cleanly.
Custom apps vs public apps vs Shopify Functions
It's worth distinguishing between the options available when the app store doesn't cover the requirement. A public app from the Shopify App Store is maintained by the vendor, costs a monthly fee, and is designed to work for thousands of merchants — which means it handles generic cases well and specific cases imperfectly. A custom app is built for one store, maintained by the agency or development team, and handles the specific case exactly. Shopify Functions are a different tool entirely: they let merchants customise Shopify's core logic (pricing, discounts, shipping, checkout validation) without a custom front end, running as serverless functions within Shopify's infrastructure. Functions are the right choice when the customisation is to Shopify's built-in behaviour; a custom app is the right choice when the requirement is a new tool or interface that Shopify doesn't have natively.
For most operational requirements, the decision is straightforward: if a public app covers 90% of the need at a reasonable cost, use it and accept the remaining 10% as a trade-off. If the requirement is genuinely specific to the brand's model and the gap between what a public app does and what the brand needs is material, a custom app is worth the investment. The production aggregation example above is a clear case — no app store product was going to solve that exact problem.
What to consider before building a custom app
Custom apps are not plug-and-play. They require scoping, development, testing, and ongoing maintenance as Shopify's APIs evolve. A custom app built for a specific Skio or Recharge integration will need updating if the subscription platform changes how it structures data. A custom fulfilment dashboard will need updating if the order structure or product range changes materially. That ongoing maintenance cost is real and should be factored into the decision.
The questions worth asking before commissioning a custom app: is the operational problem actually specific to the brand, or does a well-configured public app cover it? What is the ongoing maintenance requirement, and who owns it? Does the problem genuinely require a custom app, or could it be solved by a Shopify Function, a webhook to a third-party tool, or a change to the data structure in the subscription platform? Tribe builds custom apps for clients where the answer to these questions clearly points toward a bespoke solution — and recommends against it where a simpler path exists. If you're working through whether a custom app is the right solution for your operational requirement, get in touch.
Frequently asked questions
Are Shopify private apps still available?
No. Shopify deprecated private apps in April 2023. They are no longer available to create, and any existing private apps were migrated to custom apps or deactivated. The replacement is the custom app, which covers the same use cases but uses Shopify's modern API authentication framework and integrates with the current Shopify admin architecture.
What is a Shopify custom app?
A Shopify custom app is an app built for a single store, not available in the Shopify App Store, and not shared with other merchants. It can access Shopify's Admin API, use Shopify Functions, embed UI within the Shopify admin, and interact with any part of the store's data that the merchant needs. Custom apps are used for operational tooling, bespoke integrations, and specific workflows that no public app covers well — such as custom fulfilment dashboards, subscription data aggregation, or multi-system reporting tools.
When should a DTC brand build a custom Shopify app?
When the operational problem is genuinely specific to the brand's model and no public app solves it cleanly. Common triggers: a fulfilment or production workflow that depends on data structured in a way unique to the brand's product range or subscription mechanic, a reporting requirement that pulls from multiple systems (Shopify, Recharge, Skio, a 3PL) in a format no off-the-shelf tool produces, or a customer-facing feature that requires logic beyond what Shopify Functions and existing apps can handle. For most operational requirements, a well-configured public app is the faster and more cost-effective path. Custom apps earn their place when the specificity of the problem means a generic tool genuinely can't solve it.
What is the difference between a custom app and Shopify Functions?
Shopify Functions customise Shopify's built-in behaviour — pricing rules, discounts, shipping logic, checkout validation — running as serverless functions within Shopify's infrastructure without a separate application. A custom app is a standalone application that interfaces with Shopify's APIs to build new tools, dashboards, or integrations that Shopify doesn't have natively. Functions are the right tool for modifying how Shopify works; custom apps are the right tool for building something new that Shopify doesn't do.