Hi everyone,
I’m having an issue with SellingPlanInventoryPolicyInput (API docs). It doesn’t seem to affect how product quantity is deducted.
No matter whether I set the policy to ON_FULFILLMENT or ON_SALE, the quantity is always deducted immediately after the order is placed.
Questions:
- Am I missing something in the configuration?
- How can I properly test or trigger the
ON_FULFILLMENT behavior?
Has anyone run into this before, or is this the expected behavior? Any advice would be appreciated!
1 Like
Hey @simposk, thanks for reporting this.
Would you be able to share a few more details to help us replicate this?
I’m curious about the specific setup you’re using. Are you creating this selling plan as part of a subscription app, or for a different type of selling plan like pre-orders or try-before-you-buy? Also, would you be able to share the exact mutation you’re using to create the selling plan with the inventory policy, and maybe an x-request-id from the GraphQL logs when you tested this behavior?
It would also help to understand how you’re testing the inventory deduction timing. Are you checking the inventory levels immediately after placing an order, or are you monitoring the specific inventory states (available vs committed) to see when the change happens?
Are you creating this selling plan as part of a subscription app
Yes, I’m creating a selling plan as part of subscription plan.
would you be able to share the exact mutation you’re using to create the selling plan with the inventory policy
I’m using sellingPlanGroupCreate mutation (API docs).
It would also help to understand how you’re testing the inventory deduction timing.
I’m checking the inventory page, I’m looking at these columns after I place an order using Bogus payment provider: Committed | Available | On hand.
Essentially these columns behave the same, it doesn’t matter if InventoryPolicy is ON_FULFILLMENT or ON_SALE