Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: Scanners and printers

Set up Zebra DataWedge for the scan field

A DataWedge profile for the browser, with Keystroke output, Send ENTER key and Code ID Type as Zebra names them.

Review edition · 10 November 2026 · For Owner, Supervisor

On this page

DataWedge is the scanning software on Zebra's Android mobile computers. This page gives the DataWedge settings that make the device's scanner type into a SmartFACT scan field in the device's browser, each named as Zebra names it. Read the general scanner page first for what the scan field expects.

It was written from Zebra's DataWedge 15.0 guide on Zebra TechDocs: the pages Manage Profiles, DataWedge Profiles, Keystroke Output, Basic Data Formatting and Barcode Input, read on 10 November 2026. Those pages carry the version DataWedge 15.0 and a 2024 copyright line, and print no date of their own. Zebra says settings can differ between DataWedge versions, so check the version on your device. This page has not been checked on a device and makes no claim about any model. Zebra's cabled and cordless scanners do not use DataWedge and are not covered here.

Give the browser its own profile

DataWedge keeps its settings in Profiles. Zebra's guide says that Profile0 takes effect for any app that has no profile of its own, and that Profile0 cannot be associated with an app. Make a profile for the browser, so that nothing you set here changes scanning in the device's other apps.

  1. Open DataWedge, open the menu and choose New profile. Give it a short name, such as SmartFACT.
  2. Open the new profile and tick Profile enabled.
  3. Tap Associated apps, open the menu and choose New app/activity.
  4. Choose the browser the station uses, then tap the asterisk to associate all of that browser's activities.

The profile now applies whenever that browser is on screen. It applies to every SmartFACT product opened in that browser, because DataWedge chooses a profile by app, not by page.

Turn on Keystroke Output

In the profile, enable Keystroke output. It sends each scan to the browser as keystrokes, as if typed.

Under Key event options, leave Send Enter as string off, which is Zebra's default. Enter is then sent as a key press, and it is the Enter key itself that ends a scan in the scan field. The same applies to Send Tab as string at a station that is set to Tab.

Send Enter after each scan

Still under Keystroke output, open Basic data formatting, enable it and set:

Zebra's setting Set it to
Send data On, which is the default
Send ENTER key On
Send TAB key Off
Prefix to data Empty
Suffix to data Empty
Send as hex Off

At a station that is set to Tab, turn Send TAB key on and Send ENTER key off. Never turn both on.

Leave the code identifier off, except for GS1 labels

Under Barcode input, in Scan params, Zebra's setting Code ID Type has three choices: Code ID Type None, Code ID Type Aim and Code ID Type Symbol. Leave it at Code ID Type None for ordinary work.

To have LotTrail recognise a supplier's GS1 label, the device must send the label's identifier. That is Code ID Type Aim, which Zebra describes as a standards-based three-character prefix. In front of a GS1-128 label it is ]C1.

The setting belongs to the whole profile. With it on, every code scanned in that browser gains three characters at the front, your own codes included, and they stop matching in every other scan field. Two arrangements avoid that, and neither has been tried on a device for this page:

  • keep one device for reading suppliers' labels, with Code ID Type Aim in its profile;
  • or open LotTrail in a second browser app that has its own profile with Code ID Type Aim, and leave the first browser's profile at Code ID Type None.

Do not use Code ID Type Symbol. It sends Zebra's own single character, which LotTrail does not look for.

The separator inside a GS1 label

Zebra's guide lists the GS1 separator, character 29, as Ctrl and the right bracket key. It says DataWedge sends characters 1 to 31 as a string unless Send Control Characters as Events is on, and that this setting is off by default. Whether a separator sent in that way arrives in your browser as a character, as a key or not at all is something this page cannot state. The ScannerBench check below shows which.

If characters go missing

Zebra's Inter-character delay adds a pause after each character. Its default is 0. Zebra's advice, if keystrokes are lost, is to raise it in steps of 100 up to at most 1000 until the errors stop, and it warns that the delay can slow the app.

Check it with ScannerBench

  1. On the device, in the browser you associated with the profile, open ScannerBench.
  2. Choose Start capture and scan a label whose exact text you know.
  3. The capture should end by itself, by the Enter key. Go on to Inspect and compare, enter the label's text as Expected text and look for an exact match.

What each result means in DataWedge:

ScannerBench shows Look at
Nothing arrives Profile enabled, Associated apps (is it this browser?) and Keystroke output
The text arrives and the capture does not end Send ENTER key, and Send Enter as string
A Tab key in the key events Send TAB key
Extra characters at the front Prefix to data, and Code ID Type
Characters missing from a long code Inter-character delay

For a device set to Code ID Type Aim, scan a supplier's GS1-128 label. The received text should begin ]C1. Then open the key events and the character names: a separator that arrived as a character is named there, and one that arrived as a key shows as Ctrl and the right bracket.

A match shows what this device sent to this browser on this day. It is not a certificate for the device. Finish with the product's own scanner check at the station and one real scan.