Request status does not change when pickup location is changed

Yes, I agree! That should work fine in this kind of situation, and people can make sure to check things in if the process status needs to be changed. The question of whether overriding transit status should be allowed in general is probably outside the scope of this issue

With FOLIO, you could set up your Discovery layer to allow patrons to select pickup service point if you wanted to do that. You might want to only make that possible at the time of request creation, though, since editing the pickup location when the item is already awaiting pickup really needs support from circ staff (as noted above).

Given the current setup seems like it will work fine, I think I will close this as Won't Do. Do you agree?

Yes, this sounds like a good workaround. The most common situation I can think of is that a user forgets to change the institution's default pickup location and wants to quickly correct it without contacting a staff member.

(In my institution's current system, only staff can set a pickup location different from the default – something that has been a little frustrating for some users, especially faculty who work in the same building as a branch library and rarely visit the main library.)

Thanks for filing this ! It's a use case we hadn't considered. Is it common for a requester to want to change the pickup location after the item is awaiting pickup? Do they do this via discovery or are they contacting the library? If they are contacting the library, our advice would be that the circ staff update the pickup location in the request and and then check the item in again. That would change the item and request status accordingly and print a transit slip, as well. Thoughts?