---
title: "Built for Shopify: what the badge requires and whether it is worth it"
description: "Built for Shopify requirements: installs, reviews, Web Vitals, embedding and design rules, what Shopify says the badge does, and how to decide."
topic: "App marketplaces"
date: 2026-10-13
updated: 2026-10-13
author: "Geetansh Saini"
url: https://www.geeetansh.com/guides/built-for-shopify
tags: ["built for shopify", "shopify app requirements", "shopify app design"]
---
# Built for Shopify: what the badge requires and whether it is worth it

**In short:** Built for Shopify is Shopify's top quality status for apps, and to apply you need 50 net installs from active shops on paid plans, five reviews, a minimum recent rating, and an app that meets Shopify's admin performance thresholds at the 75th percentile, embeds in the admin with the latest App Bridge, and follows a long list of design rules. Shopify says the badge shows on your app card, lets merchants filter search to badged apps, and lifts search ranking, but it publishes no install uplift. Pursue it if you are an embedded app in a crowded category, because most of what it asks for reduces uninstalls anyway.

## What is the Built for Shopify badge?

Shopify's [overview of the programme](https://shopify.dev/docs/apps/launch/built-for-shopify) calls Built for Shopify status "the highest level of recognition and achievement that an app can reach", and says apps must meet quality standards for ease of use, safety, performance and usefulness to merchants.

The mechanics, from the same page. You cannot apply until you meet every prerequisite. Most criteria are evaluated automatically and your status shows on the Distribution page of the Partner Dashboard. When you apply, the app review team checks the rest and tells you what to fix. Failing the same criterion three times in a row suspends the application for three months. Once you have the badge, apps are reviewed annually, and an app that stops complying is told by email and gets 60 days to fix it.

So the badge is not a one-time certificate. It is a standard you keep meeting, with Shopify measuring most of it from your merchants' browsers.

## What does Built for Shopify require?

Everything below is from Shopify's [requirements page](https://shopify.dev/docs/apps/launch/built-for-shopify/requirements), with its numbering. I have grouped them by the kind of work they imply.

**Prerequisites you cannot design your way around**

| Requirement | What it says |
| --- | --- |
| 1.1.1 | Keep meeting the App Store distribution requirements, audited when you apply |
| 1.1.2 | No active or outstanding Partner Program infractions |
| 1.2.1 | At least 50 net installs from active shops on paid plans |
| 1.2.2 | At least five reviews |
| 1.2.3 | Meet a minimum recent App Store rating threshold (no number is published) |

**Performance, measured in the merchant's browser**

| Requirement | Threshold |
| --- | --- |
| 2.1.1 | Largest Contentful Paint of 2.5 seconds or less, 75th percentile, at least 100 calls in the last 28 days |
| 2.1.2 | Cumulative Layout Shift of 0.1 or less, same window |
| 2.1.3 | Interaction to Next Paint of 200 milliseconds or less, same window |
| 2.2.1 | Reduce the storefront Lighthouse performance score by no more than 10 points |
| 2.3.1 | Checkout: at least 1,000 requests in 28 days, p95 of 500 milliseconds or less, 0.1% failure rate |

The admin vitals require the latest App Bridge.

**Integration**

- 3.1.1: Embed with the latest App Bridge by adding the app-bridge.js script to the head of every document. Do not embed external web pages.
- 3.1.2: Merchants complete primary workflows inside the admin, with exceptions for things like messaging apps.
- 3.1.3: Sign-up uses Shopify credentials with no extra login, so merchants can start right after install.
- 3.1.4: Key metrics on the home page, with a simplified version in the admin if full reporting lives elsewhere.
- 3.1.5: Connection settings for third-party services are inside the embedded app, including disconnecting.
- 3.2.1: Storefront elements use theme app extensions, so uninstalling removes them cleanly.
- 3.2.2: No creating, modifying or deleting theme files through the Asset API, with narrow exceptions for page builders, backup apps and SEO or developer tooling.

**Design**

Section 4 is the longest, and it is where most of the design work sits. The headline rules: match the admin's look and feel with Polaris-style components and WCAG 2.1 AA contrast (4.1.1), stack layouts on small screens with no horizontal scroll (4.1.2), use the s-app-nav navigation with subpages highlighting their parent (4.1.4), use the contextual save bar and never let a merchant leave with unsaved changes (4.1.5), keep onboarding concise and removable once done (4.2.2), show on the home page whether the app is set up and working, with real metrics (4.2.3), show errors in red, persistently, next to the field, and never before the merchant has interacted (4.2.4), and give customisable elements a live preview (4.2.6).

Then the rules about how you treat merchants: no guaranteed outcomes (4.3.1), no visible timers, guilt copy or rewards for 5-star reviews (4.3.2), no automatic modals or popovers and red only for errors (4.3.3), no stacked banners (4.3.4), nothing that looks like a first-party Shopify app (4.3.5), promotional content that can be dismissed and stays dismissed (4.3.6), and plan-gated features that look and behave disabled with the required tier obvious, with Plus-only features hidden from non-Plus merchants (4.3.7).

**Category rules**

Section 5 applies only if your app is in that category. Affiliate, ads, analytics, email and SMS apps must use Web Pixel extensions. Reviews apps need a Flow trigger and an admin block on customer pages. Discount apps must use discount functions or the native discount APIs, not draft orders. Shopify's [changelog from 17 June 2026](https://shopify.dev/changelog/built-for-shopify-requirements-for-returns-and-exchanges-and-subscription-apps) adds that from 1 December 2026, returns and exchanges apps and subscription apps with buyer self-service must authenticate customers with the Customer Account API or risk losing the badge.

## What does Shopify say the badge does for distribution?

This is worth reading precisely, because the overview page is careful about it.

What is exclusive to the badge: a highlight at the top of your listing's highlights, the badge on your app card wherever it appears in the App Store, and a search filter merchants can use to show only Built for Shopify apps. Also priority review for future submissions and plan-based targeting for App Store ads.

What is not exclusive: Shopify says Built for Shopify apps appear higher in search rankings, and in the same breath says this benefit is shared with other apps that have ranking boosts. Homepage and category page placements are open to badged apps, and Shopify says those are not exclusive to the badge either. Badged apps may appear in the admin's "Picked for you" modal, but that collection is personalised, your app is not guaranteed to appear, and the placement is available to non-badged apps too.

Shopify publishes no figure for installs gained. I have not seen a verified one anywhere, so treat any number you read as a single developer's experience. My read is that the filter and the badge on the card are the concrete gains, and they matter most where a merchant is comparing five similar apps in a category. In a category with two serious apps, the badge changes less.

## What design and performance work does it imply?

More than the list suggests, for three reasons.

First, the performance numbers are measured in merchants' browsers at the 75th percentile, not on your staging server. A dashboard that loads a 2,000-row affiliate table on the home page will fail LCP for exactly the merchants you most want to keep. The fix is pagination, skeletons and loading the metrics first, which is design work before it is engineering work.

Second, embedding properly means App Bridge on every page, Polaris web components for navigation, modals and the save bar, and theme app extensions in place of any theme file edits. For an app that started life as a standalone dashboard with a script injected into theme.liquid, that is a rebuild of the storefront side and a re-skin of the admin side. I cover what to follow and what to adapt in [designing with Polaris](/guides/polaris-app-design).

Third, section 4.3 is a list of things many apps do on purpose. Countdown timers on upgrade pages. Modals on login. A banner for every announcement. "Leave a 5-star review and get a free month". The badge requires removing them, and so do the App Store rules on reviews, which I cover in [Shopify app reviews](/guides/shopify-app-reviews). The gating rule in 4.3.7 is the one I would start with. A greyed-out feature with the plan name on it is a better upsell than a hidden one anyway.

The test I apply before any of this is a walkthrough on a phone, on a slow connection, as a merchant who installed ten minutes ago. If that walkthrough is fine, the design section is mostly a checklist. If it is not, the badge is the least of the problems, and the walkthrough has just told you why merchants [uninstall in the first week](/guides/reduce-shopify-app-uninstalls).

## Should you pursue Built for Shopify?

| Pursue it now if | Hold off if |
| --- | --- |
| You already embed in the admin and most of your installs come from App Store search | Your core workflow has to live outside the admin and does not fit the listed exceptions |
| You are in a crowded category where merchants compare and filter | You have under 50 paid installs, because you cannot apply yet |
| Your admin pages already load fast and you can measure Web Vitals | You depend on the Asset API to edit theme files and cannot move to theme app extensions soon |
| You compete on trust, and your reviews already say the app is simple | Your pricing page relies on timers, pop-ups or review incentives you are not ready to remove |

Two more things to weigh. The badge is reviewed annually and the rules keep changing, as the December 2026 Customer Account API deadline shows, so it is an ongoing cost, not a project. And almost every requirement in sections 3 and 4 is something that lowers uninstalls whether or not you apply. If you are going to do the work for the badge, do it in the order that helps merchants first: home page status and metrics, errors and save bar, gating, then performance, then the badge.

## Where to start

1. Open the Distribution page in the Partner Dashboard and note which prerequisites and automated criteria you already pass. Work from that list, not from this guide.
2. Check your admin Web Vitals in the Dev Dashboard and fix the slowest page first, usually the home page.
3. Audit the app against section 4.3: timers, automatic modals, stacked banners, review incentives, hidden plan gating. Remove or redesign each one.
4. If any storefront element is injected through theme files, plan the move to theme app extensions before anything else, because it is the longest item.
5. Read the category rules for your category and the changelog for pending deadlines, and put the dates in your roadmap.

## Frequently asked questions

### How many installs do you need for Built for Shopify?

Shopify's requirements say a minimum of 50 net installs from active shops on paid plans, plus at least five reviews and a minimum recent rating threshold, which Shopify does not publish as a number.

### What performance does Built for Shopify require?

In the admin, at the 75th percentile with at least 100 calls in the last 28 days: Largest Contentful Paint of 2.5 seconds or less, Cumulative Layout Shift of 0.1 or less, and Interaction to Next Paint of 200 milliseconds or less. On the storefront, the app may reduce the Lighthouse performance score by no more than 10 points.

### Does Built for Shopify increase installs?

Shopify says the badge appears on your app card, that merchants can filter search results to badged apps, and that badged apps appear higher in search, though it notes the ranking benefit is shared with other boosted apps. It publishes no install uplift figure.

### Can you lose Built for Shopify status?

Yes. Shopify reviews badged apps annually, notifies apps that no longer comply by email, and gives them 60 days to fix the failures. Failing the same criterion three times in a row during an application suspends it for three months.