tiger.PHARMA connects pharmacy MSV3 enquiries with manufacturer product data, customer records, pricing, ERP orders, logistics and responses.
An MSV3 message must become a controlled, billable and deliverable order. Gateway, CRM, ERP, warehouse or 3PL and customer service are aligned and tested against realistic end-to-end cases.
tiger.PHARMA Kompetenz
Topics we master
Separate MSV3 functions from additional data integrations
A project function matrix identifies the messages actually supported by the endpoint, the information supplied by ERP or pharmacy software and the downstream processes requiring another interface. This makes data transport and commercial decisions traceable.
Separate MSV3 functions from additional data integrations
Layer
Responsibility within the agreed project
MSV3
agreed enquiries, orders, contract data and responses
ERP
pricing, customer permissions, allocations and billing
WMS
reservation, picking and dispatch
Additional integrations
further status information, documents and reporting as agreed
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
Can the solution connect to existing ERP and warehouse systems?
Yes. The integration is designed around available APIs, master data, commercial rules and operational responsibilities, then verified with controlled end-to-end cases.
Can tiger.PHARMA support ongoing operation?
Yes. The agreed service can include onboarding, monitoring, support, release coordination, reporting and continuous improvement.
What should I do when an MSV3 order response is missing?
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.
Why can warehouse stock differ from the orderable quantity?
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.
tiger.PHARMA Leistungen
MSV3 solutions and practical insights
From planning to ongoing operations: choose the right service module for your implementation.
