A scanner configuration that works on one handheld can fail across a fleet because the receiving devices use a different capture-service version, application association, input plug-in, decoder set or output method. Copying a file is only the deployment action. The project still needs a named configuration, an applicable device scope, a readback method and a rollback path.
This guide explains capture-profile control points. Obtain the profile, import and management functions for the actual device and software configuration before using the procedure in a rollout.
Define the configuration unit before distributing it
Decide whether the controlled item is one application’s capture profile or the complete capture-service configuration. Record input, processing and output settings, application associations and global settings separately. Use the proposed service’s documentation to identify what an export contains.
Give the specified item a project version and a readable change record. Include the source device or lab build, capture-service version, target application package and activity, scanner input, enabled decoders, formatting rules and output path. This prevents a file named “final” from becoming the only statement of what the fleet should receive.
Decide whether local edits are prohibited, permitted temporarily or expected to be overwritten. That governance choice determines whether a field adjustment is a valid exception or configuration drift that must be removed.
Tie the profile to the application and capture path
An application association can decide which profile becomes active. A copied profile may exist on the device but remain inactive for the intended screen, or a default profile may capture data with different rules. Check the active application and profile before diagnosing the scanner hardware.
Keep this layer separate from the choice among Wedge, Intent and SDK integration and from the supported-versus-enabled decoder guide. The deployment baseline must state both the intended output method and the decoders and parameters expected for the project labels.
Choose a deployment method with explicit version boundaries
Obtain the supported import and deployment procedure for the actual capture service, Android build and management environment. Record file or policy scope, permissions and the verification step. Do not reuse another stack’s paths or deployment controls without evidence.
Record whether deployment replaces a full configuration, merges or replaces a named profile, or creates settings through an API. Also record who can change the configuration afterward. Enterprise enrollment can deliver management policy, but the Android Enterprise enrollment guide does not by itself prove that the capture profile was installed or activated.
Separate management visibility from configuration authority
Does the quoted management service only show device status, or can it perform the configuration changes your deployment requires? If local import meets the project’s needs, do not assume a higher-tier remote-management licence is necessary. If remote changes are required, identify the supported operation, applicable device category and number of devices covered.
For a named third-party example, Datalogic Connect’s licence documentation distinguishes Essential visibility features from Professional configuration capability. It lists fixed retail scanners, handheld scanners and mobile computers as licence categories, and exposes available device seats and command-credit consumption. Check those limits only where the proposed platform actually uses them; credit-based charging is not an industry-wide rule. This example does not establish AIDC GO device compatibility, platform resale or service provision.
A platform feature and an operator’s permission are separate conditions. Datalogic Connect’s Users & Roles documentation, for example, distinguishes a Viewer who can observe devices from roles permitted to perform actions. Confirm that the intended project account can carry out the required change, not merely that the feature appears in the platform description.
In an illustrative comparison—not actual quotations—two offers both include “management service”: one provides status viewing; the other includes the required configuration operation for the agreed devices and authorised account. Compare them against the actual deployment task, rather than treating the label as equivalent scope. Licence activation still does not replace configuration readback, scanning into the business application or the rollback verification described below.
Use a state table instead of one “deployed” checkbox
| Observed state | What it can establish | Limits of this observation |
|---|---|---|
| Configuration file reaches the device | The transfer path delivered the named file | This does not establish successful import or activation |
| Import reports success | The tested service accepted the file under the observed conditions | This does not establish that the intended application is associated with the active profile |
| Profile and key settings read back | The queried device reports the expected profile state and selected values | This does not establish that representative labels reach the correct application field |
| Controlled scan completes after reboot | The tested build can perform the defined path after that restart | This does not establish fleet-wide consistency, future-version behavior or rollback readiness |
The result should identify the device, software versions, configuration checksum or project version and the exact readback fields. A successful import notification is useful evidence, but it is not the final application test.
Verify one reference device and one receiving device
Start with a reference device whose expected scan path is known. Export or generate its configuration, deploy it to a second device of the intended build, then inspect the active profile and relevant settings through the documented interface. Test the application path independently.
Scan representative labels into the intended application fields. Include an accepted value, a value that should be rejected by business rules and a screen where scanning should not enter data. Record decode feedback, delivered value, field focus and application result separately. This keeps configuration deployment from being mistaken for business acceptance.
Plan rollback and drift detection before fleet rollout
Keep the previous profile or full configuration, applicable software versions and restoration steps. Test that the saved artifact restores the required behavior on the target build. An export file alone is not a demonstrated rollback.
After deployment, compare a sample of devices against the specified state. Check the active profile, application association, input, decoder and output settings rather than relying only on the presence of a file. Define what happens when a device is offline, an import is rejected, an application package changes or a technician makes a local edit.
Package the fleet question for model-specific review
Provide the device model and configuration, OS build, capture-service name and version, application package and activity, required scanner input, decoder settings, data formatting, output method, deployment tool, readback method and rollback artifact. Add representative labels and the application fields used for acceptance.
Use the device deployment readiness checklist and spare-device planning guide to keep replacement units in the same specified state. Send the exact scope to Integration Support or Contact. AIDC GO configuration support, APIs and deployment methods must be confirmed against the selected model and current documentation.


