{"section":"known-issues","requestedLocale":"en","requestedSlug":"stock-export-does-not-work-for-a-very-large-sku-base-statuscode-429","locale":"en","slug":"stock-export-does-not-work-for-a-very-large-sku-base-statuscode-429","path":"docs/en/known-issues/Logistics/stock-export-does-not-work-for-a-very-large-sku-base-statuscode-429.md","branch":"main","content":"## Summary\n\n\n\nFor customers who have a huge base of SKUs, equal, 500k +, the inventory export will not work. During the exportation process, it will start to generate `StatusCode: 429 Message: Too Many Requests` on our internal logs, and the e-mail with the spreadsheet will never arrive.\n\n\n\n#### Simulation\n\n\nIn any account that has more than 500k+ SKUs, the inventory spreadsheet will never arrive at the e-mail.\n\n\n\n#### Workaround\n\n\n\nA possible alternative to get around this problem is to use our inventory APIs to set up a runner:\n\nBy warehouse:\nhttps://developers.vtex.com/docs/api-reference/logistics-api#get-/api/logistics/pvt/inventory/items/-skuId-/warehouses/-warehouseId-\n\nBy SKU (With all warehouses):\nhttps://developers.vtex.com/docs/api-reference/logistics-api#get-/api/logistics/pvt/inventory/skus/-skuId-\n\nPlease be aware that this process via the API is time-consuming and will most likely generate an outdated inventory report."}