Concept C · exception-first

Confirm the catalog item

Rx #482 · Frankie Review. One stall, one decision, then back to the list.

You are choosing

the prescription's item

Semaglutide / B12 5 / 1 mg/mL · 3 mL
STR-SEM-3ML

Pinned 8 days ago by Devon Review, Provider. The payment's item — Semaglutide 2 mg/mL · 3 mL — will be set aside for this fill.

Compare the two again

What this changes

Rx #482 becomes orderable Joins the paid fills waiting: 96 → 97
Semaglutide / B12 5 / 1 mg/mL · 3 mL 14 → 15 fills on STR-SEM-3ML
This stall leaves Attention 4 stalls remain · oldest 9 days
The choice is recorded against Rx #482 Your name and the time, visible on the stall's history

What this does not change

The prescription itself Unchanged. Nothing is sent to the provider
What the patient paid The charge stands as re-priced. The two records still disagree on price, and this screen does not settle that or tell anyone in billing
No order is placed The fill only becomes eligible. Someone still has to put it on an order
The patient is not notified Frankie Review is not told the fill was held for five days

Pin this item and clear the stall Cancel

Undo is drawn here and switched off on purpose. Once this is committed nothing in the console reverses it: no path removes a fill from an order, and the cancelled state on a supplier order has no way of ever being set. The only correction available today is another forward action.

What this page assumes

The consequence is stated before commit, in counts the operator can check. The measured build shows nothing before a commit and offers nothing after it — a paid fill goes onto an order with no preview and no reversal.
"What this does not change" is doing as much work as "what this changes." Choosing the prescription's item leaves the payment priced against a different preparation. This screen deliberately admits it cannot settle that rather than implying the stall is fully resolved.
Undo is rendered disabled rather than omitted. SupplierOrder.cancelled has no writer anywhere in the codebase and no path removes a fill from an order. Hiding the control would hide the gap; showing it switched off makes the missing capability part of the design record.
The unit of action is one thing. If forty prescriptions diverged the same way this morning, this screen is forty visits — the exception-first model has no batch resolution and does not want one, which is precisely where the queue-first model beats it.
Every number here is computed from the same demand data the Everything surface renders. Nothing is estimated, and no supplier rule of any kind enters the calculation.
Committing returns the operator to a shorter list, not to a confirmation screen. That is the concept's reward loop, and its trap: the operator finishes the day at an empty page with no sense of how much throughput actually happened.