For discussing the development and usage of Checkout UI extensions, post-purchase extensions, web pixels, Customer Accounts UI extensions, and POS UI extensions
Hi, I have made my first app that shows a Text on the shipping page in the checkout process. I would like to install it on my stores but as I saw in the docs I can't install my app on all my stores because I have 2 organizations.
So is there a way to install my app on my stores on the second organization or do I have to make a new app, duplicate everything and install it on my second organization?
If I have to duplicate, is there a way with git or something to simplify maintenance?
Hi AW1234,
Was this created as a custom app? If so, you can go to the app's details page in the Partner Dashboard where you'll find an option to generate an installation link that can be used in stores not associated with your partner org.
Liam | Developer Advocate @ Shopify
- Was my reply helpful? Click Like to let me know!
- Was your question answered? Mark it as an Accepted Solution
- To learn more visit Shopify.dev or the Shopify Web Design and Development Blog
Hi Liam,
to be honest I still don't fully understand the differences between types of apps, I don't see a "details" page on my partner dashboard, I have made my app using "npm init @Shopify/app@latest"
This is sort of where Shopify really dropped the ball. You can only install the link to 1 Org. Otherwise, you'll need to upload it to their public app store, unlist it, and manage it that way. The problem with that is every time you push out an update, you'll need to wait for them to approve it before you can use it.
We ran into the same problem since Shopify didn't have a good answer for us. So, what I did was create a git repo for every extension (see: extension, not *app*), and then created new apps for each Org. Then, from within the Org, I would just clone the extensions. That way, you only need to maintain them in one place.
If you ask me, this is painfully stupid. Lot's of big companies have more than 1 Org. But my experience with this entire Checkout Extensibility has been nothing but horrible. They took away our ability to do anything, and even with the tools they do give us, it's still pretty useless. Want to bold text? Use emphasis='bold' but that's only weight 500, and you can't go any higher so you can barely tell if it's bold or not based on what font you're using. Adding a favicon to Checkout? That requires a 3 different GraphQL mutations which is the dumbest thing I've ever seen.
Checkout.liquid was highly superior in every way to this garbage. Oh, you want more than 20 settings in a single extension? Nope. You want to stack more than 3 extensions together in your Checkout? Nope. You want to use the rich_text_field so you can actually have some way to add links and other text styles to part of your Checkout? Nope.
This is a huge step back, and basically their way of justifying their purchase of Remix.
I completely agree! Checkout extensibility is a huge step back!
Thanks for your suggestions on how to manage different Orgs. It's extra steps but at least makes it possible to maintain the extensions in one place, while still being able to deploy to multiple Orgs.