Hey @tomasw!
Thank you for at least considering it and passing it along!
The way I understand it and envision it is that it wouldn’t be like the inventory_sync because that is making changes to inventory, but this could be a replacement for inventory_snapshot, and be able to process any page-able queries thrown at it, whether that be orders, shipments, products, picks/packs_per_day, or whatever.
For example, I could use this to create my own inventory snapshot which contains not only sku and quantities on hand, but also bin location, kit component information, barcodes and tags. These are things that we frequently need for reporting and warehouse management. Right now I have python scripts that our users run to generate things like purchase orders, warehouse moves, take stock offline for production, etc, but in order for it to run, the user has to manually go to the inventory screen in the desktop UI and manually export and make sure the CSV is in the right location for the script to find it, and so on. It’s extra steps for them. Pulling an automated snapshot of products/inventory via normal API methods is currently slow, requires pagination, and so forth. On top of that, I’m still facing the code 22 issues, so a script may get through the first 800 products, and then suddenly error out with code 22. (I know I can catch that, but that’s a full minute wasted of the query trying to get results each time code 22 is hit) This idea of being able to supply the same query to a bulk_operations mutation and have it drop a URL that I can download in the background, process, and serve up the results for the user without them having to worry about getting it themselves would be huge.
Likewise, every day I pull data with the picks_per_day query to store in a database for user performance analysis. I’m also working on a packs_per_day version, but the nested pagination of shipments and lines are throwing me off there. If I didn’t have to worry about the nested pagination, I could more easily handle the URL drop of results, and that would be an amazing thing.
I hope that gives some idea of what it could be used for, and how it’s a generalized solution compared to having specific “snapshot” type queries that have to be separately maintained and updated.
Thanks for hearing me out, and let me know if you have any other questions!
Jeremy
