Study guide

4.1 Bar Codes, GTINs, and Product Unit Conversions

Microsoft Dynamics 365 Supply Chain Management Functional Consultant MB-330

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Product Master and Released Products

1.1 Product Masters, Variants, and Configuration Technologies 1.2 Product Templates, Category Hierarchies, and Product Lifecycle States 1.3 Product Attributes, Attribute Types, and Attribute Groups

2 Chapter 2: Bills of Materials (BOM) and Formulas

2.1 BOM Lines, Line Types, and Component Configurations 2.2 BOM Versions, Activation, Approvals, and Circularity Checks 2.3 BOM Calculations, Cost Group Types, Flushing Principles, and Scrap Handling

3 Chapter 3: Product Prerequisites and Dimension Groups

3.1 Product, Storage, and Tracking Dimension Groups 3.2 Item Model Groups, Inventory Models, and Physical/Financial Posting 3.3 Reservation Hierarchies and Unit Sequence Groups

4 Chapter 4: Additional Product Details and Warehouse Fit

4.1 Bar Codes, GTINs, and Product Unit Conversions 4.2 Default Order Settings and Site-Specific Order Settings 4.3 Product Filter Codes and Physical Warehouse Dimensions

5 Chapter 5: Inventory Costing and Pricing

5.1 Costing Versions, Costing Sheets, and Standard Costing 5.2 Base Item Prices, Price Groups, and Price Tolerances 5.3 Trade Agreements, Price/Discount Journals, and Smart Rounding

6 Chapter 6: Inventory Journals and Core Transactions

6.1 Movement, Adjustment, and Transfer Journals 6.2 Counting Journals, Tag Counting, and Cycle Count Adjustments 6.3 Item Arrival Journals, Output Orders, and BOM Journals

7 Chapter 7: Inventory Operations, Blocking, and Closing

7.1 Transfer Orders, In-Transit Warehouses, and Delivery Schedules 7.2 Inventory Blocking Mechanisms, Batch Disposition Codes, and Inventory Status 7.3 Inventory Closing, Recalculation, Settlement, and ABC Classification

8 Chapter 8: Quality Management and Nonconformance

8.1 Quality Control Setup: Tests, Test Groups, and Item Sampling 8.2 Quality Associations, Automatic Generation, and Quality Orders Processing 8.3 Nonconformances, Corrections, Corrective Operations, and Quarantine Orders

9 Chapter 9: Asset Management: Setup and Maintenance

9.1 Assets, Asset Types, and Functional Locations Setup 9.2 Asset Lifecycle Models, Lifecycle States, and Asset Loans 9.3 Work Orders Configuration, Work Order Settings, and Maintenance Capacity Management 9.4 Maintenance Plans, Maintenance Requests, Work Order Scheduling, and Journal Consumption

10 Chapter 10: Procurement and Sourcing Configuration

10.1 Vendors, Vendor Groups, and Procurement Category Hierarchies 10.2 Purchasing Policies, Spending Limits, Procurement Workflows, and Charge Codes 10.3 Purchase Agreements, Vendor Rebates, and Vendor Collaboration Portal

11 Chapter 11: Purchase Order Lifecycle and Consignment

11.1 Purchase Requisitions, Requests for Quotation (RFQs), and Bidding Processes 11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt 11.3 Consignment Inventory Replenishment/Ownership Change and Vendor Return Orders

12 Chapter 12: Landed Cost and Inbound Logistics

12.1 Landed Cost Architecture: Voyages, Shipping Containers, Folios, and Journey Templates 12.2 Cost Type Codes, Auto-Costs, and Allocation Methods 12.3 Tracking Control Center, Goods in Transit Orders, and Over/Under Tolerances

13 Chapter 13: Sales Management and Order Processing

13.1 Customers, Customer Groups, Sales Agreements, and Sales Quotations 13.2 Sales Order Processing, Manual and Automatic Reservation, and Sales Returns 13.3 Order Promising: ATP, CTP, Delivery Schedules, and Product Bundles 13.4 Intercompany Trading Chains, Sales Commissions, and Customer Rebates

14 Chapter 14: Warehouse Setup and Core Infrastructure

14.1 Warehouse Topology: Sites, Warehouses, Locations, Profiles, Formats, and Zones 14.2 Work Policies, Work Breaks, and Packing Dimensions 14.3 Wave Templates, Work Templates, and Location Directives Configuration 14.4 Label Layouts, Document Routing, Wave Label Printing, and GS1 Number Sequences

15 Chapter 15: Warehouse Execution Processes

15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway 15.2 Outbound Waves, Wave Processing, Picking (Order, Cluster, Batch), and Manual Packing 15.3 Replenishment Strategies (Wave vs. Min/Max) and Inventory Movements via Warehouse Work 15.4 Cycle Counting Plans, Thresholds, Blind Counting, and Automated Containerization

16 Chapter 16: Transportation Management and Logistics

16.1 Shipping Carriers, Carrier Groups, Carrier Services, and Rate/Route Engines 16.2 Route Plans, Route Guides, Inbound/Outbound Loads, and Dock Appointment Scheduling 16.3 Freight Bills, Freight Invoicing, and Manual/Automatic Freight Reconciliation

17 Chapter 17: Warehouse Management Mobile App

17.1 Mobile App Installation, Display Settings, Connection Profiles, and Warehouse Worker Setup 17.2 Mobile Device Menus, Work-Based and Indirect Menu Items, and Inventory Inquiries 17.3 Step Detours Configuration and GS1 Barcode Scanning Implementation

18 Chapter 18: Master Planning and Planning Optimization

18.1 Master Planning Parameters, Coverage Groups, and Planning Optimization Cloud Service Architecture 18.2 Item Coverage Settings, Positive/Negative Days, Time Fences, and Action Messages 18.3 Running Master Planning, Analyzing Results, Planned Orders Firming, and Supply Schedule 18.4 Safety Stock Journals, Safety Margins, and Copilot in Dynamics 365 Supply Chain Management

4.1 Bar Codes, GTINs, and Product Unit Conversions

Key Takeaways Explain This Topic AI

Dynamics 365 Supply Chain Management supports standard linear and composite barcode symbologies (Code 39, Code 128, EAN-13, EAN-128/GS1-128, UPC-A), configured through Bar code setups and mask characters.

Bar codes can be assigned per released product, product variant (Size, Color, Style, Configuration, Version), and packaging unit, with a dedicated Scanning toggle that activates scanning during warehouse mobile operations.

GS1-128 barcode parsing decodes international Application Identifiers (AIs) including GTIN (01), Batch number (10), Serial number (21), and Expiration date (17) in a single mobile device scan.

Unit conversions are partitioned into three architectural classes: Standard conversions (global, intra-class), Intra-class conversions (product-specific, within same class), and Inter-class conversions (product-specific, bridging different classes like volume to mass).

Dual-unit catch weight processing tracks items simultaneously in a discrete inventory unit (e.g., Box) and a catch weight unit (e.g., Kilograms), enforcing nominal, minimum, and maximum tolerance limits.

Last updated: September 2026

4.1 Bar Codes, GTINs, and Product Unit Conversions

Quick Answer: In Microsoft Dynamics 365 Supply Chain Management (D365 SCM), product identification and dimensional scaling rest on two core pillars: Bar code setups (which configure symbologies, mask rules, and GS1 Application Identifiers for mobile scanning) and Unit conversions (which define mathematical relationships between units of measure). Unit conversions follow a three-tier hierarchy: Standard conversions (system-wide, intra-class), Intra-class conversions (product-specific, within the same class), and Inter-class conversions (product-specific, bridging different classes like volume to mass). For items whose piece weight varies naturally, Catch weight processing enables dual-unit inventory tracking with nominal, minimum, and maximum tolerances.

Bar Code Setup Architecture and Symbologies

Automated data collection across receiving docks and warehouse floors requires standardized barcode configurations. In D365 SCM, bar code setup definitions are configured centrally ( Warehouse management > Setup > Bar codes or Organization administration > Setup > Bar codes ).

1. Core Bar Code Parameters

When defining a Bar code setup , several structural parameters dictate validation and generation:

Bar code setup : Unique alphanumeric identifier for the profile (e.g., EAN128 , UPC-12 , CODE39 ).

Bar code type : The underlying symbology standard.

Mask ID : Links the setup to a bar code mask to parse or format fixed prefixes, item numbers, variant codes, and check digits.

Font name and size : Specifies typography when rendering barcodes on reports and labels.

Minimum and Maximum length : Enforces string length validation to reject malformed scans.

2. Supported Bar Code Symbologies

Symbology Data Character Set Length D365 SCM Primary Use Case

Code 39 Alphanumeric (A–Z, 0–9, 7 special chars) Variable Internal inventory tracking, equipment labeling, legacy manufacturing. Self-checking.

Code 128 Full 128 ASCII character set High-density variable Warehouse bin and carton labels, container IDs, and serial tracking. Highly compressed.

EAN-13 Numeric only (12 digits + 1 check digit) 13 fixed digits Point-of-sale retail packaging worldwide outside North America.

UPC-A Numeric only (11 digits + 1 check digit) 12 fixed digits Standard consumer goods retail packaging across the United States and Canada.

GS1-128 / EAN-128 Alphanumeric with Application Identifiers Variable (up to 48 chars) Supply chain logistics, shipping containers, multi-attribute scanning (GTIN, batch, serial, expiry).

3. Bar Code Masks and Mask Characters

Bar code masks ( Warehouse management > Setup > Bar codes > Bar code masks ) parse incoming character strings into structured transactional data:

I (Item) : Released Product item number position.

M (Dimension / Variant) : Product dimension values (Configuration, Size, Color, Style, Version).

P (Prefix) : Static company prefix.

C (Check digit) : Algorithmic check digit (e.g., Modulo 10).

T (Type) : Barcode classification type.

Q (Quantity) : Embedded transactional quantity (common in weighable catch weight retail items).

E (Price) : Embedded sales price for retail point-of-sale labels.

Assigning Bar Codes to Released Products and Variants

Barcodes are assigned to released products ( Product information management > Products > Released products > Manage inventory tab > Bar codes ):

Granularity : A released product can maintain multiple barcode records. Each unique combination of Product dimensions (Size, Color, Style, Config, Version) and Packaging Unit (Each, Box, Pallet) can hold its own distinct barcode.

The Scanning Toggle : The Scanning checkbox dictates whether the Warehouse Management mobile app evaluates this barcode during inbound receiving, picking, cycle counting, and transfer operations. If unchecked, the barcode is preserved for document printing or retail POS, but returns an "Item not found" error on handheld scanners.

Default Barcode : The General checkbox marks the barcode as the primary default for that item-unit combination when printing standard labels.

Global Trade Item Numbers (GTIN) and GS1 Mobile Scanning

A Global Trade Item Number (GTIN) uniquely identifies trade items across four standard formats: GTIN-8 (small retail items), GTIN-12 (UPC-A), GTIN-13 (EAN-13), and GTIN-14 (master cartons and shipping containers).

GS1 Barcode Parsing in the Warehouse Management Mobile App

Receiving a batch-tracked, serialized product traditionally required scanning the item, scanning the batch, scanning the serial, and manually entering the expiry date. D365 SCM streamlines this via GS1 barcode parsing ( Warehouse management > Setup > Barcode parsing > Barcode parsing rules ). Scanning a GS1-128 or GS1 DataMatrix barcode causes the mobile app engine to parse standardized Application Identifiers (AIs) :

AI (01) : GTIN (14 digits) — resolves the Released product and transactional Unit.

AI (10) : Batch / Lot number — populates the Batch tracking dimension.

AI (21) : Serial number — populates the Serial tracking dimension.

AI (17) : Expiration date ( YYMMDD ) — calculates batch expiration.

AI (15) : Best before date ( YYMMDD ) — records quality advisory dates.

AI (310x) / AI (320x) : Net weight in kilograms or pounds — populates catch weight transactions.

A single scan captures the product, packaging level, batch, expiry date, and serial number simultaneously, eliminating transcription errors and accelerating dock receiving.

Product Unit Conversions: Three Architectural Classes

D365 SCM manages unit relationships through Unit conversions ( Product information management > Setup > Units > Unit conversions or via Released product > Product tab > Unit conversions ). Conversions are divided into three mutually exclusive classes:

Conversion Class Scope Unit Class Relationship Example Configuration Location

Standard conversion Global across all products and legal entities Same class ( Intra-class ) 1 Gallon = 4 Quarts; 1 Meter = 100 Centimeters Product information management > Setup > Units > Unit conversions > Standard conversions

Intra-class conversion Specific released product or product master Same class ( Intra-class ) Product A: 1 Pallet = 40 Cases; Product B: 1 Box = 24 Eaches Released product > Product tab > Unit conversions > Intra-class conversions

Inter-class conversion Specific released product or product master Different classes ( Inter-class ) Liquid Resin: 1 Liter = 1.15 Kilograms (Volume to Mass); Steel Pipe: 1 Meter = 4.2 Kilograms (Length to Mass) Released product > Product tab > Unit conversions > Inter-class conversions

Important

Exam Distinction: Standard conversions apply globally across all items and can never bridge different unit classes. Because physical density varies by product, any conversion bridging two distinct unit classes (e.g., Volume to Mass) must be configured as an Inter-class conversion on the specific product.

Mathematical Formulas, Precision, and Rounding

Unit conversions evaluate mathematical factors through ratios to prevent rounding errors: Target Quantity = Source Quantity × ( Numerator / Denominator ) \text{Target Quantity} = \text{Source Quantity} \times (\text{Numerator} / \text{Denominator}) Target Quantity = Source Quantity × ( Numerator / Denominator ) . On the unit definition ( Product information management > Setup > Units > Units ), Decimal precision (0 to 4 decimal places) defines allowable fractional increments. Discrete handling units (Each, Piece) require a precision of 0 to prevent fractional allocations, whereas bulk liquids and powders require 2 to 4 decimals. The Rounding rule ( Nearest , Up , Down ) resolves fractional remainders.

Dual-Unit Catch Weight Processing

In food processing, agricultural commodities, and steel distribution, items have natural physical weight variations per piece. D365 SCM addresses this through Catch weight item handling ( Product information management > Setup > Dimensions > Tracking dimension groups ):

Dual Units : The item tracks on-hand quantity simultaneously in an Inventory unit (discrete handling unit, e.g., Box , Each ) and a Catch weight unit (weight measurement, e.g., Kg , Lb ).

Nominal Ratio : The baseline expected conversion factor (e.g., 1 Box nominal = 25 Kg).

Tolerance Limits : Minimum and maximum weight thresholds per unit (e.g., Min = 22 kg, Max = 28 kg). The mobile app rejects inbound scans outside these boundaries.

Invoicing Principles : Sales orders can be priced and invoiced based on either the discrete Inventory unit (e.g., $100 per Box) or the actual recorded Catch weight unit (e.g., $4.00 per actual Kilogram weighed at dispatch).

Implementation Scenarios and Exam Traps

Tip

Exam Tip — Unit Sequence Group Dependency: You cannot assign a Unit Sequence Group to a released product in advanced Warehouse Management if the corresponding intra-class unit conversions (e.g., Each to Box, Box to Pallet) have not been configured first.

Warning

Exam Trap — Modifying Conversions with Active Transactions: Once an item has recorded physical or financial inventory transactions ( InventTrans ), modifying existing unit conversions can corrupt transaction history and inventory settlements. Always close open inventory and adjust on-hand balances to zero before restructuring product conversion factors.