→ Regulatory Affairs
Filing IDs and submission identifiers
Identifiers that appear in regulatory submissions: establishment IDs, product identifiers, MAH references: flow from the master record into filings as part of the same event.
Product Codification is the unglamorous work of being known by the systems your product has to flow through: supply chains, reimbursement systems, regulatory ledgers, payer databases. Get it wrong and the product doesn't ship, doesn't reimburse, doesn't transact. Krevyos handles it as a property of the operation, not a spreadsheet maintained by hand.
Capabilities
GTIN-14 codes assigned and tracked against the products, packs, and presentations they identify with country-specific variants and re-issuance rules handled as part of the operation, so a packaging change surfaces the codification work it implies rather than running as a separate project.
Marketing Authorization Holder records held against the authorizations they reference so a MAH transfer or change is a tracked event with the implications for filings, labels, and pharmacovigilance already visible.
Country-specific product identifiers: NDC in the US, PCID in the EU, equivalents elsewhere: maintained as projections of the product master record rather than as separate datasets.
FDA SPL submissions for product establishment registration and drug listing, generated from the product master record and submitted into the Establishment Registration & Drug Listing System, so a label or formulation change is reflected in SPL the same cycle rather than at the next quarterly review.
Country-specific reimbursement identifiers: payer codes, tender IDs, hospital pricing codes: held alongside the product they identify, so market access work isn't blocked on identifier hunts.
Touchpoints
→ Regulatory Affairs
Identifiers that appear in regulatory submissions: establishment IDs, product identifiers, MAH references: flow from the master record into filings as part of the same event.
→ Market Access
Reimbursement codes, payer IDs, and tender identifiers feed market access work directly not as a one-off lookup project per market.
↔ Labeling
GTINs, country codes, and pack-level identifiers appear on artwork as projections of the master record not as values transcribed by hand.
← 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 service. A conversation usually clarifies where to start.