MSV3 connects a pharmacy’s ordering software to a pharmaceutical supplier. It supports structured availability enquiries, responses and electronic orders through internet-based services.
MSV3 in Germany: the protocol carries messages; the connected systems decide availability, conditions and order handling.
Definition
What is MSV3?
MSV3 stands for Medium Speed Version 3. In Germany, it is a standardised, internet-based interface for ordering processes between pharmacies and pharmaceutical wholesalers. A pharmacy system can ask a supplier about an item and its availability, receive a machine-readable response and submit an order. The same pattern can be used in agreed direct-supply relationships with manufacturers and other pharmacy suppliers.
MSV3 is a communications standard, not a product database, pharmacy management system or supplier ERP. Product identifiers such as the German PZN, customer accounts, stock, prices and business rules have to be maintained by the connected parties. An MSV3 connection works only when both ends support the agreed version and functions.
Transaction flow
From enquiry to order
1 · Identify
The buyer’s software selects the supplier account, item identifier and requested quantity.
2 · Check
The MSV3 client sends an availability enquiry. The supplier server checks its connected data and returns a structured response.
3 · Order
The buyer submits the order according to the agreed process. The receiving system validates and processes it.
4 · Reconcile
Both sides distinguish transport success, business response, partial quantities and final order status. Later delivery information depends on the implemented version and partner agreement.
A technically delivered message alone does not guarantee stock allocation or commercial acceptance. Clear status handling, traceable transaction IDs and defined retry rules help avoid lost or duplicate orders.
Start with the business relationship: who buys, who sells, which items and customer accounts are in scope? Then agree the supported MSV3 version, endpoint, authentication, product identifiers, response handling and operational ownership. Configure the client or gateway and connect the supplier server to the relevant ERP data and order workflow.
Before go-live, test an availability enquiry, unavailable or partial quantity, a valid order, a rejected order and an interrupted connection. Document what each response means to the pharmacy team and supplier support. Functions associated with MSV3 2.0, such as digital delivery information, require explicit support from both systems; they should not be assumed for every connection.
MSV3 for manufacturers selling to German pharmacies
Manufacturers can use an MSV3 ordering channel to receive orders from authorised German community and hospital pharmacies. Start by agreeing which pharmacies can order directly, which pack sizes they can buy and which customer accounts and delivery addresses to use. In Germany, the PZN identifies a specific pharmacy product pack. Map it to the relevant ERP item and ordering unit.
For example, a hospital pharmacy requests ten packs of each of two products. The supplier reports ten available for the first product and four for the second. If the pharmacy orders those quantities, the gateway can pass both lines and their order reference to the supplier’s ERP. The same reference lets the pharmacy match the order response and distinguish accepted quantities from later dispatch information.
Supplier and ERP: Agree how to map German customer accounts, PZN, quantities and order references. Test partial availability and what happens when the ERP does not reply in time.
Hospital pharmacy: Check which suppliers allow direct ordering and which features the materials management system supports for each account. Confirm dispatch notices, delivery documents and returns individually.
MSV3 (Medium Speed Version 3) is an internet-based interface used for structured availability enquiries and electronic orders between German pharmacies and pharmaceutical suppliers, especially wholesalers.
Is MSV3 an ERP system?
No. MSV3 defines the exchange of messages. Pharmacy software, supplier ERP systems and their product, customer, stock and pricing data remain separate systems.
Can a manufacturer use an MSV3 server?
Yes, where the manufacturer or its service provider accepts direct orders from pharmacies and the pharmacy software supports the agreed supplier connection. The technical and commercial setup must be agreed with each partner.
Does a successful transmission mean that the order is confirmed?
No. Technical delivery, business validation and commercial acceptance are separate stages. The response and order status should be interpreted in the connected systems.
What is needed to connect to MSV3?
Agree the supported version and functions, supplier endpoint, customer account, authentication and product identifiers; configure the pharmacy or ERP system; then test availability, responses and an agreed test order end to end.