The EUDAMED Countdown: What the 28 November 2026 Deadline Means for Your Labels

Title

The EUDAMED Countdown: What the 28 November 2026 Deadline Means for Your Labels
Author Name
Kallik Role 1
Content Manager
8 min read

If someone asked you right now, off the top of your head, which of your medical devices are properly registered in EUDAMED and which ones aren't – could you answer? Not “pretty sure,” not “I’d have to check with regulatory.” An actual, confident answer.

If you hesitated even slightly, you're in the right place. But you've also got about two weeks left to turn that hesitation into certainty, because 28th November 2026 is the date EUDAMED registration stops being a “we're working on it” item and becomes a “did you or didn't you” one.
 

So what's actually changing on 28th November?


EUDAMED, the EU's central database for medical devices, has been mandatory for a while now. But the date that's been quietly creeping up on everyone's calendar is the deadline for legacy devices. In plain terms: if your device was first placed on the EU market before 28 May 2026, and you're still selling it after 28 November 2026, it needs to be registered in EUDAMED's UDI/Device module. Once per UDI-DI, covering every unit sold under that identifier.

If you manufacture outside the EU, you don't register it yourself – your EU Authorized Representative does, and that registration needs a validated Single Registration Number (SRN) sitting behind it. We'll come back to that distinction, because it trips up more people than you'd think.

Here's the part worth sitting with for a second: under Article 29(1) of the MDR, a device placed on the market without prior UDI registration is treated as non-conforming. That's not a slap on the wrist. That's the regulatory equivalent of the device not being allowed on the market at all. Worth checking the detail straight from the source rather than taking our word for it: the European Commission's EUDAMED page, its UDI/Devices registration guidance, and the regulation itself on EUR-Lex, if you fancy reading Article 29(1) in its full, suitably dry legal language.
 

The bit that actually catches people out


Knowing that you need to register is only the starting point though – what catches manufacturers out though, is exactly how.

Take the SRN point above. Submitted and validated sound like they mean the same thing, don't they? But they don't. An Actor registration can sit in a pending state for longer than anyone's comfortable with, and a pending SRN doesn't satisfy the requirement – it just looks like it might, right up until it doesn't.

Then there's the assumption that stopping sales means you're off the hook. Mostly true. Except if a vigilance report or a post-market action brings an old device back into scope, it can need retroactive registration – which is a genuinely unwelcome surprise to find out after you'd mentally filed that product under “done.”

And if you're a non-EU manufacturer, there's a coordination problem hiding in plain sight: who, specifically, at your EU Authorized Representative is keying in each registration, and by when? “Someone's handling it” isn't a plan. It's a hope.

What to actually do before the 28th

None of this needs to be complicated, but it does need to happen this week rather than next. A few things worth doing now:

  • Audit your UDI-DI portfolio against EUDAMED's Device module. Don't assume an older product is already registered just because it's been on the market for years. Check.
  • Confirm your SRN status is validated, not pending. If it's been sitting pending for a while, chase it now, not on the 27th.
  • Get it in writing who owns each registration, especially if you're working through an EU Authorized Representative. Ambiguity here is exactly how things fall through the cracks.
  • Double-check discontinued products for any open vigilance or post-market activity that could pull them back into scope.
  • Don't leave it to the wire. EUDAMED has a track record of getting sluggish under load, and the final few days before an EU-wide deadline is exactly when that load shows up.
  • Keep a record of who registered what, when, and against which version of the label or artwork. “Is it registered” is rarely the only question a notified body asks.

Why this keeps happening (and the real fix)

Look closely at almost every one of those failure points above, and they're not really EUDAMED problems. They're labeling data problems wearing an EUDAMED costume. Which UDI-DI matches which artwork version. Who approved what, and when. Whether the registration status, the label content, and the regulatory record actually agree with each other, across every market you sell in.

That's a hard thing to keep straight across spreadsheets, email threads, and whichever system your regulatory team happens to be relying on this quarter. It's a much easier thing to keep straight when your UDI data, your artwork, and your approval history all live in the same governed system, with a full audit trail and one version of the truth everyone's actually looking at. That's the gap Veraciti™ is built to close — cloud-based, end-to-end, and built so the question “is this registered correctly” gets a fast, confident answer instead of a frantic one.

With less than two weeks on the clock, now really isn't the moment to discover gaps in your EUDAMED data. Get in touch with the Kallik team today, and let's make sure 28 November is a non-event for you, not a fire drill.

FAQs on the EUDAMED Deadline

What is the EUDAMED deadline in November 2026? 

The 28 November 2026 deadline applies to legacy medical devices. If a device was first placed on the EU market before 28 May 2026 and it's still being sold after 28 November 2026, it needs to be registered in EUDAMED's UDI/Device module.

Which devices need to be registered in EUDAMED by this deadline? 

Any device first placed on the market before 28 May 2026 that's still actively sold after 28 November 2026. Registration happens once per UDI-DI and covers every unit sharing that identifier.

What happens if a device isn't registered in EUDAMED in time? 

Under Article 29(1) of the EU MDR, a device placed on the market without prior UDI registration is treated as non-conforming, meaning it can't legally remain on the EU market.

Do non-EU manufacturers need to register devices in EUDAMED themselves? 

No. Non-EU manufacturers register through their EU Authorized Representative, and the registration needs a validated Single Registration Number (SRN) behind it — a submitted but still-pending SRN isn't enough.

Is a discontinued medical device exempt from EUDAMED registration? 

Generally yes, if it's no longer being sold after 28 May 2026. But if a vigilance report or post-market action brings the device back into scope, it may need to be registered retroactively.

Are Barcodes Going Extinct? What GS1 Sunrise 2027 Really Means for Retail

Title

Are Barcodes Going Extinct? What GS1 Sunrise 2027 Really Means for Retail
Author Name
Kallik Role 1
Content Manager
5 min read

Every few years the good old barcode receives another death notice, and this year’s has been especially dramatic. Headlines warn of extinction, of a meteorite heading for retail, of brands quietly disappearing from shelves.

It makes for a gripping read… but it also gets the story a little wrong, and for anyone putting products in front of shoppers over the next couple of years, the details are worth getting right.

What is GS1 Sunrise 2027?

GS1 Sunrise 2027 is an industry initiative to make sure retail point-of-sale systems can read 2D barcodes by the end of 2027. That means QR codes carrying GS1 Digital Link and GS1 DataMatrix codes, scanned at the same checkouts that handle today's UPC and EAN barcodes.

Two details tend to get lost in the coverage. Sunrise 2027 is a voluntary, retailer-led milestone rather than a regulation, and phasing out the linear barcode isn't part of it. For the foreseeable future, most packs will carry both.

Why does it feel like the end of the barcode?

Mostly because what a barcode is being asked to do is changing so quickly. For fifty years, the UPC has done one job brilliantly: it tells the till which product is in your hand so it can charge the right price.

A 2D code can carry the same product number alongside batch, lot and expiry details, and, through GS1 Digital Link, a web address. The checkout reads the price. A shopper's phone, pointed at that very same code, might open allergen information, sourcing details, recycling guidance or an idea for tonight's dinner. With one small square serving the till, the stockroom and the customer, the talk of extinction is understandable. What retail is actually getting, though, is a second layer on top of a system that still works perfectly well.

The real work sits behind the code

Printing a QR code on a carton is a design task. Keeping what it points to accurate, current and consistent in every market it's sold in is a data task, and a far larger one.

Consider what happens when a product is reformulated, a supplier changes or a claim needs updating. A printed label has a natural checkpoint built in, because a change means new artwork, new proofs and a new print run. A linked label can be updated at any moment, which is a gift when something needs correcting fast and a worry when nobody is sure who approved the change. Over time, the information behind a code starts to behave like part of the label itself, and shoppers will expect it to be just as trustworthy.

What should retailers and brands be thinking about now?

The brands that handle this transition well are unlikely to be the ones that rushed to redesign every pack first. More likely, they'll be the ones that started treating product information as something to govern, with the same care they've always given to what's printed.

It starts with some unglamorous questions. Where does the content behind each code live, and who owns it? How will anyone know a link still works, and still says the right thing, two years after the pack reaches the shelf? If someone asks what a code showed on a particular date, could you prove it?

There's a physical side too. Fitting two codes onto a small pack, alongside the branding and the mandatory text, takes careful artwork planning, especially on packaging that hasn't changed in years.

A quieter, more useful story

The barcode is staying put for now. What's changing is how much a single square inch of packaging can be asked to do, and how much rests on the data sitting behind it. Research carried out with GS1 suggests shoppers don't especially want more information on their products; they want the right information when they need it. That's a sensible brief for the whole industry, and Sunrise 2027 is a good moment to start building toward it.

So with accurate, consistent and well-governed product information mattering more than ever, now's the ideal time to discover how Kallik's Veraciti platform helps businesses manage labeling and artwork across products, markets and languages, keeping information accurate, compliant and ready for what's next.

Learn how Kallik works

FAQs on GS1 Sunrise 2027

Are barcodes going extinct?  

No. GS1 Sunrise 2027 aims for checkouts to read 2D barcodes alongside UPC and EAN codes by the end of 2027. Retiring linear barcodes isn't part of the plan.

Is GS1 Sunrise 2027 mandatory?  

No. It's an industry initiative, though retailers adopting 2D scanning will shape what they expect from suppliers.

What is GS1 Digital Link?  

A GS1 standard that turns a product's identifiers into a web address, usually inside a QR code, so one code works at checkout and on a shopper's phone.

Do brands need to change their packaging?  

Many will add a 2D code next to the existing barcode, which can mean artwork changes. Managing the data that code connects to is the bigger job.

From Paper to Platform: What Electronic Product Information (ePI) Really Means for Labeling Teams

Title

From Paper to Platform: What Electronic Product Information (ePI) Really Means for Labeling Teams
Author Name
Kallik Role 1
Content Manager
10 min read

On September 1, the EMA published guidance on submitting electronic product information through its PLM Portal. Like many procedural updates, it would have been easy for regulatory affairs teams to skim it and move on.

But there’s an important change behind the guidance. Patient information leaflets, Summaries of Product Characteristics (SmPCs) and other product information have traditionally been managed as documents: drafted, reviewed, approved and sent for printing. Electronic product information (ePI) introduces a different way of managing that content, with defined statuses such as Draft, Submitted and Deactivated, and a growing role for digital processes in how product information is maintained.

That matters because product information can no longer be treated as finished once a document has been approved and published. It needs to be managed as a controlled record, with clear oversight of its status and ongoing changes.

The difference between a document and a dataset

Under the EU’s ePI Common Standard, electronic product information is more than a digital copy of an existing leaflet. It uses structured data based on HL7 FHIR (Fast Healthcare Interoperability Resources), allowing information to be searched, filtered and processed by digital systems, as well as accessed by patients and healthcare professionals. Simply uploading a PDF or converting a Word document into a digital file doesn’t achieve this; the information must follow the required structure and standard.

This also changes how pharmaceutical companies need to think about maintaining product information. Once content is held as structured data and linked to a regulatory record, it needs to remain consistent with the latest approved information. That means managing updates, versions and changes throughout the product’s lifecycle, rather than treating approval and publication as the end of the process.

What the September guidance actually asks of you

EMA’s guidance sets out several practical requirements for submitting and maintaining electronic product information (ePI). While submission is currently voluntary, there are specific rules around how records must be prepared, submitted and updated.

During the voluntary phase, ePI can be submitted in English, although multilingual product information will become increasingly important as the approach develops. Submissions are made through the PLM Portal, and reaching the correct status depends on getting the details right. The ePI must match the final approved annexes, the procedure number must be entered correctly, and the record must be set to ‘Submitted’ rather than left in ‘Draft’. New marketing authorization applications can remain in Draft status, while other procedures, including variations, renewals and transfers, follow different submission requirements.

There’s also a deadline to keep in mind when a marketing authorization is withdrawn or an application receives a negative opinion. According to the EMA guidance, the associated ePI must be moved out of Submitted status, either to Deactivated or back to Draft, within 15 working days of the EMA’s notification. For companies managing multiple products, markets and language versions, keeping track of these changes could become challenging without clear ownership and reliable processes.

This is where lifecycle management becomes important. Product information needs to be monitored and updated as regulatory circumstances change, with the right status, version and supporting information maintained throughout. As ePI develops, pharmaceutical companies will need to consider how their existing content management processes can support these requirements.

Who’s affected, and when

Nothing here is mandatory yet, and nothing happens overnight. The rollout is explicitly staged:

EU electronic product information (ePI) rollout, 2026–2028
WhenWhat happens
Now (voluntary phase)Centrally authorized products can submit ePI via the PLM Portal, English only
Q4 2026Phased voluntary go-live begins with centrally authorized vaccines
H1 2027Extends to centrally authorized oncology products
H2 2027Extends to remaining centrally authorized products
2027–2028Nationally authorized products follow, after individual Member States complete readiness assessments
~2028New rules generally apply EU-wide, 24 months after the legislation formally enters into force

Member States will still decide, for now, whether a given leaflet is paper, electronic, or both — and patients keep the right to request a printed copy regardless. Industry bodies like EFPIA have actually pushed for ePI to be phased in well before paper is phased out, precisely because nobody wants a gap where neither format is reliably available. So if you’re picturing a cliff edge where paper leaflets vanish overnight, that isn’t the plan, and it’s worth saying plainly: there’s no reason to panic-restructure anything this quarter.

What’s actually worth doing now

The organizations that will find this easy aren’t the ones who move fastest — they’re the ones whose product information already lives as structured, version-controlled data rather than static files scattered across departments. 

However, if their product information lives in a mix of Word documents, email threads, and whichever folder someone last saved to — this is a reasonable moment for those businesses to start closing that gap. Not because the deadline is close, but because the deadline being staged out over two years is exactly the kind of runway that gets wasted if nobody starts using it.

Prepare your business for ePI

If your product information is still scattered across shared drives, PDFs, and email threads waiting for final sign-off, the two-year runway on ePI is exactly the kind of deadline that gets missed by accident, not by neglect.

Veraciti™ keeps your label and artwork data as a single managed source of truth — version-controlled, audit-ready, and built to stay in sync the moment something changes, whether that change comes from the EMA, a new market, or your own regulatory affairs team. Speak to one of our labeling and artwork experts by filling in a form here or book a demo here.

Read more on how ePI affects labeling, or learn how Kallik works.

FAQs on Electronic Product Information (ePI)

What did the EMA's September 2026 guidance actually change? 

It set out, for the first time, exactly how marketing authorization holders should submit electronic product information for centrally authorized products through the EMA's Product Lifecycle Management (PLM) Portal — including submission statuses, which procedures require ePI, and the rule that an authorization's ePI must move out of Submitted status within 15 working days of a withdrawal or negative opinion.

Is electronic product information mandatory yet? 

No. As of late 2026, submitting ePI for centrally authorized products is voluntary, and it can be submitted in English only during this phase. Mandatory, multilingual ePI is being phased in through 2027 and 2028, starting with centrally authorized vaccines in Q4 2026 and extending to nationally authorized products once individual Member States complete readiness assessments.

Does a PDF of a leaflet count as electronic product information? 

No. ePI must be built to the EU's ePI Common Standard, based on HL7 FHIR, which makes the content structured, searchable, and machine-readable. A PDF, Word file, or other free-text document does not meet this standard, no matter how it's distributed.

What happens to a product's ePI if its marketing authorization is withdrawn? 

Any ePI in Submitted status for that product must be moved to Deactivated status within 15 working days of EMA's notice. The same 15-working-day window applies when an application receives a final negative opinion, unless re-examination is requested, in which case the ePI can remain in its current status until the final outcome is known.

Will paper patient information leaflets disappear? 

Not in the near term. Member States decide whether a given product's information is provided in paper, electronic, or both formats, and patients retain the right to request a printed copy. Industry groups including EFPIA have specifically called for ePI to be phased in well ahead of any phase-out of paper, so the two are expected to coexist for some time.

How is ePI different from a Digital Product Passport or eIFU? 

They solve related but distinct problems. ePI is specifically about structured, regulator-approved medicine information (the SmPC, package leaflet, and labeling) under the EU pharma package. eIFU covers electronic instructions for use, mainly in medical devices. A Digital Product Passport is a broader sustainability and traceability record that can apply across many product categories, including packaging. A single product can be subject to more than one of these requirements at once.

What should a labeling or regulatory affairs team do now, if ePI isn't mandatory yet? 

The most useful step is auditing whether your current product information already exists as structured, version-controlled, centrally managed content rather than static files. Teams that already manage their SmPC, Annex II, and labeling text this way will find the transition to ePI straightforward; teams that don't have a two-year runway to close that gap before it becomes mandatory.

10 Reasons Labeling Software Implementations Fail

Title

10 Reasons Labeling Software Implementations Fail
Author Name
Kallik Role 1
Content Manager
9 min read

Rolling out labeling and artwork management software should accelerate your operations and strengthen compliance. Yet many implementations stall, exceed budgets, or fail to deliver expected results. For packaging and labeling leaders at regulated manufacturers, understanding why projects go wrong is the first step toward getting them right.

The reasons for failure often trace back to decisions made early in the project. Kallik helps organizations in pharmaceuticals, medical devices, chemicals, and consumer goods navigate these challenges with structured workflows and proven implementation approaches. Here are the ten most common barriers to success.

Key Takeaways: Why Labeling Software Implementations Fail

  • Poor requirements definition leads to platform misalignment, delayed rollouts, and missed regulatory obligations
  • Insufficient stakeholder involvement causes resistance to adoption and gaps in critical workflow configurations
  • Underestimating data migration complexity results in incomplete asset libraries and version control failures
  • Skipping change management planning creates user frustration and undermines the benefits of new labeling technology
  • Frequently asked questions about implementation issues and advice on how to solve them
     

Implementation failure timing

Why Labeling and Artwork Management Software Implementations Go Wrong


1. Unclear Business Requirements

Many implementations begin without a complete picture of what the organization needs. Teams focus on features rather than outcomes, selecting software based on demos rather than documented requirements.

This disconnect between expectations and reality surfaces during deployment when the platform cannot support specific regulatory workflows or regional labeling variations. The fix requires going back to stakeholders, mapping current processes, and defining measurable success criteria before vendor selection.

2. Insufficient Stakeholder Involvement

Labeling touches regulatory affairs, quality, marketing, packaging, and manufacturing. When implementation teams exclude key departments, the system ends up serving only a portion of the organization's needs.

This often results in workarounds, shadow systems, and resistance to adoption. Early and ongoing involvement from all affected teams ensures the platform configuration reflects actual approval workflows and hierarchies.

3. Underestimating Data Migration Complexity

Moving existing labels, artwork files, and content libraries into a new system is rarely straightforward. Organizations frequently underestimate the time and resources required to clean, standardize, and validate their existing assets.

Without a structured approach, teams end up with incomplete libraries, duplicate files, and broken version histories. AI-enabled onboarding tools can accelerate this process by digitizing existing labels and extracting reusable components.

4. Neglecting Change Management

New software changes how people work. Without a structured change management plan, users default to familiar habits or resist the new system entirely.

Successful implementations include role-based training, clear communication about why the change is happening, and dedicated support during the transition period. Change management is not optional when dealing with thousands of labels across multiple markets.

5. Lack of Integration Planning

Labeling software does not exist in isolation. It needs to connect with ERP systems, PLM platforms, regulatory databases, and print management infrastructure.

When integration planning happens late in the project, teams discover technical barriers that delay go-live or require expensive custom development. Planning integrations from the start ensures data flows correctly across your enterprise systems.

6. Inadequate Workflow Configuration

Every organization has unique approval processes, regulatory requirements, and market-specific workflows. Treating workflow configuration as an afterthought leads to systems that do not match how teams actually work.

This creates bottlenecks, skipped approvals, and compliance risks. Taking time upfront to document and configure workflows correctly pays dividends throughout the platform's lifecycle.

7. Poor Vendor Communication

Implementation success depends on clear, consistent communication between your team and the software vendor. When expectations are unclear or feedback loops break down, misalignment compounds over time.

Establishing regular checkpoints, escalation paths, and a single point of contact on both sides keeps projects on track and surfaces issues before they become critical.

8. Unrealistic Timelines

Pressure to launch quickly leads to compressed timelines that sacrifice thorough testing, training, and configuration. Teams rush through critical phases and inherit problems that persist long after go-live.

Building in adequate time for user acceptance testing, parallel running, and refinement protects your investment and ensures the system works correctly from day one.

9. Skipping Validation Requirements

In regulated industries, labeling software must meet validation requirements. Skipping or shortcutting validation creates compliance exposure and can require costly remediation later.

Understanding your regulatory obligations early and building validation activities into the project plan ensures audit readiness from the start.

10. No Post-Implementation Support Plan

Going live is not the finish line. Without a plan for ongoing support, optimization, and user feedback, initial gains erode over time as workarounds accumulate and configurations drift.

A clear support structure, regular system reviews, and a pathway for continuous improvement ensure your labeling management platform delivers value year after year.

Implementation prekickoff checklist

How to Set Your Implementation Up for Success

Avoiding these pitfalls requires preparation, collaboration, and realistic expectations. Start by documenting your current processes and pain points. Involve stakeholders from every affected department early. Build time into your timeline for thorough testing and training.

Kallik helps regulated manufacturers navigate implementation complexity through structured workflows, AI-enabled label onboarding, and cloud-based artwork management. With over twenty years of experience supporting global enterprises, the platform is designed to reduce compliance risk and accelerate time to market.

If you are evaluating labeling and artwork management software, understanding these common failure points can help you ask better questions and make more informed decisions.

What’s Next: Preparing for a Successful Implementation

Knowing where implementations go wrong is only half the picture. The other half is knowing how to set yours up to go right from the very first conversation. That’s why this article is the first in a short series we’re running with Beth Peckover, Kallik’s Chief Delivery Officer. Beth has led labeling and artwork management rollouts for some of the world's biggest regulated manufacturers, and across the series she’ll share the practical lessons that separate smooth implementations from stalled ones.

In our next post, Beth will walk through how to prepare for implementation before your project kicks off, from defining requirements and bringing the right stakeholders to the table to planning for data migration, integration, and validation. Follow Kallik on LinkedIn or check back on our blog so you don’t miss it. In the meantime, if you’d like to speak with the Kallik team for expert advice on your own implementation, you can call us on +44 (0) 1827 318100, email us at enquiries@kallik.com, or fill in a form here.

FAQs about Why Labeling Software Implementations Fail

What is the most common reason labeling software implementations fail? 

Unclear business requirements top the list. When organizations select software without documenting specific needs and workflows, the platform often fails to support critical processes.

This leads to workarounds, user frustration, and missed regulatory obligations. Thorough requirements gathering before vendor selection prevents this outcome.

How long should a labeling software implementation take? 

Implementation timelines vary based on complexity, but rushing creates problems. Most enterprise deployments require several months to complete requirements gathering, configuration, data migration, testing, and training properly.

Building adequate time into your project plan protects your investment and ensures a stable launch.

Why is stakeholder involvement important in labeling software projects? 

Labeling touches multiple departments including regulatory, quality, marketing, and manufacturing. Excluding any group leads to workflow gaps and resistance to adoption.

Early involvement ensures the system configuration reflects how teams actually work and secures buy-in across the organization.

What role does data migration play in implementation success? 

Data migration is often underestimated. Moving existing labels, artwork, and content into a new system requires cleaning, standardization, and validation.

Incomplete migration leads to duplicate files, missing assets, and broken version histories that undermine the new platform's value.

How can organizations avoid implementation delays? 

Planning integration requirements, configuring workflows thoroughly, and building in testing time all help prevent delays.

Establishing clear communication with your vendor and maintaining realistic expectations about timelines keeps projects on track.

What happens if validation requirements are skipped? 

In regulated industries, skipping validation creates compliance exposure. Auditors may question system integrity, and remediation after go-live is more expensive than doing it correctly upfront.

Building validation activities into your project plan from the start ensures audit readiness and protects against regulatory risk.

Regulatory Label Changes: From Months to One Edit

Title

Regulatory Label Changes: From Months to One Edit
Author Name
Kallik Role 1
Content Manager
9 min read

PPWR recently became enforceable across the EU and despite most teams knowing it was coming, plenty still weren't ready. For the most part, this was not because they had misread the regulation, but rather because they just couldn't move fast enough once they knew what it meant.

Regulations affecting packaging are being introduced and updated all the time with sustainability and patient safety (quite rightly) becoming increasingly scrutinized. We’ve mapped out some of the biggest and most pressing ones in our latest free resource, but it takes a lot more than being aware of the regulation to be prepared for the regulation – especially when it could change again at any moment!

And if that’s not enough to have your regulatory affairs team stressed out, then do the multiplication and realize that each measure touches a set of SKUs and each SKU appears in several markets and each market wants its own languages, its own pack formats, its own regional variants. Seventeen regulations suddenly become tens of thousands of discrete label changes, all of which needs drafting, checking, approving and evidencing. Unfortunately, we often find that nobody plans for that number because nobody sees it until it arrives.

Download the free PDF

Why Packaging Updates Are Simpler Than You Probably Think

If you strip away the legal text, the reality of a regulation update is that a controlled element on your label has changed. Whether it’s a hazard statement, an allergen declaration, a supplier address, a sustainability claim, the work underneath is the same. This therefore raises the question: if the work is the same every time, why does every regulation land like a brand new crisis for so many businesses?

Label changes multiplication

Your Process is Holding You Back

Most organizations still hold their labels as artwork files. Unfortunately, in that world, a hazard statement is not something your system knows about or can easily locate and update for you. So when the statement changes, you can't update the statement. You can only open files and go looking for it.

Which is why the first few weeks (or even months) of every regulatory project are spent on a question that has nothing to do with regulation: which of our labels does this actually affect? Somebody builds a spreadsheet while somebody else cross-references it against the product master and then a third person finds four SKUs that were missed, usually late, usually in a market nobody thought about. And then this all gets repeated in full, from scratch, every single time. Sound familiar?

What Changes When the Element is the Unit

Now imagine the same seventeen measures landing on a library where every phrase, symbol, pictogram, warning and image is stored as its own approved, reusable asset, and templates assemble those assets into finished labels. You already know where every element is used, because the relationship is data rather than memory.

Update the hazard statement once, with one simple click, and it flows to every label that carries it, in every language, with the version history sitting behind it. The regulation stops being a project and instead becomes a simple edit. That is the difference between a team that spends 2027 reacting and a team that spends it prepared. Which would you prefer?

Where Kallik Comes In

Veraciti™ was built for regulated manufacturers from the start rather than adapted for them later, and it shows in the parts that usually hurt most.

Where Used answers the scoping question instantly, so the two weeks of archaeology never happen. Cloud Designer lets your own people build and amend labels without specialist desktop software or a third-party studio on retainer. And the approval workflows were designed around genuinely regulated sign-off, with the audit trail produced as a byproduct of the work rather than reconstructed afterward for an inspector.

The objection we most often hear when it comes to switching from emails and spreadsheets to a fully end-to-end software like ours is: migration. Twenty years of accumulated artwork files, and the reasonable fear that moving them will be long, complicated and painful. That is exactly why we built AToM, an AI-driven tool which digitizes existing labels into structured, reusable components automatically and accurately. 

We help our customers to reach full regulatory compliance and hold it there. The days of headaches and stress from regulatory updates are gone, and instead of hiring a team to help you manage the changes, you can simply make thousands of changes with the click of a button. 

Label changes one edit

See the Full Picture and Stay Ahead 

We've put some of the biggest and most important regulation updates in a single infographic, grouped by industry, mapped by market and sequenced by deadline. It's free, it's detailed, and it's the clearest view we've found of what the next few years actually look like.

Interested in learning more? Why not book in for a free, no-obligation chat with one of our label and artwork management experts by calling +44 (0) 1827 318100, emailing enquiries@kallik.com, or filling in a form here. Alternatively, learn more about how Kallik works here.

Download the free PDF

FAQs about regulatory label changes

Why do regulatory label changes take so long? 

Most of the time goes on scoping rather than on the change itself. When labels are held as artwork files, a hazard statement or allergen declaration exists only as ink inside a PDF, so the system cannot tell you which labels contain it. Teams build spreadsheets, cross-reference them against the product master, and still miss SKUs in markets nobody thought about — and the whole exercise is repeated from scratch for every new regulation.

What is structured content in label management? 

Structured content means storing every phrase, symbol, pictogram, warning, and image as its own approved, reusable asset, with templates assembling those assets into finished labels. The label becomes a set of relationships between controlled elements rather than a flat design file. That is what allows a change to one element to flow through to every label that carries it, in every language, with the version history behind it.

How do you find every label affected by a regulation change? 

If labels are stored as structured content, the system already knows where every element is used, because the relationship is recorded as data rather than held in someone's memory. A query returns every artwork containing a given phrase or symbol in seconds. In Kallik's Veraciti™, the Where Used feature does this and pulls the affected labels into a single project, so they can be updated together and approved in one sign-off rather than opened one at a time.

What is the difference between an artwork file and a label template? 

An artwork file is a finished design, and the regulatory content inside it is not separately identifiable to the system. A label template is a structure that assembles approved, individually controlled components into a finished label. The practical difference shows up when something changes: an artwork file has to be found and edited by hand, while a template updates automatically when the component it references is updated.

What happens to existing artwork when moving to a structured labeling system? 

Existing artwork does not have to be rebuilt by hand. Kallik's AToM is an AI-driven migration tool that reads existing labels and artwork, breaks them down into their areas of content, and builds structured, reusable templates automatically. It identifies and removes duplicate phrases and symbols along the way, so the result is a deduplicated library rather than a copy of the original file store.

 

What Is Label Artwork Management Software? A Buyer's Guide

Title

What Is Label Artwork Management Software? A Buyer's Guide
Author Name
Kallik Role 1
Content Manager
7 min read

One out-of-date hazard symbol can hold a shipment at customs. One mismatched ingredient statement can trigger a recall across three continents. For organizations managing thousands of SKUs across dozens of markets, label and artwork accuracy is a major business risk.

Most companies only start shopping for label artwork management software once that risk becomes visible. This guide explains what the software actually does, which features matter, and how to compare vendors before you commit.

What is label artwork management software?

Label artwork management software is a centralized platform that manages the full lifecycle of product labels and packaging artwork – content creation, translation, review, approval, version control, and print-ready output – in one controlled system. It replaces the spreadsheets, shared drives, email approval chains, and disconnected design tools that most organizations begin with, giving every team a single source of truth for label content and artwork.

The strongest platforms combine two capabilities that are often sold separately: artwork management (design, proofing, approval workflows) and labeling management (structured content, phrases, symbols, regulatory data). Keeping them in one system is what removes the copy-paste errors that cause compliance failures.


Who needs it?

Label artwork management software is built for regulated and high-complexity industries, including:

  • Pharmaceuticals and life sciences
  • Medical devices and IVD
  • Chemicals, oil, and lubricants
  • Cosmetics and personal care
  • Food, beverage, and consumer goods

If your business faces multi-market regulatory change, frequent artwork revisions, or audits that require a defensible history of every label version, manual processes will eventually become the bottleneck.


Core features to look for

Use this as your evaluation checklist:

Single source of truth: one governed repository for all label content, artwork, images, and symbols.

Component reuse: approved phrases, warnings, and symbols reused across SKUs instead of recreated each time.

Automated approval workflows: routed reviews with electronic signatures and full audit trails.

Version control and "where used" visibility: instantly see every product affected by a single content change.

Regulatory readiness: support for frameworks such as EU MDR, 21 CFR Part 211, CLP, and Digital Product Passports.

Cloud-native architecture: global access, faster deployment, and no infrastructure burden.

AI-assisted onboarding: automated migration of legacy labels so implementation is measured in weeks, not years.

Integration: connections to ERP, PLM, and QMS so label data stays synchronized with product data.

Shortlist

Label artwork management vs. label printing software


These categories are frequently confused, and the difference matters when you build your shortlist.

Label printing software vs. label artwork management software
CriteriaLabel printing softwareLabel artwork management software
Primary purposeDesign and print barcodes and labelsGovern the entire label and artwork lifecycle
Approval workflowsMinimal or manualAutomated, audited, signature-controlled
Best fitSmall to mid-sized, print-focused operationsGlobal, regulated, multi-SKU enterprises
Compliance evidenceLimitedFull audit trail and version history

If your requirement is simply printing labels on the production line, printing software may be enough. If you need to prove why a label says what it says, you need artwork management.


Five questions to ask every vendor

  1. Is labeling and artwork one platform or two integrated products? Modular suites often carry hidden integration cost.
  2. How long does implementation take, and how is legacy data migrated? Ask for a realistic onboarding timeline with named comparable customers.
  3. Can it scale across regions and languages? Multi-market expansion is where thin platforms fail.
  4. What compliance evidence does it produce automatically? Audit trails should be a byproduct of daily work, not a manual exercise.
  5. Is it genuinely cloud-native, or a hosted legacy system? The difference shows up in release cadence and uptime.

To see how leading platforms stack up on these criteria, compare Kallik vs. Loftware, Kallik vs. Esko, and Kallik vs. BarTender.

Vender Evaluation


The bottom line

Label artwork management software pays for itself in avoided rework, faster time to market, and audit confidence. The right choice depends on your scale and regulatory exposure: smaller, print-led operations may be well served by lighter tools, while global regulated enterprises need a unified platform built for complexity.

Kallik's Veraciti™ brings labeling and artwork together in one cloud-native platform designed for regulated industries. Book a demo to see it applied to your portfolio.

 

FAQs on label artwork management software

What is label artwork management software? 

Label artwork management software is a centralized platform that controls the full lifecycle of product labels and packaging artwork, including content creation, translation, review, approval, version control, and print-ready output. It gives regulated organizations a single source of truth and an audit trail for every label change.

What is the difference between artwork management and labeling management? 

Artwork management covers the visual design, proofing, and approval of packaging and label artwork. Labeling management covers the structured content within a label, such as approved phrases, warnings, symbols, and regulatory data. Unified platforms handle both, which removes the manual transfer errors that occur when the two are managed separately.

Which industries use label artwork management software? 

It is used most heavily in regulated sectors: pharmaceuticals, medical devices, chemicals, cosmetics, food and beverage, and consumer goods. These industries face frequent regulatory change, multi-market labeling requirements, and audits that demand a documented history of every label version.

How long does it take to implement label artwork management software? 

Timelines vary with portfolio size and data quality. Legacy on-premise projects historically ran for a year or more, while cloud-native platforms with AI-assisted label migration can shorten onboarding significantly. Ask each vendor for a phased plan and reference customers of similar complexity.

Do I need label artwork management software if I already have label printing software? 

Often, yes. Printing software creates and outputs labels but typically lacks controlled approval workflows, version history, and compliance evidence. If you must demonstrate to a regulator how a label was approved and by whom, printing software alone will not cover it.

How AI Simplifies Label and Artwork Migration

Title

How AI Simplifies Label and Artwork Migration
Author Name
Kallik Role 1
Content Manager
10 min read

Every labeling software project has a moment where the enthusiasm meets the archive. Someone opens the folder containing fifteen years of artwork – PDFs, InDesign files, scanned proofs, a spreadsheet that was supposed to be the master list – and the question becomes very real. How does all of that get into the new system?

For most vendors, the answer is people. A migration team, a long project plan, and months of copying content across by hand while your team keeps the current process running alongside it. That cost is why plenty of organizations stay on a system they've outgrown. The pain of switching looks worse than the pain of staying. AToM exists to change that math.

Artwork


Why Migration is the Part Everyone Dreads

Manual onboarding is often slow and painful, but the real problem is what manual work does to accuracy.

Someone reads a value off a legacy label and types it into a new template. Someone interprets an inconsistent data field and makes a judgment call. Someone recreates a template by eye because the original design file is missing. Do that a few hundred times and you've introduced variation into a label library that's supposed to be your single source of truth – and you've done it right at the point where nobody is checking, because migration is treated as an IT task rather than a regulatory one.

It's worth being honest about where those inconsistencies come from in the first place. As Tear Hambrey, Solution Consultant at Kallik, puts it, a good starting point is to "look at the entire process overall, and look at the disconnected systems that are being used. And often companies will find that a lot of the errors are stemming from those disconnected systems."

Migration is the moment you either carry those disconnected systems forward or leave them behind.


What AToM Actually Does With Your Artwork

AToM (Assisted Tool of Migration) is the AI tool Kallik uses to bring your existing labels and artwork into Veraciti™. It doesn't simply copy files across, it reads them and does the work of an entire team with just one click.

Ed Briggs, Product Requirements Analyst at Kallik, describes the process from the inside: "We'll take your existing artworks and labels and we will migrate them into the Veraciti system. One of our migration users will drop this file into AToM. And what AToM will do is it'll start breaking down the existing artwork into its areas of content, and it will create a template based on the artwork supplied."

That distinction matters. A copied file is still a flat piece of artwork. A structured template is a set of components – regulatory statements, symbols, warning phrases, brand elements, market-specific content – that the system can recognize, reuse, and control. AToM extracts the content, identifies and removes duplicate phrases and symbols along the way, and builds reusable templates with regulatory and brand logic already embedded.

You come out of migration with a clean, structured, deduplicated label library rather than a digital filing cabinet full of the same mess you had before. And the part customers tend to find most interesting is that AToM isn't static – every correction a migration user makes feeds back into the model.

"It has a machine learning process," Ed explains, "so the more artworks you feed into the system, all of the data that migration users are putting in will build a greater machine learning. So in the future, the more artworks dropped into the file, the greater accuracy AToM will have when migrating artworks and labels into the Veraciti system."

In practice that means the back end of a large migration runs faster and more accurately than the front end. For enterprises with sprawling portfolios across multiple regions and product families – exactly the organizations for whom manual migration is most punishing – that curve is the whole point.

Faster


What it Looks Like at Scale


When Kenvue separated from Johnson & Johnson, it had to rework more than 20,000 artworks across a global brand portfolio. Working with Kallik and AToM, Kenvue removed the fragmentation across its label estate and cut its rework cycles, ending up with a digital foundation rather than a repaired version of the old one. Packaging changes now run 95% faster.
That number isn't really a migration statistic. It's what becomes possible once content is structured.


The Payoff Comes After Go-Live

Structured content is what turns a regulatory change from a project into a task. Once your labels are templates rather than files, Veraciti's Where Used feature lets you find every artwork containing a given symbol or phrase, pull them into a single project, update them together, and sign the whole set off at once. As Ed puts it, "this could be thousands of labels you could be changing for a regulation change with ease with a single sign-off, rather than having to go into each of these and manually adjusting them."

That capability only exists because AToM did the structural work up front. Migrate badly and every future regulation change is a manual sweep. Migrate properly and it's a search, a project, and an approval.


What This Actually Buys You

Shorter onboarding, so your investment starts returning sooner. Fewer errors introduced at the exact moment nobody is watching for them. A deduplicated content library instead of an inherited backlog. And a label estate that's ready for whatever the next regulation asks of it, rather than one that needs rebuilding first.

If the size of your archive is the reason you haven't moved yet, that's the specific problem AToM was built to solve. Book a demo and we'll show you what AToM does with your own artwork. Speak to our labeling and artwork experts by filling in a form here, or book a demo here.

Read our free guide on getting AI-ready

Learn how Kallik works<

FAQs about label artwork migration

What is AToM? 

AToM, or Assisted Tool of Migration, is the AI tool Kallik uses to bring existing labels and artwork into the Veraciti™ platform. Rather than copying files across, it reads each artwork, breaks it down into its areas of content, and builds a structured, reusable template from what it finds — identifying and removing duplicate phrases and symbols along the way.

Why is manual label artwork migration a compliance risk? 

Manual migration introduces variation at the exact point where nobody is checking for it. Values get retyped from legacy labels, inconsistent data fields get resolved by judgment call, and missing design files get recreated by eye. Repeated across hundreds of artworks, this seeds inconsistency into a library that is supposed to serve as a single source of truth — and because migration is usually treated as an IT project rather than a regulatory one, those errors often go unreviewed.

How does AToM turn existing artwork into reusable templates? 

A migration user drops the existing artwork file into AToM, which breaks it down into its areas of content and creates a template based on the artwork supplied. The distinction matters: a copied file remains a flat piece of artwork, while a structured template is a set of recognized components — regulatory statements, symbols, warning phrases, brand elements, and market-specific content — that the system can reuse and control.

Does AToM become more accurate over time? 

Yes. AToM uses a machine learning process, so every correction a migration user makes feeds back into the model. In practice this means the later stages of a large migration run faster and more accurately than the early ones — which matters most for enterprises with sprawling portfolios across multiple regions and product families.

Can AToM handle large label portfolios? 

Yes. When Kenvue separated from Johnson & Johnson, it had to rework more than 20,000 artworks across a global brand portfolio. Working with Kallik and AToM, Kenvue removed the fragmentation across its label estate and cut its rework cycles, ending up with a digital foundation rather than a repaired version of the old one. Packaging changes now run 95% faster.

What is the Where Used feature in Veraciti? 

Where Used identifies every artwork containing a given symbol or phrase, so a single regulatory change can be applied across all affected labels at once rather than label by label. Affected artworks are pulled into one project, updated together, and signed off in a single approval. The feature depends on content having been structured during migration, because flat artwork files cannot be queried this way.

Why PFAS Will Become a Labeling and Product Information Challenge

Title

Why PFAS Will Become a Labeling and Product Information Challenge
Author Name
Kallik Role 1
Content Manager
7 min read

For most manufacturers, PFAS has been a chemistry problem. It has sat with R&D, procurement, and EHS teams, discussed in terms of substitution, testing, and supplier declarations. However, that is about to change. From January 1, 2027, New Mexico will require products containing intentionally added PFAS to say so on the label. The moment a regulator specifies what appears on the pack, PFAS stops being a chemistry problem and becomes a labeling and product information problem.


What is PFAS Regulation Actually Asking Manufacturers to Do?


Two things: get PFAS out of products, and account for it wherever it remains.

In the US, the accounting has already started. Minnesota's Amara's Law set an initial reporting deadline of September 15, 2026, requiring a description of each product, the function PFAS serves in it, and the amount of each substance present. New Mexico's first reports are due January 1, 2027. Maine, Minnesota, and New Mexico all move to broad bans on intentionally added PFAS in 2032, with phased category restrictions arriving every year in between.

In the EU, the universal PFAS restriction under REACH moved decisively in 2026. ECHA's Risk Assessment Committee adopted its opinion in March, the Socio-Economic Analysis Committee's draft opinion went out to consultation until May, and a final opinion is expected by the end of the year before the Commission drafts an amendment to Annex XVII.
 

pfas graphic deadline


Why Does PFAS End Up On the Label?


New Mexico is the first state to put PFAS disclosure on the product itself rather than in a database. The rule points toward a pictogram, a route to the state agency's information, a Spanish translation, and a health warning, with different handling for complex durable goods. That is a new mandatory element competing for space on packs that are already crowded.

Precedent rarely stays in one state. Allergen disclosure, recycled content, and packaging symbols all started as a single jurisdiction's requirement before becoming standard practice.

The other half of the label risk is voluntary. "PFAS-free" is a claim, and claims attract scrutiny. Any brand making one needs evidence that holds at component level, not a supplier reassurance filed in a shared drive three years ago.


What Happens to Your Artwork When You Reformulate?


This is the part we often see labeling teams underestimate. Removing PFAS from a product is not a single change; it cascades and affects far more of the business than most think. It means that ingredient statements shift, hazard symbols and safety phrases change, and instructions for use, storage advice, and market-specific claims all follow. A single raw material substitution can touch hundreds of SKUs across dozens of markets and languages.

The question that decides your timeline is a simple one: which of our artworks contain the affected component? If answering it means a manual audit across PDFs, email chains, and separate regional systems, then reformulation is not your bottleneck. Artwork is.

Divergence compounds it. When New Mexico requires a label element Minnesota does not, and the EU restricts a substance the US still permits, you are not managing one pack. You are managing market-specific variants of the same product, each with its own approval trail and version history.
 

pfas graphic reformulation cascade


What Should Labeling Teams Do Now?


Three moves are worth making before the deadlines force them. Map exposure at component level, not product level. Knowing which products contain PFAS is compliance. Knowing which phrases, symbols, and artwork components are affected is what makes the change deliverable.

Treat PFAS status as structured data, not a document. Supplier declarations sitting in a folder cannot be queried, versioned, or pushed through to artwork. Structured content can.

Build the "where used" view before you need it. The teams that will handle 2027 calmly are the ones who can already answer, in minutes, which labels a component appears on.

PFAS is the clearest example yet of a wider shift. Regulation increasingly asks for structured, traceable product data expressed accurately on the label — the same pattern running through PPWR, EUDAMED, ePI, and the Digital Product Passport. Companies that treat labeling as a data discipline will absorb PFAS. The rest will find out how long a manual audit really takes.


Stay Compliant By Talking it Through with Kallik


Organizations managing this kind of change in Veraciti™ work from a single source of structured content, where every phrase, symbol, and component carries full "where used" visibility. A PFAS-driven update becomes a query and a controlled rollout rather than a three-month audit.

If you want a straight read on where your labeling operation sits against what is coming, Kallik works with regulated manufacturers on exactly this and is happy to have the conversation. Call us on +44 (0)1827 318100, email info@kallik.com, or fill in a form here and we’ll be in contact.

Read our free guide on getting AI-ready

Learn how Kallik works
 

Frequently asked questions

What are PFAS?

PFAS are per- and polyfluoroalkyl substances, a group of more than 10,000 synthetic chemicals used for water, grease, and heat resistance. They are often called "forever chemicals" because they break down extremely slowly in the environment.

Which states require PFAS labeling?

New Mexico is the first US state to require an on-product PFAS label, effective January 1, 2027, for products containing intentionally added PFAS. Other states currently require reporting or restrict sales rather than mandating a label, but the precedent is expected to spread.

When is the Minnesota PFAS reporting deadline?

The initial reporting deadline under Minnesota's Amara's Law is September 15, 2026, following two extensions from the original January 2026 date. Manufacturers who applied by August 16, 2026 were eligible for a single 90-day extension to December 14, 2026; that application window has now closed. Subsequent reports are due each February 1, and products manufactured before July 1, 2023 are excluded from the requirement.

Will the EU ban PFAS?

The EU is considering a universal restriction on PFAS under REACH, proposed by Denmark, Germany, the Netherlands, Norway, and Sweden. ECHA's Risk Assessment Committee adopted its final opinion on March 2, 2026, and its Socio-Economic Analysis Committee is expected to finalize its opinion by the end of 2026. The European Commission will then draft the restriction, its scope, transition periods, and derogations.

How does PFAS regulation affect labeling and artwork?

It affects labeling in three ways: mandatory on-pack disclosure in jurisdictions like New Mexico, the evidence required to support "PFAS-free" claims, and the artwork changes triggered by reformulation, including ingredient statements, hazard symbols, and instructions for use across every affected market and language.

Top 7 Regulatory Labeling Errors in Manufacturing

Title

Top 7 Regulatory Labeling Errors in Manufacturing
Author Name
Kallik Role 1
Content Manager
11 min read

A single labeling mistake can halt production lines, trigger recalls, and put your organization at risk of regulatory penalties. For regulated manufacturers, the stakes have never been higher.

Kallik works with pharmaceutical, medical device, and consumer goods companies to eliminate these costly risks through automated regulatory labeling workflows. Understanding where errors occur is the first step toward preventing them.

This article explores the seven most common regulatory labeling errors that affect manufacturers, with practical guidance on how automated artwork approval workflows can help you avoid each one.
 

pfas deadlines


The 7 Most Common Regulatory Labeling Errors in Manufacturing


1. Version control failures

Using an outdated label file is one of the most frequent causes of packaging recalls. When multiple versions of artwork circulate across email threads, shared drives, and external agencies, teams can easily approve and print the wrong file.

This happens because many organizations lack a single source of truth for their labeling assets. Designers work from one version while regulatory teams approve another, and production receives something different entirely.

How to prevent version control errors

Implement a centralized artwork management platform that serves as your single source of truth

  • Use automated version numbering and approval status indicators
  • Restrict access to final files until all approval stages are complete
  • Maintain complete audit trails showing who approved what and when

2. Translation and localization inaccuracies

Multi-market manufacturers face significant risks when translating label content across languages. A mistranslated warning, dosage instruction, or allergen statement can have serious consequences for patient safety and regulatory compliance.

The challenge grows exponentially when managing hundreds or thousands of SKUs across dozens of markets. Copy-paste operations between documents introduce errors, and without proper version control for translations, outdated text can end up on printed packaging.

How to prevent translation errors

  • Store approved translations in a centralized phrase library
  • Pre-approve all translated content before it enters the artwork workflow
  • Track where each phrase is used across your entire label portfolio
  • Automate translation updates when regulations change

3. Missing or incorrect regulatory content

Omitting required symbols, safety warnings, or allergen declarations is one of the most persistent causes of product recalls in regulated industries — and the data shows it is not a marginal problem.

A ten-year analysis of FDA drug recall data covering 2012 to 2023 found that labeling and packaging issues accounted for 19% of drug recalls, behind only impurities and contaminants at 37% and control issues at 28%. The same study recorded an average of 330 drug recalls initiated each year, with each recall involving around 400,000 product units and taking an average of 1.3 years to move from initiation to termination.

Food and beverage tells a similar story from a different angle. Undeclared allergens — a labeling failure rather than a manufacturing one — accounted for 38.8% of the 320 food recalls issued by the FDA and USDA in 2025.

These errors often occur when regulatory requirements change and teams must update large numbers of labels quickly. Without an automated way to identify affected products and apply required changes, some labels inevitably slip through with outdated or incomplete information.

How to prevent missing regulatory content

  • Use rule-based automation to populate required content automatically
  • Configure validation checks that prevent approval of non-compliant labels
  • Maintain a current library of regulatory symbols and required phrases
  • Track regulatory changes and identify affected labels instantly

4. Incorrect data placement and measurement errors

A decimal point in the wrong place or an incorrect unit of measurement can turn a safe product into a dangerous one. Dosage errors on pharmaceutical labels, incorrect nutritional values on food packaging, or wrong concentrations on chemical products all create serious safety risks.

These errors typically occur during content entry or when transferring data between systems. When artwork teams manually input values from specification documents, transcription mistakes are inevitable.

How to prevent data placement errors

  • Automate data population from approved source systems
  • Use templates with locked data fields to prevent accidental changes
  • Implement validation rules that flag out-of-range values
  • Require separate verification of numerical data during approval

5. Approval workflow gaps and skipped reviews

When approval workflows are informal or poorly defined, critical review stages get skipped. Regulatory teams may not see artwork before it goes to production. Quality assurance might be bypassed during urgent timelines. The result is non-compliant labels reaching the market.

When a label reaches production without the reviews it needed, the investigation usually lands on human error. Regulators are explicitly skeptical of that conclusion. EU GMP Chapter 1, section 1.4(xiv), requires that where human error is suspected or identified as the cause, that conclusion must be justified — with care taken to confirm that process, procedural, or system-based problems have not been overlooked first.

The implication for labeling teams is direct. "The reviewer missed it" is not a defensible root cause if the workflow made it possible to miss. Inspectors expect controls that make the error difficult, not processes that rely on individual vigilance under deadline pressure.

How to prevent approval workflow gaps

  • Define mandatory approval stages for each label type
  • Assign role-based review responsibilities
  • Lock artwork progression until required approvals are captured
  • Maintain electronic signatures and audit trails for compliance

6. Brand and style guide deviations

Labels must carry the brand's identity and message clearly and consistently, without any spelling mistakes or deviations from the brand's style guide. Inconsistent logos, incorrect colors, or unapproved fonts undermine brand equity and can create confusion for customers.

This error type becomes more common when managing labels across multiple agencies, print suppliers, or regional teams. Each party may interpret brand guidelines differently, leading to inconsistent execution across your product portfolio.

How to prevent brand deviations

  • Centralize all approved brand assets in a single library
  • Use locked templates that enforce brand guidelines
  • Restrict access to unapproved design elements
  • Include brand compliance checks in your approval workflow

7. Last-minute change mismanagement

Urgent changes close to production deadlines create high-risk conditions for labeling errors. When regulatory updates, promotional content, or specification changes arrive at the last minute, teams face pressure to implement updates quickly without proper review.

This pressure often leads to shortcuts: skipped approval stages, incomplete version control, or changes applied to some but not all affected labels. Each shortcut compresses the next one, and teams end up fixing mistakes while still rushing to meet the launch date — which is precisely the condition in which more mistakes get made.

How to prevent last-minute change errors

  • Establish clear protocols for urgent change requests
  • Use automated tools to identify all affected labels instantly
  • Maintain abbreviated but complete approval workflows for urgent changes
  • Document the business justification for expedited timelines


What Causes Most Regulatory Labeling Errors in Manufacturing?


Most labeling errors trace back to three root causes: fragmented processes, insufficient automation, and poor visibility across the content lifecycle. When teams work in siloed systems without a single source of truth, mistakes become inevitable.

The solution lies in consolidating labeling and artwork management into a unified platform. Kallik's cloud-based, end-to-end platform, Veraciti™, collapses multiple siloed processes into one central workflow, giving you visibility over your entire labeling operation. Automated generation removes manual touchpoints where errors typically occur, and enforced approvals ensure nothing reaches production without proper review.
 

pfas cascade


How Can Automated Workflows Reduce Labeling Compliance Risk?


Automation addresses labeling errors at their source. Instead of relying on human vigilance to catch mistakes, automated systems prevent errors from occurring in the first place.

Veraciti™ automates artwork generation using pre-approved templates and content. The Advanced Rules Engine applies regulatory requirements automatically, removing the need for manual regulatory knowledge. Configurable workflows enforce proper review sequences, and audit trails document every action for compliance reporting.

The result is faster time to market with reduced compliance risk: fewer manual touchpoints, enforced review sequences, and an audit trail that can reconstruct any label's history on demand.


How Kallik Can Help Prevent Labeling Errors


Regulatory labeling errors cost manufacturers millions in recalls, regulatory penalties, and reputational damage. But these errors are preventable when you have the right systems in place.

Veraciti™ gives regulated manufacturers complete control over their labeling and artwork operations. From centralized asset management and automated artwork generation to enforced approval workflows and complete audit trails, every feature is designed to eliminate the root causes of labeling errors.

With more than 20 years of experience serving highly regulated industries, Kallik understands the compliance challenges you face. Our cloud-based platform runs on AWS with extensive security certifications, providing 24/7 access from anywhere in the world.

Ready to eliminate regulatory labeling errors from your operations? Contact Kallik to see how Veraciti™ can help you achieve total regulatory confidence.

Read our free guide on getting AI-ready

Learn how Kallik works
 

FAQs about regulatory labeling errors in manufacturing

What percentage of product recalls are caused by labeling errors?

Labeling and packaging issues accounted for 19% of FDA drug recalls between 2012 and 2023, making them the third most common cause after impurities and contaminants at 37% and control issues at 28%. In food and beverage the share is higher: undeclared allergens, which are a labeling failure, accounted for 38.8% of the 320 FDA and USDA food recalls issued in 2025. Most labeling-related recalls are preventable through content validation and enforced approval workflows. Platforms such as Kallik's Veraciti™ apply approved content automatically and prevent artwork from progressing until every required review has been captured.

How does version control prevent labeling errors?

Version control ensures teams always work from the latest approved file rather than a copy circulating by email or sitting on a shared drive. A complete version history with an audit trail also shows who changed what and when, which is what an inspector will ask for. Kallik's Veraciti™ maintains that history automatically and prevents outdated or unapproved artwork from reaching production.

What is the 'Where Used' function in labeling management?

A 'Where Used' function identifies every label and artwork in which a specific asset, phrase, or symbol appears. It matters most when a regulation changes: instead of manually auditing a portfolio to find affected products, teams get an instant list of everything that needs updating. In Kallik's Veraciti™, this runs across the entire label portfolio, so a single phrase change can be traced and applied everywhere it is used.

Can automated artwork generation reduce human error?

Yes. Automated generation assembles labels from pre-approved templates and content rather than manual data entry, which removes the transcription and data placement mistakes that cause a large share of labeling defects. Kallik's Veraciti™ generates labels in seconds rather than days using this approach, with content drawn from approved source data.

How do approval workflows improve regulatory compliance?

Enforced approval workflows ensure every label receives its required reviews before production, and produce the documentation an auditor needs to confirm it. Role-based approvals assign responsibility to named reviewers, while electronic signatures create a defensible record of each decision. Kallik's Veraciti™ configures these workflows per label type and blocks non-compliant artwork from advancing.

One Template, Hundreds of Labels: Inside Kallik's Cloud Designer

Title

One Template, Hundreds of Labels: Inside Kallik's Cloud Designer
Author Name
Kallik Role 1
Content Manager
9 min read

Every labeling team has a folder somewhere with forty variations of the same carton, saved as forty separate files, because the ingredient list changed for one market and the flavor changed for another and the barcode needed a different expiry format for a third.

None of those are design changes. They're content changes. But because the content was baked into the file, every one of them had to go back through a designer, back through approval, and back onto the launch timeline.

That's the problem Cloud Designer is built to solve. The design lives in one place. The data lives somewhere else. The label is what happens when the two meet.

Why Label Design Gets Duplicated

Three habits cause most of the duplication, and none of them look unreasonable in the moment, but trust us when we say there’s a far better way of doing things. Does the below sound familiar to you?

Content is typed into the artwork

Someone puts the net weight, the lot number, the ingredient panel straight onto the canvas. It's the fastest way to get the first label out and it's also the reason the four hundredth label takes just as long as the first.

Variants are built by copying files

A new market means a new file. A new flavor means a new file. Nobody sets out to maintain a hundred near-identical templates, but we’ve seen it happen time and time again where over time one seemingly reasonable decision gets made at a time and then suddenly it’s an issue. 

Nobody is sure which file is current

Design sits outside the system of record, so the artwork and the approved content drift apart quietly. You usually find out at press check.

As Tear Hambrey, Solution Consultant at Kallik, explained during our recent walkthrough of the tool, the point of the template is that it stays a template. Barcodes, tables, and copy pull from the project brief rather than being hardcoded, so the design is a structure rather than a finished document.

Nobody is sure which file is current


What Does Cloud Designer Do Differently?


The template is a structure, not a document

A Cloud Designer template is built from four container types: text, image, table, and barcode. Every element on the canvas is one of those four, and every one of them can be tagged to a data source instead of filled in by hand.

Those containers sit across distinct layers. The background trace carries the imagery, usually product photography. The die line holds the packaging measurements and guidelines. Graphics and copy sit on their own layers above them. Because the die line and the background are separate, swapping a pack size or a photograph doesn't disturb anything else on the label.

That separation is what makes variants cheap. Duplicate the template, change the die line or the background, and the entire content structure comes with it intact.

Barcodes that follow the brief

Barcodes are managed separately from the rest of the design, and they link to the requirements in the project brief rather than being drawn into the template.

In practice that means one template handles expiry dates, lot numbers, and market-specific symbologies without a designer touching it again. The container is configured once, including the quiet zone needed for reliable scanning, and it produces the correct code for whatever the brief calls for.

Those configurations get established during discovery, based on what your products and your markets actually require.

Dynamic tables for the panels that change most

Ingredient panels, nutrition tables, hazard statements, and multi-language content are usually the messiest part of a label, and they're the part that changes most often.

Dynamic table containers give you control at the individual cell level, including border thickness, border color, and content type. Cells populate from the project brief, so you can insert an approved phrase, a managed asset, or free text into a specific field without rebuilding the table.

Dynamic tables replaced the older composite grid system, and the practical difference is data integration. The old grid was a layout tool. This one is a connection point.

Color, variants, and spot color accuracy

The color library manages text color across the template and supports multiple color tables, which is how variant families get built. Different flavors, different market schemes, same underlying design.

Pantone colors can be imported as spot colors and then verified through the asset inspector, so you can confirm the actual color percentages rather than trusting what the file looks like on screen. For anyone who has had a print run rejected over a brand color, that verification step earns its place.

Canvas setup is equally flexible. Size the artboard in inches, millimeters, or points, and set snap-to-grid behavior and guideline colors to suit how your designers work.

Governance that comes as standard

Design tools generally treat version control as somebody else's job. Cloud Designer doesn't. Templates lock when someone is working in them, and unlocking requires the right permissions through the Asset Manager. Open a published template that already has a draft in progress and the system tells you, then asks whether you want to discard that draft, create a new version, or carry on with it. Publishing requires a reason, which is written to the audit trail and attached to the version it replaces.

Live preview only renders when the template is actively linked to a form definition and a project brief, which means what you see is the real artwork with real data, not a mockup that might be a version behind.

Governance that comes as standard


What This Actually Means For Your Business

In the long-run, this means fewer templates to maintain, faster variant creation, and artwork that can't drift away from approved content. Pharmaceutical and medical device teams get language variants and regulatory content driven from a controlled source rather than retyped. Cosmetics and FMCG teams can launch a flavor or a market extension without a full design cycle. Chemical teams get hazard content and transport symbols pulling from the same data everyone else is working from.

Cloud Designer is a tool that rewards by connecting your data end to end and simplifying your label and artwork management dramatically all in the name of better oversight, better efficiency, and better accuracy.

If your team is currently maintaining a folder of near-identical files, there's a better version of this available. Speak to our labeling and artwork experts by filling in a form here, or book a demo here.
 

Read our free guide on getting AI-ready

Learn how Kallik works
 

FAQs on Cloud Designer

What is Cloud Designer? 

Cloud Designer is the template design environment inside Veraciti™. Users build label and packaging templates from text, image, table, and barcode containers, then link those containers to data held in Veraciti so that a single template can generate many different labels.

How does Cloud Designer separate design from content? 

Containers on the template are tagged to a form definition, which maps data fields to the elements on the artwork. When a template is linked to a project brief, the containers populate with the approved content for that job. The design controls layout and brand, and the data controls what the label says.

Can one template produce multiple label variants? 

Yes. Multiple color tables support variant families such as different flavors or market schemes, and templates can be duplicated and modified at the die line or background layer to cover pack size and imagery changes without rebuilding the content structure.

How are barcodes handled in Cloud Designer? 

Barcodes sit in their own container type and link to the requirements defined in the project brief rather than being hardcoded into the template. A single configured container can carry expiry dates, lot numbers, and market-specific requirements, with the white space needed to keep the code scannable.

Does Cloud Designer keep an audit trail? 

Publishing a template requires the user to enter a reason, which is recorded in the audit trail against the version it supersedes. Templates also lock while in use, and the system flags existing drafts before a published template is reopened, so version history stays intact.