A successful barcode decode does not prove that a warehouse pick is complete. The application still has to connect the source location, product, required tracking dimensions, quantity and destination order tote to the same authorised work task.
This guide uses an editorial example with two orders that require the same item but use different totes. It is not a customer case or an AIDC GO performance test. The validation steps, field sequence and exception choices must be configured in the warehouse application and verified with the actual labels, devices and operating rules.
Start from an authorised pick task
Open the work task before scanning inventory. The task should identify the warehouse, source location, required item, quantity and unit, any batch or serial requirement, and the destination order or tote. A barcode reader supplies captured values; the application decides whether those values match the active task.
Microsoft documents configurable product, location and quantity confirmations in the Dynamics 365 Supply Chain Management Warehouse Management mobile app. Those are product-specific configuration options, not universal scanner behavior and not evidence of an AIDC GO application feature.
Confirm the source location before taking stock
At location A-01-02, the worker opens task PICK-2408. The application expects item ITEM-447, two pieces, and tote TOTE-RED. Scanning the location label first can give the application evidence that the worker is acting at the assigned source, but only when location confirmation is enabled and the scanned value is checked against the task.
Microsoft's batch, serial, license plate and location confirmation documentation notes that confirmation behavior depends on the configured work type and can be skipped in specified cases. Procurement should therefore ask which confirmations the proposed application actually presents, which values it compares and when a step can be bypassed.
Match the product and required tracking identity
Scan the product or its approved handling label and compare the resolved identifier with the work line. If the project controls batch or serial identity, capture and validate that value as a separate field. A correct product code cannot substitute for a required batch or serial number, and a batch code cannot prove that the worker is at the correct location.
The existing barcode quantity and unit guide covers quantity entry and unit conversion in detail. In this picking flow, the important requirement is that the confirmed item, required tracking identity, quantity and unit remain attached to the same work line rather than becoming independent scan events.
Keep two orders with the same item separated
The editorial wave contains two tasks. Both require ITEM-447, but order SO-8102 uses TOTE-RED and order SO-8103 uses TOTE-BLUE. A product scan can be correct for both tasks, so product confirmation alone cannot decide where the pieces belong.
Microsoft's cluster-position example shows a named Dynamics 365 flow in which the same item is sorted into different cluster positions for different sales orders. That example supports the need to distinguish destination positions; it does not establish an AIDC GO workflow or guarantee that another WMS uses the same screen sequence.
| Observed step | What the application should compare | Decision for this editorial task |
|---|---|---|
Location A-01-03 scanned |
Compare source location with A-01-02 |
Reject or route to an approved location exception; do not continue as a normal pick |
ITEM-448 scanned |
Compare resolved product with ITEM-447 |
Reject the item for this work line and keep the original task open |
TOTE-BLUE scanned for SO-8102 |
Compare tote identity and order assignment with TOTE-RED |
Do not confirm the put; present the correct destination or an authorised exception |
| Required stock is not present | Compare physical finding with remaining work and exception rules | Record a short-pick or investigation outcome defined by the WMS; do not invent completion |
Treat quantity and tote confirmation as separate decisions
After the correct product is identified, confirm the required quantity and unit under the project's rules. Then identify the target tote and compare its assignment with the active order. The scan-feedback guide explains why a beep or decoded value is not the same as application acceptance; the same separation applies to a tote scan.
If repeated reads are possible, define whether the application treats them as an intentional second unit, an accidental duplicate or a request for operator confirmation. The duplicate-read guide covers that control. Do not suppress every repeat globally, because some picking tasks legitimately require multiple units.
Route shortages and mismatches without inventing completion
If the expected quantity is unavailable, preserve what is known: the active task, confirmed location, observed item, quantity physically found and the operator's selected reason. Microsoft documents short-pick work exceptions and possible reallocation policies in Dynamics 365 work exception guidance. The exact options depend on that configured product and workflow.
A short pick may lead to investigation, reallocation, partial completion or cancellation according to the customer system. The handheld should not silently mark the order complete, and this guide does not assume that every WMS automatically finds replacement stock.
Commit one traceable result
Complete the work only after the application has accepted the required confirmations and exception outcomes. Save the work or transaction identity, source location, resolved product, tracking fields, quantity and unit, destination tote, operator decision and committed result. A stored confirmation record supports audit, but it does not by itself prove that the physical item was placed in the tote; representative observation remains part of validation.
The cycle-counting guide addresses recounts and adjustments, while the pallet receiving guide addresses inbound logistic units. Keep those business events separate from the outbound picking transaction described here.
Evaluate the device around the complete route
Use representative location labels, product barcodes, batch or serial labels, tote labels and exception screens. Check target-code selection, lighting, reach, gloves where relevant, operator feedback, quantity entry and the application's response to every mismatch. A decode-rate demonstration without the order and tote rules is incomplete evidence.
Review the rugged handheld terminal category, the warehousing and logistics workflow page and the mobile barcode data-capture solution as hardware and workflow entry points. Send the WMS name and version, label samples, confirmation sequence, tracking requirements, tote rules and exception states through Integration Support before selecting a configuration.