Map every Scripts capability before you buy.
Scripts markets a consolidated 503A ordering dashboard but does not publish a granular feature spec. This cluster breaks down each capability — what is offered, what to verify, and how pass-through ordering differs.
Proudly Partnered With
Every Scripts capability, answered one page at a time.
Scripts does not publish a complete feature matrix, so each page below isolates one capability, separates what Scripts publicly offers from what you should confirm in a demo, and shows how Fizy Health handles the same job with price visibility and pre-payment validation.
Scripts features overview
The full Scripts capability map and what to verify across catalog, cart, and tracking.
Scripts medication catalog
How broad the Scripts formulary is and the catalog details to confirm before you sign.
Scripts multi-pharmacy dashboard
How one dashboard across several 503A compounders works and what routing to verify.
Scripts one-cart checkout
Whether Scripts supports a single multi-patient, multi-pharmacy cart and checkout.
Scripts batch refills
How Scripts handles refill day across many patients and what to confirm at scale.
Scripts cart validation
Whether Scripts validates SIGs, licensure, and stock before payment or after review.
Scripts order tracking
Per-order versus per-line tracking on Scripts when batches split across pharmacies.
Scripts patient tracking texts
Whether Scripts sends patients shipment-tracking texts and how that model works.
Scripts auto-ship and subscriptions
Whether Scripts supports recurring auto-ship orders and how cycles are validated.
Scripts patient portal
Whether Scripts is patient-facing or prescriber-first and what that means for staff.
Scripts team management
How Scripts provisions staff, prescriber, and admin access across locations.
Scripts integrations and API
Whether Scripts offers an API or EMR integrations and how ordering data moves.
Scripts reporting and analytics
What Scripts exposes for spend, volume, and status reporting, and what to verify.
Scripts directions for use and SIGs
How Scripts handles SIG entry and whether directions are validated before checkout.
Scripts notifications and alerts
Which alert channels and triggers Scripts offers as orders change status.
Scripts search and catalog favorites
How Scripts handles catalog search and saved favorites for repeat-SKU refill day.
Common Scripts feature questions.
- Definition
What features does Scripts offer?
Scripts's core capability is consolidating 503A compounded-medication ordering across multiple partner pharmacies into one dashboard, with a catalog and patient-based order submission. It does not publish a granular feature matrix, so deeper capabilities should be verified directly.
- Validation
Does Scripts validate orders before payment?
Scripts's public materials do not specify pre-submit validation of SIGs, licensure, or stock. Fizy Health validates the cart before checkout so issues are fixed before payment rather than after a pharmacy rejection.
- Pricing
Do Scripts features include visible pricing?
Scripts directs clinics to request a custom quote rather than displaying per-vial prices on the catalog. Fizy Health shows resolved per-vial 503A cost on each catalog and cart line before checkout.
- Tracking
Does Scripts track orders per line?
Scripts references order status but does not publicly detail per-line tracking when a checkout splits across compounders. Fizy Health tracks each line independently, tied to its patient and pharmacy.
- Comparison
How does Fizy Health's feature set differ from Scripts?
Fizy Health is the same multi-pharmacy ordering category but builds its features around price visibility and pre-payment validation: landed cost in catalog and cart, validation before checkout, per-line tracking, and in-app support tied to orders.
Compare the full feature set on your top SKUs.
See how Fizy Health shows landed cost before you quote, validates orders before you pay, and tracks every line. Free to start.