Disconnected Packaging Artwork Process Unified with DAM, QMS, ERP, and MES Integration for Cosmetics Labeling Compliance

Overview

A cosmetics producer was routinely printing outdated packaging artwork because the Digital Asset Management (DAM), Quality Management System (QMS), and Enterprise Resource Planning (ERP) were not connected to the packaging floor. Operators pulled files from shared folders, approvals lived in email, and the Manufacturing Execution System (MES) had no way to verify which revision was loaded. Intelligex integrated DAM with QMS and ERP and added checkpoints in MES so only approved, effective artwork could be used. Misprints declined, change approvals became traceable, and packaging runs started with confidence that the right file was on press.

Client Profile

• Industry: Cosmetics and personal care
• Company size (range): Mid-market, multi-brand portfolio with in-house and co-pack operations
• Stage: Established ERP and QMS; DAM used by marketing; packaging lines relied on shared drives and local printer settings
• Department owner: Operations & Manufacturing
• Other stakeholders: Packaging Engineering, Quality Assurance, Regulatory Affairs, Marketing/Brand, IT/OT, External Packaging Vendors

The Challenge

Packaging artwork changes originated in marketing and regulatory, were approved in the QMS as controlled documents, and were stored in a DAM used by creative teams. On the floor, however, operators accessed a shared folder or a USB drive to retrieve print files. File names were similar across versions, effectivity dates were not visible at the station, and the QMS approval status did not follow the file to the printer. When regulations or claims changed, the new design often lagged behind the schedule, and a line could run packaging with old legal text or incorrect barcodes.

Artwork complexity amplified the risk. SKUs had language variants, regional compliance statements, ingredient disclosures, and promotional bursts. Some labels were printed on industrial printers using label design software, others were pre-press PDFs for cartons and inserts. The ERP’s bill of materials listed packaging part numbers, but did not enforce artwork revision. MES tracked production orders and lot numbers, yet it played no role in artwork validation. Rework and scrap followed preventable mistakes, and brand teams spent time explaining why the shelf did not match the approval.

Constraints ruled out a rip-and-replace. The organization had invested in its DAM, QMS, ERP, and MES. Print hardware and label design software were already deployed. The solution had to orchestrate the existing stack, add governance at the line, and handle both on-demand printing and pre-press workflows without slowing changeovers.

Why It Was Happening

The root causes were broken handoffs and unclear ownership at the last mile. Marketing owned artwork creation in the DAM, Quality owned approvals in the QMS, and Operations owned execution. None of those systems asserted control at the printer. The packaging bill of materials referenced box and label part numbers, but not the artwork file revision. Operators did their best to pick the right file, yet naming conventions, caching on local PCs, and rushed changeovers created room for error.

Standards existed but were not enforced in context. Barcodes followed GS1 rules, and regulatory text adhered to cosmetic labeling requirements, yet there was no mechanism to ensure the station used the approved, effective file for the current order. Approvals happened, but traceability to the printed output was thin, making it hard to prove compliance when questions arose. For background on barcode standards, see GS1 barcodes. Cosmetics labeling expectations are outlined in 21 CFR Part 701.

The Solution

Intelligex implemented an orchestration layer that connected DAM, QMS, ERP, and MES, and introduced release gates at packaging. The service synchronized approved artwork and associated metadata from the DAM/QMS, tied it to packaging components in ERP, and exposed a controlled catalog to the MES. Before a run, the MES required selection of the approved artwork for the order and verified effectivity, region, and language against the order’s attributes. For on-demand labels, the label print system pulled locked templates from the catalog. For pre-press, carton and insert PDFs were released to printers only through the controlled queue. Every print job carried a fingerprint and audit link back to the approved revision.

• Integrations: Connected DAM platforms such as Adobe Experience Manager Assets, Bynder, or Aprimo to QMS (e.g., ETQ Reliance, MasterControl) for approval status and version control. Linked ERP (SAP, Oracle, Microsoft Dynamics) for item masters, packaging BOMs, and effectivity. Integrated MES (Siemens Opcenter, Rockwell FactoryTalk ProductionCentre) for run gating. Connected label systems like Loftware/NiceLabel or BarTender for print enforcement.
• Artwork catalog and metadata: Built a canonical model that linked each SKU and pack component to approved artwork, with attributes for language, region, regulatory basis, effectivity windows, and superseded references. Stored color profiles, dielines, and bleed specs with each file.
• Release workflow: When QMS approved a change, the service created a release package that updated ERP component references and exposed the correct file to MES and print systems. Obsolete versions were retired from the production catalog but preserved for traceability.
• MES checkpoints: Added pre-run validations that ensured the selected artwork matched the order’s SKU, market, and effectivity. For label printing, MES handed order context to the label system and blocked use of local, uncontrolled templates.
• Print fingerprinting: Embedded a small, machine-readable identifier in labels and carton proofs that encoded the artwork revision. Vision systems or handheld scanners could verify a sample against the expected revision before releasing the run.
• Exception handling: Provided a controlled override path when urgent orders intersected with pending artwork changes, requiring Quality and Regulatory e-signatures and time-bound exceptions.
• Dashboards: Offered live views of upcoming effectivities, artwork availability by line, and open approvals. Production could see when a change might impact a scheduled run, and marketing could track where the new design was active.
• Security and permissions: Enforced least-privilege access and immutable audit logs. Operators saw only production-approved assets; creative-only drafts remained restricted to DAM users.
• Standards alignment: Validated barcode symbologies and quiet zones against GS1 rules and linked labeling content to regulatory references, including cosmetic labeling requirements. For general packaging and label control discipline, the team borrowed practices from packaging artwork governance used in consumer goods and life sciences. Many producers align manufacturing practices with ISO 22716 guidance for cosmetics GMP.

Implementation

• Discovery: Mapped artwork creation-to-press flow across marketing, regulatory, quality, and packaging. Inventoried print hardware, label software, and local file practices. Cataloged where misprints originated and how approvals were captured.
• Design: Defined the artwork catalog schema and cross-references to ERP items and BOMs. Established effectivity semantics, region and language attributes, and MES gating rules. Agreed on fingerprint format and sample verification points. Set exception paths and signatures.
• Build: Configured connectors to DAM, QMS, ERP, MES, and label systems. Built the release service to publish approved artwork to production catalogs and update ERP component references. Implemented MES pre-run checks and label system template locking. Enabled sample verification with scanners or existing vision systems.
• Testing/QA: Ran shadow cycles where packaging selected files through the new catalog while legacy access remained as fallback. Verified that orders blocked when artwork was missing or out of effectivity. Tested barcode and regulatory text checks on samples. Included a human-in-the-loop review for early overrides.
• Rollout: Enabled lines by product family, starting with high-volume SKUs and label-heavy packs. Retired shared drive access as lines stabilized. Worked with external printers to accept only portal-released pre-press files for cartons and inserts.
• Training/hand-off: Delivered short, role-based sessions for operators, packaging engineers, and quality reviewers. Updated SOPs for artwork selection and sample verification. Transferred ownership of metadata and effectivity rules to Packaging Engineering and Regulatory under change control.

Results

Packaging runs began with verified, approved artwork tied to the specific order. Operators chose from a controlled catalog inside MES, and on-demand labels printed from locked templates linked to the order context. Misprints and label holds decreased because outdated files could not reach printers, and sample verification caught mismatches before full runs. When changes went live, effectivity rules and ERP updates synchronized so the right pack components and artwork moved together.

Approvals and accountability became straightforward. Quality and Regulatory saw who released each change, when it took effect, and where it was running. Marketing trusted that brand updates reached shelves as intended. When auditors or customers asked for evidence, the team produced a clear trail from DAM approval through QMS record to the printer queue and sample verification. The floor spent less time reprinting and relabeling and more time meeting plan.

What Changed for the Team

• Before: Operators pulled files from shared folders. After: Operators selected approved artwork from a controlled catalog in MES.
• Before: Approvals lived in email and were hard to trace. After: QMS approvals and e-signatures linked directly to the released file.
• Before: Label templates drifted on local PCs. After: Label systems pulled locked templates with order context and effectivity checks.
• Before: Misprints surfaced during or after a run. After: Sample verification checked artwork revision before release.
• Before: ERP listed components without artwork control. After: ERP packaging BOMs referenced the approved artwork and effectivity through the release service.
• Before: Exceptions were informal. After: Overrides required reason codes and cross-functional approval with time-bound scope.

Key Takeaways

• Connect DAM, QMS, ERP, and MES so artwork approval and effectivity are enforced where printing happens.
• Publish a production-only artwork catalog; remove shared drives and local templates from the packaging workflow.
• Tie artwork to packaging BOMs and order attributes like region and language; prevent runs when metadata doesn’t match.
• Use label systems that pull controlled templates and embed a revision fingerprint for sample verification.
• Keep a governed exception path for urgent cases, with clear roles and e-signatures.
• You do not need to replace core systems; orchestration and gating create control with the tools you already have.

FAQ

What tools did this integrate with? The solution connected DAM platforms such as Adobe Experience Manager Assets, Bynder, or Aprimo; synchronized approvals and versions from QMS tools like ETQ Reliance or MasterControl; referenced items and packaging BOMs in ERP systems including SAP, Oracle, or Microsoft Dynamics; enforced pre-run checks in MES such as Siemens Opcenter or Rockwell FactoryTalk ProductionCentre; and locked label printing through Loftware/NiceLabel or BarTender. Vision systems or scanners verified sample fingerprints where available.

How did you handle quality control and governance? Artwork moved through QMS approvals and e-signatures, then was published as a controlled asset to the production catalog. MES required a match between order attributes and artwork metadata before release. Label systems used locked templates that could not be edited at the station. Every print job carried a traceable link to the approved revision, and exceptions required reason codes and cross-functional approval. Barcode and regulatory text checks aligned with GS1 and cosmetic labeling expectations.

How did you roll this out without disruption? The team piloted on a subset of lines and SKUs, running the new catalog and MES gates in shadow mode while keeping shared drive access as a controlled fallback. Once sample verification and gating behaved as intended, shared folders were retired for those lines and external printers were instructed to accept only portal-released files. Training was brief and focused on selection and verification, not on new systems.

How did you prevent outdated files from reaching printers? Only QMS-approved, effective files were published to the production catalog. The MES passed order context to the label system or pre-press queue, and the print service rejected any file not sourced from the catalog. Local folders and USB access were removed from the workflow. A small embedded identifier in the artwork allowed a quick scan to confirm the on-press file matched the approved revision.

How were regional variants and effectivity handled? Artwork metadata included region, language, regulatory basis, and effectivity windows. ERP packaging BOMs referenced the correct component and artwork pairing, and the release service updated both when changes were approved. MES matched the order’s attributes to the artwork and blocked selection of files outside effectivity or region. When a market-specific update was pending, a governed exception path allowed limited use with Regulatory and Quality sign-off.