When VSDH's wrapped pricing breaks — replace it with pass-through

VSDH's model combines wholesale catalog pricing to partners with clinic-facing economics that often include revenue share and custom quotes rather than public per-vial rates on vsdigitalhealth.com. Its public FAQ directs clinics to request a custom quote as of June 2026. That can produce competitive rates at volume inside a white-label or ConnectRxCare relationship — a real strength when launching a D2C brand. The cost is visibility: landed per-vial cost may not appear at the moment you quote a semaglutide or tirzepatide patient, and separating drug cost from platform margin requires reading partner agreements rather than reading a cart line.

Pass-through pricing inverts that for clinic ops. With Fizy Health, resolved 503A landed cost appears on each catalog and cart line before checkout, and the platform's margin is a disclosed facilitation fee at payment — not an opaque layer inside the vial cost or a revenue-share stack. For a clinic quoting cash-pay patients daily, the price you quote and the price you pay trace to the same visible number. VSDH-as-supplier and VSDH-as-platform remain distinct: you may keep overlapping fulfillment while replacing how pricing surfaces to your team.

Replace wrapped partner pricing when lack of upfront visibility actively slows your business. Common signals: you delay quoting a new patient because you are waiting on a rate from a sales or partner conversation; you cannot confidently set cash-pay prices because landed cost is not visible at point of sale; you suspect margin lives in revenue share but cannot separate drug cost from platform economics; or your volume shifted and you are unsure current VSDH partner rates still reflect reality without reopening negotiation.

Operational signals compound the financial ones: ConnectRxCare and VSDH API flows are built for pharmacy fulfillment, not batch multi-patient checkout — so pricing opacity pairs with refill-day friction. A pass-through platform like Fizy Health pairs visible per-vial cost with pre-submit cart validation, so the workflow that shows margin also catches SIG and licensure errors before payment. If none of these apply — your VSDH white-label stack, partner rates, and refill workflow are clean — staying may be correct. Replace the model when visibility and batch ops, not the vendor name, are the constraint.