340B Contract Pharmacy Restrictions by Manufacturer: 2026 Matrix

Since the first manufacturer restrictions took effect in 2020, more than 30 drug manufacturers have limited 340B pricing on drugs dispensed through contract pharmacies. No two policies are the same. Some allow a covered entity only one contract pharmacy. Others restore access to more pharmacies if the entity submits claims-level data. A growing number now require claims data from entity-owned, in-house pharmacies too.

This guide is a quick reference for 340B covered entities, contract pharmacies, and compliance teams. It summarizes each manufacturer’s published policy, explains the exemptions, and shows what to do when a manufacturer requests data.

Key takeaways

• More than 30 manufacturers restrict 340B contract pharmacy pricing; this matrix covers 20 major ones.
• Almost all require a designated contract pharmacy, and most use 340B ESP for claims data.
• 2026’s biggest shift: claims-data demands now reach entity-owned pharmacies.
• Exemptions for grantees, hospitals, and states are manufacturer-specific, never universal.
• State contract pharmacy access laws are still being challenged in federal courts.
• Review every manufacturer’s policy at least quarterly and after any new notice.

What are 340B contract pharmacy restrictions?

Short answer: They are manufacturer policies that limit how many contract pharmacies can receive 340B-priced drugs for a covered entity, or that set conditions, such as pharmacy designation or claims data, for that access.

Under the 340B Drug Pricing Program, eligible hospitals and clinics buy outpatient drugs at discounted prices. Many entities without their own pharmacy rely on contract pharmacies to dispense those drugs to patients. Starting in 2020, manufacturers began restricting that model, arguing that contract pharmacy growth increased the risk of duplicate discounts and diversion. To understand the underlying model, see how 340B contract pharmacy arrangements work.

What changed in 2026?

Short answer: The main 2026 trends are claims-data requirements reaching entity-owned pharmacies, ongoing court fights over state access laws, and new Medicare price deduplication pressure.

• Entity-owned pharmacy data: a growing number of manufacturers now ask for claims data on in-house dispenses, not just contract pharmacy dispenses. Check each notice for scope and effective dates.
• State law litigation: manufacturers continue to challenge state contract pharmacy access laws in federal courts, so the status of these laws can change.
• Medicare negotiated prices: Maximum Fair Prices for the first drugs selected under the Inflation Reduction Act took effect January 1, 2026, adding a new reason manufacturers cite for data requests.
• Product carve-outs: more manufacturers apply separate rules to specific oncology, specialty, and rare-disease products.

2026 manufacturer restriction matrix

Short answer: The table below summarizes 20 manufacturers’ 340B contract pharmacy policies: the restriction, who it applies to, how data is submitted, and the first compliance action to take.

All 20 manufacturers require a designated pharmacy (Gilead only if the entity does not submit data). “Restriction” describes the rule for entities without an entity-owned pharmacy unless stated otherwise. The “Key Compliance Action” column is a starting point, not a final answer: product lists and NDCs change, so confirm details with the manufacturer’s current notice. For updates between reviews, use our live manufacturer restrictions tracker.

Abbreviations: CAH = critical access hospital; DSH = disproportionate share hospital; RRC = rural referral center; SCH = sole community hospital; BIN/PCN = pharmacy claim routing identifiers.

Types of 340B contract pharmacy restrictions

Short answer: Most manufacturer policies combine five building blocks: a single contract pharmacy limit, a designation requirement, data-based access conditions, entity-type rules, and entity-owned pharmacy data requirements.

Not every manufacturer uses every category, and many combine several. Always check which combination applies to a specific manufacturer before assuming how its policy works.

Which manufacturers have product-specific carve-outs?

Short answer: Several manufacturers apply separate designation rules to specific oncology, specialty, and rare-disease products, on top of their main contract pharmacy policy.

If your entity dispenses any of these products, confirm both the product-specific rule and the manufacturer’s baseline policy.

How manufacturer restrictions evolved: three waves (2020–2026)

Short answer: Restrictions moved from single-pharmacy limits (2020–2021), to claims-data conditions through 340B ESP (2021–2023), to data demands that reach entity-owned pharmacies (2024–2026).

Government action also shaped the landscape. HRSA’s 340B Rebate Model Pilot, planned to start January 1, 2026 for drugs with Medicare negotiated prices, faced legal challenges from hospital groups. Learn more about preparing for the 340B rebate model.

Covered entity exemptions: who is exempt?

Short answer: No exemption applies across all manufacturers. Common categories are federal grantees, entities with an in-house pharmacy, entities in states with access laws, and certain hospital types, but each manufacturer defines them differently.

• Federal grantees: Several manufacturers, including Pfizer and GSK historically, have excluded grantees such as FQHCs, FQHC look-alikes, Ryan White clinics, and Title X clinics from some limits. Many now use a narrower grantee-specific rule instead of a blanket exemption.
• Entities with an in-house pharmacy: Many policies apply only to entities without an entity-owned pharmacy. Newer entity-owned pharmacy data requirements are eroding this distinction.
• State access laws: Some manufacturers exempt entities in states with contract pharmacy access laws, though several of these laws are in litigation (see below).
• Hospital subtypes: Critical access hospitals, disproportionate share hospitals, rural referral centers, and sole community hospitals may face different rules than community health centers.

Grantee vs. hospital quick reference

Grantee exemption eligibility follows the manufacturer’s own classification, which may not match HRSA’s. Never assume an exemption from one manufacturer, or from a previous year, still applies.

State contract pharmacy laws and litigation

Short answer: Several states have passed laws barring manufacturers from restricting 340B contract pharmacy access. Manufacturers have challenged these laws in federal court, and the Eighth Circuit upheld Arkansas’s law in 2024.

Track new laws and rulings in our 340B state law tracker. A manufacturer’s state exemption for one policy doesn’t mean every manufacturer’s policy is affected in that state. Confirm both the manufacturer’s own statement of state exemptions and the current court status before relying on a state law, and consult counsel.

Remember: a state access law is not a substitute for checking each manufacturer’s current policy, and court rulings in one federal circuit don’t automatically apply in another.

Designated pharmacy requirements

Short answer: A designated pharmacy is the specific in-house or contract pharmacy location a covered entity names to a manufacturer to receive 340B pricing. Most single-pharmacy manufacturers won’t ship 340B-priced product until designation is complete.

Designation is not the same as a contract pharmacy services agreement. The agreement creates the legal relationship between the entity and the pharmacy; designation is the notice the covered entity gives the manufacturer identifying which pharmacy should receive 340B pricing under that manufacturer’s policy.

How to choose a designated pharmacy

Records to keep

1. Confirmation of each designation (screenshot or record from 340B ESP or the manufacturer’s portal).
2. The date each designation was made and any later changes.
3. Your internal policy for choosing between pharmacies when manufacturers’ policies conflict.

Changing a designated pharmacy can affect claims routing, TPA split-billing settings, and pharmacy staff training. Put every change through a documented change-control process; our 340B policy development and training team can help. An independent TPA review and structured contract pharmacy management reduce the risk of errors.

340B ESP and claims data submission

Short answer: Most restricting manufacturers collect de-identified claims data through 340B ESP. Late or incomplete data can lead to denied or reversed 340B pricing on that manufacturer’s products.

340B ESP (Eligibility and Submissions Portal) collects claims data and processes designations. Manufacturers say the data helps them identify duplicate discounts, where the same unit could receive both a 340B discount and a Medicaid rebate. Some manufacturers use other vendors or direct channels for some products, so confirm the correct channel for each manufacturer rather than assuming ESP.

Typical data fields are de-identified, dispense-level details such as NDC, quantity, date of dispense, and pharmacy identifiers. Submission frequency varies by manufacturer, from every two weeks to monthly, and many now require submission within a set number of days after dispense (for example, 14 days).

Much of this data originates with contract pharmacies and TPAs, not the covered entity, so coordinate closely and keep your own submission records. Our split-billing and duplicate discount reviews can test whether your data and processes hold up.

How to submit claims data through 340B ESP

1. Account setup: register the entity and assign authorized users.
2. Data preparation: compile de-identified dispense data in each manufacturer’s required format.
3. Designation: select the contract pharmacy (or pharmacies) for each participating manufacturer.
4. Upload: submit claims files directly or through your TPA via an authorized connection.
5. Validation: review error and exception reports in the platform.
6. Correction: resubmit corrected files quickly; manufacturers may enforce submission windows.
7. Record retention: keep copies of submitted files and confirmations.
8. Periodic review: compare designations and submission history with current manufacturer requirements.

Confirm the current process in the 340B ESP help center; platform steps can change.

How to respond to a manufacturer 340B data request

1. Identify the manufacturer and the specific policy notice; confirm it’s current and covers products you buy.
2. Determine whether your entity is subject to it, based on entity type, in-house pharmacy status, and any state or grantee exemption.
3. Identify which claims, products, or NDCs are covered.
4. Compare the required data fields with what your dispensing system, contract pharmacy, and TPA can provide.
5. Confirm the submission channel: 340B ESP, a manufacturer portal, or direct email.
6. Validate data accuracy before submitting; errors can delay pricing restoration.
7. Keep records of all submissions, confirmations, and manufacturer communications.
8. Escalate questions about eligibility, duplicate-discount liability, or TPA and pharmacy contract terms to counsel.

How 340B restrictions interact with Medicare negotiated prices and the rebate model

Short answer: Medicare negotiated prices under the Inflation Reduction Act took effect in 2026, and manufacturers do not have to give both the negotiated price and the 340B price on the same unit. That deduplication need is another reason manufacturers seek claims data.

HRSA’s 340B Rebate Model Pilot was designed for drugs with Medicare negotiated prices and faced legal challenges before its planned start. If a rebate model moves forward, covered entities would buy at a higher price and claim the 340B discount afterward, which makes clean, timely claims data even more important. Use our 340B rebate calculator to estimate the cash-flow effect.

What restrictions mean for your 340B savings and audit readiness

Short answer: Restrictions directly reduce 340B savings at contract pharmacies, and weak designation or data records can create findings during an HRSA audit.

Every contract pharmacy that loses 340B pricing on a manufacturer’s products reduces the savings your entity reinvests in patient care. Track restricted volume by manufacturer and pharmacy, and check whether data submission would restore access. Our 340B revenue recovery team can quantify what’s been lost and what’s recoverable.

HRSA audits also examine contract pharmacy oversight and duplicate discount prevention. See the 25 areas HRSA examines, test your program with a 340B mock audit, or start with our free audit readiness scorecard.

How to use this matrix: 10-step checklist

1. Confirm which manufacturers’ products your entity dispenses.
2. Check each manufacturer’s policy for your entity type (hospital, grantee, FQHC, other).
3. Check your pharmacy arrangement (in-house, contract, or both); many policies depend on it.
4. Verify the effective date of each restriction and whether it has changed.
5. Check manufacturer-recognized exemptions (state, grantee, hospital type).
6. Review state-specific laws and current litigation.
7. Confirm any data submission requirement and its deadline.
8. Confirm the channel: 340B ESP or another method.
9. Document designations, submissions, and confirmations.
10. Re-check manufacturer policies at least quarterly and after any new notice.

Common 340B contract pharmacy compliance mistakes

• Relying on an outdated restriction list instead of the manufacturer’s current notice.
• Assuming all manufacturers use the same rules or the same mileage radius.
• Missing effective dates, including different dates for product lines within one manufacturer.
• Applying one manufacturer’s exemption (such as a grantee exemption) to all manufacturers.
• Ignoring state-specific laws and their current status on appeal.
• Submitting claims data late or incomplete, losing restored pricing.
• Not documenting designations and manufacturer communications.
• Treating third-party summaries, including this one, as the final word.

Glossary of 340B contract pharmacy terms

Conclusion

Manufacturer 340B contract pharmacy restrictions are one of the fastest-changing areas of 340B compliance. No two policies work the same way, and the legal landscape, from HRSA’s rebate model to court challenges over state access laws, is still shifting. Covered entities that use this matrix as a starting checklist, confirm each manufacturer’s current notice before acting, and keep records of every designation and data submission will be best positioned to protect their 340B savings through 2026 and beyond. For hands-on support, explore our 340B compliance services.