Zebra quickstart

Introduction

Your goal: scan a GS1 barcode with a Zebra device's hardware imager and render the GTIN-scoped evidence Vision Scan produces. This path runs through the same signed Android RC2 kit and the same evaluation contract as the Android quickstart — the only difference is the scan input: hardware imager and DataWedge instead of a CameraX pipeline.

Requirements

Quickstart

Four steps to your first scan, in order. Each step points to its detail section below.

DataWedge Coming soon

What is verified today:

• DataWedge 8.2 or newer receives the scan output.
• The DataWedge profile is assigned to your host application.
• DataWedge delivers scans through broadcast intents — com.symbol.datawedge.api.ACTION.
• Hardware trigger buttons map to session batch start/stop.

Scan input

The hardware imager is the scan input — there is no CameraX frame pipeline on this path. The trigger maps to session batch start/stop, and DataWedge output is the only supported input source.

Scan output

The adapter maps DataWedge output to canonical observations and the parser qualifies GTIN-scoped evidence. Render only that evidence — nothing the device invented locally.

Worn or partial labels that will not decode cleanly are the Focused Rescue case — rescue is constrained and never overwrites valid decoded data.

Intent handling

Register the host app for the DataWedge broadcast action. The action string is the verified contract surface:

<receiver android:name=".DataWedgeReceiver" android:exported="false">
    <intent-filter>
        <action android:name="com.symbol.datawedge.api.ACTION" />
    </intent-filter>
</receiver>

Vision Scan integration

The DataWedge adapter sits outside the portable core — camera, hardware, and OS adapters belong to the host layer. The integration pins are identical to the Android path: the signed evaluation kit, the backend-signed tenant/device JWS, and only routes pinned in the signed customer integration contract.

Applying the license follows the Android license flow — see License & Entitlement in the Android quickstart.

Result handling

A successful scan means your host app received the DataWedge scan output and rendered GTIN-scoped evidence from the signed customer integration contract — the device does not invent observations locally.

• Confirm the rendered evidence is GTIN-scoped before trusting it downstream.
• For the event vocabulary those observations feed, see Canonical JSON events.
• For retry guidance when a scan does not arrive, see Troubleshooting below.

Troubleshooting

The Zebra surface is thin on purpose: hardware validation is still in flight, so symptoms accrue from real validation runs only. For everything outside the two verified checks below, use the main troubleshooting page.

For entitlement, initialization, and scan-result symptoms beyond Zebra input, use the main troubleshooting page and assemble a support bundle with explicit user consent.