Searching for a new order de-select the previous one?

I dont know if this is a new “update” or a new glitch. But now when I search for another order, the previous selected order will get de-selected. So I can’t look for and select specific orders and print shipping labels at the same time.

Please Shopify, why is there a new issue that prevents the most fundemental and basic function from working right every day…

3 Likes

yes please, all the shipments of the day have been hauled due to this frustrating “update”.

3 Likes

Just to clarify for anyones reading this, it seems like a bot reply and the problem still persists, no one has contacted us yet…

4 Likes

Ok, please walk me through it…

2 Likes

Hey @Zencarbonfiber

That does seem like a bot response but it’s not entirely wrong. I assume what is happening in the Shopify Order Table is that when you change the query parameter, or filter parameter, and the previously selected order no longer passes these new parameters it get’s unselected because it cannot be on the new “page” of results.

I messed around a bit with the order queries and filters and that appears to be what is happening. If my selected orders still pass the new query/filter then they stay selected, but if they don’t then all selected orders get reset.

The work around would be finding a way to select all the orders you need via a single query/filter combination. Maybe all orders that need a shipping label have some field in common you can filter by or search for?

1 Like

Unfortunately since we do bepoke products, they are all random and I just search up the name and select them

2 Likes

We also have this issue and has completely broken our process we have people trained on. Cannot imagine having people have to go into each order one-by-one to do ~100 orders.

2 Likes

Yes. What a ridiculous, inefficient change. I contacted support & they said this was intended because you know, why make things easier for us? So now, instead of taking 2 hours to print 100 orders every day, it will take 4. Filters are irrelevant when you are searching by SKUs & then selecting the orders, as soon as you plug in the next SKU, it deselects everything before. I’m sure some app developer will respond with a way to do this now by paying for an app for something else that should already be a built-in feature.

2 Likes

Exactly, I cannot fathom they broke such as fundemental functional, a week later, still broken…

I feel every word of this reply. I was told they will “bring this up to the development team” and we all know what that means…

Hey, have you heard or gotten any more clue what’s up with this change? This is the only response I’ve seen so far that doesn’t read like an AI response and stated the issue.

I did find a workaround in tandem with your idea when I read this post initially the day after the change. You can type “OR” between each order number. Unfortunately it isn’t a great workaround to have to teach people to do between hundreds of orders numbers, even with some automation.

I’m still reading these forums every few days now to hope someone finds a fix or an actual Shopify response… I don’t understand the point at all of the search feature and being able to attempt to select multiple orders now with this behavior. The responses I’ve seen are “intended change”

Hey, I found a workaround to share with you.

When you are searching for an order type your order number and then “OR” between each order number.

Example: 123456 OR 123457

OR is case sensitive. You will need to do this between every order number. It will keep them on that page and will not unselect them.

1 Like

Hey, I found a workaround to share with you.

When you are searching for an order type your order number and then “OR” between each order number.

Example: 123456 OR 123457

OR is case sensitive. You will need to do this between every order number. It will keep them on that page and will not unselect them.

2 Likes

Well, that’s a nice workaround if you already know which orders you want ahead of time. But here’s the problem for us:

We enter a UPC, select the matching orders, then we enter the next UPC, select those orders, and so on. Then batch print.

Now? As soon as we search for the next UPC, the selections from the last search are wiped out. This sometimes forces us to print one order at a time, which is completely bonkers.

I spent the entire day today printing orders. A process that normally takes me 2–3 hours.

It feels like Shopify assumes everyone processes orders the same way, but for businesses like ours (who rely heavily on UPC-based workflows), this change really breaks the process.

1 Like

This works!!! Thank you so much - this helps our team with something that worked up until June 5th.

Their workflow broke when the search function didn’t preserve previously selected asynchronous order numbers. My team used it for batch printing.

The same process works with UPCs. Just tried it. It also helps to enclose the upc with " "

Example:

“850060337604” OR “850060337444”

It should work without " " as well.

Hope that helps. Still no fix on Shopify’s end. The search bar and being able to select orders functionality just seems pointless now, I don’t understand the point of the change at all. Why else would you be searching but to be able to select multiple orders? The fixes I have posted are NOT common operating knowledge, nor explained as functionality. I think they expect mostly everyone to be integrated into something else at this point and anyone who still uses the default shopify web end is out of luck.

1 Like

Hmm. I thought we tried that and it didn’t work. I’ll give it another shot. Thanks for the information!

An update if you didn’t know yet, Shopify fixed the issue and functionality has been restored to the previous way it used to work. :slightly_smiling_face:

1 Like

Tested and confirmed. And FWIW, if enough people do reach out to customer support, development will work on things. I found them to be very receptive, and it really helped escalate my case when I shared the URL of this community discussion with them.

This has been fixed!