I can't speak for Shopify and the exact reasons why they're keeping AppBridge sources private for now, but if you follow some of their dev discussions on GH issues you'll find they're considering some changes around AppBridge which to me suggests it's still not ready for releasing sources. Likewise, there have been issues with AppBridge because it still doesn't have feature parity with former EASDK. It just doesn't feel complete so it wouldn't surprise me if that's one of the reasons they're still keeping the repo private until they're happy with it.   Same can be said of a few other packages such as @Klarna/sewing-kit. I believe they'll release sources eventually.   It's quite common for companies to develop that way because expectations of their user base is quite different to that of regular open source users. Even though they'd open source it, users would expect support.   "Hey Shopify, you made so and so and it isn't working, how do I use it? Please help! Hello, why no reply? Any examples? Please provide full solution! I like AppBridge but can you give me a PHP example (oooh, my favourite type)"   If the package isn't ready, they'd flood them with questions and complaints and that would have a number of unpleasant side effects that a company cannot brush off as easily as an independent OSS dev can "Feel free to make a PR and stop complaining, I don't work for you" ;-)   Just my 2c. Best wishes! ... View more

Awesome, thanks once more @Shayne ! ... View more

Good point @leteyski . I was wondering what would happen to those vendors you mention. The fact they already released statements that they will not be affected does suggest they knew upfront. ... View more

@Irene and @Shayne    Thanks for responding with updated documentation and clarification on many concerns raised here. I am no lawyer so all this legal lingo is a little beyond me, but could you also be more explicit about   You're a partner that works with individual merchants on custom checkout needs using a   private app. These changes don't affect your current engagements with these existing merchants. mentioned in documentation. The bold text implies that the changes do not affect existing private apps but leaves a little uncertainty about new private apps. Am I reading too much in to this? The ToS simply exclude all private apps and make no mention of existing or new engagements.   Thanks for listening and being open! ... View more

Hi,   Sounds like a valid question and something the vendor of your loyalty app should be able to address or offer a reason why this isn't possible in their implementation. Have you tried contacting the vendor through their support channel?   Best wishes! ... View more

C'mon @Bryan30 what's up with necro-posting? This thread is from 2012!!!   Besides, paging is documented more broadly as it applies to several resource endpoints. Possibly elsewhere too.   Either way, why bother resurrect an ancient thread unless you have a question and if you do, why not post a new one so this one can be retired? It just messes up Google search results or prompts more users to chime in on old threads by mistake thinking they're current. ... View more

Have you applied the required Storefront API permissions for reading and modifying checkouts? Namely unauthenticated_write_checkouts and unauthenticated_read_checkouts.   Check these access scopes and try again. ... View more

The product ID is not the same as the SKU. A SKU is defined per variant. Even so, a product variant ID is not the same as a SKU. Moreover, SKUs in Shopify are not necessarily unique thus they do not lend themselves as a means of identifying or fetching single resources.   It is not clear who maintains the Zapier integration for Shopify and why they have chosen a specific integration and implementation.   I am not aware of Zapier using Shopify's GraphQL endpoint for the admin API which may be why you cannot filter by SKU. REST Admin API doesn't enable so while in GraphQL Admin API you can do something like query { productVariants(first: 1, query: "sku:SKU-123") { edges { node { id } } } } But beware, like I mentioned before, above query would return 1 product variant but because SKUs aren't enforced to be unique, there could have very well been more than one variant with the given SKU.   Hope this helps! ... View more

Hi,   Because a product object or resource is akin to a base class - it is an object representing common traits of concrete / actual products. These actual products are the product variants. Even a product that has no options defined has a default variant which is why you will always work with variants in a cart, a checkout, an order etc.   Hope this helps! ... View more

Ah, @Mircea_Piturca much more elegant. Forgot about the map. Should be the correct answer! ... View more

Because Shopify recompresses PNG images to 90% quality.   If you want more control over your image compression, use JPG and check the following reference for when and how compression is done by Shopify.   I know this isn't ideal for cases such as yours when you need transparency i.e. using PNG but you may also consider an alternative format that supports transparency and is more size effective than PNG.   Hope this helps! ... View more

Hi,   So if you need a comma separated list of your product variants' SKUs, you can do something like {%- capture variant_skus -%} {%- for variant in product.variants -%} {{- variant.sku -}}{%- if forloop.last == false -%},{%- endif -%} {%- endfor -%} {%- endcapture -%} {{ variant_skus }} You'd capture the SKUs before your TrustBox integration snippet and then simply provide the {{ variant_skus }} to it.   In case you'd need an array of variant SKUs you can also add following to above {%- assign skus_array = variant_skus | split: ',' -%} And work with that array as you'd normally do in Liquid.   Hope this helps! ... View more

I will quickly add that in addition to raising my concerns over on the FB partners group, I totally agree with @Nesters and it's a major pain point for me going forward with Shopify.   I've put a good 6 weeks in to developing a design system targeted at ReactJS based SSRs such as Gatsby or Next exactly because I wanted to provide a storefront solution that has less limitations for merchants. One of the options there is for checkout to bypass Shopify's checkout completely because let's face it people - if you have a storefront like it's 2019 and then you redirect to a checkout that's like 2014 and on top of that it's on a different URL because you can't frame it in to your PWA app... well I am short of civil words to describe this situation. It is not nice!   Look, I get it that you want to keep transactions revenues and I am totally okay with that and so is anyone signing up for Shopify. That's not really the issue or motivation to bypass checkout.   The reason to bypass Shopify checkout is you are NOT listening and from what I can tell from 2013 onward backlogs in these forums have staunchly held position that Shopify checkout is optimal and if you believe it isn't "look at your Plus plan".   Please clarify what @Nesters already mentions - is it okay for merchants to bypass Shopify checkout on their own behalf without partner / dev intervention? Please clarify what this means "Partners cannot bypass Shopify checkout unless authorized by Shopify in writing." - in particular the circumstances of getting authorisation from Shopify to bypass checkout? Please do not make assumptions about checkout and what's best for merchants. Yes you have your numbers to backup your claims and I am sure that checkout, as is, is very effective. But put that in to a completely bespoke and highly branded storefront theme, possibly not even based on Liquid or served by Shopify, and that "highly effective" checkout suddenly sticks out like a massive UX blunder. Open up checkout customisation for all plans. Please complete API checkout - no, webUrl to complete payment step is not good enough for all the reasons mentioned above. Imagine the agony of doing a mobile app and having to load a web view just so we can load that checkout step? You guys surely know that web view on some mobile platforms is quite ineffective. Not to mention the horrid UX when your customer gets kicked out of a stunning native UI experience in to that checkout web view.   So yes, guys & gals, you have my support and all if you wish to forbid bypassing Shopify checkout - but please allow us to use it properly first! ... View more

If you are using GraphiQL app to register the webhooks, the webhooks will be scoped to that app. Using GraphiQL app is fine for quick tests with the API or in your case to get acquainted with hooks. However, be aware that webhooks are always scoped to the app that registered them. So if you want to validate the HMAC in your actual app that's handling the webhooks, you'll have mismatches because of app key not being the same as that of the GraphiQL app.   That's one possibility. If you're running in to a different issue it would help if you provided more context and detailed error message.   Hope this helps! ... View more

Unfortunately not - I do not have any insights regarding their roadmap. Your best bet would be to post a new question asking that and a staff member might offer some insight. ... View more

Password seems to be incorrect or has been changed since. Can't view. ... View more

Never came across that one, but you're probably nesting to many loops within loops within loops within... you get the gist. Without knowing within what context that bit of code is run and what's done in the snippet you're including, it's hard to tell - I'd suggest you start by commenting out bottom up or top down until you locate the part of your theme that's causing this issue then look for ways to fix or provide more context here for further help from forum members. ... View more

Hi,   You have a range of options depending on your own skills with Liquid, HTML, CSS or budget for themes, apps or even bespoke design services.   If you're comfortable with web development you will find plenty resources about theme customisation published by Shopify. If that isn't quite your cup of tea, no worries there are options.   You can always start from a quality theme, whether a free one from Shopify, or a paid one from Shopify theme designers - though I do recommend picking from the Shopify theme store as the quality is generally better than what you shall find elsewhere on the internet regarding Shopify themes. A theme is a great starting point and the wiser you choose from the beginning by evaluating a number of themes and getting to know them and their features / limitations, you will probably get there 3/4 of the way.   The remaining 1/4 would probably require apps or custom development depending on your requirements. Some apps add features such as comments / reviews, bundles and much more while others may give you more flexibility how you present content such as page builder apps. Personally, I'd keep app usage to a bare minimum only of what you really need for your business - that keeps costs down and keeps your store clean and performant. Some theme style changes to suite your brand would always end up being custom adjustments in code that you can achieve yourself, ask for help here on the forums if the request isn't too complicated, or hire Shopify Experts to get the job done.   Last but not least, if your budget permits you to do so, you can have the entire storefront theme designed specifically for your brand. This does have several benefits but comes at considerable cost for many starting businesses.   Hope this helps and feel free to ask if you need more information or pointers to explore any of these options in more detail.   Best wishes! ... View more

So pull via since_id and sort on your end in app code once all orders have been fetched. You'd anyway want results in default sort order by ID so you have the last items' ID for the next request. ... View more

Unfortunately, you're right in your prediction that this is not possible - any content added in the rich text editor is rendered as HTML. Even Liquid code itself.  ... View more

Yes and I agree. That would depend on which apps you pick, their capabilities and other factors. I cannot give you any definitive answer to that (I haven't used these apps) other than trying to contact the vendors, discuss your requirements and get assurances that your requirements can be met before you make any commitments. Also, a good place to ask about apps is in the app section of the forum. ... View more

All of what you mention is possible. It really boils down to whether you will be creating all that functionality as part of a bespoke app or not. If so, it will be quite a bit of work, but there are no technical obstacles Shopify side to not make it possible.   If you wish not to do this bespoke, I suggest you have a look at recurring payment / membership apps as that will be essential. The on-demand print providers you mention already have apps for Shopify so that should be fine too. I'd recon the last bit you'd need to implement yourself would be a membership area with gallery of designs etc. and automatic creation of products / variants per apparel type and design combination to be presented to final customers. ... View more