Make manufacturer products directly orderable in pharmacy systems

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

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

Direct ordering

Place the manufacturer in the pharmacy’s established procurement workflow.

• Order from the pharmacy system
• No separate portal for routine orders
• PZN-based product selection
• Quantity and availability response

Assortment and access

Expose only approved product, customer, territory and channel combinations.

• Validate PZN and sales status
• Qualify pharmacy and site
• Control assortments by customer group
• Enforce exclusions and regulatory limits

Prices and campaigns

Bring manufacturer-specific direct terms into the order.

• Customer prices and discounts
• Campaign and tier rules
• Minimum quantities and allocations
• Clear rule validity and priority

Fulfilment model

Connect direct supply, 3PL or wholesale fulfilment.

• Pass orders to ERP or fulfilment
• Define the GDP-suitable delivery route
• Return advice and status
• Assign returns and customer support

Pilot and scale

Start with selected products and pharmacies, then expand on evidence.

• Business case and target segment
• Pilot portfolio and test pharmacies
• Activation, use and repeat-order KPIs
• Phased range and reach expansion

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