Regulated labeling solved from single-site to global enterprise.

One validated system for label design, approval, and regulatory data: meeting FDA, EU MDR, NMPA and ANVISA labeling requirements from a single plant to a global network.

An operator at a widescreen monitor showing the RONOVA print history report, a long table of label records, writing in a notebook beside the keyboard.

Every customer has agreed to act as a reference, and every one has renewed, year after year. Learn more about our record.

  • Pfizer
  • Baxter
  • Zimmer Biomet
  • Teva
  • Gilead
  • Lantheus
  • Smith & Nephew

The problem

A labeling error is not a typo. It is a recall, a finding on the record, and a product off the market.

Most manufacturers still run labeling as a chain of disconnected systems: artwork in one tool, regulatory data in a spreadsheet, approvals in email, and market content rebuilt by hand for every destination. Every handoff is a place where the label and the truth can diverge, and every market you add multiplies the handoffs.

RONOVA closes the gap. One source of regulatory and product data drives the label, the artwork, and the electronic IFU, so what prints, what ships, and what the regulator sees are the same record, whether that regulator is in Washington, Brussels, Beijing, or Brasília.

Where it hurts

Three problems, solved at the root.

Not a feature list. These are the three things that make regulated labeling expensive, and what RONOVA does about each.

01Change management

A single label change touches artwork, product data, translations and templates. Reconstructing what actually changed, and why, means reading back through email.

Every change carries its reason and everything it touched.

Change management captures the reason for a change at the moment it is made, and links every object altered as part of it. The change set is one record rather than a trail to reassemble later: what changed, why, who approved it, and what moved with it.

02Audit and e-signature

An inspector asks who approved this label, when, and on what basis. The answer is spread across systems, or in somebody's memory.

A complete audit history, signed.

Every user action and every change is recorded against a person, a time and a reason, with electronic signature for 21 CFR Part 11. The history is the evidence: it does not have to be assembled for an audit, because it was never kept anywhere else.

03Printing workflows

Production printing never quite matches the workflow a vendor assumed. So the system gets worked around at the line, and the controls get worked around with it.

Printing workflows configured to your process.

Fully configurable, web-based printing workflows built to match the production printing process a plant already runs: rather than a fixed sequence the floor has to adapt to, or abandon.

Every market you sell into

Four regulators. Four rulebooks. One record.

Each market defines its own identifiers, its own database, and its own language requirements. RONOVA holds them as configuration, not as four parallel processes your team maintains by hand.

  • United States

    FDA

    Label content, symbols and UDI carriers under FDA rules, with electronic records and signatures under 21 CFR Part 11.

    • 21 CFR Part 11 electronic records and signatures
    • UDI on labels and packaging levels
    • UDI carrier in both machine-readable and human-readable form
    • FDA labeling content and symbol requirements
  • European Union

    EU MDR / IVDR

    Label content in every language a member state requires, with UDI carriers and symbols under EU MDR and IVDR.

    • EU MDR 2017/745 and IVDR 2017/746 labeling
    • Basic UDI-DI and UDI-DI assignment
    • Label and instructions-for-use content required by EU MDR
    • Up to 24 official languages, per destination
  • China

    NMPA

    UDI coding at the smallest sales unit and Simplified Chinese content on the label, phased across device classes.

    • NMPA UDI coding at the smallest sales unit
    • UDI carrier printed on the label and every packaging level
    • Phased coverage across device classes through 2029
    • Simplified Chinese label content
  • Brazil

    ANVISA

    UDI carriers on the label and every packaging level under RDC 591/2021, in Brazilian Portuguese.

    • RDC 591/2021, as amended by RDC 884/2024
    • UDI carrier on label and all packaging levels
    • Label content and symbols required by ANVISA
    • Brazilian Portuguese label content

Deployed at every scale

One plant or two hundred: the same validated path to release.

  • Single site

    One plant, one market, and a quality system that still has to hold up to an inspection.

    1 site

  • Multi-site

    Shared templates and one master record across plants, without each site drifting into its own process.

    3+ sites

  • Global enterprise

    Dozens of sites and every regulated market, with regional requirements applied automatically.

    Dozens of sites

Validated by design

Built for every environment you operate in.

Compliance is not a module bolted on at the end. Every action in RONOVA is attributable, timestamped, and reconstructable, because that is what an inspector asks for, in whichever jurisdiction they arrive from.

The RONOVA print history report open on one released carton label, showing its version, its associated change record and its history.
  • 21 CFR Part 11Electronic records and signatures, with enforced re-authentication.
  • EU MDR & IVDRLabel and instructions-for-use content, symbols, and language per destination.
  • ANVISA & NMPAPortuguese and Simplified Chinese content, with carriers at every packaging level.
  • GAMP 5Risk-based validation and IQ/OQ/PQ documentation, delivered against Innovatum's ISO 9001:2015 certified quality system.
  • Immutable audit trailEvery change attributable to a person, a reason, and a timestamp.
  • EU 1169/2011 & FALCPAIngredient, allergen, and nutrition declarations that follow the recipe.
  • UN GHS & EU CLPHazard pictograms, signal words, and precautionary text from one classification.
  • IATF 16949 & VDA 4902Per-customer transport and part labels resolved from one shipment record.

Already running a labeling system?

Moving to RONOVA is a supported path, not a rebuild.

Templates, master data, and approval history migrate across. Innovatum handles revalidation. That applies whether you are on ROBAR, another labeling platform, or a stack of spreadsheets and workarounds.

Questions

Straight answers

Still unsure? Talk to someone who implements this.

What is RONOVA?

RONOVA is Innovatum's enterprise label management platform for life sciences manufacturers working in validated, regulated environments. It addresses three problems that make regulated labeling expensive: change management, by capturing the reason for every change and linking every object that change alters; auditability, through a complete history of user actions and changes with 21 CFR Part 11 electronic signature; and production fit, through fully configurable web-based printing workflows that match the process a plant already runs. Label design, regulatory data, destination labeling and serialization all resolve from the same product record. It is the successor to Innovatum's ROBAR platform.

Is RONOVA validated for regulated environments?

Yes. RONOVA is built for 21 CFR Part 11 compliance, with electronic signatures, immutable audit trails, and role-based access control, and the same controls satisfy equivalent expectations under EU MDR, NMPA, and ANVISA oversight. Innovatum supplies IQ/OQ/PQ documentation and validation support, and Innovatum's own quality system is certified to ISO 9001:2015.

We currently run ROBAR. What happens to our system?

Nothing has to happen: ROBAR is still supported and still sold, and there is no forced migration. If you do choose to move, RONOVA is reached on a supported path that carries across label templates, master data, and approval history, with Innovatum handling the migration and the revalidation so an existing configuration is not rebuilt from scratch. Whether the move is worth making depends on your estate, which is a conversation rather than a deadline.

How is RONOVA deployed?

RONOVA runs as a hosted cloud service or in a private cloud. It is used through a browser, including printing, so there is no client software to install on the plant floor. Regulated manufacturers with data residency requirements can keep the system in a dedicated environment.

How does RONOVA integrate with SAP and other ERP systems?

RONOVA integrates with SAP, Oracle, and other ERP and MES systems through documented APIs and message-based interfaces. Product and order data flows from the system of record into labeling without manual re-entry.

Which markets does RONOVA support?

RONOVA supports labeling for the United States, the European Union, China, and Brazil, along with other markets on request. Market-specific identifiers, symbols, and language requirements are held as configuration rather than as separate processes, so adding a market does not mean adding a parallel workflow.

Does RONOVA handle China NMPA UDI requirements?

Yes. RONOVA assigns NMPA UDI codes at the smallest sales unit and carries them on the label and every packaging level, with Simplified Chinese content resolved by destination. This matters more in China than in most markets because UDI data is a prerequisite for product registration, renewal, and modification, so the identifiers have to be right before anything else can proceed. NMPA coverage is phased across device classes through 2029.

Does RONOVA support ANVISA UDI requirements in Brazil?

Yes. RONOVA applies UDI carriers to the label and every packaging level as required by ANVISA under RDC 591/2021, as amended by RDC 884/2024. Brazilian Portuguese label content is handled through the same destination labeling rules used for every other market.

Is RONOVA only for large manufacturers?

No. RONOVA is used by single-site manufacturers and by global networks running dozens of plants. The term enterprise labeling describes the software category, not a minimum customer size. Deployment scope, validation effort, and cost scale with the number of sites, label complexity, and markets in play.

How does RONOVA handle multi-language labeling?

Label content is stored per market and applied automatically by ship-to destination, covering the up to 24 official languages the European Union may require, Simplified Chinese for China, and Brazilian Portuguese for Brazil. Translations are versioned and approved through the same audited workflow as the rest of the label, so a translation change is traceable like any other change.

How long does implementation take?

Implementation timelines depend on the number of sites, label complexity, and validation scope. A single-site deployment is typically measured in weeks; a multi-site global rollout is planned in phases. Innovatum scopes the timeline during evaluation rather than quoting a fixed figure.

Stop chasing artwork approvals.

See how to launch compliant labels faster.

Cookie preferences