# Received the wrong quantity?

**URL:** <https://community.shopify.com/t/received-the-wrong-quantity/630676>\
**Category:** Shopify Discussion\
**Tags:** inventory, inventory-management, shop-performance\
**Created:** [June 2, 2026, 8:53pm UTC](https://community.shopify.com/t/received-the-wrong-quantity/630676 "2026-06-02T20:53:21Z")\
**Posts on this page:** 5\
**Page:** 1

## AI-generated summary

Inventory counts that become inaccurate after supplier deliveries may stem from receiving shipments by carton rather than checking each unit against the purchase order (PO). Shortages, damaged goods, or incorrect variants can go unrecorded, later appearing as stockouts or unexplained discrepancies.

Recommended practices include:
- Reconcile each PO line at the unit level and record each exception immediately, ideally with packing-slip photos.
- Avoid correcting one variant to compensate for another; that can conceal the supplier error in the PO history.
- Use Shopify inventory-adjustment reason notes and barcode scanning to preserve an audit trail.
- Check for multiple apps updating inventory at once and ensure location settings reflect the warehouse setup.

The discussion’s main takeaway is to reconcile discrepancies when receiving or closing the PO, rather than trying to fix counts later. No specific workflow or tool was selected, and the conversation does not report a confirmed resolution.

<div class="post-metadata">

**Author:** ![MiloDeMilo](https://yyz1.discourse-cdn.com/shopifyforum/user_avatar/community.shopify.com/milodemilo/32/401503_2.png) [@MiloDeMilo](https://community.shopify.com/u/MiloDeMilo)\
**Post date:** [June 2, 2026, 8:53pm UTC](https://community.shopify.com/t/received-the-wrong-quantity/630676/1 "2026-06-02T20:53:21Z")

</div>

If your counts go wrong right after a supplier delivery, you need to look into how you are receiving the shipments. The common version: a delivery gets marked received against the PO based on a quick box count, but a few units were short, damaged, or the wrong variant — and none of that gets recorded. From that moment your count is wrong, and it surfaces later as a phantom stockout or an unexplained returns cluster.

What helps: receive against the PO at the unit level, not the box level, and record every discrepancy (short / damaged / wrong variant) the moment you find it rather than fixing it later. Also worth checking that no other app is writing inventory at the same time and that you’re not on multi-location if you run a single warehouse — both distort counts in ways that look like sync bugs.

Full disclosure, I’m building a tool in this space, so weight that accordingly, but the principle holds regardless of what you use: an error caught at the dock costs ninety seconds; the same error caught downstream costs you a quarter of chasing it.

---

<div class="post-metadata">

**Author:** ![DougInOr](https://avatars.discourse-cdn.com/v4/letter/d/f14d63/32.png) [@DougInOr](https://community.shopify.com/u/DougInOr)\
**Post date:** [June 2, 2026, 9:06pm UTC](https://community.shopify.com/t/received-the-wrong-quantity/630676/2 "2026-06-02T21:06:48Z")

</div>

Exactly. A large issue indeed. I built [FyreTrail](https://apps.shopify.com/fyretrail) to handle this problem exactly. So often deliveries arrive with extra, less or not even ordered items than what you originally placed the order for. I think anybody that makes a Purchase Order app needs to not only handle this, but handle it in such a way that it’s inline with how stores receive items. Good luck to you!

---

<div class="post-metadata">

**Author:** ![order\_ops\_guy](https://yyz1.discourse-cdn.com/shopifyforum/user_avatar/community.shopify.com/order_ops_guy/32/404508_2.png) [@order\_ops\_guy](https://community.shopify.com/u/order_ops_guy)\
**Post date:** [June 3, 2026, 2:10am UTC](https://community.shopify.com/t/received-the-wrong-quantity/630676/3 "2026-06-03T02:10:15Z")

</div>

The part that gets messy is when someone fixes the count later by adjusting a different variant. Shopify looks right again, but the PO history still says the original size/color was received fine, so the supplier problem disappears from the trail.

---

<div class="post-metadata">

**Author:** ![SealSubs-Roan](https://yyz1.discourse-cdn.com/shopifyforum/user_avatar/community.shopify.com/sealsubs-roan/32/278057_2.png) [@SealSubs-Roan](https://community.shopify.com/u/SealSubs-Roan)\
**Post date:** [June 7, 2026, 7:06am UTC](https://community.shopify.com/t/received-the-wrong-quantity/630676/4 "2026-06-07T07:06:48Z")

</div>

> [@MiloDeMilo](#):
>
> If your counts go wrong right after a supplier delivery, you need to look into how you are receiving the shipments. The common version: a delivery gets marked received against the PO based on a quick box count, but a few units were short, damaged, or the wrong variant — and none of that gets recorded. From that moment your count is wrong, and it surfaces later as a phantom stockout or an unexplained returns cluster.
> 
> What helps: receive against the PO at the unit level, not the box level, and record every discrepancy (short / damaged / wrong variant) the moment you find it rather than fixing it later. Also worth checking that no other app is writing inventory at the same time and that you’re not on multi-location if you run a single warehouse — both distort counts in ways that look like sync bugs.
> 
> Full disclosure, I’m building a tool in this space, so weight that accordingly, but the principle holds regardless of what you use: an error caught at the dock costs ninety seconds; the same error caught downstream costs you a quarter of chasing it.

Being a Shopify partner, this is exactly where the line goes skewed in most stock takes: Receiving too fast at carton level rather than unit level. Doing Inventory Adjustments with reason notes on receipt times in Shopify Admin you can keep your audit trail clean. Barcode scanning on receiving combined with single warehouse location per site helps eliminate cross location drift. Worth to check on any inventory syncing apps that maybe overriding the purchase order updates in real time. The trick is to catch discrepancies at intake, so reporting is trusted downstream.

---

<div class="post-metadata">

**Author:** ![clearstock](https://avatars.discourse-cdn.com/v4/letter/c/848f3c/32.png) [@clearstock](https://community.shopify.com/u/clearstock)\
**Post date:** [November 17, 2026, 10:45am UTC](https://community.shopify.com/t/received-the-wrong-quantity/630676/5 "2026-11-17T10:45:23Z")

</div>

Receive against the PO at the line level and record the exception immediately: short, damaged, or wrong variant on its own line, with the packing slip photos. If you instead ‘correct’ a different variant to make totals match, the error gets buried and the next count spends hours chasing it. Also check whether another app is writing inventory at the same time - duplicate writers are a common reason a receipt looks wrong after the fact. Closing the PO is the moment to reconcile, not later.
