What a GLP-1 Telehealth Ordering Workflow Should Check Before the Pharmacy
A GLP-1 order fails before the pharmacy when one of four checks is skipped: state eligibility, a deliverable address, the pharmacy's own sig and clinical-justification format, or a verified prescriber. Building each check separately for every pharmacy is engineering work that grows with every pharmacy added, so the practical fix is a multi-pharmacy routing platform that runs all four behind one API. AffinityRx formats the prescriber's sig and clinical-justification entries to each pharmacy's required format. The prescriber writes or approves them and signs.
By Tim Yoon, CEO, AffinityRx. Published
Why GLP-1 orders fail before they reach a pharmacy
Pharmacy rejection rates sit around the industry norm of 1% to 5% of orders, and they are mostly over the sig, otherwise backorders. At a few hundred scripts a month that is a handful of failed refills; at several thousand it is a daily support queue and a cancellation risk.
Three patterns drive those failures:
- The same order is read differently by each pharmacy. One pharmacy accepts a sig as written; another can want a different structure or different clinical-justification wording for the same GLP-1.
- State rules are wider than the ship-to state. Nonresident licensure, sterile compounding permits and office-use restrictions all decide whether a pharmacy can fill a given order in a given state.
- Bad inputs travel a long way. An address that has the right ZIP format but is not deliverable, or a prescriber record that was never verified, is found out only when the pharmacy or carrier pushes it back.
The founder's question is where the four checks live: in your application, in each pharmacy's portal, or in one layer in front of all of them.
Where each pre-pharmacy check should live: by hand, built in-house or AffinityRx
The state and sig checks differ by pharmacy, so they multiply with every pharmacy you add.
| Check | What it catches | Doing it by hand or building it per pharmacy | AffinityRx |
|---|---|---|---|
| State eligibility | A pharmacy not licensed, permitted or allowed to fill the order in the patient's state | Track each pharmacy's licensure and each state board's rules yourself | Eligibility check applies state board rules (nonresident licensure, sterile permits, office-use restrictions), not just ship-to states |
| Deliverable address | An address that passes ZIP formatting but cannot receive a shipment | A separate address-validation integration | Shipping-address validation for deliverability built in |
| Sig and clinical-justification fields | Rejection for wording or format the pharmacy does not accept | Learn each pharmacy's format from its rejections | AffinityRx formats the prescriber's sig and clinical-justification entries to each pharmacy's required format. The prescriber writes or approves them and signs |
| Verified prescriber | An order from a prescriber whose NPI or state license was never checked | Verify NPI and state license in your own onboarding | Use the prescriber's NPI to identify them. The practice is responsible for confirming prescribing authority |
| What happens after all four pass and the pharmacy is still out of stock | A stalled refill | Staff re-enter the order elsewhere | Order moves automatically to the next favorite |
How AffinityRx solves the four pre-pharmacy checks behind one API
AffinityRx is an electronic prescription routing layer, not an EMR or a pharmacy. The checks run for every pharmacy behind one integration, with one invoice, one order history and one support contact.
- State eligibility. AffinityRx checks state eligibility for you by applying state board rules, not only ship-to states. Most SKUs are available in all 50 states, and two clinics may see different pharmacies only because a pharmacy is not licensed in their state. A gap in a specific state is prioritized for sourcing.
- Deliverable address. Shipping-address validation checks deliverability, not just ZIP format.
- Pharmacy-specific sig and clinical-justification fields. AffinityRx formats the prescriber's sig and clinical-justification entries to each pharmacy's required format. The prescriber writes or approves them and signs. The prescriber remains responsible for the clinical content of each order.
- Prescriber identity. Use the prescriber's NPI to identify them. The practice is responsible for confirming prescribing authority. No documents are needed from the clinic.
- Failover after the checks. Set a primary pharmacy plus second and third favorites; if the primary is out of stock or rejects, the order moves to the next favorite. The prescriber reviews and signs the order for the new pharmacy before it is sent. The order routing page has the detail.
- What this means for your developers. The headless API integration is about 1 day of developer work, depending on how well built your front and back end are. A test order runs the same day, Live access depends on your organization's access settings, and support replies in under 10 minutes. See the API page and the compounded tirzepatide page.
Proactive auto-routing to in-stock pharmacies launches in Q4 2026, and live stock and backorder status in Q1 2027. The case builds as volume and the number of states grow; a brand with one pharmacy, a few dozen GLP-1 patients and no rejections has less to gain.
Practical asset: pre-submission checklist for a GLP-1 order
Hand this to your product lead and developers. Mark each line built or handled by the platform.
- The patient's shipping state is eligible for the pharmacy and the item under the state's board rules. [ ]
- The shipping address is deliverable, not only correctly formatted. [ ]
- Sig and clinical-justification fields match the format the chosen pharmacy accepts (fill in the pharmacy). [ ]
- Use the prescriber's NPI to identify them. The practice is responsible for confirming prescribing authority. [ ]
- A second and third favorite pharmacy are set for the same SKU. [ ]
- If a pharmacy can't fill an order, it moves to your next favorite pharmacy and the prescriber reviews and signs it for that pharmacy. [ ]
FAQs
What should a GLP-1 telehealth platform check before sending an order to the pharmacy?
Four things: the patient's state is eligible under state board rules, the shipping address is deliverable, the sig and clinical-justification fields fit that pharmacy's format, and the prescriber is verified. AffinityRx runs all four for every pharmacy behind one API.
Why do pharmacies reject GLP-1 orders?
Rejections run about 1% to 5% of orders industry-wide, mostly over the sig and otherwise because of backorders. AffinityRx formats the prescriber's sig and clinical-justification entries to each pharmacy's required format. The prescriber writes or approves them and signs.
How long does a pharmacy API integration take?
For AffinityRx, about 1 day of developer work for a headless integration, depending on how well built your front and back end are. A test order runs the same day.
A telehealth brand already integrates directly with one pharmacy. Why use a router?
A direct integration brings one pharmacy's rules and one point of failure, and each added pharmacy means another integration and set of formats. AffinityRx puts 10+ licensed compounding pharmacies and 250+ SKUs behind one API, with failover if the primary is out of stock or rejects.
Does AffinityRx charge a subscription or per-order fee?
No. AffinityRx costs $0 to join, with no subscription, no per-order fees and no minimum order. Clinics preload credit applied 100% to orders; it never expires, has no minimum balance, and is refundable if the clinic decides not to continue after the 90-day trial. Shipping is added on top, typically $15 to $30 per order.
Book a demo
If your team is writing pharmacy-by-pharmacy validation code, see all four checks running behind one API in a demo: press the Book a demo button on the right side of this page. For what happens after the checks pass and a pharmacy still cannot fill an order, read how AffinityRx failover works.
Sources
- AffinityRx: Compounding pharmacy API for telehealth platforms, reviewed October 2026
- AffinityRx: Automatic multi-pharmacy order routing, reviewed October 2026
Every compounding pharmacy in one portal
Book a demo to compare prices across 10+ vetted pharmacies.
Book a demo