Skip to main content

Scanner Settings

Configure scanner parameter rules for devices, supporting model-based or group-based settings to improve scanning accuracy and compatibility

Updated over 5 months ago

1. Feature & Application Objectives

Module Purpose:

The Scan Settings module is designed to configure scanning parameter rules for specified devices. It includes settings such as scan types, trigger modes, output encoding formats, output methods, and broadcast output options. Users can create scan configuration rules based on device models or device groups to ensure consistency and reliability of scanning functionality across different devices or scenarios.

Once a rule is issued to a device, the corresponding scan settings will be automatically applied by the system, ensuring efficient scanning and accurate data parsing.

Scan Setting Rule Notes:

  • Only one scan setting rule is allowed per device model or group;

  • If "Device Group" is selected as the scope, the rule will list all supported models within the group;

  • If multiple models exist in the group, the system will set independent scan parameters for each model;

  • If a device model has no corresponding configuration in the rule, no scan instruction will be issued for that device;

  • Once the scan setting rule is issued, the parameters on the device will be locked and cannot be modified by the user on the device side;

  • After the rule is deleted, scan settings on the device can be modified again.

Primary Operations:

  • Add Scan Setting Rules: Configure scan parameters by device model or group, then issue settings with one click;

Secondary Operations:

  • Edit: Modify the contents of an existing rule (note: scope field cannot be changed);

  • Delete: Remove unused scan setting rules and revoke the issued configuration from devices.

Typical Use Cases:

  • A store uses multiple types of scanners and needs model-specific parameters to improve scan accuracy;

  • Set the scan output encoding to UTF-8 to ensure compatibility with POS system data;

  • Disable unsupported barcode types to avoid misreading;

  • Control scan feedback behavior (e.g., sound/vibration) to meet quiet operation requirements in retail environments.

2. Primary Operations

2.1 Create Rule

Description

The "Create Rule" feature allows you to configure scanning parameters and apply the rule to a specific device model or group, ensuring that scanning behavior meets business requirements. Each scan setting rule can only be applied to one model or device group, and multiple targets cannot be selected simultaneously.

The configuration includes scanner type, trigger mode, output encoding, broadcast parameters, prefix/suffix trimming, and feedback options.

Both model-level and group-level configurations are supported. If the group contains multiple models, the system will automatically issue model-specific instructions based on device type.

Steps

  1. Enter Add Rule Page

    • Click the [Add Rule] button in the upper-right corner of the rule list page to open the scan rule configuration window.

  2. Select Scope

    • Scope (required): Choose either Model or Group as the target;

    • If you choose "Model", select the specific device model, and the system will display the corresponding configuration items;

    • If you choose "Group", the system will display a tab for each model in the group, allowing you to configure them individually.

  3. Fill in Rule Information

    • Rule Name (required): Name the rule to help identify it;

    • For each applicable model, configure the scan parameters, including:

      • Scanner type and supported barcode formats;

      • Trigger mode (auto, press to scan, long press to stop, etc.);

      • Output encoding format (UTF-8, GBK, ISO-8859-1, SHIFT-JIS);

      • Output method (emulated serial / broadcast / no output);

      • Broadcast output parameters (broadcast name, key name, etc.);

      • Character trimming (prefix/suffix);

      • Feedback mode (sound, vibration), etc.

  4. Save and Issue Configuration

    • After completing the configuration, click [Save]. The system will create and issue the rule based on the selected scope;

    • Once issued, the scan settings will take effect on the devices, and users will no longer be able to manually modify scan settings on the device.

Notes

  • Each scan setting rule can only be bound to one model or group—multi-target binding is not supported;

  • If "Group" is selected, the system will only issue configurations to device models within the group that have been configured;

  • Devices in the group without matching model configurations will be skipped automatically;

  • Issuance behavior is handled based on device type:

    • For KMA or IMA devices that are online, the configuration is pushed immediately;

    • For KMA devices that are offline, the system will issue the configuration once the device is online;

    • For IMA devices, the configuration has a validity period. If the device does not come online within this period, the configuration will expire;

  • This feature is not supported for GMA devices. These will be automatically ignored;

  • If configuration errors occur or adjustments are needed, use the Edit function. The system will re-issue the updated configuration.

3. Secondary Operations

3.1 Edit

Description

The Edit function allows you to adjust an existing scan setting rule. You can modify scan configuration parameters and update them to the target devices. The new configuration will replace the previous one.

The system does not allow changes to the "Scope" field (i.e., Model or Group). All other parameters can be modified. After saving, the system will immediately deliver the updated configuration to the relevant devices and replace the original rule.

Steps

  1. Enter the Edit Page

    • In the scan setting rule list, click the [Edit] button to the right of the target rule to open the editing page.

  2. Check Non-Editable Fields

    • The "Scope" field is read-only and cannot be modified;

    • If the scope is "Model", the "Device Model" cannot be changed;

    • If the scope is "Group", the "Group Name" cannot be changed;

    • The rule name will be retained by default but can be modified as needed.

  3. Modify Configuration Parameters

    • In the configuration area, adjust the following items as needed:

      • Scanner type and supported barcode formats;

      • Trigger mode;

      • Output encoding format;

      • Output method and connection control;

      • Broadcast output parameters;

      • Character trimming settings;

      • Beep/vibration feedback settings.

  4. Save Configuration

    • Click [Save] in the bottom right corner. The system will update the configuration and push it to replace the original one.

Notes

  • The system does not allow modifying the bound Model/Group. If changes to the scope are needed, it is recommended to delete the rule and create a new one;

  • Once saved, the system will automatically sync the updated configuration to associated devices, replacing the original one;

  • The issuing mechanism is the same as in Add Rule, as follows:

    • If the device is KMA or IMA and online, the configuration is pushed immediately;

    • If the device is KMA and offline, the configuration will be pushed once it is back online;

    • If the device is IMA, the instruction has a validity period and must be received within that time;

  • If the group includes models that are not configured in the rule, those devices will not receive the update;

  • Device-side application of rule updates requires sync with the server, so slight delays may occur.

3.2 Delete

Description

The Delete operation is used to remove scan setting rules that are no longer applicable or have been deprecated. Once deleted, the target devices will no longer be bound by the rule, and users will be able to manually modify scan settings on the device.

A confirmation dialog will appear to prevent accidental deletion. The operation will only proceed after confirmation.

Steps

  1. Initiate Deletion

    • In the scan setting rule list, click the [Delete] button next to the target rule.

  2. Confirm Deletion

    • A confirmation dialog will appear: “Are you sure you want to delete?”

    • Click [Confirm] to proceed with deletion;

    • Click [Cancel] to abort the operation without making any changes.

  3. Complete Deletion

    • After successful deletion, the rule will be removed from the list;

    • The system will no longer deliver or maintain this configuration.

Notes

  • Deletion is irreversible. Please proceed with caution;

  • Once deleted, devices will no longer enforce the corresponding scan settings;

  • If there are no other rules applied, users may configure scan parameters locally or via system apps;

  • To reapply restrictions, a new scan setting rule must be added;

  • If there are multiple rules under a group/model, only the selected rule will be deleted — other rules remain unaffected.

4. Configuration Item Description

The Scan Settings module involves a variety of configuration parameters to fine-tune device scanning behavior. This section explains each parameter used when adding or editing scan setting rules, helping users understand their actual impact on devices.

Configuration Item

Required

Description

Rule Name

Yes

Custom rule name defined by the user, used for identification in the rule list. A clear and standardized name is recommended for easy management.

Scope of Application

Yes

Specifies the target of the rule, either “Device Model” or “Group”. Each rule can only be applied to one target and cannot be changed after configuration.

Device Model / Group

Yes

If “Device Model” is selected, a specific model must be chosen. If “Group” is selected, the system will display all models within the group that support scan configuration, allowing individual settings per model.

Scanner Type

Yes

Select the type or brand of scanning engine used on the device (e.g., Zebra, Honeywell). The system will display related configuration items based on this selection.

Supported Barcode Types

Yes

Select the barcode formats that the device can recognize (e.g., Code128, EAN-13, QR Code). Multiple options supported.

Trigger Mode

Yes

Set the scan initiation method, including: - Auto trigger - Short press trigger - Long press to stop The device behavior will follow the selected mode.

Output Encoding Format

Yes

Defines the character encoding of the scanned data to ensure compatibility with business systems. Common options include: - UTF-8 (recommended) - GBK - ISO-8859-1 - SHIFT-JIS.

Output Method

Yes

Determines how scan data is output: - Simulated serial port: outputs data via serial interface; - Broadcast: broadcasts scan results to a specified application; - No output: disables output, used for testing.

Broadcast Parameters

No

Configurable when output method is set to “Broadcast”, including broadcast name, key name, etc., for integration with business apps.

Trim Characters

No

Defines whether to remove prefix or suffix characters from scan results, commonly used for data cleaning. Example: remove “http://” from a QR code URL.

Prompt Mode

No

Sets feedback behavior after a successful scan: - Sound prompt - Vibration prompt Can be selected individually or together to improve user experience.

Configuration Delivery Rules

The device type determines how configuration is delivered and applied:

  • KMA Devices:

    • Online: Configuration is delivered immediately.

    • Offline: Configuration is queued and sent once the device comes online.

  • IMA Devices:

    • Configuration commands have a validity period. If the device does not come online in time, the configuration will expire.

  • GMA Devices:

    • Not supported. Scan settings will be ignored and not applied.

Configuration Effect Behavior

  • Once a rule is created and saved, the system will automatically deliver the configuration based on the selected scope and device type.

  • After the configuration is received by the device, users will be prohibited from modifying scan parameters locally.

  • If the rule is deleted, the device will be released from the scan configuration restrictions and users will regain control to modify scan settings.

  • For rules applied by “Group”, only devices with configured parameters will receive the settings. Devices without a configured entry will be ignored.

Did this answer your question?