Custom shipping_line doesn't work with Checkout API; checkout URL format has been changed

[trungnus96]

Hi there,

I've developed an application that uses Checkout API to create a checkout URL with a custom shipping_line. For example:

{
    "checkout": {
        "line_items": [
            {
                "variant_id": 41353482141879,
                "quantity": 1
            }
        ],
        "shipping_line": {
            "price": 0,
            "custom": true,
            "title": "Pickup from somewhere"
        }
    }
}

Previously, when I set shipping_line.price as 0, the checkout page didn't have Shipping in the breadcrumb, as well as it didn't ask me to choose Shipping during checkout process:

However, I just tested my application on my development store today (03-Dec-2022), it appeared that: even though I generated a checkout URL via Checkout API with shipping_line.price 0, it now showed Shipping in the breadcrumb, and asked me to choose Shipping during checkout process.

I also noticed that the checkout URL format was changed.

Previously, the checkout URL looked like this:

domain.com/60930687159/checkouts/9bfb8841565950dd6e5e5ba74818724e

But now:

domain.com/checkouts/co/9bfb8841565950dd6e5e5ba74818724e

With the new format of checkout URL above, query parameters in the checkout URL don't work neither.

Any helps would be highly appreciated. Thank you

[Tom739]

Shopify has been messing up with the checkout url during the last several month, breaking the query parameters in the process. They seemed to have rolled back their change at the beginning of November and the issues with query parameters were gone. They seemed to have deployed the change again on November 23rd and now the problem seems widespread. It has been confirmed by another user on a different thread. Thread  

It is almost impossible to receive support from Shopify Support on this since query parameters are most often used in custom code.

[vincetsang]

This is at least the 4th time in the year that they broke the query param feature already - this time the issue started reappearing on Dec 9 and now it's been a whole week without resolution. In the previous 3 times the issue was automatically resolved after a couple days, but none of the times I got any response to the support ticket I filed, not even a single acknowledgement that they have identified the cause and fixed the issue on their side. If someone has any idea how to make them realize the importance of not breaking a well documented official feature as if it is no big deal I am all ears...