Three acronyms turn up in the same meeting and usually only one of them is relevant. PDM manages engineering definition: CAD files, drawings, revisions and bills of materials. PIM manages the commercial information you sell with: attributes, descriptions, images and channel-ready content. MDM governs the shared master records every system depends on, of which product is one domain. The phrase product data management causes most of the confusion, because it means the first one in engineering and the second one in ecommerce.
PDM, PIM and MDM defined
One sentence each, in the order they turn up in a product’s life.
PDM (product data management) controls the engineering definition of a product: CAD files, drawings, part revisions and bills of materials.
PIM (product information management) holds the commercial record of a product: attributes, descriptions, images, documents and category mappings, ready for every sales channel.
MDM (master data management) keeps shared master records consistent across systems, covering domains such as customer, supplier, location and product.
Two of those are systems you buy. MDM is a discipline first, and a system only when the scale justifies one.
PDM vs PIM vs MDM at a glance
| PDM | PIM | MDM | |
|---|---|---|---|
| Core job | Control the engineering definition. | Describe the product for sale. | Keep master records consistent across systems. |
| Primary users | Design engineers, manufacturing, quality. | Product data, ecommerce, marketing, category managers. | Data governance, IT, finance operations. |
| Typical content | CAD models, drawings, BOMs, revisions, change orders. | Attributes, descriptions, images, datasheets, category and channel mappings. | Identifiers, hierarchies, match and merge rules, survivorship rules. |
| Where the record starts | Engineering, before the product exists. | Supplier feed or ERP item creation. | Wherever the record already exists, in several places at once. |
| Domain scope | Products only. | Products only. | Multiple domains, product being one. |
| Example systems | Siemens Teamcenter, PTC Windchill, Autodesk Vault, Dassault ENOVIA. | Akeneo, Bluestone PIM, Plytix, inriver, Sales Layer, Bluemeteor. | Stibo Systems, Informatica, SAP Master Data Governance. |
| Relationship to ERP | Feeds part masters and BOMs into ERP. | Consumes ERP item data, adds everything commercial. | Governs the records ERP and everything else share. |
| What it does not do | Marketing copy, images, channel output. | Engineering change control, CAD versioning. | Author rich product content. |
| Typical trigger to buy | Engineering change goes wrong in production. | Channel launch stalls on missing content. | Two ERPs disagree about the same customer or part. |
What product data management (PDM) actually is
PDM came out of engineering, not ecommerce. It grew up around CAD, and its whole purpose is control of the design record. Which revision is current. Who approved the change. Which bill of materials the factory is building from. It is normally described as a subset of product lifecycle management. In most estates today it is a PLM module rather than a separate purchase.
If you manufacture what you sell, PDM is upstream of everything else. It knows the part exists before commerce does. If you buy and resell, you almost certainly do not need one, because your suppliers ran that process before the product reached you.
What PIM actually is
PIM starts where PDM stops caring. A CAD model does not tell a customer whether a valve fits their system, and a bill of materials does not sell anything. PIM holds the attributes people filter on, the descriptions they read, the images they zoom into, and the documents compliance teams ask for.
The other half of the job is channel readiness. The same product needs one description for your website and a different field set for a marketplace. Punchout catalogues want another. Each market often wants a translation. PIM stores one master record and publishes those views. Getting the attribute model right underneath is what determines whether any of this works.
What MDM actually is
MDM is the odd one out, because it is not really about products. It is about one awkward fact. The same real world thing exists as several records in several systems, with different keys and different spellings. Nobody can prove which is right.
An MDM programme defines the golden record and the matching rules that identify duplicates. Survivorship rules then decide which value wins when two systems disagree. Product is one domain within that. When an MDM platform is applied specifically to products, vendors call it product master data management, or PMDM. That is where MDM and PIM overlap and where most of the confusion in tool selection comes from.
Why “product data management” means two different things
Search for product data management and you get two sets of results that barely acknowledge each other. Engineering software vendors mean the CAD vault. Ecommerce vendors mean PIM, or something close to it, and use the phrase loosely because buyers type it.
Both usages are legitimate. That is why the term is unhelpful in a requirements document. We have sat in selection meetings where two directors agreed they needed product data management. The engineering one meant a CAD vault. The ecommerce one meant a PIM. The fix is cheap: stop using the phrase internally and name the job instead. Say “we need to control engineering revisions” or “we need to publish complete records to four channels”. The right category becomes obvious immediately.
Which product data management system do you actually need
Four questions settle it in most businesses.
Do you design or manufacture what you sell? If yes, you need PDM or PLM, and PIM sits downstream of it. If you buy and resell, skip PDM entirely.
Is your problem that channels are missing content? Thin descriptions, missing attributes, rejected marketplace listings, a website with four filters where customers need twelve. That is a PIM problem. Our piece on whether you need a PIM walks through the threshold.
Is your problem that systems disagree about the same record? Two ERPs after an acquisition, three customer databases, a part that exists twice with different identifiers. That is an MDM problem, and buying a PIM will not fix it.
Is it both? Common in industrial and manufacturing groups that have grown by acquisition. Sequence it. Fix the product content problem where it is visible to customers, and run the master data work as a governance programme alongside.
How the three work together
In a manufacturer the flow runs left to right. PDM or PLM holds the engineering definition and releases an approved part. ERP picks it up as an item master with cost, price and stock. PIM enriches it with attributes, copy, images and documents, then publishes to web, print, marketplaces and distributors. MDM sits underneath, keeping the identifiers consistent so those handovers do not silently create duplicates.
In a distributor the left hand side is missing. There is no PDM, because you did not design the product. The supplier feed replaces it, and it is a much worse input, because forty suppliers send forty formats with no revision control at all. That is why distributors feel the pain earlier than manufacturers do. Their product data and content work starts with intake rather than authoring.
The mistakes we see most
Buying MDM to solve a content problem. MDM platforms are expensive, slow to implement and governed by committee. If your actual problem is that 60 per cent of SKUs have no attributes, you have bought a very costly way of not fixing it.
Buying PIM to solve an identity problem. PIM assumes it knows which product is which. If your identifiers are broken, PIM will faithfully hold two rich records for one product.
Assuming PDM output is sellable. Engineering descriptions are accurate and unreadable. “Valve, ball, brass, 15mm, BSP” is a correct part description and a terrible product title. Rewriting it is a content exercise, not a data migration.
Letting the acronym pick the vendor. Several platforms sit deliberately across the PIM and MDM boundary. Judge them on the work they have to do for you, not the category label on the website. We run that comparison as part of PIM selection.
Key takeaways
- PDM controls the engineering definition of a product. It is a manufacturer’s system and most distributors will never need one.
- PIM holds the commercial record and publishes channel-ready views of it. This is what most people mean when they say product data management in a commerce context.
- MDM is a governance discipline covering several data domains. Product is one of them, and the product-specific version is often called PMDM.
- The phrase product data management is ambiguous by industry. Name the job instead of the acronym and the category picks itself.
- If systems disagree about which record is real, that is MDM. If channels are missing content, that is PIM. The two failures need different budgets.
- A manufacturer usually needs PDM and PIM. A distributor usually needs PIM, plus supplier intake discipline in place of PDM.
Working out where your product record should live
Most businesses that ask us this question already have the answer in their symptoms. Missing attributes and rejected listings point one way. Duplicate part numbers and arguing systems point the other. Thirty minutes with a data sample is usually enough to say which, and to say honestly if the answer is neither.
We do that as a straight conversation about your product data and content. If a PIM turns out to be relevant, we cover where our PIM expertise fits. Book a discovery call and bring a category export.