Shopify App Pricing / For app developers

Plan Feature Targeting
Stop stores that can't use a plan from selecting it

You can now set "store requirements" on public plans. Stores without the required features can't subscribe to that plan, so merchants don't pay for features that won't work. The setting is optional, so nothing changes if you don't adopt it.

On this page
  1. What's actually changing (30-second overview)
  2. How it works: two checkpoints
  3. The two store requirements you can choose
  4. What's in and out of scope
  5. Impact on existing subscriptions
  6. Setup steps (4 steps + verification)
  7. 5 key points for developers
  8. 3 practical use cases
  9. One-line summary for proposals

1What's actually changing

Until now, merchants could subscribe to plans that depended on features their store didn't have.
Starting now, in the plan editor in Partner Dashboard, you can declare "this plan requires this feature" and stores that don't meet the requirement can no longer subscribe.

Before: anyone could subscribe

Even without the required features, merchants could select a plan and proceed all the way to payment, only discovering after subscribing that the features didn't work.

Now: requirements gate access

On stores that don't meet the requirements, the select button is disabled and the missing features are listed. The merchant is stopped before payment.

2How it works: two checkpoints

App developer Partner Dashboard to set store requirements Public plans only 1 Plan selection page For plans whose requirements aren't met, the select button is disabled A message lists the missing features 2 At charge approval The merchant ... the charge Re-checked at approval time Subscription starts Eligible stores only
Checks run on the plan selection page and at charge approval — twice. Shopify doesn't just hide plans in the UI; it also re-verifies eligibility at the approval step.

3Two store requirements to choose from

In the plan editor's new Store requirements section, you can select either requirement, or both.

Requirement A

Checkout UI extensions (all pages) + branding customization

The store must support app customizations on every step of checkout.

B2B Requirement B

Direct company catalogs(B2B)

The store must be able to give B2B customers (companies) directly assigned catalogs .

This post doesn't list which Shopify plans meet each requirement. See the related "Store requirements" documentation for details.

4What's in scope and what isn't

In scope

Public plans in Shopify App Pricing

Store requirements can only be set on public plans.

Out of scope

Private plans

Store requirements can't be set on private plans.

Out of scope

Charges created with the Billing API

Doesn't apply to charges created with the Billing API.

Visitors to the Shopify App Store who aren't logged in still see all public plans, as before (plans aren't filtered because the store can't be identified).

5Impact on existing subscriptions

SituationBehavior
Has an active subscription Continues The merchant keeps the plan even if you add or change requirements
The subscription is canceled Re-evaluated To resume the same plan, they must meet the requirements in effect at that time
Attempts to subscribe for the first time Blocked Stores that don't meet the requirements can't subscribe
Visitors not logged in to the App Store All shown All public plans are visible

6Setup steps (4 steps + verification)

1

Open the plan editor

Open the plan editor for your public plan (see the public plans documentation for detailed steps).

2

Select under Store requirements

Check the features your plan requires.

3
Save

Click Save

Saving activates the requirements.

4

Verify on a store without the feature

Open the plan selection page from a store that lacks the required feature.

Expected result:The plan's select button is disabled, and the message names the missing feature. Stores with the feature can still select it.
Action is not required (optional). Shopify recommends adding requirements only when the plan can't work without that feature.All stores without the feature are blocked , so adding too many requirements costs you sign-ups.

75 key points for developers

PUBLIC

1. Only applies to Managed Pricing public plans

Not available if you bill through the Billing API yourself or use private plans. To use requirement gating, you must run public plans on Shopify App Pricing.

1 2

2. Checked twice: at display and at approval

The button is disabled on the plan selection page, and requirements are checked again at charge approval. The platform blocks ineligible stores, so your app doesn't need its own plan-eligibility logic.

3. Existing subscriptions are protected (grandfathered)

Active subscriptions continue even if you add or change requirements later. Existing customers aren't suddenly cut off.

4. Resuming after cancellation is evaluated against current requirements

Once canceled, the latest requirements apply when resuming. After tightening requirements, some stores won't be able to return by canceling and resubscribing, so make sure your support team knows.

?

5. Logged-out visitors see all plans

People viewing your App Store listing without logging in also see plans with requirements.Spell out the "required features" in your listing description and plan descriptions to reduce the gap where merchants log in and then find they can't select a plan.

83 use cases you can put to work

USE CASE 1

Protect the top-tier plan of an app that customizes every checkout step

Challenge
The top-tier plan's headline feature is "UI extensions and branding across all checkout pages," but stores that can't use it can still subscribe, leading to "it doesn't work" support tickets after they sign up.
Approach
Add the "Checkout UI extensions (all pages) and branding customizations" requirement to the top-tier plan only, and leave lower-tier plans without requirements.
Impact
Prevents charges for features that won't work before merchants subscribe, cutting support and refund requests. Stores that don't meet the requirement can still land on a lower-tier plan.
Technical note
Existing subscribers keep their plan after a requirement is added. Only when a store resubscribes after canceling is it evaluated against the current requirements.
B2B
USE CASE 2

Offer a B2B catalog integration app as a "B2B-ready stores only" plan

Challenge
Stores that can't assign catalogs directly to companies end up choosing a B2B plan that assumes catalogs are assigned to company customers.
Approach
Set the "Direct company catalogs (B2B)" requirement on plans that include B2B features. Leave plans with D2C-only features without requirements.
Impact
Ensures only stores that can use B2B features subscribe to the B2B plan, so your plan design matches what each store can actually use.
Technical note
You can specify two requirements at once. If a plan needs both checkout extensions and B2B, add both.
USE CASE 3

Build it into your pre-release QA checklist when adding requirements

Challenge
Adding a requirement blocks every store that lacks the feature, so a misconfiguration could unexpectedly stop new subscriptions.
Approach
After saving, add a QA step: open the plan selection page from both (1) a store without the feature and (2) a store with it, and confirm the disabled button, the missing-feature message, and whether the plan can be selected.
Impact
Guarantees before launch that requirements are attached only to the plans that truly need them.
Technical note
App Store visitors who aren't logged in see all plans, so always test while logged in to the target store.

9One-line summary for proposals

"Your app's public plans can now declare the store features they require, and stores that can't use them are stopped before subscribing.
Adoption is optional, existing subscriptions are preserved, and checks run twice: at plan selection and at billing approval.
The golden rule: only add requirements to plans where the feature is truly essential."