Six acronyms claim to be the home of your product data, and the vendor selling each one draws the boundary differently. These pages settle it the only way that survives an implementation: by deciding what each system is the source of truth for.
Written for people who have not bought anything yet, including the cases where the answer is that you do not need to. Every page ends in the same place, because it is true of all of them: these are containers, and none of them fills itself.
An ERP owns the transactional truth about a product. A PIM owns the descriptive truth. Where the line falls, where they overlap, and whether you need both.
MDM governs one trusted record across domains. PIM makes the product record sellable across channels. Where they overlap, and which one your problem actually is.
A PIM manages what a product is. An OMS manages what happens after someone buys it. Why they are not alternatives — and where bad product data breaks fulfilment.
PDM manages engineering data — CAD files, revisions, bills of materials. PIM manages commercial product data. Why the confusion costs manufacturers real money.
PLM governs a product from concept to end-of-life. PIM governs how it is described and sold. Where the handoff happens and why it usually leaks.
A PIM manages structured product data. A DAM manages rich media as an asset with rights and renditions. Where the two overlap, and when you need both.
A PIM holds product data as structured fields. A CMS holds pages and editorial content. Why product content managed in a CMS stops scaling — and what breaks first.
A PIM is the system of record for products. A CRM is the system of record for customers and deals. They do not compete — but bad product data shows up in the CRM anyway.
PXM is what several PIM vendors renamed themselves. Some of the difference is real — channel-specific experience and performance feedback — and some is positioning.
Most catalogs are still run in Excel, and for a lot of them that is the right answer. The specific failures that mean you have outgrown it — and the honest costs of both.
The item master is the transactional record in your ERP. The product master is the commercial record buyers see. Why treating them as one causes duplicate SKUs.
The three-way comparison, settled on what each system is the source of truth for — and the one job none of them does.
GDSN is a standards network for exchanging product data with trading partners. A PIM is software you operate. Why you probably need both, and in which order.
A PIM manages product content. A syndication network moves it to retailers and distributors. They are sequential, not alternative — and both arrive empty.
Feed tools transform and optimise product data for advertising and marketplace channels. A PIM is the source. Why feed tools get sold as PIM-lite, and where that ends.
Engineering-led teams build product databases and they usually work. The build-vs-buy decision, judged on the parts that get expensive in year three.
DSA measures how your products perform on retailer sites and marketplaces. A PIM manages the content. Why measurement without a way to act is an expensive report.
CPQ builds valid configurations and prices them. A PIM describes products. For configurable catalogs the two share a data model — and that is where it breaks.
DXP suites from Adobe, Sitecore, Optimizely and Salesforce bundle a PIM. When the bundled module is genuinely enough, and the specific points where it is not.
A CDP unifies customer data. A PIM unifies product data. Personalisation needs both — and the product half is usually the one that is missing.
A WMS runs the warehouse. A PIM runs the catalog. They share exactly one set of fields — the physical attributes — and those are the ones nobody owns.
If you run one ERP, it is already your master data system. MDM earns its place when several systems create the same entity — and the trigger is usually an acquisition.
Once you know which kind of system you need, the market maps name who is in it and the head-to-heads compare them directly.