Executive Summary
The boundary is a design decision
Most manufacturers running a quality system and an ERP side by side eventually hit the same conflict, and it tends to surface around a single lot. NetSuite shows the lot available to ship while the quality system still has it on hold, or the other way around. Each record is internally consistent. They just disagree with each other, and when an auditor asks which one governs, that is not always easy to answer.
MasterControl and NetSuite are both capable products, and the problems that come up are usually confined to one narrow area: the disposition and status of material.
Drug and device manufacturing need separate treatment, because the regulations pull the dividing line to different places, and an answer that works for a biologic will not necessarily work for a device. They are different objects under different rules, and a design that fits one can fail the other. Through all of it, one rule holds: each regulated decision needs one authoritative owner, and the other system stores, displays, references, or enforces the approved result rather than originating a competing version of it.
What each system owns
Most of these problems trace back to one system being asked to do the other's job.
MasterControl is a quality and manufacturing execution system. On the quality side it handles document control, training, change control, and CAPA. On the manufacturing side it runs electronic batch and production records and review by exception. What it holds is the quality state of material and the evidence behind it: whether a procedure is on its effective revision, whether an operator is trained, whether a batch was built to the approved recipe, and whether a lot has been released, held, or rejected. The decision itself is made by the authorized Quality Unit. MasterControl is the system where that decision, its supporting evidence, workflow, approvals, and electronic signatures are recorded.
NetSuite is the system of record for the business. It carries commercial item identity, units of measure, inventory locations, on-hand quantity by location and bin, lot and serial identity, expiry dates, cost and valuation, planning and costing bills of material, purchasing, work order demand, and the financial consequence of every material movement. When a lot is consumed, NetSuite is where inventory decrements and where the cost lands.
Master data ownership is itself part of the boundary. NetSuite usually owns commercial item identity, units of measure, locations, planning and costing BOMs, purchasing parameters, work order demand, and costing. MasterControl usually owns the controlled master production record or recipe, effective work instructions and process parameters, quality specifications and required data collections, batch and production record templates, and the workflows, approvals, training, and electronic signatures around them. Shared identifiers, revisions, and effective dates are synchronized under change control. A NetSuite planning or costing BOM is not automatically the same object as a controlled MasterControl recipe, and the exact split has to be documented for each implementation.
The split runs between quality state and business record. The Quality Unit decides whether material is fit to use and MasterControl records it; NetSuite tracks where the material is, how much there is, what it costs, and whether it can be committed to an order. Push either system into the other's territory and the result is higher cost and a weaker audit trail.
Auditors do not ask how elegant the integration is. They ask which system owns the release decision, and whether the other one ever disagrees with it.
The contested middle: disposition and status
Both systems can act in this space, which is why it needs discipline.
NetSuite has real quality capability. With the Inventory Status feature, statuses such as Available, Quarantine, Inspection, or Damaged are applied to inventory quantity through inventory detail, associated with the item, lot or serial number, location, bin, status, and quantity. A single lot can hold quantity under more than one status at once, and each status carries a setting that decides whether the affected quantity is available for allocation. The NetSuite Quality Management SuiteApp can run incoming inspection and record a disposition that moves quantity from an unavailable status to an available one. On the other side, MasterControl can be configured, through validated integration and execution rules, to verify material identity, authorized quantity, current status, expiry, and work order authorization at the point of use.
So both systems can touch disposition and status. If they both originate the release decision, you end up with 2 records of the same decision that drift apart over time. What breaks then is the evidence trail, and you cannot demonstrate a clean chain of custody when 2 systems each believe they own disposition.
The way to prevent this is straightforward, even if teams break it all the time. Pick where the release decision is actually made, make that the system of record for the decision, and have the other consume and enforce the approved result.
For most regulated drug manufacturers, the decision sits with the Quality Unit, because that is where the specification, the test result, and the approval signature already live. The Quality Unit approves the disposition in MasterControl, and the approved outcome updates NetSuite Inventory Status for the affected quantity. NetSuite keeps quantity, location, and cost, and does not remake the verdict.
Where this goes wrong: When 2 systems both originate a lot's release, neither can stand as the record of truth. The fix is organizational before it is technical: name the system that owns the decision, and have the other enforce the approved result.
Some manufacturers run incoming inspection and its disposition inside the NetSuite Quality Management SuiteApp instead. In that case NetSuite owns that decision, and MasterControl still verifies and enforces the current authoritative status when material is presented at the point of use. It does not independently remake the release decision. Either arrangement works. Splitting the same decision across both systems does not.
Inventory status attaches to quantity, not to the whole lot, so a lot can sit partly available and partly on hold. Unavailable status removes that quantity from allocation. Stopping a physical pick or shipment is a separate, validated warehouse control.
Example — Inventory quantity by lot, location, bin, and status:
| Lot | Location | Bin | Qty | Status | Allocatable |
|---|---|---|---|---|---|
| LOT-24815 | Bldg A | A-01 | 30 L | Available | Yes |
| LOT-24815 | Bldg A | QA-HOLD | 10 L | Quarantine | No |
| LOT-24820 | Bldg A | A-04 | 8,000 ea | On hold | No |
Same lot, two statuses: 30 L allocatable, 10 L held. Status controls allocation; a validated warehouse control stops the physical pick.
Status summary: Available 128 (Allocatable) · Quarantine 14 (Blocked) · Inspection 6 (Blocked) · On hold 3 (Blocked) · Rejected 2 (Blocked)
The integration handshake
Underneath the product names, the exchange between an ERP and a quality and execution system comes down to five moves that repeat on most implementations. The sequence holds regardless of which system owns disposition.
01 — Plan and release work. NetSuite creates and schedules the work order and sends the item, planned quantity, location, required dates, and the approved planning BOM or revision reference, with a routing reference where applicable. The finished lot or serial number is normally assigned during execution or completion, not carried on the work order, unless the organization uses a validated preassignment design.
02 — Open the controlled record. MasterControl opens the applicable electronic batch or production record using the effective controlled recipe, work instructions, training requirements, process parameters, and quality data collections, referencing the NetSuite work order and the approved shared identifiers. The NetSuite planning BOM does not replace the controlled recipe.
03 — Verify and execute. MasterControl verifies each material lot or serial against what the work order authorized and against the authoritative NetSuite inventory information, including current status and expiry, then records execution, actual material use, yield, output, deviations, in-process results, and transactional genealogy. The authoritative status may originate in NetSuite or, where a disposition is assigned to the Quality Unit, in MasterControl.
04 — Post manufacturing results. Actual consumption, yield, production output, finished lot or serial identity, completion results, genealogy references, scrap, and variance post to NetSuite through the configured assembly build or WIP issue, completion, and close transactions. Inventory, WIP, cost, and production variances update according to the manufacturing and costing design, whether that uses recorded issues or approved backflush logic.
05 — Approve disposition and enforce it. The authorized Quality Unit approves release, hold, or reject in the designated system. The approved result updates NetSuite Inventory Status for the affected quantity, which removes held quantity from allocation. Validated warehouse and fulfillment controls prevent the physical pick and shipment, and a confirmation posts back through the integration for reconciliation and the audit record.
The connection itself is a validated GxP interface. Its data flows, transformations, exception handling, reconciliation, security, audit trails, and change control belong in a documented, risk-based validation scope. That does not mean every field gets its own qualification document. The transport, whether native or through an integration platform, moves, monitors, reconciles, and records the exchange. It does not own work orders, inventory, recipes, disposition, genealogy, or cost, and it does not make regulated or business decisions.
Vertical 01: Drug Manufacturing, Including Biologics
Drug manufacturing in the United States runs under 21 CFR Parts 210 and 211, where the quality control unit holds the authority to approve or reject materials and finished product. Electronic records and electronic signatures that fall within the scope of 21 CFR Part 11 must meet its requirements along with the predicate rule. Applicable US drug establishments also register with FDA under 21 CFR Part 207. In Canada, drug GMP requirements sit in Part C, Division 2 of the Food and Drug Regulations, and a Drug Establishment Licence under Division 1A is required for specified regulated activities. The two regimes are close in intent but differ in detail, which matters if you sell into both markets.
For drug, the boundary leans toward the quality system holding more. Batch release is a formal quality act performed by the Quality Unit, and the batch record is the primary evidence. For a biologic that record is dense: in-process results, bioburden and endotoxin, potency, hold times, and stability commitments that can extend release conditions well past the point of manufacture.
Biologics put pressure on this in ways a small-molecule tablet does not. 3 areas come up most often.
Cold chain and excursions. A frozen biologic may carry rules neither system models cleanly out of the box: a limited number and duration of temperature excursions, and a shelf life that changes with the storage path a container took. That logic belongs in the quality record, which owns the excursion evaluation and conditional dating. NetSuite then carries the current approved effective date at the applicable inventory tracking level. For ordinary lot controlled inventory that date is held at the lot level; dating an individual vial differently requires serial tracking, sublots, separate inventory numbers, or a validated container level design.
Potency-based inventory. A biologic is often managed by activity rather than by count alone, so the unit of inventory in NetSuite and the unit of quality judgment have to agree from the start.
Biological source material. Supplier qualification, quality specifications, test results, and disposition are quality-owned. Transactional genealogy, the lot and serial relationships built through issues, work order execution, and completions, is generated across the ERP and MES records, and the authoritative source for each element has to be defined and reconciled across the interface.
Two regimes, satisfy both: If you release drug product for both the US and Canada, design each control to satisfy all applicable requirements. Harmonize common controls to the more demanding requirement where practical, and keep jurisdiction specific controls where they differ, such as US establishment registration under Part 207 and the Canadian Drug Establishment Licence under Division 1A.
For computerized systems, Canada's closest comparison to Part 11 is Annex 11 to the GMP guide, Computerized Systems (GUI-0050).
What to watch: A plain date field in NetSuite looks like enough until the first excursion. Decide early that the quality system owns the excursion evaluation and conditional dating logic, and that NetSuite carries the current approved effective date at the tracking level the product actually uses.
Vertical 02: Medical Device Manufacturing
Device manufacturing changed underneath the industry this year, and the boundary moved with it. As of February 2, 2026, the FDA's Quality System Regulation became the Quality Management System Regulation, and 21 CFR Part 820 now incorporates ISO 13485:2016 by reference. The US device quality baseline is now the same standard most of the world already used, with FDA-specific additions layered on top. For a manufacturer that already ran an ISO 13485 system, the shift is modest. For one that ran only to the old US regulation, it means real work to close the gap.
In Canada, medical devices run under the Canadian Medical Devices Regulations, and Health Canada relies on the Medical Device Single Audit Program, an audit built on ISO 13485, for the classes where it applies. So for a device maker selling into both countries, ISO 13485 is the shared spine on both sides of the border.
The device boundary sits differently than the drug boundary. Device records are organized around the production and acceptance records for each device or batch, often handled in electronic manufacturing systems as the electronic device history record, or eDHR, with the design and risk files behind the product. Traceability may be maintained by lot or by serial number, and the unique device identifier links to it: the device identifier portion of the UDI identifies the labeler and the device version or model, while the production identifier portion may carry the lot or batch, serial number, expiration, or manufacture date. A UDI is not, by itself, a unit level serial number. Where a drug batch posts a lot and a quantity, a device build may need to associate serialized units, a sterilization lot, and the applicable UDI elements, and keep the as-built record aligned with what NetSuite shows as finished and shippable.
Risk is explicit in the regulation now, and that carries directly into the boundary. Under the QMSR, a nonconformance or a complaint is more than something to document. It feeds a risk-based decision that can hold or release inventory, and that decision belongs to the quality system. NetSuite's job is to keep held units from being committed or shipped while the decision is open, which comes back to the same ownership rule.
What to watch: Serialization and identifier mismatch. If the quality system and the ERP disagree about which serial numbers exist in a build, you get a traceability gap, and it tends to surface during a field action rather than before one. Agree on the serialization master and the identifier format before the first unit is built, not after.
The Manufacturer That Makes Both
Some companies live on both sides of this line at once. Take a manufacturer, described here only in the abstract, that produces a biologic drug together with the delivery device used to administer it. This is a common enough shape in therapeutics now. It gets complicated because one company is suddenly running 2 quality regimes through what it wants to be a single set of systems, each regime with its own record structure and its own release decision.
The instinct is to make the two look alike so the integration is simpler, and that is the wrong move. A biologic batch and a device build are not the same object, and forcing one to imitate the other corrupts both records. What each side needs looks quite different.
Biologic drug side:
- Governs to 21 CFR 210 and 211, Part 11 where in scope, and Health Canada Division 2 GMP.
- Traceability at the lot level, with the batch record as primary evidence.
- Watch conditional expiry, excursion limits, and potency as the inventory unit.
Delivery device side:
- Governs to the QMSR and ISO 13485:2016, with MDSAP for Canada.
- Traceability by lot or serial, with the production and acceptance record and linked UDI.
- Watch serialization masters, sterilization lots, and risk-driven holds.
A combination product, where the drug and device ship as one, adds another layer. It must satisfy the applicable manufacturing requirements for each constituent part, which 21 CFR Part 4 allows to be met through a streamlined operating system rather than two full parallel systems. The electronic record architecture can use separate or integrated templates, as long as the applicable requirements, approvals, and linkages are demonstrated; that is a system design choice, not a regulatory mandate. Either way, NetSuite stays the neutral ledger for both, holding quantity, location, cost, and a status that reflects whatever the responsible quality system decided.
What to watch: Do not average the two regimes into one compromise process. You end up under-controlling the biologic and over-documenting the device, and neither team trusts the result. Treat them as 2 boundaries that happen to share one ledger.
Getting the Boundary Right
5 principles hold across both verticals, whichever system ends up owning a given decision.
01 — One owner per decision. For any fact both systems could hold, name the authority and let the other store, display, or enforce the approved result. Disposition, dating, serialization, and cost each get a single home.
02 — Decisions move one way. The authorized owner makes the call and writes the result to the other system. When authority runs in both directions over the same field, audits tend to find it.
03 — Keep the ledger neutral. NetSuite tracks quantity, location, cost, and status, and stays out of the reasoning behind them. Vertical-specific quality logic belongs in the quality layer.
04 — Validate the interface, not just the systems on either end. The integration and its GxP-relevant data flows, transformations, calculations, exception handling, reconciliation, security, audit trails, and change control belong in a documented, risk-based validation scope.
05 — Satisfy every applicable jurisdiction. If you operate under both FDA and Health Canada, harmonize common controls to the more demanding requirement where practical, and keep jurisdiction specific controls where the requirements differ.
Where Archer Fits
The NetSuite side of the boundary
Archer Insights implements NetSuite for health and life sciences organizations, and only for them. That focus puts this problem in front of us on most engagements. We build the NetSuite side, the item and lot structure, the inventory statuses, the work order and costing model, and the integration into the quality system, so it holds up when an auditor tests it.
We are not a MasterControl implementer, and nothing here pretends otherwise. What we work from is how a quality and manufacturing execution system like MasterControl behaves according to its published documentation, along with NetSuite expertise and the regulatory context on both sides of the US and Canada border. Our part is the NetSuite environment and the design of the interface into it.
Talk to Archer about your NetSuite and integration architecture
If your organization runs NetSuite, or is planning to, alongside MasterControl or a comparable quality system, a few questions decide how well the boundary holds: which system owns disposition, how dating and serialization are handled, and how the interface gets validated. Those are worth settling early. Reach us at info@archerinsights.com or +1 (610) 614-9511.
Product capabilities described for MasterControl and NetSuite are drawn from each vendor's published documentation and depend on licensing, configuration, and validated implementation. This is general guidance, not regulatory or legal advice.