I have created the development store with advanced plan with checkout extendability. After that I went to checkout profile, added checkout app so far it’s good but I am not able to save it. When I pressed save button, it does nothing so I tried to investigate from network panel. I saw that one post api is being called but in it’s response it gives the error that “"This shop’s plan does not support this extension target“
There are couple things here:
- If save fails, it should show the error to user instead of just doing nothing.
- If I can’t save the app block in checkout page, why it shows the option to add it
- Why it can’t allow me to add the checkout app in checkout page even though I had created the development store with checkout extendability. (My guess is that, to have the checkout extendability, I will need to use the shopify plus plan but then I am facing this error as mentioned in this ticket so can’t proceed with it.
You must create a Plus shopify plan to add app blocks in the checkout page.
Just to confirm: checkout app blocks can only be saved on an active shopify plus, and a development store with Checkout Extensibility enabled is not sufficient. I think that explains the silent save failure and the api error.
Okay but in that case as I mentioned, either app block should be hidden on checkout page or there should be clear indication for the user that it’s not saved and why.
App block will appear if the store is on the Plus plan.
That means my store is on Plus plan. So then doesn’t that mean, I should be able to save it?
Actually My shop is on Basic plan but still I can see the checkout app blocks
Are those blocks from Shopify or app?
Those are from the app but Shopify some times hide this sections and some times it doesn’t (for the same plan).
The inconsistency you’re seeing - blocks appearing on Basic, but save failing - actually makes sense once you look at which targets your app registers for. Not all checkout extension targets require Plus. Targets like purchase.thank-you.block.render or purchase.order-status.block.render work on all plans. The actual checkout page targets (purchase.checkout.block.render, etc.) are Plus-only. So if your app declares multiple targets, the editor will show all of them, but only the Plus-restricted ones will silently fail on save. That’s why it looks inconsistent - it kind of is, from a UI perspective, but the plan gating is happening per-target at the API level.
For testing checkout page blocks specifically, the right path is to create a development store through your Partner Dashboard and select ““Checkout and Customer Accounts Extensibility”” as the store type when creating it. That simulates Plus behavior for checkout testing without needing a real Plus plan. A regular dev store on Advanced doesn’t get you there regardless of how it’s configured - that option in the Partner Dashboard is the intended route for this.
As for the silent save failure, you’ve already done the hard part of diagnosing it from the network panel. The API is doing the right thing by returning the plan restriction error, but the checkout editor just isn’t displaying it. That’s a Shopify bug worth filing through Partner feedback - you’ve got a clear reproduction case and the exact API response, which makes it actionable.
Thank you for replying.
The problem with the testing is that, earlier we had this “Checkout and Customer Accounts Extensibility” option but after the new dev dashboard introduced, while creating the store from this dev dashboard, we no longer see this option.
