Direct answer: Specify a rugged handheld’s scan engine from the codes the job must actually capture, not from a generic “barcode scanner” line. A 1D linear imager is a candidate when the approved label set contains only supported linear symbols. A 2D area imager is the candidate when the job includes Data Matrix, QR or other required two-dimensional symbols—but the exact engine, enabled decoders, label condition and application output still need a sample test. An aiming laser on an imager does not make it a laser-decoding engine.
Start with the label set, including what may change
Collect the actual label artwork or physical samples for every receiving, picking, service and returns task. Record the symbology, printed or screen-based carrier, smallest and largest symbol, working distance, surrounding codes and the field that the business application expects. A single familiar Code 128 label is not evidence that the next supplier’s Data Matrix or a customer’s phone QR code will work.
Editorial procurement example, not a device test: a warehouse now receives cartons with Code 128, but a new supplier will also send items marked with Data Matrix. A return desk must read a QR code displayed on a phone. A quote for a linear-only engine may satisfy today’s carton task but not the approved future label set. The buyer can either keep the linear configuration for that restricted job or evaluate a specific 2D engine and software profile for all three tasks. The decision is about the actual work, not a claim that every 2D engine reads every printed or electronic code.
The older symbology and enabled-decoder guide explains why a listed symbology can still be disabled in software. Here the first decision is which physical engine configuration to buy; decoder settings are a second gate.
Do not confuse the imager, aimer and camera
A linear imager captures a one-dimensional image for its supported linear codes; an area imager captures a two-dimensional image and may decode both linear and 2D symbologies when the particular model and profile support them. A laser aiming pattern may be present on either type of product. For example, Zebra’s LI36X8 Product Reference Guide identifies the LI36X8 as a linear imager and separately describes the LI3608-ER’s laser aimer. The DS3600-HD specification sheet lists both 1D and 2D decode capabilities for that different, specific imager. Neither document describes an AIDC GO handheld configuration.
A device’s rear camera is another capture path, not proof that its integrated scan engine is equivalent to an area imager. Zebra’s DataWedge 15.0 Barcode Input documentation distinguishes camera, imager and laser-based input, then applies decoder and output processing. That is a bounded example of a software stack: another Android device may not include DataWedge or the same controls.
Do not buy a 2D engine merely because its category name sounds more capable. Ask for the exact engine and device SKU, supported symbologies and enabled profile, decode conditions, application interface and service options. Conversely, a linear-only quote is not a safe cost saving if the workflow must accept a 2D symbol next quarter.
Test the difficult task, not just one clean label
Build a small acceptance set with real labels and the intended application. Include a clean linear code, each required 2D code, the smallest approved print, a worn or reflective sample if it occurs in the job, a phone-screen code if applicable, and a label containing several nearby symbols. Keep the source value and expected business field for each sample. Test from the operator’s actual distance and hand position under representative light; do not invent a universal read-range target from another engine’s brochure.
Record separately whether the engine decodes a symbol, which value it outputs and whether the business app accepts it into the correct field. A successful beep is not a completed inventory transaction. If a 2D sample decodes in a vendor demo but not in the work app, check the active scanner selection, decoder configuration and app input path before declaring that the optics failed. DataWedge 15.0 illustrates that scanner selection and decoders are distinct settings; the chosen AIDC GO model’s actual software must be verified independently.
On a crowded label, verify that the intended code is selected. The existing multiple-code selection guide handles that application decision. On a part marked directly into metal or plastic, use the printed-label versus direct-part-mark guide; a normal 2D symbol claim does not establish DPM illumination or decode performance. For near and far targets, the near/far configuration guide covers the separate depth-of-field decision.
Turn the comparison into an orderable acceptance result
- Freeze the current and approved future symbology list, symbol samples and application fields. Label each sample with its expected decoded value without treating an editorial sample as a real customer result.
- Identify each candidate by complete handheld SKU, scan-engine option, firmware, OS build, scanner profile and application version. Record which decoders are enabled.
- Use the same samples, operator path and lighting for each candidate. Log decode, raw output, selected target and final application record separately; classify no-read, wrong-target and rejected-field outcomes differently.
- Repeat the job after a normal configuration import or device replacement. A feature that works only in a supplier’s demo profile has not passed the project deployment gate.
- Approve the exact configuration that meets the agreed sample set and workflow, or keep the missing item open. A printed code’s quality and placement may also need correction; do not promise that changing the engine alone will repair a defective label.
Compare the available handheld terminal directions against this label set. Send the actual code samples, task distances and application interface to Integration Support, then contact AIDC GO for the precise proposed model and engine documentation. No AIDC GO model-specific 1D/2D capability is inferred from the third-party examples above.
Sources and scope
Zebra’s LI36X8 Product Reference Guide, DS3600-HD specification sheet and DataWedge 15.0 Barcode Input documentation were read on 2026-09-23 for the distinction between linear and area imaging, aimer and scanner hardware, and software configuration. Their capabilities and settings apply only to the named products or software versions. The warehouse example and acceptance method are editorial, not measured AIDC GO performance.