Why can't functions run on draft order based checkouts? #393
Replies: 22 comments 15 replies
-
This would be a great addition, and it would help with overall app compatibility. |
Beta Was this translation helpful? Give feedback.
-
Agreed on the fragmentation part, there’s quite some merchants using functions were confused because the functions were not running sometimes (on draft order checkout), please look into this or at least make an option for merchant or developer to run functions on draft order. |
Beta Was this translation helpful? Give feedback.
-
Automatic discount functions work in draft orders now, but I'm not sure about other Functions APIs. |
Beta Was this translation helpful? Give feedback.
-
We also need Functions in Draft orders because we get a ton of uninstalls if the people use Hulk Options for example. These "Customiziation Apps" often work with draft orders. |
Beta Was this translation helpful? Give feedback.
-
Moving to General as this affects multiple APIs. |
Beta Was this translation helpful? Give feedback.
-
Bump for this, as this is causing huge problems and really bad and fragmented experience for merchants. |
Beta Was this translation helpful? Give feedback.
-
Wow, this is a huge oversight. Honestly why is there even a separate checkout to begin with. I have plus Merchants who wish to allow certain customers who pass a credit check to buy on invoice. The results of the credit check are stored in a metafield attached to the customer. When the customer goes to the checkout and they have the appropriate score they can purchase on invoice, if not the payment method is hidden. Now one merchant has an app that applies discounts to the order, but it creates a draft order and routes the customer to the draft order link instead of going to to the normal checkout. and suddenly for customers who shouldnt be able to purchase on invoice the option is available. This could cause serious headaches for the merchant having to deal with this huge potential for fraud. In any of the other APIs I would say ok, it takes a bit of time to roll things out everywhere, but the payment API that just needs to work and work everywhere. Cheers, Gary |
Beta Was this translation helpful? Give feedback.
-
I'll bump this too! It's quite frustrating to tell merchants that there is no way that the customizations will work for them for a reason totally out of our control. Around 30% of the merchants that use my customizations have problems with this. I hope Shopify will support draft orders with functions 😪 |
Beta Was this translation helpful? Give feedback.
-
Will the payment customization API work for draft orders? I would like to disable postpaid payment if a product with a specific tag exists in an order created by draft order using the payment customization API of shopfiy functions. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
According to this timeline there is no mention whatsoever to Draft Orders in future Shopify Functions features: https://shopify.dev/docs/apps/checkout |
Beta Was this translation helpful? Give feedback.
-
This is really bad over sight in my opinion. This has ruined the customer experience for some of my clients, as we just assumed our functions would be working, a lot of merchants use draft order checkouts! |
Beta Was this translation helpful? Give feedback.
-
Please work on this! Shopify sales talked up it's B2B capabilities when selling me on the Plus subscription and I keep running into missing functionality with draft orders which I absolutely need when working with wholesale buyers. |
Beta Was this translation helpful? Give feedback.
-
Does the first video on the Summer '24 page talk about this? It looks like Draft Order now works with payment customisations but then if you search on the page you'll find no information about this. |
Beta Was this translation helpful? Give feedback.
-
This is also not great for POS, since emailed carts use draft order checkout now 😅 |
Beta Was this translation helpful? Give feedback.
-
Any updates on this? Is order discount supposed to work on draft orders? Because it doesn't work for me =( |
Beta Was this translation helpful? Give feedback.
-
This is a big issue for us, and I don't understand why it's not even mentioned on the roadmap https://shopify.dev/docs/apps/build/checkout#product-roadmap Any updates? |
Beta Was this translation helpful? Give feedback.
-
Also need this. |
Beta Was this translation helpful? Give feedback.
-
Can we get a timeline on this? @shopify-admins |
Beta Was this translation helpful? Give feedback.
-
Has the Function API started working with draft orders? I just tested the Validation API, and it’s suddenly working with draft orders. |
Beta Was this translation helpful? Give feedback.
-
I can confirm Payment Customizations are still not working with Draft Orders. @shopify-admins Is there a possibility that this is added to the roadmap? It would make Payment customizations a more complete product. |
Beta Was this translation helpful? Give feedback.
-
Closing as draft orders now support payment & delivery functions: https://changelog.shopify.com/posts/draft-orders-now-support-delivery-and-payment-method-customizations-and-checkout-rules |
Beta Was this translation helpful? Give feedback.
-
This issue is related to #357.
What was reported in #357 is that draft order based checkouts are running Shopify functions recently. But this has been actually happening for at least 5 months or so. This is not a new behavior. I tested draft order based checkouts 5 months ago using functions and they were running fine, the only issue I observed was that the cart line details and delivery groups details were not being reflected in the function input, the cart lines/delivery groups details were always set to be null. Other than that, everything seemed to work fine.
This means that there are a lot of merchants in the last 5 months who set Shopify functions on their store, while they also had some other app which was creating draft order based checkouts on their store (There are a lot of apps who use draft order API). They were able to successfully use the functions to modify the checkout, even when it was generated using draft order API, since functions were running fine on these checkouts as well.
After #357 was resolved, functions are not allowed to run on the draft based checkouts anymore, so all of those merchants who were using functions successfully in the last 5 months (while having other apps which caused their checkout to be draft order based), now have huge problems, since functions were suddenly not running anymore on the checkout and all the logic they set in the function to show correct options at the checkout went down the drain.
This has caused a lot of problems for those merchants and I've been trying to mitigate it as much as I can by communicating to them and explaining to them, why is this happening. But if the functions team can answer questions mentioned below, that would be very helpful.
1 - When can functions run on the draft order based checkouts again? what should I tell merchants?
2 - Is there any way to make this feature high priority?
This is creating a
fragmented experience for merchants
(even for those who are new to functions), they set the function on their store and it works, then they install another app and suddenly their checkout breaks, since functions stop working and they have to go through a lot, just to figure out what happened and how to fix it.It is
nice
to add new features into functions, but functions are useless when a lot of merchants can't even use them, since they are already using other apps which use draft order API. Enabling thisessential
feature will create a more smoother experience for merchants and reduce a lot of issues.Beta Was this translation helpful? Give feedback.
All reactions