15.4 Cycle Counting Plans, Thresholds, Blind Counting, and Automated Containerization

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

15.4 Cycle Counting Plans, Thresholds, Blind Counting, and Automated Containerization

Key Takeaways Explain This Topic AI

Cycle counting plans automate periodic inventory audits using scheduled batch jobs filtered by item velocity (ABC classifications), location types, counting pools, and maximum count limits.

Cycle counting thresholds trigger immediate counting work when on-hand quantity or percentage drops below a specified level during normal picking execution.

Blind counting hides expected on-hand quantities and license plates from the mobile device screen, preventing worker confirmation bias and ensuring audit rigor.

Cycle counting discrepancy thresholds enforce maximum variance limits (percentage and value) by worker profile; variances exceeding thresholds route to the Cycle count work pending review journal for supervisor approval.

Automated containerization executes during wave processing via the containerize wave method, pre-determining container types, splitting pick work by carton, and bypassing manual packing benches.

Last updated: September 2026

15.4 Cycle Counting Plans, Thresholds, Blind Counting, and Automated Containerization

Quick Answer: Dynamics 365 Supply Chain Management maintains perpetual inventory accuracy through Cycle Counting and optimizes outbound fulfillment throughput via Automated Containerization . Cycle counting work is initiated via scheduled Cycle Counting Plans (evaluating ABC classifications, zones, and elapsed days) or dynamically triggered by Cycle Counting Thresholds (when picking drops bin stock below a defined quantity or capacity percentage). Audit rigor is enforced via Blind Counting (hiding expected quantities on mobile screens) and Discrepancy Thresholds (routing variances exceeding dollar or percentage limits to the Cycle count work pending review form for supervisory approval). For high-volume shipping, Automated Containerization evaluates item dimensions during wave processing to pre-assign container types and split picking work by carton, completely bypassing manual packing benches.

1. Cycle Counting Architecture & Scheduling Plans

Traditional warehouses rely on disruptive annual physical inventory shutdowns where all operations halt for days to manually count stock. WMS-enabled facilities in D365 SCM replace shutdowns with perpetual cycle counting —continuous, scheduled audits of subset items and locations performed during standard operating hours.

Cycle counting creates warehouse work under Work order type Cycle count . ┌────────────────────────────────────────────────────────┐

│ Cycle Counting Triggers │
│ │
│ 1. Scheduled: Cycle Count Plans │
│ Batch job runs queries (ABC class, zone, elapsed │
│ days since last count). │
│ │
│ 2. Triggered: Cycle Count Thresholds │
│ Picking work reduces bin stock below minimum │
│ threshold; prompts immediate or scheduled count. │
│ │
│ 3. Ad-Hoc: Spot Counting │
│ Worker observes damaged or disordered bin and │
│ initiates count directly from mobile device. │
└────────────────────────────────────────────────────────┘
Cycle Counting Plans ( Warehouse management > Setup > Cycle counting > Cycle count plans )

Cycle counting plans automate the periodic creation of counting work based on configurable inventory criteria:

Cycle count plan ID & Description : Unique plan identifier.

Maximum number of cycle counts : Caps the total work headers created per batch execution, preventing counting backlogs.

Days between cycle counting : Enforces a minimum cooldown interval (e.g., 30 days ensures a location counted yesterday is not counted again today, even if it matches the query).

Cycle count query : Filters items and locations based on business criteria:

ABC Classification : Count high-value/high-velocity Class A items monthly, Class B quarterly, and Class C annually.

Location Profile / Zone : Restrict counts to forward pick locations ( PICK ) or secure bulk cages ( HIGH-VAL ).

Cycle counting pools ( Warehouse management > Setup > Cycle counting > Cycle counting pools ): Group work lines into pools assigned to specific shifts, departments, or specialized audit teams.

2. Cycle Counting Thresholds (Triggered Counting)

A common cause of warehouse fulfillment delays is inventory discrepancy discovered during active order picking (e.g., system says 10 units are present, but the bin is physically empty).

Cycle counting thresholds solve this by triggering counting work dynamically based on inventory depletion:

Navigation : Warehouse management > Setup > Cycle counting > Cycle count thresholds .

Threshold based on :

Quantity : Triggers count work when on-hand quantity in the location drops below an absolute number (e.g., <= 2 eaches ).

Percentage : Triggers count work when on-hand inventory drops below a percentage of total location capacity (e.g., <= 5% ).

Process cycle count immediately :

If set to Yes : When an order picker completes a pick line that drops stock below the threshold, the mobile device immediately pauses the picking flow and prompts the worker: "Perform Cycle Count: Enter quantity in bin" . The worker counts the remaining stock before leaving the aisle.

If set to No : The system creates an independent cycle count work order assigned to the cycle counting team, allowing the picker to continue their pick route uninterrupted.

3. Blind Counting vs. Guided Counting

When configuring mobile device menu items for cycle counting ( Warehouse management > Setup > Mobile device > Mobile device menu items with Mode = Work , Work creation process = Cycle counting or Cycle count grouping ), the functional consultant must balance operational speed against audit integrity. ┌──────────────────────────────┐ ┌──────────────────────────────┐

│ Guided Counting │ │ Blind Counting │
│ │ │ │
│ Location: PICK-A-01 │ │ Location: PICK-A-01 │
│ Item: A0001 (Microchip) │ │ Item: A0001 (Microchip) │
│ Expected Qty: 50 │ │ Expected Qty: [HIDDEN] │
│ Confirm Qty: [ 50 ] │ │ Physical Count: [ ? ] │
│ │ │ │
│ (Risk of confirmation bias) │ │ (Forces honest physical verification) │
└──────────────────────────────┘ └──────────────────────────────┘
Guided Counting (Display Expected Quantity)

Configuration : Mobile menu item has Display quantity set to Yes .

User Experience : The screen displays the system on-hand inventory (e.g., "Expected: 42 EA"). The worker simply validates whether the number looks correct and presses enter.

Risk : High risk of confirmation bias—workers frequently glance at the bin, assume the system number is accurate, and confirm without physically counting individual items.

Blind Counting (Hidden Expected Quantity)

Configuration : Mobile menu item has Display quantity set to No and Display license plate set to No .

User Experience : The screen indicates the location and item to count, but conceals on-hand quantities and expected license plates. The worker is forced to physically handle and count every piece, keying the true number into the scanner.

Compliance : Mandated by external financial auditors for public enterprises complying with Sarbanes-Oxley (SOX) and ISO quality standards.

4. Discrepancy Thresholds, Adjustments, and Supervisory Review

When physical counts do not match system on-hand records, D365 SCM uses Cycle count discrepancy thresholds to determine whether adjustments post automatically or require supervisory review.

Discrepancy Threshold Configuration

Navigate to Warehouse management > Setup > Cycle counting > Cycle count thresholds (or Cycle count threshold users to define limits per worker profile):

Maximum quantity limit : Maximum unit variance allowed before review is required (e.g., variance > 5 units).

Maximum percentage limit : Maximum percentage variance allowed before review is required (e.g., variance > 2%).

Maximum value limit : Maximum total financial dollar variance allowed before review is required (e.g., variance > $100.00 USD). [Worker Submits Physical Count via Mobile App]

│
▼
[System Evaluates Discrepancy]
│
─────────┴─────────
│ │
▼ ▼
┌─────────────────┐ ┌──────────────────────────────────────┐
│ Within Threshold│ │ Exceeds Threshold │
│ (e.g., -$15.00) │ │ (e.g., -$2,500.00) │
└────────┬────────┘ └──────────────────┬───────────────────┘
│ │
▼ ▼
┌──────────────────────┐ ┌───────────────────────────────┐
│ Work Auto-Closed │ │ Work Status = 'Pending Review'│
│ Inventory Adjustment │ │ Held in Supervisory Journal │
│ Posted to Ledger │ └───────────────┬───────────────┘
└──────────────────────┘ │
▼
┌───────────────────────────────┐
│ Supervisor Actions: │
│ 1. Accept Diff (Post Adj) │
│ 2. Reject Diff (Cancel Work) │
│ 3. Recount (New Work Created) │
└───────────────────────────────┘
Automated Posting vs. Supervisory Review

Within Threshold : If the variance falls within all three configured limits (quantity, percentage, and value), D365 SCM immediately closes the work and automatically posts an inventory adjustment journal (using the default profit/loss adjustment journal configured in Warehouse management parameters).

Exceeds Threshold : If the variance breaches any single limit, D365 SCM moves the work order header to status Pending review . The physical inventory adjustment is held in abeyance.

Supervisory Approval Workflow

Supervisors review flagged discrepancies at Warehouse management > Cycle counting > Cycle count work pending review :

Accept difference : The supervisor confirms the physical loss/gain. D365 SCM updates on-hand inventory and posts financial adjustments to the inventory write-off ledger accounts.

Reject difference : The supervisor cancels the variance. No inventory adjustment is posted.

Recount : The supervisor suspects counting error. D365 SCM creates a new cycle count work order line, assigning another worker to perform a second verification count.

5. Automated Containerization Architecture

While manual packing stations (Section 15.2) work well for low-volume or fragile shipments, high-velocity distribution centers deploy Automated Containerization (Cartonization).

Automated Containerization vs. Manual Packing

In manual packing, pickers retrieve loose items in bulk totes and deliver them to a pack bench, where a packer manually determines which box size to use. In Automated Containerization , D365 SCM calculates the optimal carton sizes, box counts, and packaging materials algorithmically during wave processing before picking begins. Picking work is split directly by container, allowing pickers to pick directly into final shipping boxes on their carts, completely eliminating the manual packing bench! [Wave Processing: containerize Wave Method]

│
▼
┌────────────────────────────────────────────────────────┐
│ Volumetric Containerization Algorithm │
│ │
│ Evaluates: │
│ - Item Dimensions (Length x Width x Height) │
│ - Item Gross Weight │
│ - Container Types (Box-S, Box-M, Box-L) │
│ - Maximum Volume Utilization (e.g., 90%) │
│ - Maximum Payload Weight Limit │
└──────────────────────────┬─────────────────────────────┘
│
▼
[Picking Work Split by Final Container]
Work Line 1: Pick 4 items into Container C-101 (Box-M)
Work Line 2: Pick 8 items into Container C-102 (Box-L)
Core Containerization Configurations

Container Types ( Warehouse management > Setup > Containers > Container types ):

Defines physical container attributes: Dimensions (Length, Width, Height), Maximum gross weight, Tare weight, and Maximum volume.

Container Groups ( Warehouse management > Setup > Containers > Container groups ):

An ordered sequence of available container types (e.g., Sequence 1 = Small Box, Sequence 2 = Medium Box, Sequence 3 = Large Box). The algorithm tests smaller containers first to minimize packaging waste and dimensional weight freight charges.

Container Packing Policies ( Warehouse management > Setup > Containers > Container packing policies ):

Controls container closing behavior (e.g., auto-close upon pick completion, manifest requirements).

Containerization Templates ( Warehouse management > Setup > Containers > Containerization templates ):

Connects the Container Group, Container Packing Policy, and query criteria (e.g., Customer group = Retail).

Wave Template Integration :

The outbound wave template must include the containerize wave process method in its execution sequence (positioned after allocateWave and before createWork ).

Attribute Manual Packing Station Automated Containerization
Carton Determination Decided by human packer at pack bench Calculated algorithmically during wave processing

Work Segmentation Picking work is consolidated; packed later Picking work is pre-split directly by target container ID

Labor Touchpoints 2 Touches: Picker picks to tote, Packer packs to box 1 Touch: Picker picks directly into shipping carton

Master Data Dependency Low (packer visually selects box) High (requires 100% accurate item weights and 3D dimensions)

6. Implementation Scenarios and Exam Traps

Important

Exam Tip — Physical Dimensions Dependency : On the MB-330 exam, questions frequently highlight containerization failures where the wave engine fails to cartonize items and throws an allocation error. Automated containerization strictly depends on physical item dimensions (Gross weight, Width, Length, and Height) configured on the Released product master ( Manage inventory FastTab). If dimensions are zero or missing, the containerization algorithm cannot calculate volumetric displacement and fails.

Warning

Exam Trap — Threshold Limits Are Evaluated by 'OR' : When configuring cycle count discrepancy thresholds (Quantity, Percentage, Value), the system flags work for supervisory review if ANY single threshold is breached. For example, if a worker miscounts 1 single unit (within the 5-unit limit) of a $10,000 diamond ring (breaching the $100 value limit), the work immediately moves to Pending review .

Tip

Best Practice — Spot Cycle Counting : In addition to scheduled plans and thresholds, always provide warehouse floor workers with an ad-hoc Spot cycle counting mobile menu item. If a worker notices broken cartons, spillage, or suspicious physical stock in an aisle during their daily duties, spot counting empowers them to initiate an immediate audit without waiting for a scheduled plan.