Shopify Legacy Custom Apps in 2026: Build the Next Integration in Dev Dashboard

A merchant searching for a Shopify private app developer in 2026 may be handed instructions for a screen that no longer creates new apps. Shopify stopped creating legacy custom apps from the store admin on January 1, 2026. Existing apps continue to work. New custom apps are created in Dev Dashboard, where versions, scopes, installation and authentication follow a different workflow. This distinction matters when a warehouse, ERP or reporting integration has to be commissioned without interrupting live orders.

This guide is for the US ecommerce owner or engineering lead who owns one store or a group of stores in one Shopify organization. It addresses the operating decision behind a new integration. If you are building an App Store product for unrelated merchants, read our Shopify app development company guide first. Our Shopify app development service covers the implementation and ongoing support of merchant tools, public apps and commerce integrations.

What changed for Shopify custom apps in 2026?

Shopify’s legacy app announcement and app management guide, read October 18, 2026, say that new legacy custom apps cannot be created in the admin after January 1, 2026. Existing legacy apps are not affected and remain manageable in the admin. New custom apps are managed in Dev Dashboard. That is a creation and management change, not a published deadline to replace every existing integration.

Shopify separately documents a migration from the Partner Dashboard to Dev Dashboard for apps previously managed there. Its Partner Dashboard migration guide, read October 18, 2026, says apps without extensions migrate automatically and apps with extensions need further developer steps. That is a different situation from an admin-created legacy custom app. A proposal should name which app you have before it promises a migration.

Keep the old app or commission a replacement?

Start with a dependency map. Identify which warehouse feed, finance job, support view or inventory update uses the app. Record where credentials are stored, which Shopify scopes were granted, which API versions and webhooks are used, who receives failures and how a missed event is reconciled. If the integration works and has a known owner, preserving it may be the least disruptive decision. If nobody owns the token, the job cannot be tested, or the business needs new data access, commission a bounded remediation with a cutover plan.

A replacement should not be described as moving an access token from one dashboard to another. The new app has its own credentials, installation and permission approval. Run old and new outputs against the same representative orders or products in a test environment, then record how discrepancies are resolved. Our legacy system API integration guide explains source-of-truth, retries and reconciliation when Shopify is only one part of the workflow.

Build a new app in Dev Dashboard, then prove it can call the API

Shopify’s Dev Dashboard tutorial, read October 18, 2026, describes the sequence: create the app, create and release a version with the required URLs and scopes, install it on a store, then authenticate. A version is required before installation. Shopify also notes that changing scopes in a later version does not automatically update installed stores; the merchant has to approve the new scopes. Put that approval in the release checklist instead of discovering it after an API request fails.

For an app that acts only on stores in its own organization, Shopify’s client credentials guide, read October 18, 2026, shows a server-side exchange of Client ID and secret for an access token. The token is requested programmatically and expires after 24 hours. The secret belongs in environment configuration or a secret manager, never in a repository or browser bundle. This grant is not a generic shortcut for apps serving other merchants; Shopify points those builds toward its CLI and appropriate merchant authorization flow.

Test the integration at business boundaries

A successful API response does not prove an order reached the warehouse or a stock update is correct. Write acceptance tests around the transaction the merchant pays for. For a fulfillment connector, submit an eligible order, trigger the same event twice, delay the warehouse response, change a line item and compare the resulting records in both systems. For a reporting connector, compare totals with the system of record and show when data was last refreshed. Store only the data needed to operate the feature, and decide who can view customer information before a dashboard is built.

The app also needs operational ownership: alerts that reach a named person, an API version review schedule, scoped credentials, secret rotation, and a runbook that explains safe retry and rollback. Our production Node.js security guide covers supporting controls for a backend service. Ask the developer to demonstrate the failure drills with your data model, not a sample store that never experiences an exception.

What to put in a Shopify developer brief

Give the engineering team one real workflow, the authoritative systems, a representative order or product record, the organization and store ownership, and the business outcome you want to measure. Ask for a written app type, scope list, grant choice, installation process, token handling plan, reconciliation method, cutover sequence and handoff artifacts. A quote for “a private app” without those details cannot tell you whether the team understood your current Shopify setup.

Dude Lemon builds merchant integrations and public Shopify applications. Our work portfolio shows the wider engineering practice, and the services overview covers adjacent API and cloud work. If you have a legacy app that is hard to operate or a new store workflow to automate, send us the workflow and the systems it touches. We can scope a small proof that demonstrates the authorization, transaction and recovery path before a full build is estimated.