Compounding Rx Ordering & Routing Platforms Compared (2026): VITL, Bask Health, Karpa, OpenLoop, Photon, neolife

There is no single best compounding pharmacy ordering platform — there are different tools for different jobs, and picking the wrong category is the expensive mistake. VITL is a procurement marketplace; Bask Health is an all-in-one platform; Karpa is white-label; OpenLoop is a provider network; Photon is an e-prescribing rail; neolife is a clinic-side fulfillment overlay. Compare them on who pays, fee model, provider approval, API, and pharmacy neutrality.

This guide is intentionally neutral. Each of these tools is a reasonable choice for the buyer it was built for, and each is a poor choice for a buyer it was not. Below, the categories, the dimensions that decide fit, and an honest table — using each vendor's public positioning, and flagging where terms are simply not disclosed.

What are the categories, not just the brands?

Start by sorting the market into what each tool fundamentally is, because the brand names hide real category differences. A procurement marketplace, a platform, a provider network, an e-prescribing rail, and a fulfillment overlay are not competing for the same slot — they occupy different layers of the same workflow.

• Procurement marketplace (VITL): compare pharmacy prices and route orders; typically free to clinics, procurement-oriented.
• All-in-one platform (Bask Health): a bundled telehealth business — storefront, workflows, routing, payments — in one system.
• White-label platform (Karpa): a brand-in-a-box, often with rented providers and pass-through pharmacy pricing.
• Provider network (OpenLoop): supplies licensed clinicians and clinical back-office; you bring the commerce.
• E-prescribing rail (Photon): a developer-first prescribing/pharmacy API for routing prescriptions.
• Clinic-side fulfillment overlay (neolife): overlays your existing pharmacy, keeps you the system of record, routes patient-specific orders.

If you want the conceptual version of why "which layer" matters more than "which brand," it is the clinic-side rail versus pharmacy-side software distinction — most buyer confusion comes from comparing tools that live on different layers.

Which dimensions actually decide fit?

Five, and price is not the first of them. The dimensions that separate these tools in practice are who pays, the fee model, whether provider approval is built in, whether there is a usable API, and whether you can choose your pharmacy. Each maps to a risk or a lock-in you will feel later.

1. Who pays — clinic, pharmacy, or patient. This shapes the incentives of the whole arrangement.
2. Fee model — flat SaaS vs percentage/spread vs rev-share. A compliance design choice, discussed below.
3. Provider approval — is a licensed provider approving every order, and is that recorded?
4. Developer API — can you automate storefront-to-pharmacy dispatch, or is it portal/manual?
5. Pharmacy neutrality — can you switch or add pharmacies without a rebuild?

Why is the fee model a compliance question?

Because in healthcare, how you charge can be as scrutinized as how much. Regulators look hard at arrangements where fees scale with the value or volume of federally reimbursable business or referrals. The Anti-Kickback Statute prohibits knowingly paying or receiving remuneration to induce referrals of items or services reimbursable by federal healthcare programs (HHS OIG, https://oig.hhs.gov/compliance/physician-education/fraud-abuse-laws/), and EKRA extends similar concern to referrals involving laboratories, clinical treatment facilities, and recovery homes (18 U.S.C. 220, https://www.law.cornell.edu/uscode/text/18/220).

The practical implication for platform selection: flat, fair-market-value, value-blind fees paid by the clinic are generally the cleanest structure, while percentage-of-value, spread-funded "free" models, and pharmacy take-rates invite more scrutiny. Cash-pay compounding sits outside federal reimbursement in most cases, which changes the analysis — but state all-payor statutes and EKRA can still apply, so this is a question for your counsel, not a marketing claim. It is exactly why neolife uses a flat model and why we flag fee structure as a first-order diligence item in the questions to ask before signing.

The comparison table

Here is the head-to-head using each vendor's public positioning. Where a vendor does not publicly disclose a term, the cell says so rather than guessing — that is a diligence prompt, not a criticism.

Platform	Category	Who pays	Fee model	Provider approval	API	Pharmacy neutral
VITL (vitlrx)	Procurement marketplace	Clinic (free)	Not publicly detailed	Not the focus	Not publicly documented	Yes (multi-pharmacy)
Bask Health	All-in-one platform	Operator	Platform bundle	Bundled workflows	Platform-oriented	Within platform
Karpa	White-label platform	Operator	Bundle / pass-through	Rented/bundled	Platform-oriented	Often single-source
OpenLoop	Provider network	Operator	Enterprise (per public materials)	Supplies clinicians	Enterprise integrations	Coordinated by platform
Photon	E-prescribing rail	Developer/clinic	Usage/API (verify)	Bring your own	Yes (developer-first)	Yes (routing)
neolife	Clinic-side overlay	Clinic	Flat FMV + per-order; pharmacies free	Yes, every order	Yes	Yes (bring-your-own)

Read the table as a fit map. No row is best on every dimension, and the "right" row depends entirely on which job you are hiring for. A developer building a routing integration and a first-time founder wanting a turnkey brand should not pick the same row.

How do I choose for my situation?

Match the tool to your constraint, in this order. The first question that returns a hard "yes" usually narrows the field to one or two rows.

1. Do I need clinicians supplied? If yes, a provider network (OpenLoop) or a bundle that brokers providers leads.
2. Do I want a whole business turnkey and accept renting the stack? An all-in-one (Bask) or white-label (Karpa) fits — mind the lock-in.
3. Am I a developer wiring prescriptions programmatically? An e-prescribing rail (Photon) is the natural fit.
4. Do I just need to shop pharmacy prices? A procurement marketplace (VITL) is enough.
5. Do I need to stay the system of record and route patient-specific orders across pharmacies I choose? A clinic-side overlay (neolife) targets exactly that.

Two cross-cutting cautions regardless of row. First, pharmacy neutrality is worth protecting: single-source lock-in turns a pharmacy's bad week into your outage, which is the whole argument for multi-pharmacy routing. Second, if a tool leaves you juggling many pharmacy logins, you have re-created the five-portal problem the category was supposed to solve. For the platform-rental trade-offs specifically, the white-label telehealth alternatives comparison goes deeper.

Where does neolife fit in this map?

neolife occupies the clinic-side fulfillment overlay slot — the layer that operates patient-specific commerce while leaving ownership with the operator. It does not supply providers (bring your own), does not hand you a storefront (keep your own), and does not replace your pharmacy (it overlays it). What it does is keep a licensed provider approving every order — consistent with 503A's patient-specific requirement (FDA, https://www.fda.gov/drugs/human-drug-compounding/compounding-and-fda-questions-and-answers) — produce a compliance record per order, and route across pharmacies you choose, with a flat fair-market-value fee and free pharmacy access.

That is a deliberate position, not a claim to be everything. If your job is procurement, buy procurement. If your job is a turnkey brand, buy a platform and accept the trade. If your job is to run a durable direct-to-patient business you actually own, the overlay is built for that. Talk to us if you want help placing your own requirements on this map — including the honest cases where another row is the better buy.

This article is for informational purposes only and is not legal, medical, or regulatory advice; consult qualified counsel and licensed clinicians for your specific situation.