Hi @George_Drakakis,
Thanks for the additional context, I do just want to point out the edit I made in my previous post, as I did share some incorrect information initially and corrected it after.
It does sound like you have a solid understanding of the needed workflow, and have it implemented already which is great, and unfortunately due to all apps being created in the Dev Dashboard now, including Merchant Custom Apps, all apps will require the merchant to approve the scopes to use them.
I think going forward you have two options for the simplest workflow for the merchant themselves.
Partner Custom App using Authorization Code Grant:
- Create a Partner Custom App, in the Dev Dashboard from your own Partner Account
- Implement Authorization Code Grant to set the scopes and get access tokens on install.
- Provide the merchant with the install link from the Dev Dashboard when you select Custom Distribution.
- Merchant will only need to visit the install link, then will be redirected to the scope approval page automatically, they simply have to press the button to install the app, then press the button to approve the scopes requested.
- This is the simplest for the merchant, but it does add complexity in your implementation with the Authorization Code Grant workflow.
Merchant Subscribed Webhooks:
- Provide the Merchant with the webhook topic, and your webhook endpoint URL that you need to subscribe
- Guide the merchant in their store’s admin to
settings > notificationsand have them subscribe the webhooks directly
- This method is less simple for the merchant, but it’s still not very complex and is a well documented process in our Shopify Help Center. This also does not require ANY apps on your end as the webhooks are subscribed directly via the merchant’s admin. This won’t be viable if your app does need to make any other API calls other than just subscribing to webhooks.
I do understand that the new methods of app creation and authentication is not ideal, compared to the previous Legacy Custom App workflow. Our developers are aware of this and will be looking into way to improve this workflow in the future, and I will be submitting some feedback on your behalf internally regarding this as well.