What happens when sales, purchasing, warehouse teams, and your online store all have different information about the same product? A supplier changes a specification, one spreadsheet gets updated, another system doesn't, and suddenly customers receive outdated information or employees order the wrong item. In this episode of M365 FM, Mirko Peters explains how Dynamics 365 Product Information Management (PIM) creates a shared product definition across the business and manages products, product masters, variants, dimensions, configurations, categories, attributes, legal entities, and integrations. WHAT IS DYNAMICS 365 PRODUCT INFORMATION MANAGEMENT? Dynamics 365 Product Information Management provides a central place for defining and maintaining product information. Purchasing needs supplier information and units. Warehouse teams need accurate information for receiving, storing, and picking. Sales needs understandable product names. Finance needs the correct product setup, while commerce channels need descriptions, images, and specifications. Without a shared product definition, each department can create its own version of the same information. PIM provides the common product record those different business processes can use. ONE PRODUCT RECORD ACROSS THE BUSINESS Consider an insulated water bottle originally sold as a 500-milliliter product. The supplier changes it to 750 milliliters. Purchasing receives the new specification, but the online store still shows 500 milliliters. Sales sends customers an outdated specification sheet, while warehouse employees see labels that don't match their orders. Nobody intentionally created incorrect information. The problem is that different departments were working from different copies. Product Information Management creates one central product definition where agreed product information can be maintained and reused. WHAT INFORMATION DOES A PRODUCT RECORD CONTAIN? The product number provides a consistent identifier even when different teams use different terminology. The record can also contain names, descriptions, units, images, attachments, categories, attributes, and translations. Units are particularly important because organizations might buy, sell, store, or count products as pieces, boxes, kilograms, liters, or pallets. Attachments can provide supplier documents or specifications, while images help employees and customers recognize products. Translations allow the same underlying product to have appropriate names and descriptions for different languages and markets. SIMPLE PRODUCTS VS PRODUCT MASTERS Dynamics 365 distinguishes between a simple product and a product master. A simple product represents one fixed item without choices that create separate variants. A product master represents an entire family of related products. A pair of jeans provides a useful example. Customers might consider it one product, but a warehouse needs to distinguish blue medium jeans from black large jeans. The product master contains the shared information for the jeans range. Individual variants represent the exact products employees purchase, stock, sell, and ship. PRODUCT VARIANTS EXPLAINED A variant is a specific sellable or manageable version of a product master. Blue medium jeans can represent one variant. Black large jeans can represent another. Although both belong to the same product family, they're not interchangeable. Each variant can have different inventory availability, labels, barcodes, and operational requirements. The product master therefore acts as the parent definition while variants represent the individual members of that family. PRODUCT DIMENSIONS Dynamics 365 Supply Chain Management includes five product dimensions discussed in the episode: Color, Size, Style, Configuration, and Version. Color and size are straightforward examples for clothing. Style can distinguish variations such as regular fit and slim fit. Configuration can identify a particular build or setup, such as different equipment specifications. Version can distinguish engineering changes to a product over time. Organizations choose the dimensions appropriate for each product family rather than applying every dimension to every product. PRODUCT DIMENSIONS VS PHYSICAL DIMENSIONS Product dimensions shouldn't be confused with physical dimensions. Weight, height, width, length, and volume describe the physical characteristics of a product. They don't necessarily create another sellable variant. Product dimensions identify which specific variant somebody wants. Physical dimensions describe what that product is physically like. For warehouse operations, physical dimensions can help determine how much space something requires. For a customer ordering black jeans in size large, product dimensions identify the correct variant. THREE WAYS TO CONFIGURE PRODUCT VARIANTS Dynamics 365 Supply Chain Management supports three approaches covered in the episode: Predefined variants, dimension-based configuration, and constraint-based configuration. The appropriate method depends on whether the organization already knows every valid product combination or whether the final product is configured according to customer choices and business rules. Choosing the appropriate configuration model early is important because it shapes how the product family is managed afterward. PREDEFINED VARIANTS Predefined variants work well when the organization already knows which combinations it will sell. A retailer might sell jeans in several colors and sizes but not offer every mathematically possible combination. Instead of generating unnecessary variants, the business creates only the combinations that actually exist. This keeps the catalog cleaner and prevents somebody from ordering a combination the organization doesn't sell. DIMENSION-BASED CONFIGURATION Dimension-based configuration can be useful in manufacturing. Imagine a company producing industrial pumps where different configurations require different components. The organization can use a shared Bill of Materials while associating particular components with specific configurations. A pump requiring one voltage might need one motor, while another configuration requires a different motor. The configuration determines which relevant component lines should be used for the resulting product. CONSTRAINT-BASED CONFIGURATION Constraint-based configuration becomes useful when customers can select many options but not every combination is technically possible. A custom machine might provide choices for its housing, motor, voltage, safety equipment, and control panel. Some combinations work together. Others don't. A product configuration model defines available choices and the rules controlling them. The system can therefore prevent an impossible product configuration before the order reaches manufacturing. CHOOSING THE RIGHT CONFIGURATION MODEL ㅤ The key question is: Does the business know every valid product combination before an order arrives, or does the customer create a valid product through a controlled set of choices? A retailer with a fixed clothing range probably doesn't require a sophisticated configurable-product model. A manufacturer producing made-to-order equipment might. The product configuration approach should follow the real purchasing, sales, and production process rather than simply choosing the most flexible technology available. PRODUCT CATEGORIES Categories provide structure around product information. Think of them like aisles inside a well-organized store. A company might organize products into clothing, tools, office supplies, or more specialized categories. One product can also participate in multiple categories when those categories serve different business requirements. Categories make products easier to find, organize, and manage while providing structure for related product information. PRODUCT ATTRIBUTES Attributes provide additional details describing a product. For a water bottle, attributes might include material, capacity, lid type, insulation, brand, and care instructions. For industrial equipment, attributes might describe physical dimensions, power requirements, temperature ranges, or technical standards. Categories can carry attributes appropriate for the products they contain. This gives organizations a structured way to capture useful product information rather than inventing unrelated fields for individual products. IMAGES, ATTACHMENTS AND TRANSLATIONS Product information isn't limited to structured fields. Images can help warehouse employees, salespeople, and customers recognize an item. Attachments can contain supplier documentation, specifications, and other supporting information. Translations allow product names and descriptions to be presented appropriately across different languages while retaining the same underlying product definition. Together, these capabilities make the product record a richer source of information than a simple item number and description. CONTROLLING ACCESS TO PRODUCT DATA Not every employee should be allowed to modify every product record. Changes to product names, specifications, categories, or other information can affect multiple downstream teams and systems. Dynamics 365 can apply product-data access rules at category or individual-product level. Different teams can therefore manage the product areas for which they're responsible while sensitive or restricted products can receive tighter controls. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
