Integrate MSV3 with ERP, WMS and warehouse 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 →

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

Architecture and ownership

Map systems, data ownership and responsibilities across the order flow.

• Separate pharmacy system, gateway, ERP, OMS and WMS
• Define sources for PZN, stock, price and customer terms
• Separate synchronous enquiries from downstream processing
• Define retry, error and continuity paths

Product, customer and commercial rules

Connect technical messages with the wholesaler’s trading rules.

• Validate PZN, product status and assortment eligibility
• Resolve customer account, site and MSV3 credentials
• Apply prices, discounts, minimum quantities and exclusions
• Control allocations and restricted availability

Inventory, order and warehouse

Prevent avoidable overselling and duplicate order creation.

• Distinguish available, reserved and blocked stock
• Use unique references and idempotent order creation
• Return warehouse and dispatch status
• Handle partial supply, back order and cancellation

Testing and monitoring

Controlled end-to-end cases demonstrate normal and failure behaviour.

• Positive, boundary and error scenarios
• Correlation IDs and appropriate logging
• Response-time, error-rate and stuck-order alerts
• Regression testing for releases and changes

Controlled launch

Scale from sandbox through pilot to production.

• Acceptance criteria and test environment
• Pilot with selected pharmacy customers
• Reconcile initial live orders
• Phased rollout 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