We are setup with the WooCommerce connector which automatically syncs inventory values from ShipHero to WooCommerce, it works well overall but we have had a couple instances where for whatever (unknown) reason our WooCommerce did not get updated properly. So I’m wondering if there is a way that I could occasionally kick off an inventory sync from the graphql api, similar to the inventory force “Push” button in the ShipHero UI.
I poked around and the only thing I could find that was remotely close was the inventory_sync mutation, but I wonder if that has a different purpose, maybe it is for pushing inventory values INTO ShipHero?
Good instinct to double-check before using it. inventory_sync won’t do what you’re after. That one works the other way around: you give it a URL pointing to a CSV, and ShipHero reads that file to update inventory quantities inside ShipHero. It’s meant for bulk-loading a physical count, so running it hoping to update WooCommerce would actually overwrite your ShipHero numbers instead.
Unfortunately, there’s currently no functionality in the Public API to trigger an inventory sync to a sales channel. That applies to all channels, not just WooCommerce.
What we can do is look into why those pushes are failing. ShipHero keeps a record of every inventory push attempt per product, so with a few examples we should be able to see what went wrong.
Could you send over the SKUs of the products that didn’t sync correctly, along with roughly when you noticed it? Two or three is enough to start.
It would also help if you linked your ShipHero account ID to your Community profile:
Click your profile picture in the top right corner and go to your profile.
Select Preferences.
From the options that appear, click Profile.
Scroll down until you find the text box for your ShipHero account ID, and add it there.
Once I have that I’ll take a closer look and let you know what I find.
One more thing. Could you also open a ticket with our Customer Support team about this? Community is a bit limited for digging into account-specific data, so having it there means we can look at your store’s push history properly and follow up with you directly.
Thanks, this was a helpful clarification. I did reach out to customer support and after that my ops guy decided it wasn’t worth looking further into at the moment. If we experience more problems in the future we might follow up. Thanks.