Running into this regularly: a product is in front of me — a return came back, or there’s a stock discrepancy — and I need to know which unfulfilled orders include it.
What I’ve found so far: shipping platforms like ShipStation let you search shipments by barcode, but that means adopting a whole shipping platform. Inside Shopify itself, the closest is scanning into admin search and checking the committed quantity on the product — workable, but slow when you’re doing it dozens of times a day.
Higher-volume stores: how do you handle this? Spreadsheet, an app, something in your picking tools? I’m considering building something in this space, so I’d genuinely like to know if I’d be solving a real problem or just my own.
Hi @Simon_builds ,
This is definitely a real challenge for high-volume stores. Shopify doesn’t have a built-in way to quickly search unfulfilled orders by SKU or barcode, so many teams end up using workarounds.
A few approaches I’ve seen work well are:
Using an OMS or WMS that supports SKU/barcode-based order lookup.
Building a simple internal app that searches open orders by SKU and lists all unfulfilled orders containing that item.
Using the Shopify Admin API to query open orders by line item SKU, which is much faster than searching manually in the admin.
If you’re thinking about building a tool that lets staff scan a barcode and instantly see all unfulfilled orders containing that product, I think it would solve a genuine operational pain point for many merchants handling large order volumes.
Hi,
Hope this message finds you in good spirit!
If you’re open to an app, you could check out Stock Flow. It gives you better inventory visibility than the native Shopify admin and can make it easier to track products tied to open orders.
There is a native route before adding a WMS or app. In Orders, open the Unfulfilled view, add the Product filter, and select the product or individual variants. Shopify’s Unfulfilled view includes unfulfilled and partially fulfilled orders that still need work.
I would not add only fulfillment_status:unfulfilled if you also care about partially fulfilled orders. There is another caveat: fulfillment_status is an order-level filter. It proves the order contains that SKU and the order has that overall status; it does not prove that this SKU is the line still waiting to be fulfilled.
Barcode is not a documented Orders search field, so a scanner workflow still has to map the barcode to the variant first. For a guaranteed line-level result, use the API to fetch candidate orders and check remainingQuantity on the matching fulfillment-order line item. For one-off lookups, though, the native Product filter should avoid opening every order.
This is the most useful answer in the thread, thank you — especially the line-level caveat.
You’ve pinned down exactly where the gap sits: the Product filter proves the order contains the SKU and is unfulfilled overall, but not that that particular line is still outstanding. And since barcode isn’t a searchable Orders field, any scanner workflow has to resolve barcode → variant first, which is the part that doesn’t exist today.
So the honest version of the problem is: for occasional lookups the native filter is fine. It’s the repeated, at-volume case — someone standing in the warehouse with a product in hand, dozens of times a day — where the click-path and the line-level ambiguity start to cost real time.
For merchants reading: at what volume did the native filter stop being good enough for you?
Hi there @Simon_builds
For stores that do frequent inventory counts this is a typical workflow problem. Many merchants address this with inventory or fulfilment apps that allow you to filter open orders by sku, barcode, or product variant. A light custom workflow via Shopify data exports or API connections can also be a good solution for groups that desire a quicker lookup. A product-specific tool to quickly locate committed inventory by product might be useful, particularly for high order volume stores.