
Scope your MSV3 integration project
We clarify your role as a pharmacy, wholesaler or manufacturer and identify the systems that own products, customers, prices and available stock. For SAP, Microsoft Dynamics or another ERP, we assess available connections and agree the integration scope before implementation.
- ERP, pharmacy system, WMS and existing interfaces
- Product and customer rules, messages and responses
- Order volumes, pilot partners and support requirements

Deliverables and next steps
The proposal separates setup, mapping, testing, onboarding and ongoing operation. Acceptance criteria cover rejection, partial fulfilment, retries and error handling. Scheduling also accounts for configuration and approval by the participating pharmacy-system providers.
Server, gateway, ERP integration and operation. MSV3 integration for German pharmacies →

MSV3.tiger and pharmabuyer.TIGER: both sides of procurement
MSV3.tiger connects supplier order intake to operational systems. pharmabuyer.TIGER supports recurring PZN searches and rule-based purchasing. They structure enquiry, decision, order and response, and can also be used independently.
- Supplier: receive pharmacy orders from existing pharmacy software
- Buyer: query approved suppliers by PZN, quantity and availability
- Shared foundation: clear customer accounts, current data and documented rules

Understanding MSV3 version 1, version 2 and MSV3 plus
The MSV3 name alone does not establish compatibility. Pharmacy software, supplier and provider must support the agreed version and functions. MSV3 plus requires separate assessment for manufacturer and hospital supply. Naming a software vendor is not evidence of a tested installation.
- Record version, endpoint and required functions before implementation
- Maintain a compatibility matrix with system version, test date and acceptance status
- Confirm delivery notices, returns and accompanying documents for each procedure and partner

An MSV3 availability enquiry is not an order
A positive PZN enquiry describes the queried supplier’s response at that moment. It does not in itself reserve stock. Inventory, allocations and customer permissions may change before ordering. Requested, confirmed and delivered quantities therefore need separate evaluation.
- Keep the supplier, timestamp and PZN with every response
- Distinguish general availability from confirmed quantity and delivery date
- Recheck shortages and account for outstanding orders

Separate MSV3 functions from additional data integrations
A project function matrix identifies the messages actually supported by the endpoint, the information supplied by ERP or pharmacy software and the downstream processes requiring another interface. This makes data transport and commercial decisions traceable.

Application scenario: digital ordering for a specialist wholesaler
Illustrative project model, not a customer reference: a specialist wholesaler wants to reduce telephone orders. Define customer accounts, PZN assortment and stock sources, then test pilot pharmacies and error cases and reconcile initial orders through dispatch. Performance claims require measured results.
- Starting point: manual entry and follow-up calls
- Project: gateway, system integration and pharmacy onboarding
- Evidence: compare processing effort, error rate and adoption

Ordering from the familiar pharmacy system
Pharmacists and purchasing teams remain in their existing system. Product enquiries, orders and responses use the established MSV3 workflow without requiring another shop portal or login.
- Direct MSV3 order intake from pharmacy systems
- Integration into existing purchasing workflows
- Suitable for pharmacies and pharmacy groups across the DACH market
- Industry-standard connectivity for ADG, PHARMATECHNIK, Awinta and CGM

White label, pricing and commercial terms
The gateway can operate under your brand. Prices, current offers, customer-specific terms and available quantities are passed from the connected systems into the ordering process.
- White-label presence for direct suppliers
- Customer-specific prices and terms
- Rules for offers, quotas and allocations
- PZN-based assortment and customer mapping

Availability and order response
During ordering, the pharmacy receives a structured response on availability, quantity and expected lead time. Where data and rules permit, suitable alternative PZNs can be offered during shortages.
- Availability and inventory enquiries
- Lead-time and quantity responses
- Rule-based alternatives when stock is unavailable
- Status and error messages for clear follow-up

ERP, WMS and managed operation
The MSV3 gateway connects to an ERP, merchandise system or WMS and is accepted against controlled test cases. Logging, validation and ongoing interface maintenance support traceable operation in a GxP/GDP-influenced environment.
- ERP integration, including SAP scenarios
- WMS, warehouse and order integration
- Logging and validation of data exchange
- Monitoring, maintenance and a scalable managed service

Use by pharmacy groups
Groups can pool order volume without disrupting members’ familiar workflows. Central terms, quotas and assortments can be managed and evaluated through the group server.
- Central purchasing campaigns in member systems
- Consolidated ordering volume
- Management of terms and quotas
- Visibility into usage and order status

Use by hospital, practice and specialist suppliers
Documented data transfer supports hospital and practice-supply processes. Specialist wholesalers can establish imports, temperature-controlled products and high-cost therapies as a permanent digital ordering route.
- Traceable handover for hospital and practice supply
- Direct ordering from specialist and niche providers
- Selected cold-chain, import and high-cost portfolios
- Integration with existing delivery and quality processes

Assess your MSV3 project
For an initial assessment, describe your role as supplier, pharmacy or network, your software and your objective. A technical discussion then defines the interface scope, implementation effort and an appropriate demonstration or pilot.
- Assess an MSV3 connection: identify systems, assortment and target pharmacies
- Request a white-label demo: describe brand, membership and functions
- Automate PZN purchasing: outline search effort, suppliers and approval rules