When post-submit pricing stops fitting — replace it with pass-through

A post-submit pricing model reveals your cost after you place the order. Wells Pharmacy Network shows per-Rx pricing in WellsPx3 order management after order placement — you see the number once the order is in the system, not while you are building the cart or quoting a patient. That can work fine when your formulary is stable, your margin is already set, and refill day is not bottlenecked on price lookups. The cost is timing and visibility: you do not see the per-vial number at the exact moment you are quoting a new cash-pay patient, and comparing landed cost across SKUs means placing test orders or checking historical rows in WellsPx3.

A pass-through model inverts that. With Fizy Health, the resolved 503A landed cost appears on each catalog and cart line before you check out, and the platform's margin is a disclosed facilitation fee at payment rather than embedded inside the vial cost. The drug cost is what the assigned LegitScript-certified 503A pharmacy charges; the platform fee is stated separately at checkout. For a clinic quoting cash-pay semaglutide or tirzepatide daily, that means the price you quote and the price you pay are the same visible number, confirmed self-serve, without submitting an order first.

Replace a post-submit pricing model when the lack of upfront pricing actively slows your business. Common signals: you delay quoting a new patient because you are not sure of the current per-vial cost; you cannot confidently set cash-pay prices because landed cost is not visible at the point of sale; you re-check rates by scrolling through past WellsPx3 orders instead of opening a catalog; or your volume has shifted and you are not sure your effective per-Rx cost still reflects it without placing another order.

Another signal is operational, not just financial: if paid orders get rejected after payment for SIG or licensure issues, the pricing question compounds with a validation gap. A pass-through platform like Fizy Health pairs visible per-vial cost with pre-submit cart validation, so the same workflow that shows your margin also catches the errors that cost you a refund cycle. If none of these signals apply — your WellsPx3 per-Rx pricing is predictable, your 503B office-use workflow is solid, and refill day is clean — a post-submit model may still be the right fit. Replace it when the model, not the compounder, is the constraint.