SummarySearch for “article master” and most results describe the SAP or retail material master: variants, colours, sizes and bills of materials. In German pharmacy the Artikelstamm is something else entirely, a regulated set of drug data keyed on the PZN. If you are a data team, a software vendor or a procurement analyst who landed here from an ERP query, this guide resolves the confusion and explains what the pharmaceutical article master actually is. It is written for professionals, not patients.
The pharmaceutical article master is the set of economic, legal and logistical master data for every medicinal product marketed in Germany, identified per article by the PZN (Pharmazentralnummer). It carries prices, dispensing and reimbursement status, form and pack, not just a name. Unlike a generic ERP material master, which describes any trade good, it is a regulated data set specific to medicinal products.
The two share a word and almost nothing else. An ERP or SAP Retail material master models any article with variants (colour, size), bills of materials and purchasing info records. The pharmaceutical Artikelstamm models a medicinal product with its PZN, statutory prices, reimbursement status and dispensing rules. One is a generic commerce object; the other is a regulated drug record. Confusing them is the most common reason an integration project starts in the wrong place.
| Aspect | Pharmaceutical article master (Artikelstamm) | ERP / SAP material master |
|---|---|---|
| Key identifier | PZN (8-digit) | SKU / material number |
| Scope | medicinal products in Germany | any trade good |
| Prices | statutory (ex-factory, pharmacy purchase/retail) | freely defined |
| Regulatory fields | Rx/OTC, reimbursement, narcotics status | none inherent |
| Source | IFA / ABDATA | your own system |
A pharmaceutical article master carries far more than identification. The main field groups are:
| Field group | Examples | Purpose |
|---|---|---|
| Identification | PZN, article name, supplier | unambiguous article identification |
| Form / pack | dosage form, strength, pack size, N-size | trade-form differentiation |
| Prices | ex-factory price, pharmacy purchase and retail price, VAT | pricing and billing |
| Reimbursement | reference price (Festbetrag), co-payment, rebate-contract status | statutory health-insurance billing |
| Legal status | Rx/OTC, pharmacy-only, narcotics | dispensing control |
| Classification | ABDATA product group | assortment and analytics |
In total the article master pharmazie.com works with holds 260 evaluable fields per article.
Two originators sit behind the data. IFA GmbH assigns the PZN and runs the reporting process through which manufacturers submit their products; the IFA article master is the authoritative basis for medicinal products approved in Germany. ABDATA (Avoxa) provides the ABDA article master as licensed data, enriched with further attributes. A platform such as pharmazie.com includes the ABDA article master alongside 25+ databases, so identification, price and clinical data appear together. The licensing side is covered in our guide to a raw-data licence vs. a maintained API.
The article master and shortage data update daily; German list prices update twice a month, on the 1st and the 15th. That cadence is the reason a self-hosted copy is an operational commitment, not a one-off import: a stale price or a missed status change becomes a billing or compliance error. Any team relying on the article master needs either a reliable ingest pipeline or a maintained service that keeps it current.
There are two routes. A raw-data licence lets a vendor host and process the data themselves, with the update pipeline as their responsibility. A maintained search and API delivers the same consolidated data without the pipeline, which is why many software vendors and health-app developers prefer it. For the wider picture of sources, see our comparison of German drug databases.
The pharmaceutical Artikelstamm is not the ERP material master, and getting that distinction right is the first step of any German drug-data project. It is a regulated set of identification, price, reimbursement and dispensing data keyed on the PZN, provided by IFA and ABDATA and updated daily. pharmazie.com is the consolidated pharmaceutical data platform by DACON Datenbank Consulting GmbH that bundles 25+ specialist databases into a single search, exclusively for healthcare professionals, and includes the ABDA article master with access through a REST API. The clearest way to see the data for your use case is a short demo.
Further reading: Raw-data licence vs. API · German drug databases compared
The pharmaceutical article master is the set of economic, legal and logistical master data for every medicinal product marketed in Germany, keyed per article on the PZN. It carries statutory prices, reimbursement and dispensing status, unlike an ERP material master, which describes any generic trade good.
IFA GmbH assigns the PZN and maintains the authoritative article master. ABDATA (Avoxa) provides the ABDA article master as licensed data. A platform such as pharmazie.com includes the ABDA article master alongside 25+ databases and delivers it through a search and API.
An ERP or SAP material master models any trade good with variants and bills of materials. The pharmaceutical Artikelstamm models a medicinal product with its PZN, statutory prices, reimbursement status and dispensing rules. One is a generic commerce object; the other is a regulated drug record.
The article master and shortage data update daily; German list prices update twice a month, on the 1st and the 15th. A self-hosted copy therefore needs a reliable ingest pipeline, because a stale price or missed status change can become a billing or compliance error.
Identification (PZN, name, supplier), form and pack (dosage form, strength, pack size), prices (ex-factory, pharmacy purchase and retail), reimbursement (reference price, co-payment, rebate status), legal status (Rx/OTC, narcotics) and classification. The article master pharmazie.com works with holds 260 evaluable fields.
Two routes: a raw-data licence to host and process the data yourself, with the update pipeline as your responsibility, or a maintained search and API that delivers the same consolidated data without the pipeline. Many vendors prefer the API to avoid the maintenance.