Order Queue Felxibility

Github Tickets

Value: Expand the range of customers that can use the Procurement Workflow.

Requirements:

When a user scans a Kanban Card that has already been added to the Order Queue, the system should still allow adding it again (e.g., “add additional 50”) rather than blocking the action.
The user should be able to specify a quantity different from the card’s default reorder quantity.
A “strict mode” toggle on the Loop configuration could optionally restore the current one-card-one-entry behavior for customers who want it.

Derived requirements (from this analysis):

Add a card multiple times from the UI or by scanning.
Add from an Item directly (from the UI, scanning a label, or breadcrumb) — currently adding from an Item results in adding a card for that Item if one is available; this should not require a card at all.
Edit the quantity to add to the Order Queue, defaulting to the card quantity or reorder quantity but allowing the user to change it.

Value: Reduce friction (increase adoption) in Order Queue management.

Requirements:

Items in the Order Queue that do not have a supplier assigned should still allow the user to advance the state.
The system should show a notice that there is no vendor, with a clickable link in the notice that takes the user to the edit field to input a vendor.
Generic vendors (e.g., “supermarket” instead of “Whole Foods”) are a valid use case — the system should not force specificity when the user’s workflow does not require it.
A sign of failure would be users entering fake vendor data just to bypass the restriction, rather than leaving it blank.