Integrate MSV3 orders with ERP and fulfilment

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 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

PZN, stock and allocation: what can actually be ordered

Physical stock, released stock and the quantity still available to a customer may differ. tiger.PHARMA structures how quarantine, reservations, allocations and outstanding orders affect ordering. The interface must obtain its answer from the appropriate source system.

• Validate PZN mapping and units before creating an order
• Make stock age and refresh intervals explicit
• Test concurrent requests for the last available units

Order-to-cash design

Define synchronous checks and downstream processing.

• Separate enquiry, order and confirmation
• Set customer, credit and delivery approvals
• Connect pricing and tax rules
• Include invoicing and payment data

Product and customer data

Map PZN and pharmacy identity to manufacturer master data.

• Map PZN to material number
• Validate pack, unit and status
• Resolve pharmacy, site and delivery address
• Control duplicates, blocks and missing data

Availability and allocation

Return the quantity that can actually be promised.

• Separate ATP, reserved and blocked stock
• Apply customer, region or period allocations
• Define partial supply and back order
• Offer alternatives only under approved rules

3PL and distribution

Control order and status exchange with outsourced logistics.

• Order handover to warehouse or 3PL
• Pick, pack and dispatch status
• Hold, error and manual approval
• Quality agreement and data ownership

Validation and release

Approve technology, commercial rules and physical delivery together.

• Reference end-to-end orders
• Boundary cases for price, quantity and blocks
• Error reconciliation and logs
• Go-live criteria and hypercare

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