As of February 27, 2026, the Shopify Partner Program Agreement requires every app to use transparent, fair pricing, which it says includes giving merchants advance notice before any price change. The era of the silent intro-then-hike is over, even though the agreement never names the tactic.
- Advance notice of any price change is now a contractual requirement, not a courtesy.
- Partners are responsible for the pricing-notification laws of every region their merchants operate in, so the strictest jurisdiction sets your floor.
- Payment apps face new rules: periodic compliance reviews, plus a mandatory wind-down period and all fees paid before an app can be removed.
- Before the deadline: write a price-change notice policy, surface intro rates and their future price up front, and build a real notification flow.
Buried in Shopify's February 2026 Partner Program update, under the heading of billing transparency, is a clause that quietly outlaws one of the most common growth tactics in the app store: the low introductory price that silently jumps once the merchant is locked in. The agreement does not name that tactic. It does something more durable. It makes the surprise version of it a breach of contract, by requiring advance notice before you change any price.
This post decodes the billing and pricing-transparency clauses specifically. It is not the full agreement walkthrough, which covers the AI data rules, the new partner roles, and the checkout redefinition. You can read all of that in the complete 2026 Partner Program Agreement breakdown. And it is not a how-to-price guide. If you want the strategy of setting your number in the first place, that is the Shopify app pricing strategy post. Here I am decoding the rules you now have to price inside of.
I write this from the seat of having helped build the Partner Program, and from having run my own software company's billing. The instinct behind these clauses is one I recognize from the inside. The app store is Shopify's storefront as much as it is yours, and a merchant burned by a surprise app charge blames Shopify, not just the app. The platform is protecting its own trust with merchants here, and the practical effect is a higher bar for how every app handles pricing changes.
What the billing
clause actually
requires of you.
The text is short and the obligation is broad. Shopify's FAQ states that all apps must ensure transparent and fair pricing for merchants, and that this includes providing advance notice before adjusting any prices, so merchants can make an informed decision. Two phrases carry the weight: "advance notice" and "any prices." There is no carve-out for small changes or for changes the merchant might not notice. Any price adjustment triggers the notice obligation.
The second sentence is the one founders underweight, and it is the one that varies by where you sell. Partners are responsible for understanding and complying with all applicable laws on pricing notifications and changes, including the laws specific to the regions their merchants operate in. Shopify is explicit that requirements vary by jurisdiction and recommends independent legal counsel. In plain terms: the platform set a floor, and the law in your merchants' countries can raise it above that floor.
"Shopify set the floor. The law in your merchants' countries can raise it. Your billing has to satisfy the strictest jurisdiction you sell into, not the most lenient."
So the real standard is not one rule, it is two stacked. Shopify's contractual requirement of advance notice on any change, plus whatever consumer and pricing law applies in each region you serve. An app selling only to one country has a simpler job than one selling globally. Either way, the days of treating a price change as a quiet backend toggle are finished. This is the kind of operating constraint that, like the wider terms in the 2026 Partner Program, every founder needs to actually read rather than assume.
The silent intro-then-hike
is what this clause
was built to kill.
You know the pattern, because it is everywhere in the app store. An app launches at a low monthly rate to win installs, then raises the price months later once switching is painful, often with no real warning. The merchant discovers it on the next invoice. That move worked because the friction of leaving exceeded the annoyance of the increase. The advance-notice rule attacks exactly that calculus.
Here is the important nuance: the clause does not ban introductory pricing. You can still launch low and raise later. What you cannot do is make the increase a surprise. The legitimate version discloses the future price at sign-up and notifies before the change lands. The non-compliant version hides the increase and lets the invoice deliver the news. Same intro rate, completely different compliance posture, and the difference is disclosure.
| Practice | Compliant | Non-compliant |
|---|---|---|
Intro rate at sign-up | Allowed | Allowed |
Future price disclosed up front | Yes | No |
Notice before the increase | Yes, in advance | None, invoice surprise |
Merchant can decide before it hits | Yes | No |
The cost of getting this wrong is not just a policy strike. A merchant who feels ambushed churns angry, leaves a one-star review, and tells the platform. That is the chain Shopify is trying to break, because it pollutes the store's trust. Worth remembering: a price increase that drives a merchant out the door is a churn event, and as I have argued, churn is usually a symptom, not the problem. A surprise hike is a self-inflicted churn cause that the new rule now also makes non-compliant.
How much notice,
through what channel,
and to whom.
Shopify did not put a number of days in the agreement, which frustrates founders who want a clean rule. The reason is the second clause: the required notice period is whatever the strictest applicable law in your merchants' regions demands, and Shopify is not going to author a global number that could undercut a local one. So the platform says "advance notice" and pushes the specifics onto you and your counsel.
My practical guidance, and it is guidance, not legal advice: pick a clear lead time, apply it everywhere, and make it the strictest one you reasonably need. Thirty days is a sensible floor for a SaaS price change and clears most consumer-protection regimes, but check the jurisdictions you actually sell into before you commit, because some are tighter. A consistent, generous notice window is cheaper to operate than a patchwork of per-region timers, and it reads as fair to merchants, which is the whole point.
Channel matters as much as timing. A notice buried in a billing-API event the merchant never opens does not satisfy "so merchants can make an informed decision." Notify through a channel a human actually sees: an in-app banner plus an email to the account owner, with the new price, the effective date, and what to do if they want to cancel. The same logic that governs good app onboarding applies to billing changes: if you want the merchant to act on information, you have to deliver it where they will see it, not where it is technically delivered.
If you run a payment
app, you got two
more obligations.
The February update added a separate set of rules for payment apps, and if you build one, these matter more to you than the pricing clause. Two are new. First, payment apps are now subject to periodic compliance reviews, and apps that fail to meet the requirements of Shopify's payment ecosystem can be removed from the Payment Program. The bar is no longer a one-time approval, it is an ongoing standard you have to keep clearing.
Second, and more operationally significant, every payment app must support a wind-down period for merchants after the app is removed from the platform. The intent is merchant continuity: a store that relies on your payment app cannot be left stranded mid-transaction-flow when the app exits. You have to provide a transition runway. And there is a money condition attached: all fees owed to Shopify, inclusive of annual program fees where applicable, must be paid before your app is successfully removed from the program.
Read together, these change how a payment app plans its own exit, whether that exit is voluntary or forced. You cannot simply switch off. You owe merchants a graceful transition and you owe Shopify a clean balance, and both have to be satisfied before removal completes. That is worth modeling into your runway now, because it affects how an acquirer underwrites the business too, which feeds directly into what buyers actually want when they acquire a Shopify app.
Why Shopify put these
rules in writing, and
what it signals.
None of this is the platform turning on its partners. It is the platform protecting the asset it cares about most: merchant trust in the app store. Read it from Shopify's side. Every surprise charge, every ambushed merchant, every payment app that vanishes mid-flow erodes the store's credibility, and the store is one of Shopify's strongest distribution surfaces. Writing fairness into the agreement is the platform defending its own storefront.
There is a strategic signal here too. As Shopify pushes deeper into payments and into agentic commerce, where software, not a human, may be choosing and paying, predictable, transparent billing becomes infrastructure, not nicety. A pricing model an agent cannot understand is a pricing model that loses in an agent-mediated store. The transparency rules quietly prepare the ground for that world. The same shift is reshaping distribution, which I cover in the app distribution playbook.
The honest founder takeaway is that this is the platform's leverage showing, in a benign form. Shopify can rewrite the terms you operate under, and it just did, in the direction of merchant fairness. That is a fine direction. But it is a reminder that the rules layer is theirs to change, and building a business that only works if you can spring a quiet price increase was always building on sand. The terms move, and they move in the platform's interest, which here happens to align with the merchant's.
What to change in your
billing before the
deadline lands.
This is a manageable list, and most apps can clear it in days, not weeks. Run it in order.
If you run a payment app, add a fourth item: document your wind-down plan, including how merchants transition off and how outstanding fees get settled before removal. Build it before you need it, because the situations where you need it, a forced removal or a wind-down, are the worst times to be designing the process from scratch. And whatever your app type, write the policy down. When the burden of proof is on you, your documentation is your defense, the same principle that runs through the whole 2026 update. The economics of all this, including how your pricing interacts with Shopify's cut, are worth running through the revenue share and lifetime cap post and a quick free-to-paid conversion check, because a fair, well-notified price change should still protect your unit economics.
The billing-transparency clauses are not a punishment, they are a standard, and a reasonable one. Give merchants advance notice of any price change, do not spring a hidden hike, and if you handle payments, plan a graceful exit and keep your account clean. The apps that get hurt will be the ones whose growth quietly depended on the surprise increase. The apps that come out ahead will treat transparent pricing as a feature, because a merchant who trusts your billing is a merchant who stays. Take the deadline as the nudge to build the fair version on purpose.
What app founders ask me
about the billing
transparency rules.
Effective February 27, 2026, the Partner Program Agreement requires every app to use transparent and fair pricing for merchants, which it says includes giving advance notice before adjusting any prices so merchants can make an informed decision. Partners are also responsible for complying with the pricing-notification laws of every region their merchants operate in. The full update is in the agreement breakdown.
It does not name the tactic, but it makes the surprise version of it non-compliant. The agreement now requires advance notice of any price change. A low introductory rate that silently jumps later, with no warning to the merchant, fails the advance-notice and transparency standard. You can still use intro pricing, but the increase has to be disclosed up front and notified before it lands. How to price well is in the pricing strategy post.
The agreement requires advance notice without naming a fixed number of days, and it makes partners responsible for the notification laws of the regions their merchants operate in, which do set specific windows. The practical answer is to pick a clear lead time, 30 days is a sensible floor, apply it consistently, and check the strictest jurisdiction you sell into before settling on it. This is guidance, not legal advice.
Payment apps must support a wind-down period for merchants after the app is removed from Shopify, so stores can transition without losing business continuity. All fees owed to Shopify, including any annual program fees, must be paid before the app is successfully removed from the Payment Program. Payment apps are also now subject to periodic compliance reviews, so the bar is ongoing, not a one-time approval.
Set a written price-change notice policy with a clear lead time and a defined channel, in-app and email. Make any introductory rate and its future price visible at sign-up. Build a real notification flow rather than relying on a billing-API charge to surprise merchants. Payment apps should add a wind-down plan. Then document the policy so you can show compliance if asked. Pair it with a revenue share check so the new fairness does not break your margins.
Reworking your billing and pricing under the new terms?
I helped build the Shopify Partner Program, the rules layer your app prices inside, then founded and sold a software company with its own billing model. If you are setting a notice policy, fixing intro pricing, or planning a payment-app wind-down, that is the view I bring.
Start a conversation See the case studies →A note on sources: the February 27, 2026 effective date and the billing, payment-program, and wind-down clauses are from Shopify's developer changelog and the Partner Program Agreement FAQ, which states that all apps must ensure transparent and fair pricing including advance notice before adjusting any prices, that partners are responsible for regional pricing-notification laws, that payment apps face periodic compliance reviews, and that payment apps must support a wind-down period with all fees, including annual program fees, paid before removal. The reading of intro-then-hike as the implicit target, the notice-window guidance, and the compliance sequence are mine, from building the Partner Program and running a software company in this ecosystem. This is not legal advice; consult independent counsel for your specific case.