Concept A · queue-first

Review before you commit

One action. Here is everything it will change.

What this will do

Create supplier order #15 as a draftNothing is transmitted
Attach 46 patient fills across 4 preparations46 vials
Remove those 46 fills from "Ready to order"50 will remain
Add one item to "Draft never transmitted"Becomes 2

Order lines

4 lines · 46 vials

Preparation	Catalog item	Fills	Vials
Semaglutide / B12 5 / 1 mg/mL · 3 mL	STR-SEM-3ML	14	14
Tirzepatide / B6 5 / 2 mg/mL · 2 mL	STR-TIR-2ML	12	12
BPC-157 3 mg/mL · 5 mL	STR-BPC-5ML	11	11
NAD+ 100 mg/mL · 5 mL	STR-NAD-5ML	9	9

Worth checking first

3 of the 46 fills are missing prescriber licence details. Those rows will export blank in the patient-fill file that goes to the supplier.

Show the 3 fills Continue anyway

Teardown finding F9: in the measured build a fill with empty strength, form, route, directions and prescriber licence exports silently, and the operator sends it to the supplier with no warning.

Create draft order #15 Back to selection

What this page assumes

A batch action gets a review step. The brief asks that an operator can answer "what will this action change?" — this page is the only place in any of the three concepts where that question is answered before the commit rather than discovered after it.
Consequences are stated as counts that move, not as a description of the feature. "50 will remain", "becomes 2" — the operator can predict the next screen.
Quality problems surface before transmission, not after. An incomplete row is caught here because here is the last moment it is cheap.
Selection state survives this page. Teardown finding F12: staff sessions expired twice during measurement, and an unsaved 46-fill selection is a real loss.
Nothing here invents a supplier rule. There is no minimum-quantity warning because RonanRx has no supplier-provided minimum — the only such number in the codebase is a hardcoded constant on the other lane.