Inventory report and credit usage

GraphQL API
1

Hi, this post is somewhere between a feature request and a limit-increase request.

We need to pull a complete inventory report each day.

We use this to place orders with suppliers and to transfer stock between warehouses.

At our currently SKU volume, the inventory report requires in excess of 15,000 credits. And this credits-requirement will rise in the future.

Once the inventory report is fetched our system makes transfer and purchase orders. And this requires even more credits.

So in the first few hours of operation each day, we need a significant multiple of the current credit-limit of 5,000 per hour.

So could you please look at

  1. either increasing the credit limit?

  2. Or setting the limit at 120,000 credits for 24 hours instead of an hourly limit

  3. Or have a separate query with separate credit limits for standard reports like inventory?

Thank you.

2 Likes
2

I, too, would like to see something like this.

We’ve been moving some of our reporting and automation to use data from ShipHero instead of some of our other systems, but since some of the standard reports don’t include fields we need, we have to use the API. And since we generally need to have a full list of inventory and product attributes as a basis for the reports, hitting those limits makes the workflow a lot harder.

I get why there are limits in place, but it certainly does create headaches when the data we need to get at en masse is available only in the API.

3

@jeremyw @amit.wilson could you please share the queries you are using to fetch the inventory report you are trying to mimic?

4 
Hi Seba,

here is the query we are using:

query {
    products {
         data ( after:  "' + nextPage + '" ) {
            pageInfo {
                 endCursor
                 hasNextPage 
            } 
            edges {
                 node {
                     id 
                     name 
                     sku
                     barcode 
                     value 
                     warehouse_products {
                         on_hand inventory_bin 
                     } 
            }}}}};

And the variable *nextPage* is the endCursor value.
5

Hi @seba ,

Mine is a bit more hypothetical as we’re still so new to ShipHero and are in the process of development of our automation and reporting processes around it, so this is something that, I think, would cover nearly all bases in terms of product export, regardless of the final destination of the data.

query ($cursor: String){
    products {
        request_id
        complexity
        data(sort: "sku", after: $cursor) {
            edges {
                cursor
                node {
                    sku
                    name
                    value
                    price
                    kit
                    kit_build
                    barcode
                    created_at
                    components {
                        sku
                    }
                    warehouse_products {
                        inventory_bin
                        inventory_overstock_bin
                        on_hand
                        reserve_inventory
                    }
                    vendors {
                        vendor_id
                        vendor_sku
                    }
                }
            }
        }
    }
}
6

Thanks guys, we will be looking into the inventory report issue and ways to make this possible.