No content to show
User Activity
05-24-2024
@Richard_L Can you take a look at this new discussion? It is closely related.https://community.shopify.com/c/payments-shipping-and/impossible-to-sync-inventory-with-duplicate-skus/m-p/2588487#M87389
According to Shopify docs a properly implemented fulfillment service integration should respond to the "fetch_stock.json" callback with the on-hand amount of the SKUs requested. Shopify then subtracts the "Committed" amount from this number to derive...
I think if Shopify just always took the number from fetch_stock.json as "on hand" and did "on hand (from fetch_stock.json) - committed - reserved - unavailable = available, even if negative" this all would be way less confusing for everyone.Great obs...
10-23-2023
Thanks, Richard. Your understanding is correct, we just want to update Shopify inventory immediately rather than wait for the next hourly sync to avoid oversells. I had a support ticket open with Dan T. in which he stated that some changes and data c...
10-11-2023
Hi Richard, Thanks for looking into this and your reply. @Richard_L wrote:I believe you were using the inventorySetOnHandQuantities mutation, with the reason "reservation_created".I checked the logs to be sure and we were only using `inventoryAdjustQ...
10-05-2023
No, you should use a query to get all item ids, cache this locally and use it to map the SKUs to location ids. You can use `inventory_levels/connect` and `inventory_levels/disconnect` webhooks to invalidate your local cache. GraphQL to get all item i...
09-27-2023
Hi,Our fulfillment service app makes inventory adjustments based on various factors. One is when an order is placed in the WMS from a source other than Shopify. We were recording these in Shopify with the "reservation_created" reason so they could ea...
Ahh, you are correct, sorry - I forgot that the full destination was included on the FO response already. Thanks again! Still, Shopify should change the way they define the age of an order to be after it is complete, in my opinion.
Brilliant, Gary! We'll try using the GraphQL as you stated when updating note and tags. Thanks! However, there is still the issue of not being able to read orders that are not complete yet. If fulfillment was not requested until the order was over 60...
As an API consumer that represents a WMS which provides a fulfillment service there are not enough details exposed on the FulfillmentOrder API to be able to fulfill the order without also using the Order API to get additional order details. This pose...
We used the GraphQL for this one API request and kept the rest of the app using REST which took longer than it would have to use REST but it did work..
Just adding a data point here, we would definitely appreciate the REST API being brought to parity with the GraphQL API, lack of multiple tracking number support has been an often reported problem and it is good to know there is support in the GraphQ...
Kudos to you and the Shopify product and dev teams for handling this! There was a lot of blowback, and rightfully so, but you've handled it well. I have no doubt it was a large effort to make such significant changes so quickly. Will these changes be...
@Shay The Committed/On Hand behavior also makes inventory syncing way overly complicated with a Fulfillment Service with "inventory_management: true". Our WMS already tracks inventory with great detail and supports orders from many sources so to get ...
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 558 | 10-05-2023 09:10 AM |
