[BUG] Subscription shipping profiles ignored if products are not also in the general shipping profile

There’s a pretty rough bug that’s impacting all merchants that sell products on subscription. If a product is included in a subscription shipping profile but its not found in the general profile Shopify won’t allow customers to check out with the product event when it has a selling plan attached and any existing subscriptions billing attempts fail with the INVENTORY_ALLOCATIONS_NOT_FOUND error code.

It’s fairly easy to replicate if you’re using a Shopify Subscription app that allows you to create and manage subscription shipping profiles. Steps to reproduce:

To reproduce the issue that leads to the incorrect INVENTORY_ALLOCATIONS_NOT_FOUND error code:

  1. Set up general shipping profile to include all US states ($10 rate)
  2. Set up subscription shipping profile to include all US states ($20 rate) and add it to the selling plan you’ll use in the next step
  3. Purchase subscription to a product in the selling plan mentioned above and use an address in California (should see the $20 shipping rate bc its a sub)
  4. Now remove California from the general shipping profile
  5. Now try to trigger an order on the new subscription you have
  6. See that there’s an INVENTORY_ALLOCATIONS_NOT_FOUND error on the billing attempt

Similar steps to reproduce the issue that leads to the cart thinking that the shop doesn’t delivery to a location that is supported in the subscription shipping profile:

  1. Set up general shipping profile to include all US states but leave out California ($10 rate)
  2. Set up subscription shipping profile to include all US states ($20 rate) and add it to the selling plan you’ll use in the next step
  3. Purchase subscription to a product in the selling plan mentioned above and in checkout, use an address in California (should see the $20 shipping rate bc its a sub)
  4. See that after entering California address, checkout shows a modal saying that the shop can’t delivery to that address and kicks you out of checkout

This is blocking new subscription purchases and renewals on shops that need to not have the product in the general profile (products only sold on subs with sub specific shipping rates) but do have the product in a subscription shipping profile

Let me know if you need a hand replicating : )

Thanks in advance for any help!

Hey Brian,

Sorry for the delay on this - checking with the subscriptions product team on this today.

1 Like

Hey @Liam-Shopify , just checking in here if you have any updates on this. We are also facing a similar issue on our store and a lot of our subscriptions are not getting processed due to this. Appreciate any help on this!

Hi Alex,

I’ve connected with the product team on this and they’ve said “as far as I understand the behaviour is correct here – the subscription contract stores the delivery method and delivery address, and if during the billing attempt we can no longer find any delivery options (due to removing the zone from the shipping profile) then the inventory allocations not found error response is the correct behaviour.”

I think the full context may not have been conveyed then. The problem here is that there is a profile with product and location correctly in it but a subscription shipping profile was updated so that it no longer has the product. Still though, the general shipping profile has the product and covers the location indicating that the shop still ships that product to that location. Note that a shop can have multiple shipping profiles - the problem here is that just because a product isn’t in a subscription shipping profile it seems to break the standard general shipping profile’s ability to indicate that a product can be shipped

If you don’t mind please take another look. The steps (above) are very easy to replicate and should raise alarm

Hey @Liam-Shopify All those subscription renewals were working fine earlier and this issue has started occurring recently without any changes done by the subscription app team. Let us know if you need an API request and response so we can check with them and share it across if that helps to resolve this faster.

This has cost us so much money. Absolutely ridiculous. Are you going to compensate this negligence?

Hi @Alex_5958 - if you could provide an API request and response that would be helpful, thanks!

@Liam-Shopify Here is the required details shared by the team, please have a check once and let us know if you require any further information.

X-Request-Id
Cd48d0d6-bc94-4a73-b638-0f759813269b-1732805850

Request Payload


{
    subscriptionBillingAttempt(id: "gid://shopify/SubscriptionBillingAttempt/xxxxxxxx") {
        id
        idempotencyKey
        ready
        order {
            id
        }
        errorCode
        errorMessage
        nextActionUrl
        originTime
        completedAt
        createdAt
    }
}

Response Payload
{
    "data": {
        "subscriptionBillingAttempt": {
            "id": "gid://shopify/SubscriptionBillingAttempt/xxxxxxxx",
            "idempotencyKey": "XX_44_XX94_17326342XX",
            "ready": true,
            "order": null,
            "errorCode": "INVENTORY_ALLOCATIONS_NOT_FOUND",
            "errorMessage": "No inventory location found or enabled",
            "nextActionUrl": null,
            "originTime": "2024-11-26T15:17:54Z",
            "completedAt": "2024-11-26T15:17:54Z",
            "createdAt": "2024-11-26T15:17:54Z"
        }
    },
    "extensions": {
        "cost": {
            "requestedQueryCost": 2,
            "actualQueryCost": 2,
            "throttleStatus": {
                "maximumAvailable": 2000.0,
                "currentlyAvailable": 1998,
                "restoreRate": 100.0
            }
        }
    }
}




Thanks folks - our team are able to reproduce and looking into a fix now.

@Liam-Shopify Perfect, let us know in case any further information is required from our end.

@Liam-Shopify Just checking in if you have any updates on this.

Hi folks - the product team in this space is working on a fix. As soon as it’s shipped I will update this forum post, but considering it is currently BFCM, this fix may not be shipped today (Dec 2nd).

2 Likes