Five Questions Before You Commit
The direct-to-employer pharmacy market is crowded with vendors claiming to deliver manufacturer-direct pricing, lowest net cost, and full transparency. Some of them do. Most do not. The difference between genuine pharmacy benefit infrastructure and a clinical wrapper or cash-pay arrangement is structural, not cosmetic, and it has significant implications for plan fiduciaries, members, and the employers writing the checks.
Before any self-funded employer or health plan commits to a direct-to-employer pharmacy platform, five questions should be answered clearly and completely. These questions are not theoretical. Each one addresses a specific failure mode that has already shown up in the market. A platform that cannot answer all five affirmatively has a structural gap that will eventually create a compliance problem, a member experience failure, or a fiduciary exposure.
Question 1: Is the Platform Pharmacy-Licensed With No Channel Ownership?
The entity making routing decisions must hold appropriate pharmacy licensure and must have no ownership interest in any dispensing channel. No retail pharmacies, no mail-order operations, no specialty pharmacies. If the platform owns or is affiliated with a dispensing channel, it has a financial incentive to route prescriptions to that channel regardless of cost. This is the same structural conflict that defines the PBM problem today. A platform that replicates that conflict while calling itself an alternative is not a solution. It is the same problem wearing different branding.
This requirement is not about perception. It is about structural incentives. When the routing entity and the dispensing entity share ownership, the routing decision is compromised at the entity level. No amount of internal firewalls or compliance policies can fully eliminate the conflict that exists when one division's revenue depends on another division's routing choices.
Ask for the pharmacy license number. Ask directly whether the platform or any corporate affiliate owns or operates a dispensing pharmacy, mail-order facility, or specialty pharmacy. If the answer is anything other than a clear no, the platform does not meet the independence standard that a self-funded employer should require.
Question 2: Does It Route Across All Channels or Only Its Own?
A genuine routing platform evaluates every in-scope prescription across all available supply channels in real time. That means manufacturer-direct programs, standard supply channels, independent pharmacy, and any other activated pathway. The platform routes to the lowest net cost regardless of which channel wins.
A platform that only routes to its own preferred channel or its own pharmacy partners is not routing. It is fulfillment with a different vendor. The distinction matters because the value proposition of a direct-to-employer pharmacy platform is that it evaluates alternatives that the PBM does not consider. If the platform itself does not evaluate alternatives, the employer has simply replaced one single-channel model with another.
Ask the platform to walk through exactly which channels are evaluated for a given prescription. Ask what happens when the manufacturer-direct channel is not the lowest cost option. If the platform always routes to its own channel regardless of the comparison, it is not performing independent evaluation. It is selling its own supply chain.
Question 3: Does It Produce Decision-Level Documentation for Every Prescription?
This is the fiduciary test. Under ERISA and CAA 2026, plan sponsors must be able to demonstrate that each high-cost drug benefit decision was made in the interest of plan participants. Aggregate reporting does not satisfy this requirement. A quarterly summary showing average net cost across a population cannot prove that any individual prescription was routed optimally.
Decision-level documentation means a per-prescription record showing which channels were evaluated, what the net cost was in each channel, which program rules were applied, and why the winning channel was selected. This record is created at the point of decision, not reconstructed after the fact from aggregate data. It is the pharmacy benefit equivalent of an investment committee memo, and it serves the same purpose: proving that the fiduciary considered the alternatives and made a documented, defensible choice.
Ask the platform to show you a sample decision-level record for an actual prescription. If they cannot produce one, they do not have it. If they offer aggregate reports instead, they are describing a different capability than what fiduciary compliance requires. The distinction between aggregate reporting and decision-level documentation is not a matter of preference. It is the difference between a defensible fiduciary record and an indefensible one.
Question 4: Does It Integrate With the Existing TPA for Claims and Accumulator Reporting?
A direct-to-employer program that sits outside the benefit is not a benefit. It is a side arrangement. For a prescription to count toward the member's deductible and out-of-pocket maximum, it must be submitted as a claim through the employer's TPA or through standard claims channels. For the employer to see it in their claims data, it must flow through the same reporting infrastructure as every other covered prescription.
A platform that collects member cost-share but does not submit claims to the TPA is operating outside the benefit by definition. The member's payment does not count toward their deductible. The prescription does not appear in the employer's claims analytics. And the employer cannot include it in their aggregate plan reporting or fiduciary documentation. This is not a minor operational detail. It is a structural requirement that determines whether the program is a covered benefit or a parallel vendor workflow.
Ask specifically how the platform handles accumulator reporting and claims submission for each prescription. Ask whether the member's cost-share counts toward their deductible and out-of-pocket maximum. If the platform cannot confirm that every prescription flows through standard claims channels, it is not operating as pharmacy benefit infrastructure. It is operating as a discount program that happens to involve a pharmacy.
Question 5: Does It Work Alongside the Existing PBM Without a Full Replacement?
The right answer is yes. A platform that requires replacing the PBM to function is asking the employer to take on significant operational risk and potential contract liability for the sake of a carve-out program on a handful of high-cost drugs. That is a disproportionate trade.
The correct architecture is a parallel channel for targeted drugs, with the PBM continuing to administer the rest of the formulary. The carve-out should be clearly scoped, documented, and structurally separate from PBM adjudication. The employer selects the specific drugs that qualify for the program. The platform evaluates those prescriptions across all channels. Everything else stays with the PBM exactly as it does today.
Ask the platform how it handles the PBM relationship and what happens to the rest of the formulary during implementation. Ask whether any PBM contract modifications are required and whether the platform has experience navigating PBM contract provisions with employer legal counsel. A platform that has done this before will have clear answers. One that has not will offer generalities.
Why These Five Questions Matter Together
Each question addresses a different structural failure mode. Pharmacy licensure without channel independence is insufficient. Channel independence without real-time all-channel routing is insufficient. Routing without decision-level documentation cannot prove anything. Documentation without TPA integration does not produce a covered benefit. And TPA integration without PBM compatibility creates an implementation problem that falls on the employer.
These are not aspirational criteria. They are the minimum structural requirements for a direct-to-employer pharmacy platform that can operate as genuine benefit infrastructure inside a self-funded employer's plan. A platform that answers yes to all five is built for the regulatory and fiduciary environment that exists today. A platform that cannot answer yes to all five has a structural gap that will eventually surface as a compliance problem, a member experience failure, or a fiduciary exposure that the employer bears personally.
A Platform That Meets All Five
ApalyRx answers yes to all five questions. It is pharmacy-licensed with no ownership in any dispensing channel. It evaluates all available supply channels in real time and routes to the lowest net cost. It produces decision-level documentation for every prescription. It integrates with the employer's TPA for claims and accumulator reporting. And it works alongside the existing PBM without requiring a full replacement. For self-funded employers ready to evaluate a direct-to-employer pharmacy platform against these criteria, schedule a briefing. For the full structural standard behind these five questions, read the Drug Benefit Integrity standard.