Launch and operate MSV3 under the manufacturer brand

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 →

White-label MSV3 for pharmacy groups and cooperatives

A network can offer MSV3-based services under its own brand. Tenants, member pharmacies, supplier accounts and data permissions must remain distinct. Central purchasing campaigns need defined validity periods and clear responsibility for ordering and pharmaceutical suitability.

• Member-specific assortments, terms and allocations
• Onboarding, training and support as network services
• Purpose-limited reporting and authorised access
• Pilot with selected members before network rollout

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

Measuring MSV3 operations

Technical uptime and successful procurement are different measures. Service reporting should identify failed enquiries, unresolved orders and abandoned onboarding. Evaluate improvements against documented baselines.

• Median and 95th-percentile response time and technical error rate
• Accepted orders and unresolved transmissions
• Time to the first successful pharmacy order
• Support effort and manual processing per transaction

White-label presence

Align naming, communication and access with the manufacturer.

• Manufacturer-branded MSV3 access
• Dedicated products and customer groups
• Branded setup and support guidance
• tiger.PHARMA as operating partner

Service ownership

Separate manufacturer, tiger.PHARMA, IT and logistics responsibilities.

• RACI for platform, data, order and support
• Service hours, SLA and escalation
• Privacy, security and retention
• Change, release and continuity processes

Pharmacy onboarding

Guide target pharmacies to the first successful order.

• Customer verification and credentials
• Setup in the pharmacy system
• Test enquiry and test order
• Measure activation and support needs

Monitoring and support

Combine technical and business signals to resolve order problems.

• Availability and response time
• Errors and unprocessed orders
• Impact-based support priorities
• Usage and service-quality reporting

Scaling

Grow products, customers and capabilities in a controlled way.

• Capacity and load planning
• Standardised onboarding of PZN and segments
• Regression tests before releases
• Value-led roadmap

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