Radiopharmaceutical ERP Architecture & License Management

Executive Summary

Fluorine-18, the isotope behind FDG-PET scans, has a half life of about 110 minutes and comes out of a cyclotron, not off a shelf. A batch made at 7:00 a.m. has lost half its usable activity by 8:50 a.m. It decays on a clock that doesn't care about a delayed courier or a purchase order stuck in approval.

A conventional pharmaceutical company plans around expiration dates measured in months or years. A radiopharmaceutical company plans around a clock measured in hours, sometimes minutes: production scheduled backward from a delivery window, inventory whose value is already falling before it's sold, licenses that account for possession limits rather than just who's allowed to sell what, and books closed on batches that lost most of their value before reaching a patient.

A radiopharmaceutical company runs on several kinds of information: measured activity, dose and clinical workflow, financial and inventory value, and licensing status. Each needs a system of authority responsible for it. Specialized nuclear medicine and radiopharmacy platforms own activity measurement, dose calculation, and clinical workflow. NetSuite is the system of record for the enterprise: general ledger, AP/AR, multi-entity consolidation, procurement, inventory accounting, project accounting, and audit controls. Archer Insights extends NetSuite for radiopharma-specific controls and integrates it with the systems that own the physics.

Radiopharmaceuticals Are Not Just Another Pharmaceutical Supply Chain

A conventional pharmaceutical manufacturer works with drug substances stable for the length of their shelf life. Licensing comes down to who's permitted to sell, ship, or receive a drug in a jurisdiction. Quality release happens once, and the product then sits in inventory until it's sold or expires.

Radiopharmaceuticals sit inside that same FDA framework, with a second regulatory system layered on top: possession, use, and transfer of radioactive material falls under the NRC or, in most states, an NRC Agreement State. A radiopharmaceutical company is a drug manufacturer, a licensed handler of radioactive material, and sometimes a DEA registrant, all at once, and each regime defines "authorized" differently.

Then there's the physics. A dose of a short-lived isotope isn't a stable unit of inventory. Its usable quantity starts falling the moment it's produced and doesn't stop. A batch that's fully compliant, fully licensed, and fully paid for can still become a write-off if it sits on a loading dock forty minutes longer than planned. The answer isn't a different ERP. It's deciding up front which system owns activity measurement, dose and clinical workflow, licensing, and the enterprise financial picture, then connecting them deliberately.

The Regulatory Intersection

A radiopharmaceutical or nuclear medicine organization usually answers to several regulatory authorities at once, depending on what it does and where it operates.

FDA. Radiopharmaceuticals fall under the same cGMP framework as any drug, 21 CFR Parts 210 and 211. PET drugs get a partial exception: FDA wrote 21 CFR Part 212 for them, since short half-lives, small batches, and on-demand manufacturing called for different standards ^10,12. Investigational PET drugs can instead follow USP Chapter <823>, referenced directly in Part 212 ¹⁰.

NRC and Agreement States. Possession and medical use of radioactive byproduct material falls under 10 CFR Part 35, protecting the radiation safety of workers, the public, and patients ^1,2. Most of that authority has been handed to the states: 39 Agreement States issue licenses and enforce safety rules over radioactive material ³, covering roughly 16,000 licenses, about 90 percent of the national total ⁴. NRC keeps jurisdiction only in non-Agreement States, territories, and federal land. A company operating across a dozen states can face a dozen separate licensing authorities.

DEA. Depending on the isotopes or drug products involved, an operator may also carry DEA registrations, a third license type layered on the other two.

USP. General Chapter <825> covers compounding, preparation, dispensing, and repackaging outside the PET-specific chapter <823>, applying to all settings where radiopharmaceuticals are handled ⁷. Its facility and personnel requirements parallel USP <797> while accounting for radiation safety ⁹, and since 2023 it's compendially applicable through <795> and <797> ⁸.

DOT. Once a shipment leaves the building, transportation is a separate regulatory question. Class 7 radioactive material shipments fall under 49 CFR Part 173, Subpart I, and packaging also falls under 10 CFR Part 71 for NRC and Agreement State licensees, with air shipments subject to IATA rules too ^13,14,15. A 1979 memorandum of understanding keeps NRC and DOT's overlapping authority from producing conflicting requirements ¹⁶.

The Operational Impact of Half Life

Half life is the variable that reorganizes production planning, inventory visibility, order fulfillment, waste handling, and cost recognition.

Production planning. A conventional manufacturer can build inventory ahead of demand. A radiopharmaceutical producer largely can't, since inventory built too far ahead decays before it sells. Production gets scheduled backward from a firm delivery time: a hospital appointment, a courier cutoff, a generator's availability window. Cyclotron-produced isotopes add another constraint, since equipment scheduling and yield windows don't flex to absorb a late order.

Batch timing and release. Release has to move fast enough that the product still has useful activity left when it ships. A batch that passes every test can still be a business failure if release takes too long. That's part of why Part 212 gives PET manufacturers narrower, more realistic testing and release provisions, including conditional final release and simplified sample-identification rules ¹¹.

Delivery. A late courier is a different problem when the product has a two-hour half life: delivery windows are part of the product spec, not scheduling convenience. A delayed shipment can arrive clinically unusable, and the company still has to account for and dispose of material that was fully compliant when it left the building.

Waste and decay accounting. Decayed and rejected material has to be tracked through disposal in a way that satisfies radiation safety recordkeeping, on top of standard write-off procedures. Waste driven by decay, not defects, is a routine cost that belongs in financial reporting as a budgeted line, not a monthly exception.

Production and release run on a clock measured in minutes; financial reporting runs on a different rhythm. A layered architecture keeps each system on the clock it's built for.

Licensing Is an Operational Master Data Problem

It's tempting to treat radioactive materials licenses, DEA registrations, and state pharmacy licenses like any compliance document: scanned into a folder, tracked in a spreadsheet, with a renewal reminder. That works when a license is static. It breaks down once a license has to be evaluated transaction by transaction.

In one pharmaceutical environment Archer worked with, a company distributing controlled and non-controlled drugs across multiple states needed its licensing data to answer several questions the moment an order was placed: was the selling subsidiary authorized to sell into the destination state, did the customer hold a valid license, was the receiving location licensed for that jurisdiction, was the shipper authorized to move the product between states. Each license record carried its role, expiration, status, and controlled/non-controlled designation. A missing, expired, or invalid license stopped the order for review.

Radiopharmaceutical licensing runs on the same principle with a different data shape. The governing question wasn't whether a company could sell a drug into a state, but whether a specific company-and-facility combination was authorized to possess a defined level of radioactivity for a specific isotope, and whether a customer-and-receiving-facility combination was authorized to receive that same level. A license might allow a facility to hold up to some number of millicuries of a named isotope, and separately cap an aggregate limit across a group of isotopes. The record tracked expiration, status, maximum activity per isotope, any aggregate limit, and which company-location or customer-location combination it applied to. A transaction pushing a facility over its permitted level threw a warning or a hard stop.

Radioactive material licenses are built around possession limits tied to isotope and activity level, not a simple authorized-or-not determination for a product and jurisdiction. Isotopes, Agreement State versus NRC jurisdiction, and license scope all shape what the data model needs to hold, and that view has to stretch across facilities, states, customers, ship-to and ship-from locations, products, authorized activities, and sometimes authorized users, with expiration, renewal, and amendment data attached. The same product moving between two facilities can face very different licensing conditions depending on the states involved.

What Belongs in ERP and What Does Not

The question isn't whether NetSuite is capable enough, it's which system should hold authority over which decision.

A smaller nuclear pharmacy might run on a specialized platform plus a lightweight accounting package. A growing multi-site manufacturer reaches a point where it needs NetSuite's multi-entity consolidation, project accounting, and financial controls alongside the specialized systems it already relies on.

Inventory, Traceability, and the Three Numbers That Do Not Move Together

Physical quantity, radioactive activity, and financial inventory value are not the same number expressed three ways. Quantity doesn't change on its own as material decays. Activity falls continuously and predictably according to half life, independent of the container. Financial value is set by accounting policy, not physics. Each has a natural owner: the specialized platform holds measured and modeled activity, NetSuite holds financial value, and the two stay connected through integration, not a shared field.

During the design of a NetSuite environment for a radiopharmaceutical operator, Archer built exactly that connection. A vial doesn't get smaller as it decays, and the design question was how to keep NetSuite's financial picture aligned with a continuously changing value without asking the ERP to become a decay calculator. The answer was a scheduled process inside NetSuite that recalculates activity on a fixed interval (hourly for something fast like Tc-99m or F-18, daily for something slower like I-131 or Lu-177) and posts the result as a discrete inventory adjustment. Run often enough, this tracks the real decay curve closely without generating an unmanageable number of transactions. Decay loss posts to its own account instead of getting buried in cost-of-goods-sold variance, and the cost basis set at calibration time stays fixed rather than getting recalculated with every later adjustment, so a sale's margin reflects what actually shipped.

A modeled activity number is not a measured one. NetSuite's decay-adjusted figure is an estimate, useful for valuation and reporting, not for deciding whether a specific dose is safe to dispense. That decision needs a calibrated dose calibrator reading at time of use, corrected to the requested calibration time, which is what USP <825>'s dispensing and radioassay requirements are built around ^6,9. NRC and Agreement State recordkeeping obligations under 10 CFR Parts 20 and 35 extend to surveys and authorized-user attribution that live with the specialized system ^1,5. Reconciling NetSuite's calculated activity against the platform's calibrator readings on a defined cadence keeps both honest.

A radiopharmaceutical traceability model generally needs radionuclide identity, lot or batch number, calibration time, expiration, location, container identity, chain of custody, quality status (quarantine or released), waste disposition, facility authorization, and often a parent-child link between a bulk batch and the doses dispensed from it. How much a company needs to formally capture, and in which system, depends on its products, license conditions, and operating model.

Licensing, Distribution, and Finance Interact

A radiopharmaceutical shipment delayed by even a fraction of a half life can arrive with meaningfully reduced activity, or past the point of clinical usability, in a way a delayed conventional shipment usually doesn't, making courier reliability and chain-of-custody documentation load-bearing here in a way they aren't for most pharmaceutical products. Quality obligations (deviations, CAPA, out-of-spec investigations, document control) apply the same way they do for any drug manufacturer, but a deviation investigation has to close within a window measured against the isotope's half life, or the product decays past usability before it concludes.

Isotope inputs are often high cost and, for some isotopes, genuinely scarce, making procurement a more direct driver of margin than for most pharmaceutical inputs. Decay-driven waste is a recurring, expected cost, and failed production runs (equipment issues, cyclotron scheduling conflicts, missed release windows) happen at a frequency conventional pharma rarely sees. Capacity is constrained by cyclotron or generator availability, making site- and program-level profitability reporting matter more here. CDMO programs bring their own project accounting needs, capital-intensive equipment shapes depreciation policy, and companies approaching an IPO find multi-entity audit readiness becomes a near-term priority.

A modern ERP handles multi-entity consolidation, project accounting, and procurement as a matter of course. What's specific to radiopharma is the combination: financial data reconciling against decay-driven waste, license-constrained sales, and time-critical production, all at once, across several jurisdictions.

Building the Radiopharma Technology Stack

The architecture is layered: specialized systems for dose calculation and decay-adjusted activity, NetSuite for the enterprise backbone, Archer's extensions for isotope-specific licensing and transaction validation, and integration connecting activity readings, dose events, and disposition status between them.

A single-site nuclear pharmacy may need very little of the ERP or extension layer today. A multi-site manufacturer with institutional investors and a growing customer base typically needs all four layers, which is where Archer's role as integrator matters most.

Specialized Platforms in the Broader Architecture

Radiopharmacy and nuclear medicine software is a narrower market than general pharmaceutical software, and the platforms in it serve distinct roles rather than competing with each other or with NetSuite. A hospital department typically relies on a platform for inventory, doses, patient information, and billing. A commercial nuclear pharmacy relies on one for compounding and dispensing, tied to a connected dose calibrator. A manufacturer relies on a quality management platform built around batch records and document control. Current examples include EC2 Software's BioDose/NMIS and BioRx/RMIS ^18,19, EC2's BioTrax QMS ²⁰, Comecer's IBC Radiopharmacy and IBC Nuclear Medicine ²¹, and Cardinal Health's Nuctrac ^22,23.

None are built to carry enterprise financial consolidation or audit-ready controls, and none are trying to be. The platform closest to the physics owns the physics. NetSuite, extended and integrated by Archer, owns the enterprise backbone connecting that operational reality to financial and compliance reporting.

Where NetSuite Fits

NetSuite is a strong enterprise foundation for a regulated life sciences manufacturer or distributor. General ledger and multi-entity consolidation, AP/AR, purchasing, sales orders, vendor and customer records, financial reporting, fixed assets, and inventory accounting are native strengths. NetSuite describes its lot tracking as following goods from supplier to shop floor to customer using traceable lot numbers, aiding compliance and audits, with lot data shared across accounting, finance, and CRM modules ¹⁷.

Radioactive decay calculation, dose calibrator integration, health physics recordkeeping, and nuclear medicine dose management belong to the specialized systems built to own measured activity and clinical operations, the same division of labor NetSuite follows across every industry it serves: a genomics company runs DNA sequencing in a purpose-built platform, a CRO runs clinical trial randomization in one, and NetSuite runs the enterprise financials underneath both. A radiopharmaceutical company gets the most value from NetSuite by configuring it fully for the enterprise functions it's built to run and connecting it to the specialized systems that handle the operational and clinical work.

Extending NetSuite for Radiopharma

Archer's Drug License App is built natively inside NetSuite and already does real, transaction-level work: it centrally stores and validates three license categories (Seller License, DEA Ship To/From License, State Ship To/From License), with field-level validation enforced before an order processes ²⁴. A transaction involving an unlicensed or non-compliant entity gets blocked automatically with a clear reason flagged for review, and every validation lands in an audit-ready record. It also revalidates license data pulled from an external system, so stale data doesn't reach a live transaction ²⁴.

Radiopharmaceutical licensing adds requirements this architecture doesn't yet cover: possession limits per isotope, aggregate limits across a group of isotopes, and NRC-versus-Agreement-State jurisdiction rather than a federal-versus-state split. A scoped NetSuite extension can absorb these with the same transaction-level validation, blocking, and audit logging pattern already proven for pharmaceutical and controlled-substance licensing: new license record types for NRC or Agreement State facilities, activity and aggregate limits, and jurisdiction-aware validation tied to a company or customer location. The exact configuration depends on the customer's license structure, isotopes, jurisdictions, and operating model, the same scoping discipline Archer applies to any extension.

An Example Target Architecture

A representative architecture for a mid-sized manufacturer or multi-site nuclear pharmacy looks like a flow of information between systems of authority, converging on NetSuite as the enterprise system of record:

Show Image

The arrows represent information flow, not a hierarchy of importance. The specialized platform measures activity and runs the clinical workflow; NetSuite holds the enterprise financial and compliance record; Archer's extensions give NetSuite the transaction-level licensing controls this industry requires. What flows from the specialized platform to NetSuite is limited to what finance and compliance need to act on: a completed transaction, a disposition event (released, quarantined, disposed as waste), and enough identifying information (lot, isotope, activity at a reference time) to support decisions downstream. The continuous, physics-driven recalculation of activity stays with the specialized platform.

Questions a Radiopharmaceutical Company Should Ask Before Selecting an ERP

1. Which regulatory regimes apply today, and which will apply as we grow: FDA drug cGMP, PET-specific cGMP, NRC or Agreement State licensing, DEA registration? Does our architecture treat these as distinct systems of authority, not one compliance bucket?
2. Which system is the authority for decay and activity calculation, and how does its output reach NetSuite for financial and inventory purposes?
3. How are inventory quantity, radioactive activity, and financial value represented as three distinct data points instead of one, and which system owns each?
4. What does our license structure actually look like, isotope-specific limits, aggregate group limits, facility-level possession limits, or a mix, and does that match our NetSuite extension's data model?
5. Which of our current or near-term states are Agreement States versus NRC jurisdiction, and how will the system account for license conditions differing between them for the same product?
6. How does the system handle a transaction that would exceed a licensed limit: an overridable warning, a hard stop, or configurable behavior?
7. What's our plan for integrating a specialized radiopharmacy or nuclear medicine platform with NetSuite, and who owns that integration once both systems are live?
8. How will decay-driven waste, failed runs, and isotope cost volatility get modeled in financial reporting as a normal cost category, not a recurring anomaly?
9. Does our project accounting structure support CDMO or development program billing and profitability reporting at the level of detail our contracts require?
10. As we approach multi-entity operations or outside investment, what audit trail and control capabilities does NetSuite provide natively, and where must our partner configure or extend it?

Conclusion

A radiopharmaceutical or nuclear medicine company is, at minimum, three regulated businesses under one roof: a drug manufacturer, a licensed handler of radioactive material, and often a controlled-substance registrant, operating a product that loses value on a clock it doesn't control. That calls for an architecture assigning each requirement to the system built to own it, not one platform stretched to cover all of it.

NetSuite is the enterprise backbone: the ledger, procurement, inventory accounting, project accounting, and audit controls a regulated, multi-entity business depends on. Specialized platforms measure activity and run the clinical workflow. Archer's role is designing the connection between the two: extending NetSuite for the licensing and compliance controls this industry needs, and building the integration that keeps each system doing its own job.