# Incorrect PO receive quantity
**URL:** https://community.shiphero.com/t/incorrect-po-receive-quantity/2638
**Category:** GraphQL API
**Created:** [October 5, 2023, 7:33pm UTC](https://community.shiphero.com/t/incorrect-po-receive-quantity/2638 "2023-10-05T19:33:27Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@kolbykskk](https://community.shiphero.com/u/kolbykskk)
#### Post date: [October 5, 2023, 7:33pm UTC](https://community.shiphero.com/t/incorrect-po-receive-quantity/2638/1 "2023-10-05T19:33:27Z")
Hi, we have a SKU on a PO with a quantity of 3, but when we look at the product’s inventory logs, it’s showing that the PO caused the inventory to increase by 6. This doesn’t make sense to me since the PO should only be able to receive up to 3.
This is the product link: [https://app.shiphero.com/dashboard/products/details/406902358](https://app.shiphero.com/dashboard/products/details/406902358)
This is the PO link: [https://app.shiphero.com/dashboard/purchase-orders/details/1725743](https://app.shiphero.com/dashboard/purchase-orders/details/1725743)
You can ignore the inventory logs with a note of just “PO 1004”, those were performed manually by us. The other 3 logs were automatic from the receiving on the PO which is where the issue is.
---
### Author:  [@sh-agent](https://community.shiphero.com/u/sh-agent)
#### Post date: [October 6, 2023, 12:04pm UTC](https://community.shiphero.com/t/incorrect-po-receive-quantity/2638/2 "2023-10-06T12:04:00Z")
Hey @kolbykskk,
Thanks for bringing this to our attention!
I wasn’t able to find that PO in your account,
I’ve tried to reproduce the issue on my end as well. I have created, received, and closed the PO all through the API in my tests, as well as created via API, received through [shipping.shiphero.com](http://shipping.shiphero.com/), and closed via API, all unsuccessfully.
Are you still experiencing this issue, and if you are would you mind sharing another example?
Please let me know if you have any questions or concerns.
Best,
RayanP
---
### Author:  [@kolbykskk](https://community.shiphero.com/u/kolbykskk)
#### Post date: [October 10, 2023, 8:27pm UTC](https://community.shiphero.com/t/incorrect-po-receive-quantity/2638/3 "2023-10-10T20:27:38Z")
> [@sh-agent](#):
>
> issue on my end as well. I have created, received, and closed the PO all through the API in my tests, as well as created via API, received through [shipping.shiphero.com](http://shipping.shiphero.com/), and closed via API, all unsuccessfully.
>
> Are you still experiencing this issue, and if you are woul
It’s a major issue that is still happening across many POs and products. Has nobody else reported it? It has started recently after an update you guys made.
Here’s another example:
[https://app.shiphero.com/dashboard/products/details/295075661](https://app.shiphero.com/dashboard/products/details/295075661)
[https://app.shiphero.com/dashboard/purchase-orders/details/1731875](https://app.shiphero.com/dashboard/purchase-orders/details/1731875)
We did 4 separate receive calls of 1 qty. Each time it happened, the quantity updated on the product double what it should have. The qty ended up being 11, which doesn’t even make sense because the PO has a total qty of 4.
---
### Author:  [@kolbykskk](https://community.shiphero.com/u/kolbykskk)
#### Post date: [October 10, 2023, 8:44pm UTC](https://community.shiphero.com/t/incorrect-po-receive-quantity/2638/4 "2023-10-10T20:44:19Z")
Here’s another example:
The product ended up getting a qty of 78 even though that PO only had a total qty of 12. It doubled every single time.
I thought maybe a race condition was happening, aka making receive calls too fast, but these calls happened over almost 5 minutes and they consistently doubled in qty.
---
### Author:  [@sh-agent](https://community.shiphero.com/u/sh-agent)
#### Post date: [October 11, 2023, 3:56pm UTC](https://community.shiphero.com/t/incorrect-po-receive-quantity/2638/5 "2023-10-11T15:56:03Z")
Hey @kolbykskk,
Going to post a reply in this thread as well, just in case!
A change was made internally to address another issue that impacted receiving POs through our Public API. As soon as we got the first reports, our Engineers started working to address the problem and rolled out a fix as of yesterday.
Best,
RayanP