Selling plan anchors

Solved
smathur
Tourist
8 0 1

Hi,

Thanks for setting up this forum focused on the Subscriptions API. I have been working with this API for some time now and looking for answers to the following questions:

1) In the SellingPlanRecurringDeliveryPolicy object, anchors field is defined as an array. However, it appears that Shopify only takes into account, the 0th element supplied in the array and ignores the rest. Could you please confirm this and explain the behavior in case multiple anchor days are specified along with cutoff period?

2) The sellingPlanGroupCreate mutation requires that anchors defined on Delivery Policy and Billing Policy should match. Otherwise the following error occurs: "Selling plan's billing and delivery policies anchors must be equal". If they are required to be same, why 2 inputs are provided? Is there any plan to allow these delivery and billing anchors to be different in future?

3) Is it correct to say that the cutoff and preAnchorBehavior fields are only relevant and effective when anchors are specified in the Delivery Policy of a Selling Plan? Do they have any impact on the Subscription Contract or first fulfillment order if anchors field is empty?

Philibert_Dugas
Shopify Staff
Shopify Staff
4 4 4

This is an accepted solution.

Hey   Thanks for the questions

1) In the SellingPlanRecurringDeliveryPolicy object, anchors field is defined as an array. However, it appears that Shopify only takes into account, the 0th element supplied in the array and ignores the rest. Could you please confirm this and explain the behavior in case multiple anchor days are specified along with cutoff period?

You're right, we currently only take the first element in the array. This seems to be an inconsistency in the API, we'll definitely take a look  

2) The sellingPlanGroupCreate mutation requires that anchors defined on Delivery Policy and Billing Policy should match. Otherwise the following error occurs: "Selling plan's billing and delivery policies anchors must be equal". If they are required to be same, why 2 inputs are provided? Is there any plan to allow these delivery and billing anchors to be different in future?

We don't have any short terms plan to let them be different, you can see our goals this year inside the FAQ. Perhaps something in the long run that we'd look at revisiting

3) Is it correct to say that the cutoff and preAnchorBehavior fields are only relevant and effective when anchors are specified in the Delivery Policy of a Selling Plan? Do they have any impact on the Subscription Contract or first fulfillment order if anchors field is empty?

This is correct, without anchors there is no impact on the contract Thanks for the question, we'll look at improving our documentation in the API reference to make this clearer

smathur
Tourist
8 0 1

Thanks for your quick response.

0 Likes