Practical guides · Practical guide

How to select an ERP system for pharma or medical devices

During an ERP demo, try assigning a blocked batch to a shipment. Which system enforces the hold? Who can change it, after which decision, and what record remains? Scenarios like this let you compare offers against your operation and expose the integration, validation and ongoing support work still to be done.

Table of contents

At a glance

What should suppliers demonstrate before you shortlist an ERP system?

Define the material, inventory and distribution decisions your operation actually makes. Pharmaceutical and medical device manufacturers may have different requirements for the same-looking transaction. Give each supplier the same demo scenarios and scoring criteria. Record the edition shown, how the required data moves through it, what evidence is available and which controls your team or implementation partner must provide.

  • For each process, identify the system that holds the authoritative record and the status used for the decision.
  • Distinguish the demonstrated functions, the supplier's version-specific evidence and the tests still open.
  • Follow failures through to the affected warehouse, shipping or quality process.

Which processes should the ERP cover?

Start with goods receipt, batch use or traceability after delivery. Map where data originate and which role makes each decision. Identify the system of record at each step. For example, the QMS may determine the quality status, the ERP may display it and the warehouse system may enforce it when material is picked.

Include the supply chain management (SCM) systems you use. If the ERP holds the authoritative batch status and a warehouse management system enforces the picking block, check the transfer and what happens at the storage location. For planning and transport systems, identify which information triggers a decision.

EU GMP Annex 11 addresses computerised systems used in GMP-regulated activities. Article 10(9) of the EU MDR sets quality management system requirements for the medical device manufacturers it covers. These include verifying UDI assignments for relevant products. Describe whether the ERP captures, transfers or uses those data. Assess the requirements separately for each relevant market and product type.

Two intended uses to consider in the same ERP selection
Intended useExample of a critical processDefine before the demo
Human medicinal products A batch blocked by quality control remains blocked for the warehouse or shipment in question. Identify the decision, the supporting data and each point at which the block must act.
Medical devices under the EU MDR A device or packaging record reaches the relevant systems with the intended UDI assignment. Identify products, packaging levels, fields and roles responsible for assignment, verification and any required reporting.

Sources: [1] [2]

Further reading:

A vendor-neutral matrix for comparing ERP proposals

Set mandatory criteria before scoring offers. Record the edition, modules, add-on products and deployment model in each proposal. Define the evidence expected for every criterion. Assess the demo against the agreed result and check separately which supplier records apply to the offered version.

Compare costs over the same period. Include licences, implementation, internal work, migration, testing, operations, updates and data handover. Assign an owner to every unresolved mandatory criterion. If a vendor proposes an alternative control, agree its expected effect and test it against the intended process before selection.

ERP selection criteria and the evidence to request
CriterionAsk the supplier to demonstrateClarify in the proposal and contract
Batches, serial numbers and UDI Trace a representative record forwards and backwards. Introduce an incorrect assignment and show how it is detected and resolved. Which fields, relationships and packaging levels are included?
Quality status and release Attempt to use a blocked stock item. Show a permitted status change, the responsible role and the resulting record. Which system makes the decision, which system enforces it and who checks the handover?
Roles, changes and signatures Demonstrate denied and permitted access. Show the relevant change history and the link between a signature and its record. Which roles or controls need configuration, add-ons or a procedure outside the ERP?
Interface and error handling Interrupt a status message, resend it and reconcile the business outcome in the target system. Who detects a disruption, authorises the interim arrangement and closes the finding?
Migration and access to data Find and read related records after an export or test import. Which histories, attachments and references move with the data? Which remain accessible elsewhere?
Validation and operations Show a sample test record with its version, criteria, result and open findings. Who provides documentation, test access and change information? What does your team need to do?

Sources: [1] [2]

Four ERP demo cases to run with every supplier

Define the decision-maker, authoritative status and condition for the next step in your test data. Give every vendor the same business starting conditions. Document which version was shown and how it differs from the offer.

ERP demo scenarios with failure paths, expected outcomes and evidence
Test caseActionExpected evidence in the example
E01 · Blocked stock Block item B-0403. With the dispatch role, try to assign it and then attempt an unauthorised unblock. Have the responsible role make the decision after a documented test finding. The block acts at the point of use before the authorised decision. The subsequent change can be traced to the role, decision and item.
E02 · Batch or device assignment For pharma, use two batches with similar names. For medical devices, trace a device identifier to the relevant lot or serial number. Deliberately swap an assignment in each case. Reconciliation detects the incorrect relationship despite matching record counts. Reviewers can trace the correct record and its use in source and target.
E03 · Interruption and repeat delivery Interrupt the blocking message, then deliver it twice. Compare the record in the system of record and the system that acts on it. The error is visible and the interim control works. After reconciliation the target status is correct. In this example, repeat delivery has no duplicate effect.
E04 · Export for review Make a permitted correction and give the reason. Export the transaction with its status history, related records and signature link where applicable, then read the export. The record ID, role, time and evidence reference preserve the relationships. Record recovery and archive access questions separately.

Sources: [1] [2]

Which decision in your ERP project needs evidence next? Describe the workflow in your enquiry.

Ask about ERP selection

From a demo result to a comparable proposal

For each criterion, record what you observed, the evidence reference and the remaining question. A feature in the demonstration system may depend on a configured role or an integration. Obtain written confirmation of which features and evidence the offer includes and any differences from the demo.

Rate mandatory criteria as demonstrated, open or failed. Demonstrated means the agreed outcome was seen and evidenced in the version shown. Open means evidence is missing or a difference between demo and offer remains unresolved. Failed means the process did not meet the agreed outcome. Decide before the demos which open issues must be resolved before selection.

Assign the remaining checks. Documented supplier observations can inform your work. Base the decision to use the ERP on your own requirements, actual configuration and evidence assessed for that use.

Example comparison of two proposals, A and B, in test case E01
Mandatory criterionProposal AProposal B
The warehouse enforces the block before dispatch. Demonstrated. The warehouse rejects the assignment. Demo record E01-A identifies the transaction and system version. Open. The ERP rejects the assignment. The proposal puts the warehouse adapter in the next project phase, outside the demo.
The dispatch role cannot remove the block. Failed. The demo role can change the block through an import. Ask the supplier to repeat that failure case after correcting the configuration. Demonstrated. The import is rejected and the status remains unchanged. Demo record E01-B identifies the role, attempt and result.

Both proposals remain open for selection. For A, ask the supplier to repeat the corrected import using the dispatch role. For B, request a test with the planned warehouse adapter. You can then assess both proposals against the same mandatory criteria.

Sources: [1]

Further reading:

Questions about ERP selection

How do we compare SAP, Business Central and industry-specific ERP systems?

Compare the offered modules, extensions and roles using the same workflow. Ask each supplier to connect the observed process, system version and evidence. Decide which controls belong in the ERP and which belong in connected systems.

What validation evidence should suppliers provide?

Request a version-specific example showing the requirement, expected result, actual result and open findings. Ask which documents your team can review or reuse after a change. Compare them with your requirements and record any checks still needed.

Sources: [1]

Does every ERP need an electronic signature?

The need depends on the process and applicable requirements. Where electronic signatures are intended, identify the record to be signed, who may sign it and how the link is preserved. A signature field in a demo answers these questions only for the workflow shown.

Sources: [1]

Sources and review date

Sources were checked on 10 November 2026. The examples address selected use cases in EU GMP for human medicinal products and in medical devices under the EU MDR. We developed the evaluation matrix and demo cases.

  1. European Commission, EU GMP Annex 11, January 2011 revisionPrinciple and sections 1 and 3–5 address use, risks, suppliers, validation and data exchange. Sections 7–9, 12, 14 and 17 address records, change history, access, signatures and archiving.
  2. EUR-Lex, Regulation (EU) 2017/745 on medical devicesConsolidated text of 19 July 2026. Article 10(9), particularly point (h), and Article 27 concern manufacturers' responsibilities for assigning and verifying UDI for relevant devices.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Discuss your ERP selection and validation scope

Tell us where you are in your ERP selection and which workflow you want to test in a demonstration. We will reply by email.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Ask about ERP selection Customer testimonials →