https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43317 --- Comment #2 from lhilleary@wrl.org --- (In reply to Katrin Fischer from comment #1)

The closing of the basket will switch the status from new to ordered, indicating it's not a draft or in progress, but has been actually sent out to the vendor or ordered on the vendor's platform. The late order process and some other things depend on that status, so I am not sure changing that would be a good idea workflow wise.

Why do you not create new baskets for the order lines? Is it the extra clicks?

For us, whether the basket is open or closed, any item added gets an "Ordered" status. Item status only updates to newly received once we receive in Koha. I am specifically referring to baskets that we don't send from Koha to a vendor. The biggest example is Amazon. We place orders with Amazon as they come in to get them asap and those orders could be one item, two items, or 50 items. When we first migrated, we did create a basket for every order, even if it was just one item, but this quickly became impractical both in the number of baskets we had in a single month for one vendor and when we had to process the monthly invoices (which was a nightmare). So now, for sanity's sake, we do not create a new basket for every single thing we order. So I might have a weekly basket open that I'm adding orders to while orders added earlier in the week to the basket need to be received (but they can't be while the basket is open and I'm adding to it). It's not a major issue, but it is a workflow blocker since we either have to wait on ordering or wait on receiving. The only solution is creating a ton of baskets which again, created it's own headaches. This doesn't need to be a global setting, but if it could be an option that libraries could apply at their discretion on individual vendors, that would be optimal. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.