Fragmented Supplier Visibility Unified with ERP and QMS Integrated Portal for GMP-Compliant Pharma Contract Manufacturing

Overview

A pharmaceutical brand relied on contract manufacturers and labs but had little real-time visibility into work-in-process and quality status. Schedules slipped, shipments arrived with surprises, and receiving teams discovered issues late. Intelligex implemented a secure supplier portal that integrated with the brand’s Enterprise Resource Planning (ERP) and Quality Management System (QMS) to capture lot progress, test results, certificates, and deviations under governed access. Operations gained a reliable view of outsourced production, enabling earlier decisions, cleaner receipts, and fewer rounds of rework or quarantine.

Client Profile

• Industry: Pharmaceuticals (drug product and packaging, outsourced to contract manufacturers)
• Company size (range): Mid-market brand with multiple Contract Manufacturing Organizations (CMOs) and Contract Labs (CROs)
• Stage: Established ERP and QMS; limited supplier visibility via email and spreadsheets
• Department owner: Operations & Manufacturing
• Other stakeholders: External Manufacturing, Quality Assurance (QA), Regulatory Affairs, Supply Chain, Procurement, IT/Security, Receiving/Warehouse

The Challenge

Outsourced batches progressed through compounding, filling, packaging, and testing without a unified view for the brand. Updates arrived through emails and attachments with varied formats. QA could not see the status of deviations or investigations until late, and Operations learned about delays only after planned deliveries shifted. Receiving teams opened pallets to find missing Certificates of Analysis (CoAs), unexpected label variants, or open deviations that put lots on hold.

The brand’s ERP held purchase orders, planned receipts, and lot numbers. The QMS tracked quality agreements, deviations, and change controls. CMOs used their own systems for execution and labs used their own Laboratory Information Management System (LIMS). None of these tools shared a consistent model for lots, stages, and release readiness. Without early WIP signals, planners carried buffer assumptions that masked risk until it became a scramble.

Constraints were significant. The brand could not mandate that CMOs adopt its internal systems or expose its internal networks. Each partner had different digital maturity and preferred to work through simple, secure interfaces. Any solution had to respect data ownership defined in quality agreements, align with current good manufacturing practice (cGMP) requirements in 21 CFR Part 211, and follow the spirit of FDA guidance on quality agreements for contract manufacturing arrangements: FDA Quality Agreements. The solution also needed to fit within existing validation and change control expectations.

Why It Was Happening

Root causes centered on fragmentation and inconsistent identifiers. CMOs ran their own Manufacturing Execution System (MES) and scheduling tools; labs ran LIMS with their own sample identifiers. Lot numbers and milestones did not align cleanly with the brand’s ERP references. Information traveled by email, and attachments were saved to shared drives without a consistent structure or audit trail. When someone asked “What is the status of Lot X?” the answer depended on who last touched a spreadsheet.

Ownership of visibility was unclear. The quality agreement defined responsibilities for manufacturing and release, but there was no operational mechanism to show stage gates, exceptions, and release prerequisites in one place. Deviations opened at the CMO took time to surface; test failures were shared as PDFs without structured data; and document packages arrived piecemeal. Without a governed, shared channel, surprises were the norm.

The Solution

Intelligex implemented a secure supplier portal that sat alongside the brand’s ERP and QMS. CMOs and labs submitted structured updates and attachments tied to the brand’s lot identifiers, or connected through lightweight APIs. The portal normalized naming, tracked progress through defined stage gates, and synchronized quality events with the brand’s QMS. Role-based access limited each partner to only their scope, and the brand’s teams saw a single, governed view of outsourced WIP, test status, deviations, and readiness for release.

• Integrations: Two-way integration with ERP platforms such as SAP or Oracle for purchase orders, lot numbers, and planned receipts; and with QMS platforms such as ETQ Reliance, MasterControl, or TrackWise for deviations, change controls, and final release records. Optional pull of lab results from partner LIMS via secure file exchange or API.
• Canonical data model: Cross-referenced brand lot IDs with CMO batch IDs and LIMS sample IDs. Standardized stage definitions (e.g., compounding complete, fill complete, packaging, testing, QA review) and quality states (e.g., open deviation, disposition pending, released).
• Submission workflows: Guided forms for CMOs and labs with validations, required fields, and attachment types (CoAs, packaging records, test reports). Support for bulk upload and API submissions for partners with higher digital maturity.
• Deviations and quality events: Synced deviation headers and status from partner input to the brand’s QMS with controlled fields. Linked CAPA numbers when applicable and routed brand approvals according to the quality agreement.
• Readiness gates: Calculated lot readiness based on stage completion, required documents, and quality dispositions. Flagged gaps like missing CoAs, open deviations, or label approvals not yet synchronized.
• Notifications and alerts: Routed changes in status, late milestones, or blocked readiness to External Manufacturing and QA via Microsoft Teams or email, with links back to the portal record and source documents.
• Security and access: Role-based access by company, site, and product. Multifactor authentication for external users, least-privilege service accounts for integrations, and an immutable audit trail of submissions and decisions. Electronic signatures aligned to Part 11 expectations where required.
• Validation approach: Requirements traceability, risk-based testing, and change control aligned to ISPE GAMP 5 practices. Periodic review of configurations and partner access.

Implementation

• Discovery: Mapped the end-to-end outsourced process by product family. Cataloged lot identifiers across ERP, CMO batch systems, and LIMS. Reviewed quality agreements to confirm who submits what, when, and with which approvals. Identified typical gaps leading to receiving holds.
• Design: Defined the canonical lot model, stage gates, and submission templates. Aligned deviation and disposition fields with the brand’s QMS. Established role-based permissions and the escalation path when a readiness criterion failed.
• Build: Configured ERP and QMS connectors, built the portal workflows and validations, and set up secure SFTP/API endpoints for partners. Implemented cross-reference logic for lot, batch, and sample IDs. Stood up dashboards and alert channels for Operations, QA, and Receiving.
• Testing/QA: Executed risk-based tests for data integrity, access controls, and audit trails. Ran the portal in shadow mode with select CMOs, reconciling portal status to emailed updates and internal records. Included a human-in-the-loop review of early submissions before synchronization with the QMS.
• Rollout: Onboarded partners in waves, starting with sites that produced the highest volume or most variability. Kept email as a controlled fallback during the first cycles. No changes were required to partner MES; submissions used the portal forms or simple file/API interfaces.
• Training/hand-off: Delivered short training for CMO coordinators and lab contacts, plus role-based sessions for External Manufacturing, QA, and Receiving. Updated the quality agreement appendices to reflect portal use, data fields, and response expectations.

Results

Operations gained early visibility into milestone progress and blockers. Lots with missing documents or open deviations were flagged before trucks were scheduled, allowing plans to adjust rather than react. Receiving saw fewer pallets moved to quarantine for paperwork or labeling gaps, and QA had a single record tying test results, deviations, and approvals to the lot. When issues surfaced, the team could point to a consistent trail rather than reconstructing events from scattered emails.

Suppliers appreciated a clear submission path and fewer ad hoc requests. The portal reduced back-and-forth for routine updates and set expectations for what constitutes a release-ready lot. Internally, leaders saw steadier schedules and fewer last-minute expediting moves caused by unseen delays at partners. Audits were more predictable because records lived in governed systems with full traceability to source documents and approvals.

What Changed for the Team

• Before: Status lived in inboxes and spreadsheets. After: A single portal showed lot stage, documents, and quality status in real time.
• Before: Receiving discovered missing CoAs at the dock. After: Readiness gates flagged documentation gaps before shipment was booked.
• Before: Deviations at CMOs surfaced late. After: Deviation headers and status synchronized to the brand’s QMS with clear routing.
• Before: Lot and sample IDs did not align across systems. After: Cross-references linked ERP lots, CMO batches, and LIMS samples.
• Before: Partners sent updates in many formats. After: Guided forms, templates, or APIs standardized submissions and evidence.
• Before: Audit trails had to be reconstructed. After: Submissions, decisions, and signatures were captured with immutable logs.

Key Takeaways

• Do not force partners onto your internal systems; provide a secure, governed portal that integrates with ERP and QMS and meets quality agreement obligations.
• Normalize lot, batch, and sample identifiers so updates, test results, and deviations align without manual reconciliation.
• Use stage gates and readiness rules to catch missing documents or open quality events before shipment, not at receiving.
• Keep humans in the loop for exceptions and quality decisions; automate the routine and route the ambiguous.
• Design for validation and auditability from the start; clear traceability and controlled access make inspections predictable.
• Onboard partners in waves, starting where visibility gaps cause the most disruption, and keep a controlled fallback during early cycles.

FAQ

What tools did this integrate with? The portal connected to the brand’s ERP (for example, SAP or Oracle) for purchase orders, lots, and receipts, and to the QMS (such as ETQ Reliance, MasterControl, or TrackWise) for deviations, dispositions, and release records. Where possible, lab results were ingested from partner LIMS via secure file or API. Notifications surfaced through Microsoft Teams or email, and dashboards were provided for Operations, QA, and Receiving.

How did you handle quality control and governance? The portal enforced required fields, document types, and validations aligned with cGMP expectations in 21 CFR Part 211. Deviations synchronized to the QMS with role-based approvals and audit trails. Electronic signatures were applied where required, and the system was validated using a risk-based approach consistent with GAMP 5. Access and changes followed existing change control procedures.

How did you roll this out without disruption? The team piloted with a small set of CMOs and labs, running the portal in shadow mode against existing email-based updates. During early cycles, email remained an approved fallback. Partners were onboarded in waves using guided forms or simple integrations, and no partner had to change their MES. Internally, ERP and QMS integrations used approved interfaces, so core systems were not replaced.

How was data security and supplier access managed? External users accessed the portal with multifactor authentication and roles limited to their company, site, and assigned products. Data movement used least-privilege service accounts and encrypted channels. Every submission and decision carried an immutable audit log, and document access was governed by the quality agreement. The brand retained system-of-record control in ERP and QMS.

How did you reconcile lot and test data across different systems? A canonical model cross-referenced ERP lot IDs with CMO batch IDs and LIMS sample IDs. Submissions required at least one matching identifier, and the portal validated associations against open purchase orders and planned receipts. Test results and CoAs were linked to the correct lot automatically, reducing manual matching and late holds at receiving.