Hi everyone, I wanted to get some more context on this issue. When customers use shop app or opt for express checkout with shop pay etc, customer is routed off webssite to shop.app etc, In these cases I don’t receive any checkout webhook updates.
In addition to this these checkouts aren’t even available with the adminn or graphql api’s. Is this a known issue? And Can we expect a fix for this? Steps to Reproduce
Create a checkout on shop.app or use shop pay on checkout, monitor webhooks ( not received )
Create a checkout on shop app, try to fetch latest checkouts with rest admin api and graphql abandonedCheckouts endpoint, shop pay checkouts are not included here.
Hey @ShahzaibJak, thanks for flagging this. I do know that with the Shop app/ Shop Pay itself, there are limitations with session/user tracking and it may be similar for webhook triggers (since the checkout is techncially on another domain rather than the shop itself): Shop Pay And Web Pixel Events
I’ll take a look into this to see if we can confirm expected behaviour and share any additional info - speak with you soon!
Hey @Alan_G really appreciate you looking into this , I understand the possible limitation with webhooks, I’m more concerned with these checkouts not being accessible through the checkouts (rest api) or abandoned checkouts (graphql api), hopefully I’m wrong about that but looking forward to hearing from you on this, thanks!
Hey @ShahzaibJak - just looping back with you here. When it comes to webhooks for Shop app/Shop Pay accelerated checkouts, I can confirm that enabling triggers for webhooks to be sent out isn’t something that’s currently on our roadmap.
For accelerated checkouts on the storefront though, these should be accessible through the Storefront API (although you would need to know the cart/checkout ID which isn’t exposed automatically, like through a webhook for example).
For checkouts within the Shop app itself, we generally don’t expose those checkout/cart IDs, although I know there are future plans to enable more third party developer control of the Shop app API through Shop Minis:
That said, I realize how this isn’t the most ideal. Just out of curiosity, what would your use case be for accessing or modifying these carts? Would this just be for storing/validating checkout data for the shop? I just want to make sure I’m understanding your use case here a bit, so that I can better advocate on my end - hope to hear from you soon!
Hey @Alan_G thanks for circling back to me on this, really appreciate you looking into this Our use case is just to store the checkout data for custom tracking, and analytics of our traffic over time.
Thanks @ShahzaibJak I’ve set up that feature request for you on my end. I can’t guarantee a turnaround time on this or if/when we’d enable webhooks or easier retrieval for those checkouts, but your use case is very fair for sure.
Hope this helped a little bit, thanks again for flagging this, I am hoping we do enable this in the future as well as I can see it be very needed for checkout/sales analytics.
, I understand the possible limitation with webhooks, I’m more concerned with these checkouts not being accessible through the checkouts (rest api) or abandoned checkouts (graphql api), hopefully I’m wrong about that but looking forward to hearing from you on this, thanks!
I’ve set up that feature request for you on my end. I can’t guarantee a turnaround time on this or if/when we’d enable webhooks or easier retrieval for those checkouts, but your use case is very fair for sure.