MSV3 access, pharmacy onboarding and managed operations

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 →

Setting up MSV3: access, supplier and test order

Configuration starts with the correct supplier account and pharmacy establishment. Credentials, service provider and protocol version must match. Test the complete flow using approved cases; keep passwords out of support logs and public contact forms.

• Confirm supplier activation, customer number and endpoint
• Distinguish test from production access
• Accept enquiry, order and response together
• Coordinate setup for the deployed version of IXOS, ADG, NOVENTI or CGM

Order cut-offs, delivery routes and order identifiers

Transmission speed alone does not determine delivery time. Ordering windows, route assignment and contractual parameters influence fulfilment. Order types and suborders must fit the supplier model; direct suppliers can require different workflows from full-line wholesalers.

• Distinguish order cut-off from delivery time
• Preserve the order identifier throughout downstream processing
• Apply contractual configuration changes in a controlled way

MSV3 timeout: resolving an uncertain order

A missing response does not prove that no order was created. Support must reconcile the order reference, transmission time and known status before repeating an order. Uncontrolled retries can create duplicates.

• Separate transport errors, authentication failures and business rejection
• Use stable references and defined duplicate checks for retries
• Assign uncertain orders to an owner for resolution
• Reconcile recovery against ERP orders and responses

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

Onboarding model

Give every pharmacy a clear route from registration to its first live order.

• Assign sales, service, IT and customer responsibilities
• Define mandatory data and approvals
• Distinguish standard, group and special customers
• Set service levels and escalation

Secure credentials

Create, transmit, activate and revoke access in a controlled way.

• Verify customer and site relationship
• Separate test and production credentials
• Document activation and changes
• Control suspension and reactivation

Pharmacy-system testing

Verify realistic cases in the systems pharmacies use.

• Guidance for ADG, PHARMATECHNIK, Awinta and CGM
• Test PZN enquiry, order and response
• Test price, quantity, unavailable and error cases
• Approve before production

Rollout communication

Explain the practical value: order within the familiar pharmacy workflow.

• Segmented pilot and rollout plan
• Concise setup and ordering guidance
• Sales material without technical overload
• Measure activation and use

Managed operations

Monitoring and support keep the service reliable.

• Availability, latency and errors
• Prioritised tickets and unresolved orders
• Service reviews and capacity planning
• Continuous operational improvement

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