↔ Regulatory Affairs
Filings, registrations and variations
The product's status, its open registrations and its planned variations are the filings themselves, read from Regulatory Affairs rather than restated beside it.
Pharmaceutical Product is the record of the product itself, and it holds almost nothing of its own. Its status in each territory, the formula registered there, the registrations open, the variations planned, the identifiers that name it: each one is a reference to the domain that owns it. So the product view is what the operation currently says, not a report someone assembled last quarter.
Capabilities
Where the product stands in each market: registered, under review, suspended, withdrawn, and since when. Read from the filings themselves rather than kept as a parallel list someone has to remember to update.
The composition actually approved in each market, held territory by territory rather than as one global formula with its divergences noted somewhere else. Where two territories differ, the difference is visible as data instead of as institutional memory.
The registrations open against the product, the stage each has reached and what it is waiting on, so the question of what is being registered where has an answer rather than an owner.
The variations against the product, planned or in flight, with the territories each one touches and the filings it implies: connected to the change that prompted them rather than tracked separately from it.
GTIN-14 codes, NDC, EU PCID and country identifiers, MAH records and authorization linkage, SPL submissions to FDA Listing, reimbursement and pricing codes: every identifier the product is known by, held against the product rather than in a spreadsheet maintained by hand.
Touchpoints
↔ Regulatory Affairs
The product's status, its open registrations and its planned variations are the filings themselves, read from Regulatory Affairs rather than restated beside it.
→ Market Access
Reimbursement codes, payer IDs, and tender identifiers feed market access work directly not as a one-off lookup project per market.
↔ Labeling
The label approved in a territory and the identifiers printed on its artwork resolve against the same product record, so a pack change surfaces what it touches.
← Organizations & Resources
Contract manufacturers and packagers carry their establishment identifiers as part of the partner record so SPL submissions and country registrations inherit the partner data structurally.
Outcomes
Every system that consumes a product identifier reads it from the same master record: drift is a structural impossibility, not a periodic reconciliation.
Identifier issues surface before submission rather than as a rejection from a payer.
Reconciliation is replaced by single-source projection. The work becomes maintaining the master, not mediating between copies.
When an identifier changes, every downstream system sees the change as a property of the data not as a manual update task.
Figures marked indicative are directional benchmarks against comparable generics operations; per-customer numbers replace them in working sessions.
Same foundation under every domain. A conversation usually clarifies where to start.