Skip to content
Vayra Platform

Pharmacy fulfillment

Prescription to doorstep, with every step visible.

A 503A personalized compounding lane plus routing, order tracking, exception handling and reshipments, so a prescription becomes a delivered order without a spreadsheet in between.

What it does

  • 503A compounding lane

    Patient-specific compounded prescriptions are filled by licensed 503A pharmacies, the same lane Vayra's own practice uses.

  • Pharmacy routing

    Orders route by medication, patient state and pharmacy licensure, so a prescription only goes to a pharmacy that can legally ship it.

  • Order lifecycle

    Received, in compounding, shipped, delivered. Each status change is recorded and visible to your team and, if you choose, to the patient.

  • Exceptions and reshipments

    Address problems, lost packages and damaged shipments land in a resolution queue with the order history attached, not in someone's inbox.

  • Cold chain where it matters

    Temperature-sensitive medications ship with cold-chain packaging and the shipping method the pharmacy specifies for them.

The order lifecycle

  1. Step 1

    Prescribed

    The clinician's approved prescription is transmitted from the chart.

  2. Step 2

    Routed

    Routing picks a pharmacy licensed for the patient's state and the medication.

  3. Step 3

    Compounded

    The pharmacy prepares the patient-specific prescription.

  4. Step 4

    Shipped

    Tracking flows back to the order and to the patient portal.

  5. Step 5

    Delivered or resolved

    Delivery closes the order. Anything else opens a resolution case.

What you control, and what we operate

You control

  • Which programs and medications you offer, within clinical review
  • Patient-facing pricing, with medication cost disclosed to you
  • Whether patients see tracking in your portal

Vayra operates

  • Pharmacy relationships and routing rules
  • Order tracking and status events
  • The resolution queue for exceptions

Integration notes

Order status changes are emitted as events, including the shipment tracking reference once the pharmacy ships.

Payloads on this page are illustrative. The public partner API is planned for v1.1; see developers for what exists today.

Illustrative event: order.shipped
{
  "type": "order.shipped",
  "id": "evt_01J9ZQ8T",
  "data": {
    "orderId": "ord_93b1",
    "carrier": "your-carrier",
    "trackingNumber": "XXXXXXXXXXXX",
    "shippedAt": "2026-10-28T09:12:00Z"
  }
}

See the platform with your own use case

A 30 minute walkthrough of the dashboards, the clinical workflow and the fulfillment path, shaped around what you are building. No slides unless you ask for them.